sysvol replicating to the wrong place??

i have recently had some problems with two DCs in the same site not
replicating the sysvol share between each other. To fix this it i did a
non-authority restore.

However now on the DC that i did the restore on, logon scripts and policies
are now replicating in the sysvol\domain\scripts and sysvol\domain\policies
folders not the the actual sysvol\sysvol\domain.local\scripts (i.e not in the
proper sysvol share!)

this is very confusing for me, has anyone else experienced this?

All servers are windows 2003, both are DCs, GCs, DNS servers.

FRSDiag and/or Ultrasound might be able to help you out with this issue.
http://www.microsoft.com/technet/pro...9a0db2a56.mspx

Here is a how to on troubleshooting intra-site replication issues:
http://support.microsoft.com/kb/249256/en-us

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Luca" <Luca@discussions.microsoft.com> wrote in message
news:BB44130B-9AB3-45CC-BF7C-AF26A33D720D@microsoft.com...
>i have recently had some problems with two DCs in the same site not
> replicating the sysvol share between each other. To fix this it i did a
> non-authority restore.
>
> However now on the DC that i did the restore on, logon scripts and
> policies
> are now replicating in the sysvol\domain\scripts and
> sysvol\domain\policies
> folders not the the actual sysvol\sysvol\domain.local\scripts (i.e not in
> the
> proper sysvol share!)
>
> this is very confusing for me, has anyone else experienced this?
>
> All servers are windows 2003, both are DCs, GCs, DNS servers.

what do you mean?

those locations are linked to each other as a result of a junction point at
a higher level

open a command prompt window and navigate to the second SYSVOL folder
do a DIR

you should see something similar as below...



--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Luca" <Luca@discussions.microsoft.com> wrote in message
news:BB44130B-9AB3-45CC-BF7C-AF26A33D720D@microsoft.com...
>i have recently had some problems with two DCs in the same site not
> replicating the sysvol share between each other. To fix this it i did a
> non-authority restore.
>
> However now on the DC that i did the restore on, logon scripts and
> policies
> are now replicating in the sysvol\domain\scripts and
> sysvol\domain\policies
> folders not the the actual sysvol\sysvol\domain.local\scripts (i.e not in
> the
> proper sysvol share!)
>
> this is very confusing for me, has anyone else experienced this?
>
> All servers are windows 2003, both are DCs, GCs, DNS servers.

what do you mean?

those locations are linked to each other as a result of a junction point at
a higher level

open a command prompt window and navigate to the second SYSVOL folder
do a DIR

you should see something similar as below...



D:\AD\SYSVOL\sysvol>dir
Volume in drive D has no label.
Volume Serial Number is C89E-038A

Directory of D:\AD\SYSVOL\sysvol

03/25/2007 12:18 AM <DIR> .
03/25/2007 12:18 AM <DIR> ..
03/25/2007 12:18 AM <JUNCTION> ROOT.DEMO
0 File(s) 0 bytes
3 Dir(s) 16,996,065,280 bytes free

D:\AD\SYSVOL\sysvol>


--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Luca" <Luca@discussions.microsoft.com> wrote in message
news:BB44130B-9AB3-45CC-BF7C-AF26A33D720D@microsoft.com...
>i have recently had some problems with two DCs in the same site not
> replicating the sysvol share between each other. To fix this it i did a
> non-authority restore.
>
> However now on the DC that i did the restore on, logon scripts and
> policies
> are now replicating in the sysvol\domain\scripts and
> sysvol\domain\policies
> folders not the the actual sysvol\sysvol\domain.local\scripts (i.e not in
> the
> proper sysvol share!)
>
> this is very confusing for me, has anyone else experienced this?
>
> All servers are windows 2003, both are DCs, GCs, DNS servers.

What i mean is, logon scripts are replicating to the sysvol\domain\scripts
folders but not to the netlogon share, so when i user logs in and their
script runs, its runs from netlogon which is not the most up to dat script.

When i did what you suggested on the DC in question i did not get a
<junction> i got this:

:\WINDOWS\SYSVOL\sysvol>dir
Volume in drive C is OS
Volume Serial Number is F8CE-977D

Directory of C:\WINDOWS\SYSVOL\sysvol

26/02/2007 11:34 AM <DIR> .
26/02/2007 11:34 AM <DIR> ..
26/02/2007 11:36 AM <DIR> domain.local


