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
Who is Participating?
DavidConnect With a Mentor Author Commented:
Yes thanks

The resolution for the issue, Server 2008R2 , system state restore, global catalog missing;
You had opened the case with us for issue, Domain Controller '' is failing test advertising in dcdiag.
We found that, DC was in Journal Wrap
1.) DC was not advertising as GC.

2.) Checked DCDIAG, it was failing connectivity test.

3.) Checked using net share command and the sysvol and netlogon shares were not shared.

4.) In the events found that the DC was in Journal Wrap.

5.) Performed authoritative restore for sysvol as follows;
i. Click Start, and then click Run.
ii. In the Open box, type cmd and then press ENTER.
iii. In the Command box, type net stop ntfrs.
iv. Click Start, and then click Run.
v. In the Open box, type regedit and then press ENTER.
vi. Locate the following key in the registry:
-- KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Cumulative Replica Sets
vii. Below the Cumulative Replica Sets subkey, locate the GUID.
viii. In the right pane, double click BurFlags.
ix. In the Edit DWORD Value dialog box, type D4 to complete an authoritative restore, and then click OK.
x. Quit Registry Editor, and then switch to the Command box.
xi. In the Command box, type net start ntfrs.
xii. Quit the Command box.

6.) Got the event 13516 for sysvol. Issue resolved.
DavidAuthor Commented:
to add this is the only DC which runs active directory and exchange on server 2008 R2
DavidAuthor Commented:
running dcdiag i see the follow fails
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

DavidAuthor Commented:
nltest / /gc

gives error

getting DC name failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN
Mohammed HamadaSenior IT ConsultantCommented:
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.
Mohammed HamadaSenior IT ConsultantCommented:
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.
DavidAuthor Commented:
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
Mohammed HamadaSenior IT ConsultantCommented:
Great. so your problem got solved?
DavidAuthor Commented:
spoke with MS support
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.