SMS Advanced Client Push Installation process

The article describes the SMS Advanced Client Push Installation process

Pre-installation stage
 1. During the pre-installation stage, When the Client Push Installation wizard starts, Client Configuration Request (CCR) is created for each targeted computer. Each CCR is placed into the Inboxes\CCR.box folder on the site server. Client Configuration Manager (CCM) selects a CCR from the Inboxes\CCR.box folder on the site server (CCM tasks are logged in ccm.log on the site server) The CCR file contains the client computer name and additional information.
 2. The SMS Client Configuration Manager connects to the ADMIN$ share on the client. This is based on the information in the CCR file.
 3. The Client Configuration Manager attempts to connect to the computer using the Client Push Installation Account (if the connection was not successful it attempts to connect to the computer by using the site server computer account). The Client Configuration Manager connects to the client registry and gathers information about the client. This process is displayed as a log entry in the Ccm.log as connecting to IPC$.
 4. Client Configuration Manger copies CCMSetup.exe and mobileclient.tcf which are located in the SMS\bin\I386\ folder to the %windir%\System32\ccmsetup folder (32-bit version of windows) on the client computer or if it is 64-bit version of windows copies to %windir%\ccmsetup folder on the client computer.
 5. The Client Configuration Manager verifies that the Ccmsetup service started successfully before disconnecting. The CCR file is added to the SMS\Inboxes\Ccrretry.box folder for verification that the installation succeeded. On a second verification pass, SMS determines that the SMS Agent Host is running, and then deletes the CCR file.
 6. If the Client Configuration Manager encounters any errors during this process, the CCR file is renamed to the name of the target client computer and is put in the SMS\Inboxes\Ccrretry.box folder. The Client Configuration Manager checks for files in this inbox folder every 60 minutes and tries to reprocess them 168 times (7 days) before they are discarded. This information is logged in the Ccm.log.
Installation Stage
 1. Ccmsetup.exe starts, and then scans the MobileClient.tcf file. This file is a configuration file from which Ccmsetup.exe obtains information that is required to locate the Client.msi file on the site server. The MobileClient.tcf file also provides the SMS site code, the management point server name, the site boundary, and other information.
 2. Ccmsetup.exe downloads the client.msi file from the SMSClient\i386 shared folder on the SMS management point or from the Client\i386 folder in the SMS_sitecode shared folder on the SMS site server. The Advanced Client Installer runs the Client.msi Setup program by using the parameters that the administrator specifies in the SMS Administrator console.
Post-installation Stage
 1. By default, if the Advanced Client Push Installation properties specify that the client is automatically assigned to a site by using the property SMSSITECODE=AUTO, the client queries Active Directory for its site assignment.
 2. If Active Directory is not installed, or the SMS schema is not extended, the client searches for a server locator point from which to obtain the site assignment and the management point information.
 3. If the Active Directory schema is extended, the client obtains its site assignment and management point information by using an LDAP query to Active Directory.
 4. When the client uses an SLP lookup or Active Directory lookup to locate the default management point, the client requests the initial policy from the management point.

Comments

Post a Comment

Popular posts from this blog

Hardware Inventory Action missing

Other than the obvious, if on your site server or client the Hardware Inventory action is missing, most of the time the issue is may be a misconfigured hardware inventory MOF file, configuration.mof, on your primary site. In this case, the Hardware Inventory Action was missing on some of the Primary site Server as shown in the following figure. Also looked in %systemroot%\system32\wbem\logs --> mofcomp.log file, it was showing  following error Error Number: 0x80041026, Facility: WMI In this case the MOF file it was compiling was correct, but somehow from the log file it was showing that there is some issue with WMI. As per the above error, while compiling the mof file, the a ttempt was made to delete or modify a class that has instances in WMI . But anyway it was not happening. Further we compared the sms_def.mof file objects with the WMI & found that one additional customized entry in WMI. On further investigation we found that earlier, some day’s back one
Read more

Description = "User \"Domain\\SCCMAdmin2\" does not have permissions to grant rights on this instance."; ErrorCode = 1112017920;

The domain user account which had full Security rights in SCCM console, if got disabled & your new domain account is not having equivalent full rights. Then how will you access SCCM objects or delgate access to other user accounts? Security rights provide the capability to define and refine the level of access that users have when working with configuration manager objects. This gives you the ability to delegate specific tasks to specific groups of users. In my environment SCCM 2007 was installed by domain admin account "domain\SCCMAdmin1" on Primary site server. Domain\SCCMAdmin1 account has full access on all instances. As employee left the organization, this user account got disabled. Then we created another domain admin account "domain\SCCMAdmin2", Now if anyone will try to copy permissions of "domain\SCCMAdmin1" to "domain\SCCMAdmin2", definately it will give following error Errors ConfigMgr Error Object: instance of SMS_Extende
Read more