running the same command on other DCs shows the proper junction point.
Would using the a linkd command re-link the problem DC to the correct
junction?

thanks

"Jorge de Almeida Pinto [MVP - DS]" wrote:

> what do you mean?
>
> those locations are linked to each other as a result of a junction point at
> a higher level
>
> open a command prompt window and navigate to the second SYSVOL folder
> do a DIR
>
> you should see something similar as below...
>
>
>
> D:\AD\SYSVOL\sysvol>dir
> Volume in drive D has no label.
> Volume Serial Number is C89E-038A
>
> Directory of D:\AD\SYSVOL\sysvol
>
> 03/25/2007 12:18 AM <DIR> .
> 03/25/2007 12:18 AM <DIR> ..
> 03/25/2007 12:18 AM <JUNCTION> ROOT.DEMO
> 0 File(s) 0 bytes
> 3 Dir(s) 16,996,065,280 bytes free
>
> D:\AD\SYSVOL\sysvol>
>
>
> --
>
> Cheers,
> (HOPEFULLY THIS INFORMATION HELPS YOU!)
>
> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services
>
> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
> ------------------------------------------------------------------------------------------
> * How to ask a question --> http://support.microsoft.com/?id=555375
> ------------------------------------------------------------------------------------------
> * This posting is provided "AS IS" with no warranties and confers no rights!
> * Always test before implementing!
> ------------------------------------------------------------------------------------------
> #################################################
> #################################################
> ------------------------------------------------------------------------------------------
> "Luca" <Luca@discussions.microsoft.com> wrote in message
> news:BB44130B-9AB3-45CC-BF7C-AF26A33D720D@microsoft.com...
> >i have recently had some problems with two DCs in the same site not
> > replicating the sysvol share between each other. To fix this it i did a
> > non-authority restore.
> >
> > However now on the DC that i did the restore on, logon scripts and
> > policies
> > are now replicating in the sysvol\domain\scripts and
> > sysvol\domain\policies
> > folders not the the actual sysvol\sysvol\domain.local\scripts (i.e not in
> > the
> > proper sysvol share!)
> >
> > this is very confusing for me, has anyone else experienced this?
> >
> > All servers are windows 2003, both are DCs, GCs, DNS servers.
>
>
>

Personally I would do a non-authoritative restore on your sysvol.

A domain controllers will erase their local copy of the sysvol and then
replicate it from an another domain controller.

How to perform a non-authoritative restore
http://support.microsoft.com/?id=840674

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Luca" <Luca@discussions.microsoft.com> wrote in message
news:EEE4EF88-86AA-474A-A1D0-8A5667CB7285@microsoft.com...
> What i mean is, logon scripts are replicating to the sysvol\domain\scripts
> folders but not to the netlogon share, so when i user logs in and their
> script runs, its runs from netlogon which is not the most up to dat
> script.
>
> When i did what you suggested on the DC in question i did not get a
> <junction> i got this:
>
> :\WINDOWS\SYSVOL\sysvol>dir
> Volume in drive C is OS
> Volume Serial Number is F8CE-977D
>
> Directory of C:\WINDOWS\SYSVOL\sysvol
>
> 26/02/2007 11:34 AM <DIR> .
> 26/02/2007 11:34 AM <DIR> ..
> 26/02/2007 11:36 AM <DIR> domain.local
>
>
> running the same command on other DCs shows the proper junction point.
> Would using the a linkd command re-link the problem DC to the correct
> junction?
>
> thanks
>
> "Jorge de Almeida Pinto [MVP - DS]" wrote:
>
>> what do you mean?
>>
>> those locations are linked to each other as a result of a junction point
>> at
>> a higher level
>>
>> open a command prompt window and navigate to the second SYSVOL folder
>> do a DIR
>>
>> you should see something similar as below...
>>
>>
>>
>> D:\AD\SYSVOL\sysvol>dir
>> Volume in drive D has no label.
>> Volume Serial Number is C89E-038A
>>
>> Directory of D:\AD\SYSVOL\sysvol
>>
>> 03/25/2007 12:18 AM <DIR> .
>> 03/25/2007 12:18 AM <DIR> ..
>> 03/25/2007 12:18 AM <JUNCTION> ROOT.DEMO
>> 0 File(s) 0 bytes
>> 3 Dir(s) 16,996,065,280 bytes free
>>
>> D:\AD\SYSVOL\sysvol>
>>
>>
>> --
>>
>> Cheers,
>> (HOPEFULLY THIS INFORMATION HELPS YOU!)
>>
>> # Jorge de Almeida Pinto # MVP Windows Server - Directory Services
>>
>> BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
>> BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
>> ------------------------------------------------------------------------------------------
>> * How to ask a question --> http://support.microsoft.com/?id=555375
>> ------------------------------------------------------------------------------------------
>> * This posting is provided "AS IS" with no warranties and confers no
>> rights!
>> * Always test before implementing!
>> ------------------------------------------------------------------------------------------
>> #################################################
>> #################################################
>> ------------------------------------------------------------------------------------------
>> "Luca" <Luca@discussions.microsoft.com> wrote in message
>> news:BB44130B-9AB3-45CC-BF7C-AF26A33D720D@microsoft.com...
>> >i have recently had some problems with two DCs in the same site not
>> > replicating the sysvol share between each other. To fix this it i did
>> > a
>> > non-authority restore.
>> >
>> > However now on the DC that i did the restore on, logon scripts and
>> > policies
>> > are now replicating in the sysvol\domain\scripts and
>> > sysvol\domain\policies
>> > folders not the the actual sysvol\sysvol\domain.local\scripts (i.e not
>> > in
>> > the
>> > proper sysvol share!)
>> >
>> > this is very confusing for me, has anyone else experienced this?
>> >
>> > All servers are windows 2003, both are DCs, GCs, DNS servers.
>>
>>
>>

