This forum is closed to new posts and responses. New discussions are now taking place in the IBM Developer Answers forum.


Jul 20, 2016, 5:29 AM
5 Posts
topic has been resolvedResolved

Windows 10 upgrade and single sign on not working - resolved

  • Category: Notes Client
  • Platform: Windows
  • Release: 9.0.1
  • Role:
  • Tags: sso,windows 10,single sign on,password
  • Replies: 6

Just to save anyone else the pain - if you are still using the single sign on service and can't get it to work after upgrading to Windows 10 from a previous Windows version, the solution (without having to reinstall the Notes client which does work but not good when you have customers with multiple machines already upgraded to Windows 10) is....

 

1. As mentioned on other forums/postings, you need to ensure that the following registry entry contains "npnotes" for 32-bit Windows and "npnotes64" for 64-bit:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
Name: "ProviderOrder"

So value must contain npnotes or npnotes64 eg: RDPNP,LanmanWorkstation,webclient,npnotes64

AND it MUST be directly after "webclient" or it will also fail.

 

2. As NOT mentioned anywhere else it would seem is the fact that an entire registry key is missing.  If you copy the following to Notepad and save as .reg you can execute to auto-add the entries:

------------------------------------------------------------------------------------------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\npnotes64]
"Group"="NetworkProvider"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\npnotes64\NetworkProvider]
"Name"="IBM Notes Single Logon"
"ProviderPath"="c:\\notes\\npnotes64.dll"
"Class"=dword:00000002
------------------------------------------------------------------------------------------------------------------------------------

 

You will need to change the ProviderPath value to the path of the Notes executables and remove all 3 "64" instances for 32-bit machines (so npnotes/npnotes/npnotes.dll). Obviously check that you actually have the necessary .dll in there!

Also make sure that the IBM Notes Single Logon service is running and set to Auto.

Note a restart IS required!

Please shout if this helped! Thanks.

 

 

Sep 6, 2016, 8:46 AM
7 Posts
Windows 10 upgrade and single sign on not working - resolved

This is awesome.  Fixed our issue.  I can't believe IBM doesn't come out and have this in any of their documentation.  Their support has been pretty useless lately.

Sep 6, 2016, 8:46 AM
7 Posts
Windows 10 upgrade and single sign on not working - resolved

This is awesome.  Fixed our issue.  I can't believe IBM doesn't come out and have this in any of their documentation.  Their support has been pretty useless lately.

Sep 16, 2016, 5:31 AM
5 Posts
Windows 10 upgrade and single sign on not working - resolved

Hi Patrick - yes it's unbelievable that I had to trawl through an entire registry comparing with a working machine due to IBM's total lack of communication! Thanks for the feedback anyway - good to know I've helped at least one other person! 

Dec 7, 2016, 5:30 PM
1 Posts
Windows 10 upgrade and single sign on not working - resolved

Thank you for the sleuthing this one out and posting it.  This article gets you on the right track - http://www-01.ibm.com/support/docview.wss?uid=swg21304525  but doesn't have the ultimate fix for it.     Seriously,  I really appreciate it because we potentially had up to 350 users where we would have to fix this but now that we got in front of it we can fix the 25 or so who already have it and fix the image before we roll out  the rest.   

Our install path is different but we just changed that part of your entry below and made a .reg file out of it and it works.  Thanks again!

Jan 4, 2017, 9:45 PM
5 Posts
Windows 10 upgrade and single sign on not working - resolved

Hi Dave - glad this helped and thanks for taking the time to post!

Jan 25, 2018, 2:16 PM
6 Posts
Works!

Dang, this has plagued me sporadically for years. Really nice to finally have a fix. How is this happening today...?


This forum is closed to new posts and responses. New discussions are now taking place in the IBM Developer Answers forum.