Install packages created in SEPM do not have the correct policies of the group it was created in
I have a standard group I put end-user's machines into which is locked down. Tamper protection is enabled and password in place, etc. I also have a group that is NOT locked down designated for IT. Tamper protection is not enabled w/ no password being required when you run the client clone prep tool.
I'm trying to export an installation package from the IT group to give to administrators at different sites to use when making an image of a machine. For whatever reason when they install this package on a machine they're building to make an image, the machine then points to the standard group, and of course the standard group is locked down so then the administrators cannot run the client side prep tool.
I have found a workaround, by simply moving the machine into the IT group and then forcing it to update. I can then run the clone prep tool and am successful in removing the UID. I'm trying to figure out though why this happens keeps happening when I create the install packages for the IT group.
Any help would be appreciated.