As per my original post i have already performed a non authoritative restore...

"Paul Bergson [MVP-DS]" wrote:

> Personally I would do a non-authoritative restore on your sysvol.
>
> A domain controllers will erase their local copy of the sysvol and then
> replicate it from an another domain controller.
>
> How to perform a non-authoritative restore
> http://support.microsoft.com/?id=840674
>
> --
> Paul Bergson
> MVP - Directory Services
> MCT, MCSE, MCSA, Security+, BS CSci
> 2003, 2000 (Early Achiever), NT
>
>

It appears you did it incorrectly and I would review and retry if you found
your process incorrect.

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Luca" <Luca@discussions.microsoft.com> wrote in message
news:3BC89DA4-0E80-482E-96DF-AE05BE64DAE0@microsoft.com...
> As per my original post i have already performed a non authoritative
> restore...
>
> "Paul Bergson [MVP-DS]" wrote:
>
>> Personally I would do a non-authoritative restore on your sysvol.
>>
>> A domain controllers will erase their local copy of the sysvol and then
>> replicate it from an another domain controller.
>>
>> How to perform a non-authoritative restore
>> http://support.microsoft.com/?id=840674
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCT, MCSE, MCSA, Security+, BS CSci
>> 2003, 2000 (Early Achiever), NT
>>
>>

Ok i went through the steps and following them exactly. Problem still
remains. Still no junction point in c:\windows\sysvol\sysvol as mention in
previous post and logon scripts do not replicate to the netlogon share.

"Paul Bergson [MVP-DS]" wrote:

> It appears you did it incorrectly and I would review and retry if you found
> your process incorrect.
>
> --
> Paul Bergson
> MVP - Directory Services
> MCT, MCSE, MCSA, Security+, BS CSci
> 2003, 2000 (Early Achiever), NT
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Luca" <Luca@discussions.microsoft.com> wrote in message
> news:3BC89DA4-0E80-482E-96DF-AE05BE64DAE0@microsoft.com...
> > As per my original post i have already performed a non authoritative
> > restore...
> >
> > "Paul Bergson [MVP-DS]" wrote:
> >
> >> Personally I would do a non-authoritative restore on your sysvol.
> >>
> >> A domain controllers will erase their local copy of the sysvol and then
> >> replicate it from an another domain controller.
> >>
> >> How to perform a non-authoritative restore
> >> http://support.microsoft.com/?id=840674
> >>
> >> --
> >> Paul Bergson
> >> MVP - Directory Services
> >> MCT, MCSE, MCSA, Security+, BS CSci
> >> 2003, 2000 (Early Achiever), NT
> >>
> >>
>
>
>

