Wednesday, January 23, 2013 10:29 PM
So I have recently began pushing out some software with a third party app called SpecOps. It has been working fine pushing software out to pc's at our main branch, but now I am beginning to push out to our remote branches, using various WAN speeds. It appears that it is pushing out the software installs(similar to SCCM) such as MS Office 2010 Pro Plus, Java, Adobe pick your poison, etc. The smaller installs have not been an issue, but Office is what has decided to shine a light on a possible issue. It it taking about 3 hours to install Office 2010 a 1.18GB folder share being shared with DFS. I have checked the DFS properties and it appears to be configured correctly from what I have found on here already. The software should be pushing from the local DC/DFS which is at the remote branch.
My question is do I need to mess around with AD Sites and Services? Currently our cost is set at 100 flat across the board and we have 10 branches total.(9 Remote and 1 Main) Do I need to set costs to specific values for DFS to work properly? I *think* that it is being fed from our main server because last night when it was attempting to deploy to 13 pc's, it was only at 83% complete this morning about 8am and it had started at 12am and using MRTG it showed the 9mb/s link saturated the entire night. (3 BondedT1's)
I have read a few threads on here, but I need help, seeing as how I did not configure DFS, have never worked with DFS or AD S+S.
I will appreciate any assistance,
Wednesday, January 23, 2013 11:48 PM
Most likely the installation is occuring over the wan link that is why is running so slow.
Here are some things you can do:
If you are using a DFS namespace to replicate those folders you have the following options you can configure either on the namespace or on the indivitdual folder:
So depending on how you have configured you sites and subnets in active directory, the settings you select here will work for you or against you.
You can also use Dfsutil for troubleshooting, for example:
Displays the following client information currently in the Partition Knowledge Table (PKT):
• Parts of the DFS namespace cached by the client
• Names of the servers participating in the DFS share
• Clients’ randomization order of the participating servers
• Current "go to" server
Flushes the client's locally cached target referral list provided by the DFS server. When the client tries to access the corresponding link, this forces the client to refresh the referral list of targets from the DFS server. Some of the entries in the PKT may not get flushed, especially if DFS is in the process of using the referrals.
Displays the content of SPC. The SPC contains the list of trusted domains; under each trusted domain there may be one or more domain controllers.
Forces the client to fetch the latest information on the trusted domains and their domain controllers, when the client programs try to access a corresponding link or root. By using this option, the client flushes out its cached knowledge about the trusted domains and the domain controllers of these domains.
Output Description for dfsutil /spcinfo
SPC table information can be displayed by using the /spcinfo parameter. The following describes the type of output produced when /spcinfo is used. The description numbers correspond to the numbers in the sample output.
1. Entries beginning with [*] are not expanded, and are local to the domain.
2. Entries beginning with [+] are expanded into the DC list due to access.
3. Indented entries are expanded entries of the domain entry of the domain1.companydom.com domain.
4. Unexpanded domains which have not been accessed or required to expand by the client. The local client cache contains no further information about these domains. Only trusted domains are listed.
"Example: Force a DFS Client to Get a Target Referral List from the Server
A client benefits from high availability in DFS by getting a list of link target referrals within the same site as well as targets in farther sites. In some cases targets in the closer sites may be inaccessible at the beginning of the client's use, causing the client to successfully failover to a target at a farther site. Once a closer and less expensive target is available, you would like the client to use it. If you do not want to reboot the client to cause a closer site to be selected, type the following at the command line:
This command statement flushes the local partition knowledge table (PKT). This forces the client to get the referral list of the targets from the server again. Some of the entries in the PKT may not get flushed, especially if DFS is in the process of using the referrals. Once the PKT is flushed from the client cache, the client gets a new list of referrals from the server and it surely will try accessing the closer targets.
• There is no guarantee that the client select a desired target in the same site when there are other equivalent candidates available in the same site.
• Rebooting the client can replace the need of using the /pktflush parameter."
Check the Dfsutil syntax for additional info.
If you test this on a windows 7 client you need the RSAT tools
Wednesday, January 23, 2013 11:50 PMAlso if this doesn't work for you, its possible you can get more help on the File and Storeage forum: http://social.technet.microsoft.com/Forums/en/winserverfiles/threads
Thursday, January 24, 2013 9:11 PMThanks for the info, but it appears to still be pulling from HDQ. I tried running dfsutil and also some commands using dfsdiag on the servers that are part of the DFS configuration. The server here at HQ is a standalone box that runs SpecOps and WSUS, but WSUS is not pushing out but daily around 2am. I don't know if there should be more than this in the AD-S&S or not?
Wednesday, January 30, 2013 1:59 AMModerator
You may read this articles:
How DFS work
Active Directory Sites and Services
As Marius mentioned, perhaps you can get help on the File and Storage forum:http://social.technet.microsoft.com/Forums/en/winserverfiles/threads
TechNet Community Support