Client push installation on secondaries

Product:  SMS 2003 R2 on W2K3.
Design:  Single primary site, multiple secondary's

Could somebody tell me whether enabling Client Push Installation on SMS secondary sites will result in the advanced client being installed on computers in that site? AD system discovery and Client Push installation will have already have been enabled at the primary site.  MP exists at the primary, PMP at secondary.

I'm designing SMS (no lab at the moment) and the answer to this question changes depending on who you talk to - in particular between M$ and a M$ MVP.

Some extensive background below:

M$ MVP:
> 2)  Enabling AD Discovery and Client Push Installation for the primary site
> will result in only those clients within that site boundaries being
> installed?  I.e., computers at secondary sites will not get installed?
Nope, enabling client push will push the client to all clients assigned to
that site. (Secondary site clients are assigned to that site as well, but
aren't part of the site's boundaries)

> 3)  Enabling AD discovery and Client Push Installation at a secondary site
> will result in clients within the site boundary being installed, and (in
> our case) assigned to the primary site.
Unfortunately not, that is how we would like it to work.
http://blogs.msdn.com/smsperfguy/archive/2004/05/13/131528.aspx
This blog post explains the issue in detail.

M$:
=====================================================
(A) - ASSESSMENT - Troubleshooting/Communication
=====================================================
Tested in LAB
Configured a router connected to 2 different subnets.

192.168.0.0/24 (The Primary Site Server 000)
192.168.1.0/24 (The DC, Secondary site Server 001 and one XP client)


TEST1: (We are focused on installing Advance client on XP client in Secondary site)

The Primary site server is configured Site as following:

Site Boundaries = 192.168.0.0/24
AD system Discovery Enabled = YES
Client push is enabled. = YES

Secondary Site as follows:

Site Boudaries = 192.168.1.0/24
AD System Discovery = NO
Client Push = NO

Checked the log files on Primary site server:

ADSYSDISC.LOG (Primary Site)
===================
Starting the data discovery. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:37 PM 3476 (0x0D94)
Bound to AD Container LDAP://DC=Litware,DC=com. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:37 PM 3476 (0x0D94)
Server name: smsdc01.litware.com SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:38 PM 3476 (0x0D94)
Searching AD Container LDAP://DC=Litware,DC=com. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:38 PM 3476 (0x0D94)
Server name: smsdc01.litware.com SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:38 PM 3476 (0x0D94)
System SMSDC01 is accessible. IP address is 192.168.1.1. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:38 PM 3476 (0x0D94)
System SMSSITE is accessible. IP address is 192.168.0.2. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:38 PM 3476 (0x0D94)
System MOM2005 is accessible. IP address is 192.168.0.10. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:39 PM 3476 (0x0D94)
System XPCLIENT is accessible. IP address is 192.168.1.55. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:39 PM 3476 (0x0D94)
System SMSDC01. AD Site Name Default-First-Site-Name. Subnet 192.168.1.0/24 SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:39 PM 3476 (0x0D94)
System SMSSITE. AD Site Name SMS. Subnet 192.168.0.0/24 SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:39 PM 3476 (0x0D94)
System MOM2005. AD Site Name SMS. Subnet 192.168.0.0/24 SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:39 PM 3476 (0x0D94)
System XPCLIENT. AD Site Name Default-First-Site-Name. Subnet 192.168.1.0/24 SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:39 PM 3476 (0x0D94)
DDR was written for system 'SMSDC01' - C:\SMS\inboxes\auth\ddm.box\ads1u1i3.DDR at 2/16/2007 23:23:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:40 PM 3476 (0x0D94)
DDR was written for system 'SMSSITE' - C:\SMS\inboxes\auth\ddm.box\adsx4k8k.DDR at 2/16/2007 23:23:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:40 PM 3476 (0x0D94)
DDR was written for system 'MOM2005' - C:\SMS\inboxes\auth\ddm.box\ads6b6le.DDR at 2/16/2007 23:23:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:41 PM 3476 (0x0D94)
DDR was written for system 'XPCLIENT' - C:\SMS\inboxes\auth\ddm.box\adsy1zvq.DDR at 2/16/2007 23:23:37. SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:41 PM 3476 (0x0D94)
AD Discovery under container LDAP://DC=Litware,DC=com found 4 objects SMS_AD_SYSTEM_DISCOVERY_AGENT 2/16/2007 11:23:41 PM 3476 (0x0D94)
===============================


