Windows 10: Group Policy Object Editor error "No mapping between account names and security IDs was...

Recently I customized an image using System Audit Mode, what I've done for the image :1. Create two account and put under "Administrator" group2. Install Microsoft PowerToys and dotnet 8 runtime.3. Amend local group policy through "gpedit.msc"4. Create a new group policy object through mmc.exe and applied to one of the account I create in steps 1.After that I generalize the image, and use WinPE to capture the image, everything was perfect and fine.But when I try to open the group policy object I create on steps 4, the error happens. I've encounter the error "No mapping between account names an

:)

 

Copying Group Policy Object Editor - Non Administrators

Hi, my name is Kelly, and I'm an independent consultant and I'm here to help.

Yes, it is possible to use MMC snap-in to create a Group Policy Object Editor and configure it to lock down the local machine for non-administrative users. Once you have configured the Group Policy Object Editor to your desired settings, you can save it as a configuration file and then apply it to multiple machines.

Here are the general steps you can follow:

Open the Group Policy Object Editor MMC snap-in: Press the Windows key + R to open the Run dialog box, type "mmc" and press Enter. Then, go to File > Add/Remove Snap-in, select Group Policy Object Editor, and click Add.

Configure the Group Policy settings: Expand the Local Computer Policy node and navigate to the settings you want to configure. Once you have made your desired changes, save the configuration by going to File > Save As and choose a location to save the configuration file.

Apply the configuration to other machines: To apply the configuration to other machines, copy the configuration file you saved in step 2 to the other machines. Then, open the Group Policy Object Editor MMC snap-in on each machine, go to File > Open and select the configuration file you copied in the previous step. The configuration settings should then be applied to the local machine.

Note that you may need administrative privileges to apply the configuration file on other machines. Additionally, it's important to thoroughly test the configuration settings on a test machine before applying them to production machines to ensure that they work as expected and do not cause any unintended consequences.

 

Copying Group Policy Object Editor - Non Administrators

I apologize for the confusion. To ensure that the Group Policy settings are applied correctly on the new machine when you open the .mmc file, you will need to perform the following steps:

Open the .mmc file that you want to transfer to the new machine.

Right-click on "Group Policy Object Editor" in the console tree and select "Add/Remove Snap-in".

Select "Group Policy Object Editor" from the list and click the "Add" button.

In the "Select Group Policy Object" dialog box, select "Local Computer" and click "Finish".

Click "Close" in the "Add/Remove Snap-in" dialog box.

In the console tree, expand "Local Computer Policy" and navigate to the settings that you want to configure.

Configure the settings as desired.

Save and close the .mmc file.

When you transfer the .mmc file to the new machine and open it, the Group Policy settings that you configured should be applied correctly.

I hope this helps! Let me know if you have any further questions.

 

Group Policy Object Missing

Hi,



Thank you for writing to Microsoft Community Forums.



Let me point you in the right direction, where you would get the appropriate help for this issue. I would suggest you to post your query in
TechNetforums,
where we have experts and support professionals who are well equipped with the knowledge on Group policy to assist you with the appropriate troubleshooting steps.



You may also refer this article: Create
a Group Policy Object



Aditya Roy

Microsoft Community – Moderator