As previously the GPO was being tested we only had it linked to lớn a few users. With testing now complete I removed the users & added the "WHOLE DOMAIN". Expletives....!!!

The problem I"m now experiencing is that nothing can be modified on either of the domain name controllers with any of the domain name admin accounts. The error "The Snap-In below, referenced in this document, has been restricted by policy" Click ok & the message "MMC could not create the snap-in". Also none of the MMC snap-in"s are now accessible.

Bạn đang xem: The snap

I believe life would return to lớn normality once I remove the GPO linked khổng lồ the “Whole Domain”. Is there a way to vì this without having access khổng lồ any of the management snap-in’s or possibly through Powershell?


Wednesday, March 19, năm trước 9:54 PM

Answers


*

*

1
Sign in lớn vote

Hi Andy,

Thanks for your input, yes I"ve noted both those articles when troubleshooting the issue. Ultimately the problem was resolved by rebooting one of the DC"s and (even though it suffered the same symptoms previously) upon trying lớn access MMC snap-in manager I could. So disconnected it from the network (It"s running as a VM) và made changes to Group Policy as required.

Connecting it back to the network và forcing the sync lớn the other DC resolved the issue.

Thanks for your input Andy.

Xem thêm: Gta San Andreas Requires At Least Directx 9, 404 Not Found


Sunday, March 23, năm trước 8:00 PM

All replies


*

*

1
Sign in to vote

Hi Andy,

Thanks for your input, yes I"ve noted both those articles when troubleshooting the issue. Ultimately the problem was resolved by rebooting one of the DC"s and (even though it suffered the same symptoms previously) upon trying khổng lồ access MMC snap-in manager I could. So disconnected it from the network (It"s running as a VM) và made changes khổng lồ Group Policy as required.

Connecting it back to the network and forcing the sync to the other DC resolved the issue.

Thanks for your đầu vào Andy.


Sunday, March 23, 2014 8:00 PM
Newsletter|Contact Us|Privacy Statement|Terms of Use|Trademarks