Luca schrieb:
> What i mean is, logon scripts are replicating to the sysvol\domain\scripts
> folders but not to the netlogon share, so when i user logs in and their
> script runs, its runs from netlogon which is not the most up to dat script.
>
> When i did what you suggested on the DC in question i did not get a
> <junction> i got this:
>
> :\WINDOWS\SYSVOL\sysvol>dir
> Volume in drive C is OS
> Volume Serial Number is F8CE-977D
>
> Directory of C:\WINDOWS\SYSVOL\sysvol
>
> 26/02/2007 11:34 AM <DIR> .
> 26/02/2007 11:34 AM <DIR> ..
> 26/02/2007 11:36 AM <DIR> domain.local

recreate the junctions. How to do this is described in this article:

http://support.microsoft.com/kb/315457/en-us


--
Viele Grüße
Frank Röder
MVP Windows Server System - Directory Services
Ex oriente lux

Ok. I was going to point you to how to create a Junction point but it
appears Frank has already done that.

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Luca" <Luca@discussions.microsoft.com> wrote in message
news:551FC506-9624-4E28-A390-67872D0A0ED2@microsoft.com...
> Ok i went through the steps and following them exactly. Problem still
> remains. Still no junction point in c:\windows\sysvol\sysvol as mention in
> previous post and logon scripts do not replicate to the netlogon share.
>
> "Paul Bergson [MVP-DS]" wrote:
>
>> It appears you did it incorrectly and I would review and retry if you
>> found
>> your process incorrect.
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCT, MCSE, MCSA, Security+, BS CSci
>> 2003, 2000 (Early Achiever), NT
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Luca" <Luca@discussions.microsoft.com> wrote in message
>> news:3BC89DA4-0E80-482E-96DF-AE05BE64DAE0@microsoft.com...
>> > As per my original post i have already performed a non authoritative
>> > restore...
>> >
>> > "Paul Bergson [MVP-DS]" wrote:
>> >
>> >> Personally I would do a non-authoritative restore on your sysvol.
>> >>
>> >> A domain controllers will erase their local copy of the sysvol and
>> >> then
>> >> replicate it from an another domain controller.
>> >>
>> >> How to perform a non-authoritative restore
>> >> http://support.microsoft.com/?id=840674
>> >>
>> >> --
>> >> Paul Bergson
>> >> MVP - Directory Services
>> >> MCT, MCSE, MCSA, Security+, BS CSci
>> >> 2003, 2000 (Early Achiever), NT
>> >>
>> >>
>>
>>
>>

I have followed the the steps described in the article however on the problem
DC it seems to be falling down at the linkd steps.

I have done the following:
typed
ntfrsutl ds |findstr /i "root stage"
this returns the same as in the artice i.e.:
Root: C:\WINNT\SYSVOL\domain
Stage: C:\WINNT\SYSVOL\staging\domain

then i type
Linkd c:\windows\SYSVOL\SYSVOL\ domain.local
c:\windows\sysvol\sysvol\domain.local is not linked to another directory

the seccond linkd command seems to work:
C:\>linkd "c:\windows\sysvol\staging areas\domain.local"
Source c:\windows\sysvol\staging areas\domain.local is linked to
c:\windows\sysvol\staging\domain

I then follow the steps further down the page:
Type linkd C:\WINNT\SYSVOL\sysvol\DNS_Domain_Name Source, where Source is
the root path that is determined by using the NTFRSUTL command.

so i type
C:\>linkd c:\windows\sysvol\sysvol\domain.local c:\windows\sysvol\domain
Cannot create a link at: c:\windows\sysvol\sysvol\domain.local

So that seems to be the problem, it cannot create a link. Could this maybe
be some type of permission problem? All the ACLs look to be good.

Thanks for the help so far as well!


""Frank Röder [MVP]"" wrote:

> Luca schrieb:
> > What i mean is, logon scripts are replicating to the sysvol\domain\scripts
> > folders but not to the netlogon share, so when i user logs in and their
> > script runs, its runs from netlogon which is not the most up to dat script.
> >
> > When i did what you suggested on the DC in question i did not get a
> > <junction> i got this:
> >
> > :\WINDOWS\SYSVOL\sysvol>dir
> > Volume in drive C is OS
> > Volume Serial Number is F8CE-977D
> >
> > Directory of C:\WINDOWS\SYSVOL\sysvol
> >
> > 26/02/2007 11:34 AM <DIR> .
> > 26/02/2007 11:34 AM <DIR> ..
> > 26/02/2007 11:36 AM <DIR> domain.local
>
> recreate the junctions. How to do this is described in this article:
>
> http://support.microsoft.com/kb/315457/en-us
>
>
> --
> Viele Grüße
> Frank Röder
> MVP Windows Server System - Directory Services
> Ex oriente lux
>

