Client Push Installation Properties - Client TAB
Greetings, The scenario is the following: 1 Primary site. 1 Server. SCCM 2007 SP2 R3.Win2008R2 SP11 Secondary site. 1 Server. SCCM 2007 SP2 R3. Win2008R2 SP1In Primary site, in Client Push Installation Properties, Client Tab, the setting is: SMSSITECODE=AUTOIn Secondary site, in Client Push Installation Properties, Client Tab, the setting is: SMSSITECODE=AUTO (same as primary site).Both servers are Management Points. When I use the Client Push Installation Wizard (from SCCM Console) in the primary site server to install the client in a PC in the secondary site, I get the following: Adding file 'http://PRIMARY_SITE_SERVER.MYDOMAIN.COM:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\client.msi'. ccmsetup 30/08/2012 10:34:18 1088 (0x0440) But, when I manually install the client in another PC in the secondary site using "ccmsetup.exe /SMSSITECODE=AUTO" I get the following: Adding file 'http://SECONDARY_SITE_SERVER.MYDOMAIN.COM:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WINDOWS\system32\ccmsetup\client.msi'. ccmsetup 30/08/2012 9:52:11 5792 (0x16A0) The Question is: What would be the settings in Client Tab in Client Push Installation Properties that allow the PCs at secondary site get the installation files from the secondary site server? Thanks in advance!
August 31st, 2012 11:54am

First note, your command line is incorrect: SMSSITECODE is a public property passed to msiexec for use by the MSI and thus should not have a slash prefixing it. Your command-line should be ccmsetup.exe SMSSITECODE=AUTO. However, if you don't specify SMSSITECODE, it will default to auto so there's really no need to even specify it. Next note, the settings in the Client tab of the Client Push Installation dialog on the secondary are not used for manual client push, only auto-client push. Not exactly sure of the difference for downloading the pre-reqs but I suspect that manual push is adding a /mp switch to the ccmsetup command line whereas the manual push is using auto MP location based on boundaries to download the content.Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2012 2:57pm

Hi Jason, Thanks for your response. You say: "Not exactly sure of the difference for downloading the pre-reqs but I suspect that manual push is adding a /mp switch to the ccmsetup command line whereas the manual push is using auto MP location based on boundaries to download the content." manual push vs. manual push? (are you comparing the same?) Thanks!
August 31st, 2012 5:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics