asked on
Active Directory problem after System State restore
After performing a system state restore on a different hyper V hardware, Active directory seems to run on for a little bit then we lose it. When opening Active directory we get a message ![ad]()
I restarted the active directory service and it looks like it started workign again after about 10 minutes. The event log points towards the global catalogue missing, but im not sure why this would be after a system state restore ![ScreenHunter_21-Jul.-26-22.51.jpg]()
Advise would be very helpful
ScreenHunter_21-Jul.-26-22.51.jpg
I restarted the active directory service and it looks like it started workign again after about 10 minutes. The event log points towards the global catalogue missing, but im not sure why this would be after a system state restore 
Advise would be very helpful
ScreenHunter_21-Jul.-26-22.51.jpg
Active DirectoryWindows Server 2008Exchange
Last Comment
David
ASKER
to add this is the only DC which runs active directory and exchange on server 2008 R2
ASKER
running dcdiag i see the follow fails
dcdiag.txt
dcdiag.txt
ASKER
nltest /dsgetdc:domainaname.co.uk
gives error
getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
gives error
getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
Seems like your DNS is not updated or have some staled records. you'll need to enable scavenging on it. make sure that all your domains are replicating properly.
use repadmin /showrepl and repadmin /replsum to see the replication. you can add /e parameter to include all DCs in the forest.
make sure all firewalls are disabled.
use repadmin /showrepl and repadmin /replsum to see the replication. you can add /e parameter to include all DCs in the forest.
make sure all firewalls are disabled.
I would also highly recommend that you install an additional new DC as soon as possible and demote this one that you got from a recovery. it's not recommended to work on recovered DC in production environment.
ASKER
Early this morning I made the call to Microsoft and it was an issue with the file replication service
And the netlogon and sysvol were no longer shared causing the issue.
Yes we are planning to migrate the email off to office365
And then will make a decision on the rest
The reason for recovery was because of a crypto virus that got onto the c drive
And the netlogon and sysvol were no longer shared causing the issue.
Yes we are planning to migrate the email off to office365
And then will make a decision on the rest
The reason for recovery was because of a crypto virus that got onto the c drive
Great. so your problem got solved?
ASKER CERTIFIED SOLUTION
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.
ASKER
spoke with MS support