Novell authentication windows 7

Solutions to this are either you reenter your alias so the context is the same as during initial login or - much better to configure ldap contextless login at the client, so you can forget about the context at all.

I am conscerned about the local profiles that were created when referencing the alias object contexts. When enabling contextless login, aren't these dereferenced to the actual user objects which in turn would not match with the existing local profile.

I am going to run a few tests here to see if this is the case. Maybe another way around this is to tell windows to authenticate against the local workstation account instead of against novell after locking a workstation. Is this possible? Thanks for the quick feedback. To authenticate against Windows instead of Edir was easily possible in WinXP and before and you could lock it to only this mode, but in the Client 2 properties I don't find the corresponding entry, so maybe you have to do this manually, which is not very intuitive click on login as another user - click on WS only and enter the local credentials - you are asked if you want to connect to the existing session - click ok - and you are in -- W.

Trying to unlock the workstation gives me the same error message listed in the original post. This also was happening on Vista with an older client. One thing I found that looks strange. Don't know if that is significant or not. The bottom line is that every time a user tries to unlock a Windows 7 workstation they have to respond to the error and then enter their domain password. VERY inconvenient.

We need a fix. Windows 7 Novell Client 2. Not sure if this will help you but it works for our situation. Tried turning off NMAS and it works nicely. Thank you. Disabling NMAS isn't really an option for us. It would cause our passwords to become out of sync. Is there a better solution for this? I don't know if you're still having this issue but I have a customer that resolved their issue by adding an additional tab 4 for NMAS to the registry.

Before adding the below, we: - installed fresh Win7 - added an NCIMAN customized installation to Win7 - reboot - login with eDirectory creds - lock - immediately try to unlock - hit error by just adding the registry entries below, and without even rebooting, we were able to lock. Thank You! Resources Support. CyberRes Academy.

Partner Portal. Contact us. MigrationDeletedUser over 5 years ago. Up 0 Down Reply More Cancel. Related Discussions. Resources Support. CyberRes Academy. Partner Portal. Contact us. Privacy Policy Terms of Use. Accessibility Anti-Slavery Statement. Support How To Buy. Careers Investor Relations.