An Active Directory (AD) only user to logoning on to a Windows 2008 R2 RD farm. Every 2008 R2 RD server has the Novell Client 2 for Windows sp1 ir6 installed. Everything works great when a Novell user (with an AD account too) logs on to the RD server. The challenge is when an AD only user who does not have a Novell user account tries to logon. The Novell client does not do a computer only logon. So the AD only user gets this error.
The system could not log you on to the network.
Make sure your name and connection infomation are correct, then type your password again.
The Novell logon window appears after clicking the OK button on the error message.
The AD only user finally gets to the desktop by clicking the Logon's "Cancel" button.
Here are the Novel properity combinations we tried.
Computer Only Logon: On On On
Computer Only Logon after failed Novell Logon: Automatic Never Always .
Computer Only Logon Default: Never Automatic Always.
Login With Non-Novell Credential Provider: On Off On
Novell Logon: On Off On
How can it be configured so an AD only user can go directly to the desktop without the error.
It would be accecptable to manually log, accecpt the error and then do a registry hack so the next time the AD only user can logon without challenges.
The system could not log you on to the network.
Make sure your name and connection infomation are correct, then type your password again.
The Novell logon window appears after clicking the OK button on the error message.
The AD only user finally gets to the desktop by clicking the Logon's "Cancel" button.
Here are the Novel properity combinations we tried.
Computer Only Logon: On On On
Computer Only Logon after failed Novell Logon: Automatic Never Always .
Computer Only Logon Default: Never Automatic Always.
Login With Non-Novell Credential Provider: On Off On
Novell Logon: On Off On
How can it be configured so an AD only user can go directly to the desktop without the error.
It would be accecptable to manually log, accecpt the error and then do a registry hack so the next time the AD only user can logon without challenges.