• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 894
  • Last Modified:

Recovery of SYSVOL policies and NETLOGON shares

I recently had to wipe my primary server due to server errors (refer my only other question), however before I wiped the server (my only DC) I was able to add another DC online. Unfortunately, it would not allow me to transfer the FSMO roles, so I had to shut the original server (henceforth known as Svr1) and seize the all of the roles, that process was successful. Since, I have been able to do much more, since I was having replication errors, but the only error I have left is my SYSVOL is practically empty (read: 1 folder named to my domain name) and my netlogon doesn't exist.

I've read through these articles, followed them to the letter, to no avail. Let me know if you have any ideas or need any more info.

http://support.microsoft.com/kb/315457/
http://support.microsoft.com/kb/316790/
0
blizzard907
Asked:
blizzard907
  • 2
1 Solution
 
blizzard907Author Commented:
P.S....I ran a dcdiag, my only favor is such.

Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\<servername>\netlogon)
[<servername>] An net use or LsaPolicy operation failed with error 53, The network path was not found..
0
 
blizzard907Author Commented:
err...meant to say "my only ERROR is such"....had too much caffiene today. Perhaps thats the problem.
0
 
snusgubbenCommented:
Try "Resolution 1" in this KB: http://support.microsoft.com/kb/958804

SG
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now