From above log, XPClient is discovered by AD System Discovery in Primary site and DDR is written.

DDM.log (Primary site)

===============================
==>Name = <XPCLIENT> SMS_DISCOVERY_DATA_MANAGER 2/16/2007 11:23:49 PM 2188 (0x088C)
==>Assigning to site <001>. Discovery property <IP Subnets> matches (192.168.1.0) SMS_DISCOVERY_DATA_MANAGER 2/16/2007 11:23:49 PM 2188 (0x088C)
insert base table: System_DISC : execute sql insert into System_DISC (ItemKey, DiscArchKey, Netbios_Name0, Operating_System_Name_and0, Resource_Domain_OR_Workgr0, AD_Site_Name0, Name0, Creation_Date0) values (9, 5, "XPCLIENT", "Microsoft Windows NT Workstation 5.1", "LITWARE", "Default-First-Site-Name", "XPCLIENT", "02/16/2007 23:23:49") SMS_DISCOVERY_DATA_MANAGER 2/16/2007 11:23:51 PM 2188 (0x088C)
insert agent information: DiscItemAgents : execute sql insert into DiscItemAgents (ItemKey, DiscArchKey, AgentID, AgentTime, AgentSite) values (9, 5, 7, "02/16/2007 23:23:37", "000") SMS_DISCOVERY_DATA_MANAGER 2/16/2007 11:23:51 PM 2188 (0x088C)
Database operations finished. SMS_DISCOVERY_DATA_MANAGER 2/16/2007 11:23:51 PM 2188 (0x088C)
CDiscoverDataManager::FilterDDR - Will not create CCR. This item is not assigned to this site. SMS_DISCOVERY_DATA_MANAGER 2/16/2007 11:23:51 PM 2188 (0x088C)
CDiscoverDataManager::ProcessDDRs_PS - finished processing file C:\SMS\inboxes\auth\ddm.box\adsy1zvq.DDR. SMS_DISCOVERY_DATA_MANAGER 2/16/2007 11:23:51 PM 2188 (0x088C)
===============================

So from the above log file, the DDR is written, but no CCR is created as this client is not assigned to site (However SMS Admin console showing the client as Assigned)

==
CDiscoverDataManager::FilterDDR - Will not create CCR. This item is not assigned to this site.
==

Because their is no CCR, no client will be pushed to XPClient from Primary site, however it does send .PDR for this to secondary site.



DDM.LOG on secondary site
======================
SMS_DISCOVERY_DATA_MANAGER is starting... SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:21:02 AM 3604 (0x0E14)
Refreshing site settings..... SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:21:04 AM 3604 (0x0E14)
Legacy Client Remote Install: AutoInstallSiteSystem = 0 SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:21:05 AM 3604 (0x0E14)
Legacy Client Remote Install: FILTERS = 2 SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:21:05 AM 3604 (0x0E14)
Legacy Client Remote Install: Settings = ACTIVE SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:21:05 AM 3604 (0x0E14)
CDiscoverDataManager::THREAD_Forwarder - Forwarder thread has started. SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:21:05 AM 2532 (0x09E4)
Refreshing site settings..... SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:23:07 AM 3604 (0x0E14)
Processing file ed1z0sfc.PDR SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:23:07 AM 3604 (0x0E14)
Processing discovery item 11 SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:23:07 AM 3604 (0x0E14)
CDiscoverDataManager::FilterDDR - Will not create CCR. 'Client Push Installation to Assigned Resources' is not enabled, and this DDR was not found by Windows NT Server Discovery Agent. SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:23:07 AM 3604 (0x0E14)
=======================

