Avatar of Bernd Oldenbeuving
Bernd Oldenbeuving
 asked on

Windows 2016 Server, Locked out myself (administrator) after updating GPO

Windows 2016  Server, Locked out myself (administrator) after updating GPO

Cannot access gpedit.msc
Windows 10AzureWindows Server 2016* grouppolicy

Avatar of undefined
Last Comment
Bernd Oldenbeuving

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
McKnife

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Bernd Oldenbeuving

ASKER
Trying to find the corresponding items, but I am not sure where and which one to disable

Cannot access gpedit.msc

Can I edit the registry, and remove the entries blocking the access?

getting messages like:

MMC Could not create the snap-in
MMC cannot create the snap-in because of current user policies.
McKnife

Did you understand the plan that I outlined?
Please share what setting locked you out.
Bernd Oldenbeuving

ASKER
I was limiting access for RDS Users and limited a lot... (not recalling everything as I expected to edit only "Local Users" ) ...
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
McKnife

What GPO exactly? The registry settings are out here: https://gpsearch.azurewebsites.net
Bernd Oldenbeuving

ASKER
McKnife

Are you able to edit the registry offline as outlined before? You could rename the whole branch HKLM\software\policies and create an empty policies branch.
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Mahesh

what you can do, install GPMC on other member server or on client PC from RSAT and access group policy management console from there and from there open affected GPO and undone all settings you done one by one and then reboot the DC, it will solve your issue
Bernd Oldenbeuving

ASKER
Thx Guys, you helped me finding the solution!