Solved

Copy to Sysvol Very Slow

Posted on 2011-03-04
6
693 Views
Last Modified: 2012-06-22
When I copy to the sysvol, a file takes ~3minutes to copy, where as if i copy to a DC in the site via \\server\sysvol\domain\, it takes ~10 seconds.  I don't see replicaiton errors in the logs.  I have looked over assignment of subnets in sites and services and it looks to be good.  This is a new occurance.  Until about a month ago, copying to the sysvol was just fine.

Domain & Forest are 2003 function level

8 sites, the site in question has 3 DCs.  
0
Comment
Question by:whoam
  • 3
  • 3
6 Comments
 

Author Comment

by:whoam
ID: 35041258
from what I can tell, replication is very healthy.  Replmon and ultrasound concur and files place in the sysvol at the site in question replicate quickly.  It seems that the server in question is going off site when it copies to the sysvol.  So, how do I one figure out what site it thinks its in and two correct the server?
0
 
LVL 21

Expert Comment

by:snusgubben
ID: 35047763
Have you created subnets in AD Sites and Services and assigned them to the correct site?

0
 

Author Comment

by:whoam
ID: 35051272
snusgrubben,

Yes, I have thanks.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 21

Expert Comment

by:snusgubben
ID: 35055073
So I can assume the IP to the spesific server, has a subnet defined in AD S&S?

Do all clients have this delay copying to SYSVOL?
0
 

Author Comment

by:whoam
ID: 35073523
No, clients okay, in fact doing some testing I find that
1.  it's only one server that exhibits this behavior that I have found so far.
2.  I have found that DC that the trouble server considers authoritative for the sysvol.  The problem server and it's preferred DC are in different sites.  
3.  The logon server of the trouble server is in the same site with the trouble server, but it isn't looking to it for sysvol queries.

Let’s say site 1is the main site and site two is the distant site

Server A is ‘the trouble server’.  Server B is the DC listed by Server A is it’s logon server when I log in.  Server A and B are in site 1.  Server C is the DC in site 2.  Server B is looking to server C for sysvol queries.  Very odd.  The subnets folder in AD S&S is populated with my subnets and they are assigned to sites.  Sites list their correct DCs.
0
 
LVL 21

Accepted Solution

by:
snusgubben earned 500 total points
ID: 35080672
When "Server A" authenticate towards a DC in its site, it does not mean it will use the SYSVOL that the authenticating DC holds.

The authenticating DC (GC) will send "Server A" a list of SYSVOL servers across the domain.

1. All site-local SYSVOL servers
2. A random list of all SYSVOLs (not based on site link costs)

"Server A" should pick a SYSVOL from #1. If all those are unavalible, it will pick one from #2.

Why "Server A" picks one from #2 in your case, can be caused by lots of things. Take a look at possible causes that the MS Storage team made.

http://blogs.technet.com/b/filecab/archive/2006/04/13/425169.aspx

(they talk about DFS, but SYSVOL = DFS namespace)
0

Featured Post

DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

One of the most often confused topics in the area DNS is the idea of GLUE records. Specifically, what they are, when they are needed, when they are provided, and how they are created. First, WHAT IS GLUE? To understand GLUE, you must first under…
Disabling the Directory Sync Service Account in Office 365 will stop directory synchronization from working.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

815 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now