From above log file, its clear that it recieved a .PDR from primary site, but will not create a CCR because Client push is not enabled on Secondary site.


TEST2.

We left Primary as it is.

Secondary site is configured as follows:

Site boundaries : 192.168.1.0/24
Client push enabled: YES
AD system Discovery: NO
MP = YES (Proxy MP)


DDM.LOG on secondary site.
====================
SMS_DISCOVERY_DATA_MANAGER is starting... SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:44 AM 3060 (0x0BF4)
Refreshing site settings..... SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 3060 (0x0BF4)
Legacy Client Remote Install: AutoInstallSiteSystem = 0 SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 3060 (0x0BF4)
Legacy Client Remote Install: FILTERS = 2 SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 3060 (0x0BF4)
Legacy Client Remote Install: Settings = ACTIVE SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 3060 (0x0BF4)
DDM has detected that it has been activated. Will refresh client list for CCRs. SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 3060 (0x0BF4)
CDiscoverDataManager::THREAD_RefreshCCRs - beginning CCR refresh... SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 2180 (0x0884)
CDiscoverDataManager::THREAD_RefreshCCRs - Finding all NT systems assigned to this site. SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 2180 (0x0884)
CDiscoverDataManager::THREAD_Forwarder - Forwarder thread has started. SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 3628 (0x0E2C)
Name = <XPCLIENT> SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 2180 (0x0884)
CDiscoverDataManager::CreateCCRFile - Creating CCR o0km5ntt for XPCLIENT in E:\SMS\inboxes\ccr.box SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 2180 (0x0884)
CDiscoverDataManager::THREAD_RefreshCCRs - Reevaluation completed successfully. Exiting thread. SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:28:46 AM 2180 (0x0884)
CDiscoverDataManager::THREAD_Forwarder - Forwarder thread is stopping. SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:32:16 AM 3628 (0x0E2C)
SMS_EXECUTIVE started SMS_DISCOVERY_DATA_MANAGER as thread ID 3236 (0xCA4). SMS_DISCOVERY_DATA_MANAGER 2/17/2007 3:32:24 AM 1704 (0x06A8)
====================================


From above log its clear that CCR is created at secondary site after enabling Client push at secondary site.


CCM.LOG (Secondary site)
===================================
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:27 AM 3868 (0x0F1C)
Received request: "O0KM5NTT" for machine name: "XPCLIENT" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:27 AM 3868 (0x0F1C)
Stored request "O0KM5NTT", machine name "XPCLIENT", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:27 AM 3868 (0x0F1C)
----- Started a new CCR processing thread. Thread ID is 0xed8. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:29 AM 3868 (0x0F1C)
Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:29 AM 3868 (0x0F1C)
Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:29 AM 3868 (0x0F1C)
======>Begin Processing request: "O0KM5NTT", machine name: "XPCLIENT" SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:29 AM 3800 (0x0ED8)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:29 AM 3800 (0x0ED8)
---> Attempting to connect to administrative share '\\XPCLIENT\admin$' using account 'litware\administrator' SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:29 AM 3800 (0x0ED8)
Waiting for change in directory "E:\SMS\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:29 AM 3868 (0x0F1C)
---> Connected to administrative share on machine XPCLIENT using account 'litware\administrator' SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:29 AM 3800 (0x0ED8)
---> Attempting to make IPC connection to share <\\XPCLIENT\IPC$> SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> System OS version string "5.1" converted to 5.10 SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Could not retrieve the heartbeat time from the client (2) SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Unable to retrieve a sites list from machine "XPCLIENT". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Unable to retrieve travel mode switch from machine "XPCLIENT". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Unable to retrieve pending command value for sms client base components from machine "XPCLIENT". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Could not retrieve the site config timestamp from the client (2) SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Unable to retrieve the mobile client version from machine "XPCLIENT". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Client type to be installed on XPCLIENT: Advanced client SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Copying client files to \\XPCLIENT\admin$\system32\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Copying file "E:\SMS\bin\I386\MobileClient.tcf" to "\\XPCLIENT\admin$\system32\ccmsetup\MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:30 AM 3800 (0x0ED8)
---> Created service "ccmsetup" on machine "XPCLIENT". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:32 AM 3800 (0x0ED8)
---> Started service "ccmsetup" on machine "XPCLIENT". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:33 AM 3800 (0x0ED8)
---> Completed request "O0KM5NTT", machine name "XPCLIENT". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:33 AM 3800 (0x0ED8)
Deleted request "O0KM5NTT", machine name "XPCLIENT" SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:33 AM 3800 (0x0ED8)
<======End request: "O0KM5NTT", machine name: "XPCLIENT". SMS_CLIENT_CONFIG_MANAGER 2/17/2007 3:37:33 AM 3800 (0x0ED8)
=====================================


