The Generic GNOME policy is not being enforced for some applications
Source:
ZENworks Linux Management; Policy Handlers; Generic GNOME Policy
Explanation:
The Generic GNOME policy defines setting for many applications. Not all the applications reflect the settings that are defined in the policy.
Possible Cause:
The applications that do not reflect the policy settings might not be working properly with GConf.
Action:
To check if the problem is with the application and not with the ZENworks Linux Management, perform the following:
-
Open the GConf Editor.
-
Navigate to the settings that you have configured.
-
Select the setting you have defined.
If the GConf Editor displays that this value cannot be changed, the policy is enforced appropriately. The problem might be with the application. Refer to the application documentation to resolve the issue.
If the GConf Editor displays that this value can be changed, see The new policy is not enforced on the device after multiple refreshes
Possible Cause:
The application is started before the policy settings are enforced.
Action:
Restart the application.
The warning is logged even if the distribution system requirements are met
Source:
ZENworks Linux Management; Policy Handlers; Generic GNOME Policy
Possible Cause:
After the settings are imported from the managed device, the system requirements might have changed or removed before the policy was applied on the managed device.
Action:
If the settings in the policy are not distribution dependent, ignore the warning.
If the policy is distribution dependent, add or modify system requirements on the Details page of the policy.
GNOME-based polices might not be enforced
Source:
ZENworks Linux Management; Policy Handlers; Generic GNOME Policy
Explanation:
GNOME-based policies such as Epiphany*, Evolution*, Firefox*, Generic GNOME*, Novell Linux Desktop, and SUSEĀ® Linux Enterprise Desktop might not be enforced.
Action:
Log in as an administrator and remove all the hidden files (file names starts with '.') with .status.completed extension from the HOME directory of the user, for whom the policy enforcement is not working. The policy is enforced for the same user on subsequent logins.