This action will install SCCM client from scratch by running ccmsetup.exe. The UNC path to ccmsetup.exe must be defined either in config.ini (ccmsetupPath) or entered in “Client Install Configuration” form that is shown right before executing the action. Setup parameters can also be either defined in configuration file (ccmsetupParameters) or in GUI.

The “Client Installation Configuration” form will allow configuring most common ccmsetup.exe and client.msi properties by using HTML controls. The ccmsetup.exe command-line string is automatically updated according the control values. The automatic updating of the command-line string can also be disabled by unchecking “GUI” checkbox next to the command-line textbox. All controls are context sensitive (eg BITS priority can only be set if there’s at least one BITS server defined in the source list). Controls also know the default values and properties with default values are not included in command-line. All of the intelligence has been set up according this TechNet article: http://technet.microsoft.com/en-us/library/bb680980.aspx

image

The configuration can be saved in config.ini “ccmsetupParameters” parameter by clicking “Save this configuration as default” button. This will make sure that the same settings are active next time when SCCM CAT is run.

Once the configuration is ready, click on “Start client installation” button to initiate the action on remote computers in target list. The ccmsetup.exe command line is scheduled to start after 1 minute on remote computer. This way it is run as LOCAL SYSTEM. SCCM CAT only schedules the installation but doesn’t give any feedback about the results.

The network share where the defined ccmsetup.exe UNC path is pointing should allow read access to domain computers as the installations on clients side are initiated by LOCAL SYSTEM accounts. When providing the default UNC path to client files such as \\siteserver\SMS_sitecode\client then consider that “SMS_Sitecode” share by default doesn’t allow anyone but members of local administrators and site system connection groups. Therefore, when using the default client installation source folder, I recommend sharing the “Client” folder itself and granting read rights to “Domain Computers” in share permissions and also in NTFS security.

Last edited Nov 15, 2011 at 8:28 AM by pr3m, version 4

Comments

No comments yet.