M
Manuel Alvarez
Hello Everyone,
We had an Active Directory crash a few months ago, and
for some reason the sysvol didn't restore properly from
the backup. Specifically, the reparse (link) points were
not there. I tried manually recreating the reparse
points, but the sysvol still won't initialize on it's own
on the master DC, which means it can't initialize on the
member DC's either.
Active directory (the NTDS part of it) is actually up and
running (user and computer changes are propagating
correctly throughout the enterprise), but because of the
sysvol problem the DFS doesn't start and therefore logon
scripts and group policy changes aren't propagating.
Currently the sysvol and netlogon shares have to be
manually recreated each time a member DC is rebooted.
Well, now to my quesion (thanks for hanging in there!):
Since SYSVOL is my only problem, is there a way I can
just have Windows completely kill the sysvol and recreate
a new one? That way I could just plug in my policies and
logon scripts and I should be good to go.
I have actually worked on this problem for quite a while
with no success... I really hope someone out there can
point me in the right direction!
Thank you for your time and kindness,
Manuel Alvarez
We had an Active Directory crash a few months ago, and
for some reason the sysvol didn't restore properly from
the backup. Specifically, the reparse (link) points were
not there. I tried manually recreating the reparse
points, but the sysvol still won't initialize on it's own
on the master DC, which means it can't initialize on the
member DC's either.
Active directory (the NTDS part of it) is actually up and
running (user and computer changes are propagating
correctly throughout the enterprise), but because of the
sysvol problem the DFS doesn't start and therefore logon
scripts and group policy changes aren't propagating.
Currently the sysvol and netlogon shares have to be
manually recreated each time a member DC is rebooted.
Well, now to my quesion (thanks for hanging in there!):
Since SYSVOL is my only problem, is there a way I can
just have Windows completely kill the sysvol and recreate
a new one? That way I could just plug in my policies and
logon scripts and I should be good to go.
I have actually worked on this problem for quite a while
with no success... I really hope someone out there can
point me in the right direction!
Thank you for your time and kindness,
Manuel Alvarez