Active directory not opening after apply plug n play service disable through GPO

What is the first rule of change management - if you are unable to open an app because of the result of the change you just made..  roll it back - period..

Once you have rolled it back - does AD work again?

If it works, take the new code into a test lab and sort it out there.

start the plug and play service and restart the domain .. then check

Hi Shaik,

I am unable to start the service of Plug n Play. This is my big problem. Any workaround for this. I have doing this by logging with Domain administrator.

go to the services... right click the plug and play service

check dependencies ..

and start them all...

in services - click start up type - automatic status services should started..

try this...

dependencies services are also disabled and cannot be enabled or start through this user. Any other idea?

did u tried in safe mode ?

is it physical server or virtualserver ?

A Virtual server in Hyper v

Server is running in Safe mode. But it is not giving access to start this service.

check the virtual disk service ...


go to services. and start the virtual disk service

all the best

virtual disk service is depends on plug n play services... check weather it's start or not...

if not start it...

We have checked, but still whenever i tried to start virtual disk service. It is saying the dependency service not started, so it could not start. ERROR 1068

Have you tried to restart domain controller in normal mode, if yes, what error you are getting ? still you are facing same issues ?

If yes, How many domain controllers do you have ?

if you have more than one functional DCs, check if you are able to open all AD snap ins including GPMC on another functional server
Also check if all AD services are running on that server for ex:
Netlogon
NTFRS (File replication service)
Intersite messaging
Kerberos key distribution center
security accounts manager
AD domain services
Also check if Sysvol and netlogon shares are populated

In that case just remove affected server from network and if it contains FSMO roles just seize them on functional DC then do metadata cleanup on functional DC and rebuild the affected server from scratch and promote it again as ADC

if this is the only domain controller you have, then check if you have valid AD system state backup and if yes, just make authoritative restore of system state on affected server by restarting it in directory service restore mode and then check if its working

Mahesh.

Woilla.....Excellent. I have never think that i can escape from this problem. But yess, after mad these registry changes, i got my DC back.

GURU.....You too good man. God for me.

Cheers,

You deserves a bottle.

-Abhijit
From Syinfra