A secondary site has been created at my office and I am having difficulty with the client installations. The client discovery defined in the secondary site settingsworks fine. The adsysdis.log on the secondary site server shows all the clients being discovered and DDR files being written at \inbox\auth\ddm.box. If I look in the ddm.log file, there does not appear to be any discovery items. If I do a manual client install, everything works fine. But, from what I understand if you do it that way the install comes from the primary site. I then tried to run a script to install the client:set objFSO = CreateObject("Scripting.FileSystemObject")set objShell = CreateObject("WScript.Shell")if not objFSO.FileExists("c:\windows\system32\ccm\ccmexec.exe") thenobjShell.Run "\\secondarysite\SMS_secondarysite\Client\CCMSETUP.EXE /mp:secondarysite /logon SMSSITECODE=AUTO FSP=primarysite", trueend ifset objFSO = Nothingset objShell = NothingThe log file on the client ends with:Source \\secondarysite\SMS_secondarysite\Client is inaccessible (5)ccmsetup5/11/2009 2:30:14 PM2132 (0x0854)Failed to find accessible source. Waiting for retry.ccmsetup5/11/2009 2:30:15 PM2132 (0x0854)I have had nothing but issues with getting this secondary site running.....be it issues with our VPN software, not installing BITS right away, WebDav being prohibited....etc....all of which have been fixed. But all of which have given me a headache at some point. What logs should I be looking at? What else can I do to troubleshoot?Any help would be appreciated.

Initiating a push using the console will result in the primary pushing the client. Have you enabled the automatic client push on the secondary? have you defined the boundaries?

Yes, client push is enabled and boundaries are set based on active directory sites.

OK I figured out what it was. I found all the client installs had gone through when I came in the following day. I then noticed that they all started the install at 8 PM based on the log on the client. Which made me think about the network load settings we set between the two sites. We had set only "Allow high priority only" during 6AM and 8PM and also had the rate limits set to use 10% of the bandwith during 6AM to 8PM. So for now we just set them to unlimited and to allow all priorities. After doing that, the client installs after discovery worked as expected. Does anyone know which setting would have prevented the client install from happening between 6 AM and 8 PM?

I don't know for certain, but would client install be considered Hi Pri traffic? If not, then it sounds like it might restrict that during that time.

Hi, we're seeing exactly the same issue - closing the senders to high priority only kills client install after discovery on secondary sites. The minute you open up to high and medium traffic between the primary and secondary the clients start installing. Can anyone else confirm that this is correct, and also can any tell me what other traffic will start to flow on high & medium? Assuming Packages are set to low, to take them out of the equations, what increase in volume of traffic will we see with High & Medium allowed instead of just High?