Hello Luca,


> I have followed the the steps described in the article however on the problem
> DC it seems to be falling down at the linkd steps.
>
> I have done the following:
> typed
> ntfrsutl ds |findstr /i "root stage"
> this returns the same as in the artice i.e.:
> Root: C:\WINNT\SYSVOL\domain
> Stage: C:\WINNT\SYSVOL\staging\domain
>
> then i type
> Linkd c:\windows\SYSVOL\SYSVOL\ domain.local
> c:\windows\sysvol\sysvol\domain.local is not linked to another directory
>
> the seccond linkd command seems to work:
> C:\>linkd "c:\windows\sysvol\staging areas\domain.local"
> Source c:\windows\sysvol\staging areas\domain.local is linked to
> c:\windows\sysvol\staging\domain
>
> I then follow the steps further down the page:
> Type linkd C:\WINNT\SYSVOL\sysvol\DNS_Domain_Name Source, where Source is
> the root path that is determined by using the NTFRSUTL command.
>
> so i type
> C:\>linkd c:\windows\sysvol\sysvol\domain.local c:\windows\sysvol\domain
> Cannot create a link at: c:\windows\sysvol\sysvol\domain.local
>
> So that seems to be the problem, it cannot create a link. Could this maybe
> be some type of permission problem? All the ACLs look to be good.

please check your filesystem for errors (chkdsk). After this you can
completly restore your Sysvol again. Import it from a replication partner.

http://technet2.microsoft.com/Window....mspx?mfr=true

--
Viele Grüße
Frank Röder
MVP Windows Server System - Directory Services
Ex oriente lux

I'm having problems with step 9 on the link your provided. When i change to
the SYSVOL2 directory and do a dir, the <junction> is not there, just the
normal <dir>

and a bit further down the page where you need to verify the sysvol junction
when i type linkd fqdn it just comes up with "domain.local is not linked to
another directory"

Still when i try to manually link the folders using the following command:
linkd c:\windows\sysvol\sysvol\domain.local c:\windows\sysvol\domain i get
the error "cannot create a link and c:\windows\sysvoldomain.local"

""Frank Röder [MVP]"" wrote:

> Hello Luca,
>
>
> > I have followed the the steps described in the article however on the problem
> > DC it seems to be falling down at the linkd steps.
> >
> > I have done the following:
> > typed
> > ntfrsutl ds |findstr /i "root stage"
> > this returns the same as in the artice i.e.:
> > Root: C:\WINNT\SYSVOL\domain
> > Stage: C:\WINNT\SYSVOL\staging\domain
> >
> > then i type
> > Linkd c:\windows\SYSVOL\SYSVOL\ domain.local
> > c:\windows\sysvol\sysvol\domain.local is not linked to another directory
> >
> > the seccond linkd command seems to work:
> > C:\>linkd "c:\windows\sysvol\staging areas\domain.local"
> > Source c:\windows\sysvol\staging areas\domain.local is linked to
> > c:\windows\sysvol\staging\domain
> >
> > I then follow the steps further down the page:
> > Type linkd C:\WINNT\SYSVOL\sysvol\DNS_Domain_Name Source, where Source is
> > the root path that is determined by using the NTFRSUTL command.
> >
> > so i type
> > C:\>linkd c:\windows\sysvol\sysvol\domain.local c:\windows\sysvol\domain
> > Cannot create a link at: c:\windows\sysvol\sysvol\domain.local
> >
> > So that seems to be the problem, it cannot create a link. Could this maybe
> > be some type of permission problem? All the ACLs look to be good.
>
> please check your filesystem for errors (chkdsk). After this you can
> completly restore your Sysvol again. Import it from a replication partner.
>
> http://technet2.microsoft.com/Window....mspx?mfr=true
>
> --
> Viele Grüße
> Frank Röder
> MVP Windows Server System - Directory Services
> Ex oriente lux
>