-
Notifications
You must be signed in to change notification settings - Fork 4
Troubleshooting
Make sure you have followed the steps on the Group Policy page on where you need to copy the Group Policy files.
This can be due to a few reasons:
- The adml file is not in the appropriate language directory (en-US for example)
- The group policy itself has an issue, if you are sure the adml is in the right location, then raise an issue
There are a few reasons why the Group Policy may not apply some settings
If the user has previously opened LibreOffice, the LibreOffice Group Policy will not override their settings unless the Enforce check-box is checked.
Some policies don't contain an Enforce check box yet, if they don't you have three options:
- If the users don't mind losing their settings, you can delete the users %appdata%\LibreOffice profile. The next time LibreOffice opens it should pull the settings from Group Policy.
- Create a DWORD called Final with the value of 1 in the policy location you wish to enforce. Eg:
- Either open regedit or create a Group Policy Preference
- You'll need to find the key the policy set (eg HKLM\Software\policies\LibreOffice\org.openoffice.UserProfile\Data\o for Organisation Name)
- Create the DWORD Final in this location
- If you are unsure of how to do the above, raise an issue and it'll be added to the Policy
If only some settings apply (and you have made sure there are no Pre-existing Settings). Then there may be an issue with the registry keys the Group Policy sets.
LibreOffice will read the policy registry keys up until it meets a key it doesn't understand, at which case it seems to just set all the settings prior to the failed key.
If you have added some Policy keys yourself for LibreOffice (via GPP for example), you may wish to check that they are correct. If you haven't set any custom LibreOffice GPP, then raise an issue.