The user is prompted to log in again immediately after logging in to ZENworks by using ZENworks icon
Source:
ZENworks 11 Configuration Management; Policy Management.
Explanation:
If the following conditions are met, a ZENworks user is prompted to log in again immediately after logging in to the device, in spite of providing the right credentials:
-
The user has logged in to a device where another ZENworks user has logged in and logged out within 5 to 10 minutes of the desktop login.
-
The Dynamic Local User policy or the Windows Group policy that is assigned to the user has the option selected.
Action:
Edit the policy to deselect .
Unable to view the newly added user source in all the other concurrent sessions of ZENworks Control Center
Source:
ZENworks 11 Configuration Management; Policy Management.
Explanation:
If ZENworks Control Center is opened by more than one user at the same time and a new user source is added to the management zone by one of the users, the newly added user source is not reflected in the other open sessions of ZENworks Control Center. Consequently, the policies might not be assigned to the new user source.
Action:
To assign policies to the new user source, log in to ZENworks Control Center again.
The Wake-on-LAN policy is not available in ZENworks Configuration Management
Source:
ZENworks 11 Configuration Management; Policy Management.
Action:
Perform the following steps to create the functionality of the Wake-on-LAN policy:
-
In ZENworks Control Center, create an empty bundle without any actions.
-
Select the bundle and click > , then click .
-
Select the option, then click .
-
Select the option, then click .
-
Click .
The zman pvst command might not display the correct status of the policy assignment and deployment on a managed device
Source:
ZENworks 11 Configuration Management; Policy Management.
Explanation:
If you assign a policy to a user or device and run the zman pvst command on the server, the assignment status and the overall deployment status of the policy might not be displayed correctly.
Action:
Refresh the device.
The enforcement of policies such as DLU policy, Roaming Profile policy, or Group Policy fails on the managed device
Source:
ZENworks 11 Configuration Management; Policy Management.
Possible Cause:
If a user logs into a managed device by authenticating with a eDirectory user account that has trailing space characters, policies such as DLU policy, Roaming Profile policy, or Group Policy are not enforced on the managed device.
Action:
Ensure that the eDirectory user account does not have trailing space characters.
Closing a published application or logging out of the shared desktop of a Citrix server fails to terminate the session on the Citrix server
Source:
ZENworks 11 Configuration Management; Policy Management.
Explanation:
Even after closing a published application or logging out of the shared desktop of a Citrix server, a user remains logged in to ZENworks. Consequently, some of the policies might not be unenforced on the device.
Action:
Perform the following steps on the device:
-
Open the Registry Editor.
-
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI.
-
Change the value of LogoffCheckSysModules from ZCMUMHelper.exe to ZenUserDaemon.exe,ZCMUMHelper.exe
-
Reboot the device.
Some of the policy settings might not get enforced on a Terminal Server session
Source:
ZENworks 11 Configuration Management; Policy Management; Windows Configuration Policy.
Explanation:
Some policies might not be applied when a user logs into a Terminal Server session. The policy would get automatically enforced during the next device refresh schedule. For example, Browser Bookmarks policy, iPrint policy, and Internet Explorer maintenance settings that are configured in the Group policy are not applied to the device.
Possible Cause:
ZEN user daemon might not have started when the policies were getting enforced on the device.
Action:
If you want to enforce the policy immediately on the device, you must manually refresh the ZENworks Adaptive Agent in one of the following ways:
-
Right-click the ZENworks icon, then select .
-
In the command prompt, run the zac ref command.
Policies might not be listed on Linux managed devices even if the policies are enforced
Source:
ZENworks 11 Configuration Management; Policy Management; Linux Configuration Policy.
Explanation:
After you have enforced a policy on a device, the policies might not be listed on the Linux managed devices.
Action:
To ensure that the policies are listed correctly on the device:
-
Forcefully reapply the policy on the Linux managed device by using the zac pr command.
-
To verify that the policy is getting listed on the managed device use the zac pl command or use the 
icon.
When you upgrade a ZENworks Server from ZENworks 11.2 to 11.3, Power Management Policy settings with value configured as Not Configured are not upgraded properly
Source:
ZENworks 11 Configuration Management; Policy Management; Windows Configuration Policy
Explanation:
ZENworks 11 SP2 allows us to configure Power Management Policy settings with value Not Configured represented by -1. ZENworks 11 SP3 does not support this configuration.When ZENworks Server is upgraded from ZENworks 11.2 to 11.3, and this policy is applied to a ZENworks 11.3 agent, the agent machine will ignore this value that is configured by ZENworks Configuration Management.
Action:
After upgrade from ZENworks Control Center, open the existing Power Management policy and save it. This will update the policy data with the 11.3 supported format.