Novell ZENworks 7 Desktop Management Support Pack 1 - ZDM7 SP1
NOTE: This is only for troubleshooting WOL object login problems. This is VERY insecure as it exposes the admin password in cleartext.
Various authentication errors during WOL startup for WOL Service object or WOL policy object logins. How to test whether the objects themselves are bad by using a generic admin login instead.
- Modify DAPConfig.properties file after making a backup copy. On NetWare this file is in ZENworks\RemMgmt\server\properties.
Change the ADMIN_LOGIN_OPTION to:
ADMIN_LOGIN_OPTION = true
- Modify startWOL.ncf file after making a backup copy. On NetWare this file is in sys:\system .
- Add the following to the load line:
-DNDSTree=MY-TREE -DAdminContext=container -DAdminPassword=password -DUser=user
where MY-TREE is the tree, container is the user context, password is the user password and user is the eDirectory user which will be used to login to eDirectory instead of the WOL objects.
java -jszenwsWOL -sn"ZENworks Wake on Lan Service" -nsac -mx128M -DMgrName="WOLServiceManager" -DNDSTree=NDSTREE -DAdminContext=novell -DAdminPassword=novell -DUser=admin -DMgrPropName=WOLStart.properties -classpath $wolpath;$CLASSPATH com.novell.zenworks.desktop.remotewakeup.ZENWorksWOLServiceManager
- Restart the WOL service.
This can be helpful to ensure that the setup is working outside of the login issues with WOL service or policy objects. After testing, change the files back to original and troubleshoot the failure of authentication on the WOL service or policy objects.