Re: Duplicate SYSVOL trees on the same server
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Mon, 14 May 2007 20:19:14 +0100
for some reason I can't see your posts can you post your answers again?
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
"Lance" <Lance@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:F0A96AA6-122F-43E5-A342-DD9AB0886ACD@xxxxxxxxxxxxxxxx
I may have solved my own problem with this. I found a post elsewhere from
someone that had a similar issue due to the file restore of a tape backup of
SYSVOL, which automatically created a link to the restored files.
I simply ran LINKD d:\test\windows\sysvol\sysvol\domain.com /D and the
replica of sysvol was removed. I will attempt to physically remove the
directories after hours, just in case.
What I was looking for, was a utility to show all link relationships, to see
exactly what was linking to the main sysvol directory. I never thought to
run linkd on the copied folders.
Hope this helps someone out..
Thanks for your help Jorge, you pointed me in the right direction.
Lance
"Lance" wrote:
I have a rather interesting issue with one domain conrtoller. It's the owner
of all FSMO roles for our environment.
Some time ago, through testing some backup software, a duplicate Windows
directory was created on the server's D: drive under D:\test\Windows\... As
a result, there is a complete duplicate of SYSVOL under it.
How do I safely remove this? I attempted to delete the entire folder
structure before I realized it contained a Windows system file, but it
completely waxed my scripts and policies directories in FRS, so I had to
restore them. Some files were in use, as well. I can't find any reference
to this directory in the registry, even under ntfrs replicas.
There are no issues with FRS as far as replication is concerned. I have
some GPO issues to sort out (error 1058, etc), but I may perform a complete
sysvol rebuild this weekend to fix that.
I don't want to hose FRS, since i've already had some security permissions
issues due to restoring the 'duplicate' tree, so I am hesitant to remove it.
Last time I tried, i ended up with morphed directories that cause me to
perform a bulk restart following a Microsoft KB article. I'm also concerned
that with a server reboot, and the Windows directory gone, I could blue
screen the server if Windows decided it was using that system folder for
anything.
THanks...
.
- Follow-Ups:
- Re: Duplicate SYSVOL trees on the same server
- From: Jorge Silva
- Re: Duplicate SYSVOL trees on the same server
- Prev by Date: Re: Questions on transfer DHCP from an old DC to a new one...
- Next by Date: Advanced ADAM Technical and Design Resources??
- Previous by thread: Re: Duplicate SYSVOL trees on the same server
- Next by thread: Re: Duplicate SYSVOL trees on the same server
- Index(es):
Relevant Pages
|