CCM at secondary site started the CCMSETUP.EXE on XPClient in secondary site.


Checked CCMSETUP.LOG on XPClient.

=====================================
==========[ ccmsetup started in process 1340 ]========== ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
Version: 2.50.3174.1000 ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
No network access account provided. Ccmsetup will use current credentials for network access. ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
Config file: C:\WINDOWS\system32\ccmsetup\MobileClient.tcf ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
Retry time: 10 minute(s) ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
MSI log file: ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
MSI properties: INSTALL="ALL" SMSSITECODE="AUTO" ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
Source List: ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
\\SMSDC01\SMSClient\I386 ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
Status MPs: ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
SMSDC01 ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 2/17/2007 3:37:33 AM 1684 (0x0694)
Running as user "SYSTEM" ccmsetup 2/17/2007 3:37:33 AM 1848 (0x0738)
Downloading file client.msi ccmsetup 2/17/2007 3:37:33 AM 1848 (0x0738)
Determining source location... ccmsetup 2/17/2007 3:37:33 AM 1848 (0x0738)
Found accessible source: \\SMSDC01\SMSClient\I386 ccmsetup 2/17/2007 3:37:35 AM 1848 (0x0738)
Downloading \\SMSDC01\SMSClient\I386\client.msi to C:\WINDOWS\system32\ccmsetup\client.msi ccmsetup 2/17/2007 3:37:35 AM 1848 (0x0738)
File download 0% complete (61440 of 7078400 bytes). ccmsetup 2/17/2007 3:37:36 AM 1848 (0x0738)
File download 1% complete (122880 of 7078400 bytes). ccmsetup 2/17/2007 3:37:36 AM 1848 (0x0738)
File download 2% complete (184320 of 7078400 bytes). ccmsetup 2/17/2007 3:37:36 AM 1848 (0x0738)
===========================================


From the above log, we can see that XPClient contacted SMSDC01 (Secondary Site server and Proxy MP) to download the Client.msi file.
===========================================

Finally I got advance client installed on XPClient.

So everything is clear here:

To install Advance client, following is the process:

1. Client got discovered in Primary site using some discovery method.
2. DDR is generated at primary site
3. no CCR is generated at primary site, because client is not assigned to site (Admin console is saying that its assigned), bacause its not a part of primary site boundaries. so it will send a respective .PDR file to secondary site.
4. Secondary site's DDM will process the .PDR file recieved and will create a CCR (Only if Client push is enabled in secondary site).
5. CCM at secondary site will connect to client and start the CCMSETUP.EXE
6. CCMSETUP.EXE will contact the MP of site generated the CCR and will download the file(Client.msi) from Proxy MP and completes the Advance client installation.

Start Free Trial