There seems to be some confusion about how the client push installation method works to get the SMS 2003 Advanced Client installed on discovered resources at secondary sites lately. I've done some research on this and tried to explain the process here to try and avoid any further confusion. The main point to understand before beginning is the difference between enabling the site-wide client push intallation method and using the Client Push Installation Wizard. The site-wide client push installation method will only install clients to assigned resources (within the site's boundaries), while the Client Push Installation Wizard will attempt to install the client on non-assigned systems (not within the site's boundaries).
I’ve tried to summarize this using three scenarios:
1. Discovery and the site-wide client push installation method IS NOT enabled at the secondary site
2. Discovery and site-wide client push installation method IS enabled at the secondary site
3. Discovery IS enabled at the primary site, but it IS NOT enabled at the secondary site, and site-wide client push installation method IS enabled at the secondary site.
So, first a quick summary of how all of this works. Getting the Advanced Client installed via the site-wide client push installation method requires (very high level summary here) a Discovery Data Record (DDR) created by a discovery method, and a Client Configuration Request (CCR) generated by a site server for the discovered resource. CCR's are only created for systems discovered that are (a.) within the site's boundaries (not roaming boundaries) and (b.) the discovered resource matches the criteria you've set in the site-wide client push installation properties. Once a CCR is processed by the site server's Client Configuration Manager (CCM) component, the client installation process is initiated.
Scenario 1. Discovery and client push IS NOT enabled at the secondary site.
If a discovered resource is within the boundaries of a secondary site, how is it installed using a client push method (when discovery and client push at the secondary site IS NOT enabled)?
Step 1 (DDR creation). If you have enabled a discovery method at the primary site that discovers a resource within a secondary site's defined boundary, the primary site will create a DDR for the resource. Because the resource is not within the primary site's defined site boundaries no CCR will be created (client will not be installed). The DDR created will be stored in the database until it is deleted by the "Delete aged discovery data" maintenance task. The DDR is then sent to the secondary site as a PDR (processed DDR). Because the secondary site does not have client push enabled, that's the end of the line for that PDR and it will not be processed.
Here's where it get interesting:
Step 2 (CCR creation). If you use the Client Push Installation Wizard to push the client out to discovered resources--AND uncheck the "Include only clients assigned to this site" check box, a CCR will be created for the DDRs representing non-assigned resources in the database and an attempt will be made to get the client installed on them. Once installed, the Advanced Client (at the secondary site) will be assigned to the primary site and report up via the secondary site's proxy management point--if one exists at the secondary site.
Scenario 2. Discovery and client push IS enabled at the secondary site.
If a discovered resource is within the boundaries of a secondary site, how is it installed using a client push method (when discovery and client push at the secondary site IS enabled)?
Step 1 (DDR creation). A discovery method at the secondary site discovers a resource and creates a DDR (forwards to primary site to store in the site database). The primary site receives the DDR, stores it in the database and sends the PDR (processed DDR) back to the secondary site.
Step 2 (CCR creation). The secondary site recieves the PDR (processed as a DDR) and sees that a discovered resource is within its boundaries (and meets the defined site wide client push installation properties) and creates a CCR for the resource itself (CCR's do not travel up the hierarchy). At this point, CCM at the secondary site will begin the client installation process by checking for a management point to push the source files to the resource to get the client installed. If the secondary site has a proxy management point, the client installation files will be pushed from there, otherwise, the site's default management point (at the primary site) will be where the source files come from. Once installed, the client will be assigned to the primary site and report up via the secondary site's proxy management point--if one exists at the secondary site.
Scenario 3. Discovery IS enabled at the primary site, but it is NOT enabled at the secondary site, and site-wide client push installation method IS enabled at the secondary site.
If the primary site discovers a resource that is located within the boundaries of a secondary site, how is it installed using a client push method (when discovery IS NOT enabeld at the secondary site, but client push IS enabled)?
Step 1 (DDR creation). If you have enabled a discovery method at the primary site that discovers a resource within a secondary site's defined boundary, the primary site will create a DDR for the resource. Because the resource is not within the primary site's defined site boundaries no CCR will be created (client will not be installed). The DDR created will be stored in the database until it is deleted by the "Delete aged discovery data" maintenance task. The DDR is then sent to the secondary site as a PDR (processed DDR). Unlike Scenario 1, because the secondary site does have client push enabled, the PDR can now be processed.
Step 2 (CCR creation). The secondary site recieves the PDR (processed as a DDR) and sees that a discovered resource is within its boundaries (and meets the defined site wide client push installation properties) and creates a CCR for the resource itself (CCR's do not travel up the hierarchy). At this point, CCM at the secondary site will begin the client installation process by checking for a management point to push the source files to the resource to get the client installed. If the secondary site has a proxy management point, the client installation files will be pushed from there, otherwise, the site's default management point (at the primary site) will be where the source files come from. Once installed, the client will be assigned to the primary site and report up via the secondary site's proxy management point--if one exists at the secondary site.
So, there you go, in a virtual nutshell, how the client push installation method works to install the SMS 2003 Advanced Client.
Hope this helps, and as always:
This posting is provided "AS IS" with no warranties, and confers no rights.
Bonus info:
Either way, once CCM begins processing the CCR for a resource, it will attempt to install the client once an hour for about 168hrs (one week) before giving up.
If you need help troubleshooting SMS 2003 client push issues, check out How to Troubleshoot Advanced Client Push Installation Issues in Systems Management Server 2003 on the SMS&MOM team blog at http://blogs.technet.com/smsandmom/archive/2007/08/28/how-to-troubleshoot-advanced-client-push-installation-issues-in-systems-management-server-2003.aspx.