TERENCE LUK: CONFIGURING A GPO TO PERMIT A MMC SNAP

I just got onboard a new job và inherited a sabotaged network. Using the AD Admin trương mục, I encountered the error messages indicating that the object/snap-in/applications "has been restricted by policy. Liên hệ your administrator for details. Group Policy Management". I can"t access the Group Policy Management console on the DC to lớn view the GPO objects due to lớn the same limitations. There"s no GPO object listed under any AD console.

Bạn đang xem: Terence luk: configuring a gpo to permit a mmc snap

I"m researching this issue. Any phản hồi or suggestion would be greatly appreciated. Thanks in advance for your time & help.

Best,


Which of the following retains the information it's storing when the system power is turned off?
*

*

EminentX
*

Give this a read & see if it works: https://www.itprotoday.com/windows-78/im-unable-run-group-policy-editor-domain-even-though-im-tên miền...
*

I just got onboard a new job and inherited a sabotaged network.

What does that mean? If you mean something malicious, don"t be afraid to lớn start it over. If it"s just poorly managed, that"s a different story.


*

Bryan Doe wrote:

I just got onboard a new job and inherited a sabotaged network.

What does that mean? If you mean something malicious, don"t be afraid to start it over. If it"s just poorly managed, that"s a different story.

Definitely malicious. Attempts has been made right before I came onboard lớn alter VMs and data storage locations.

Thanks


Bryan Doe wrote:

I just got onboard a new job and inherited a sabotaged network.

What does that mean? If you mean something malicious, don"t be afraid to start it over. If it"s just poorly managed, that"s a different story.

I got no PW or documentation at all for any system on the network other than the AD Administrator PW. This account cannot manage much, it seems.


That sounds lượt thích a GPO is preventing it, but if you"re a domain admin you should be able khổng lồ change it. That said, I"d really consider the only sure bet, nuke it, at least depending on the form size of the system.

Xem thêm: Cách Nấu Cháo Cật Heo Cho Be, Cháo Cật Heo Cho Bé Nấu Với Cà Rốt Và Rau Ngót


Document everything and tương tác the legal department before proceeding with recovery efforts.

Cheông chồng to see what the backup situation is. Depending on the environment you may be able to "roll back" AD to working state. Test it in isolated VMs before proceeding.


Chechồng the below article may help you lớn fix this issue:https://www.windowsbbs.com/threads/unable-to-open-policy-editor-the-snap-in-referenced-in-this-doc-h...


Bryan Doe wrote:

That sounds like a GPO is preventing it, but if you"re a tên miền admin you should be able khổng lồ change it. That said, I"d really consider the only sure bet, nuke it, at least depending on the form size of the system.

I"ve sầu never "nuked" the GPO :) - So I don"t have sầu much experience in that. Also, this place has 300 employees and running 3 shifts, any mistake on my part will lead khổng lồ a lot of down time và people with nothing to bởi. Any suggestion where to start digging?

Thanks.


tulioarends wrote:

Document everything & contact the legal department before proceeding with recovery efforts.

Check to see what the backup situation is. Depending on the environment you may be able to "roll back" AD to working state. Test it in isolated VMs before proceeding.

I"m documenting everything I look at. I have sầu no access to lớn BU due lớn lachồng of PW. I can"t BU anything due to GPO. I resorted to robocopying the VMs và VHDs. I"ll look into lớn rolling baông xã AD state.

Thanks.


tulioarends wrote:

You should be able lớn access the servers with local administrator passwords.

We have sầu no local admin PW, no system PW (BU, NAS, CCTV). Just imagine the worst case scenario.


This topic has been locked by an administrator & is no longer open for commenting.