Environment
Novell ZENworks 10 Configuration Management Authentication
Novell ZENworks 10 Configuration Management ZENworks Control Center - ZCC
Novell ZENworks 10 Configuration Management User Source
Novell ZENworks 11 Configuration Management Authentication
Novell ZENworks 11 Configuration Management ZENworks Control Center - ZCC
Novell ZENworks 11 Configuration Management User Source
Novell ZENworks 10 Configuration Management ZENworks Control Center - ZCC
Novell ZENworks 10 Configuration Management User Source
Novell ZENworks 11 Configuration Management Authentication
Novell ZENworks 11 Configuration Management ZENworks Control Center - ZCC
Novell ZENworks 11 Configuration Management User Source
Situation
If the first server in the list of User Sources (ZCC > Users> User Sources) is unavailable or goes down, there is a significant delay before the second LDAP server in the list is used.
Symptoms include:
Symptoms include:
- Agent login from Windows times out after 5 minutes and never authenticates
- ZCC Login as an LDAP user can take 3 or 4 minutes to complete
- Once logged in to ZCC, browsing the LDAP configuration takes several minutes to return a page
- Any attempt to change the order of LDAP servers (e.g. to take the bad server to the bottom of the list) times out
- After deleting the unavailable server, everything works as expected without any delays
Resolution
For ZCM10: This is fixed in version 10.3.2 - see KB 7007237 "ZENworks
Configuration Management 10.3.2 - update information and list of fixes"
which can be found at https://www.novell.com/support
For ZCM11: This is fixed in version 11.1 - see KB 7008746 "ZENworks Configuration Management 11.1 - update information and list of fixes" which can be found at https://www.novell.com/support
Workaround
Remove the unavailable server from the list while it is unavailable.
For ZCM11: This is fixed in version 11.1 - see KB 7008746 "ZENworks Configuration Management 11.1 - update information and list of fixes" which can be found at https://www.novell.com/support
Workaround
Remove the unavailable server from the list while it is unavailable.