Consequences of Restoring System State from backup

I cannot access Active Directory on our SBS2003 domain controller and after some research it appears as though the correct course of action is to restore the system state data from a backup.

What are the side effects of restoring the system state data from a backup from last Friday? Will it effect Exchange anyway?

Any other precautions in doing so? (I've never had to do this before)

On a sidenote this problem seems to be a continuation of a problem I reported yesterday with the SysVol folders permissions.

http://www.experts-exchange.com/Networking/Protocols/DNS/Q_23791187.html

Any help is greatly appreciated as we are dead in the water.
waltb123Asked:
Who is Participating?
 
waltb123Connect With a Mentor Author Commented:
Reboot wasnt necessary. All is ok now after the above mentioned procedure and some help with how to remove a failed BDC from AD via this link.

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_23794168.html

0
 
ryansotoCommented:
What exactly is the ongoing issue at this point?
Reading your previous post it looks you can try to rebuild the sysvol and netlogon folders
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B315457
0
 
waltb123Author Commented:
The issue is that I cannot load AD on the DC at all. One of the side effects of that issue is that everyone is getting authentication errors while trying to access applications such as CRM that are on another server.

I'm reading your link now.

I've found information I think may be related to my problem, regarding FRS tombstones preventing a DC from becoming a DC. I've just tried this below

1. Stop the File Replication service on the domain controller.
2. Start Registry Editor (Regedt32.exe).
3. Locate and then click the BurFlags value under the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
4. On the Edit menu, click DWORD, click Hex, type D4, and then click OK.
5. Quit Registry Editor.
6. Move data out of the PreExisting folder.
7. Restart the File Replication Service.

However I still cannot access AD. I think a reboot may be in order and will do so shortly.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
ryansotoCommented:
Yup that does work well, reboot and post back
0
 
waltb123Author Commented:
Now that I'm thinking about it, I think I know what may have caused this problem in the first place (but I still dont know how to fix for sure).  Nearly a year ago our BDC crashed and burned.

The server itself was replaced. I never did promote the new fileserver to a BDC and I've seen errors in the event viewer regarding FRS trying to replicate with the now non-existent BDC. I removed every trace of the old server from AD and DNS but apparently this isnt where FRS info is stored because I still saw errors trying to replicate with the old server.

I'm going to open a new question in regards to how to properly remove the old BDC from FRS.
0
 
waltb123Author Commented:
reboot in 30 minutes, I'll be back with an update.
0
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.