3978
This scenario can happen if a Group Policy Object with AppSet entries is COPIED and PASTED using the GPMC. Or if the GPO is “Imported” using the GPMC’s Import command.
Here’s an example that can illustrate the problem and the resolution.
Assume you have a Group Policy Object named ORIG. When you do this, a GPO gets GUID like this.
When you make a PolicyPak entry, data is stored in the Group Policy Object.
Then if you copy the Group Policy Object that data is copied with the Group Policy Object, but is now pointing to the original Group Policy Object.
This is not a supported scenario using PolicyPak Application Manager.
The correct supported scenario using PolicyPak Application Manager would be to:
- In the original Group Policy Object, open the Entry. Use the OPTIONS button in the AppSet entry and EXPORT AS XML.
- In the new Group Policy Object, create a new Entry. Use the OPTIONS button in the AppSet entry and IMPORT AS XML.
When you look at the settings report, what you want to see is that the REAL Group Policy Object’s GUID…
That now matches the Group Policy Object’s guts:
If you already have this situation and need to get out of it, it’s an easy fix:
- Export the XML settings (from the original –or- new Group Policy Object – it doesn’t matter.)
- In the Group Policy Object with the problem, delete the AppSet Entry.
- Then re-create the Entry.
- Then Import the XML settings
This will create a new AppSet Entry and all the “guts” should be aligned correctly.
