Bug 13825 - GPO export fails when a GPE.INI file exists in a policy folder
GPO export fails when a GPE.INI file exists in a policy folder
Status: NEW
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB
4.10.0rc3
All All
: P5 normal
: ---
Assigned To: Andrew Bartlett
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-03-08 00:06 UTC by Garming Sam
Modified: 2019-03-08 00:27 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Garming Sam 2019-03-08 00:06:24 UTC
The GPE.INI file does not appear to be documented anywhere in the protocol specifications and seems to be due to legacy code. It appears that it used to be how the gPCUserExtensionNames and gPCMachineExtensionNames were maintained without the requirement for LDAP.

https://social.technet.microsoft.com/Forums/lync/en-US/512c4e0f-4a47-4df6-9030-08c19ba0761a/why-some-gpo-has-adm-folder-some-has-group-policy-folder?forum=winserverGP

Other ini files are encoded as UTF-16, but this is a notable exception. 

To create a GPE.INI file:

In User Configuration -> Preferences -> Windows Settings -> Shortcuts, create a new shortcut