Part 13 - SCCM 2012 R2 Installation : Configuring SCCM Primary Site (Accounts)

Previous Post : Part 12 - SCCM 2012 R2 Installation : Configuring SCCM Primary Site (Client Settings)

Configuration of SCCM primary site is a process of preparing the site for various types of deployments like Client push, Application deployment, update deployment, reporting etc. 

Lets start the configuration process by setting up the site for client push installation.

Go to Administrator\Site configuration\sites

Client installation account -

Click on Client installation settings\Client push installation :-

Check if "Enable automatic site-wide client push installation" is disabled, Keep the setting disabled so that you have control over client installation :-

Go to the Accounts Tab, Click the yellow icon & select "New Account":-

 Enter the account details & click on verify :-

Enter a network path to the site & click on test connection :-

Verify if it works :-

Network Access Accounts :-

Click on Configure site components & select Software Distribution :-

Click the yellow icon:-

Click on "New Account" :-

Provide the Network Access account details & click on verify, Add a network path & test the connection :-

Click Ok to end the wizard :-

Important Links:-

Next Post :

SCCM 2012 R2 Installation Series 

Read more about SCCM client push account - 

Microsoft System Center Configuration Manager (SCCM), the "Client Installation Account" refers to the user account that SCCM uses to install the SCCM client software on devices in the network. During the client installation process, the SCCM client installation account requires administrative permissions on the target devices to perform the installation and configuration tasks successfully.

Here are some key points about the Client Installation Account:

1. Privileges: The Client Installation Account should have local administrative privileges on the devices where the SCCM client is being installed. Administrative access is necessary to modify system settings and install software components.

2. Network Access: The account should have network access to the SCCM server and relevant distribution points where the SCCM client installation files are stored. This allows the client installation process to download the necessary files.

3. Assigned during Client Push Installation: When using client push installation, which is one of the methods to deploy the SCCM client to devices automatically, you specify the Client Installation Account in the SCCM console. SCCM uses this account to remotely install the client on targeted devices.

4. Assigned during Client Installation Wizard: If you are manually installing the SCCM client on individual devices using the SCCM Client Installation Wizard, you will need to provide the Client Installation Account credentials during the installation process.

5. Secure Account: Since the Client Installation Account requires administrative permissions, it is essential to ensure that this account is secure and its credentials are not shared widely. Limit access to this account to only authorized SCCM administrators.

6. Client Push Installation Method: SCCM offers multiple methods to deploy the client (manual, GPO-based, software update point, etc.), but the Client Installation Account is commonly used with the Client Push Installation method for automated client deployment.

7. Client Installation Troubleshooting: If there are issues with the client installation, one of the things to check is whether the Client Installation Account has the necessary permissions and network access to perform the installation.

Managing the Client Installation Account is critical to ensure that SCCM clients are installed and configured correctly on the target devices. By using a properly configured account with the appropriate permissions, administrators can streamline the client deployment process and improve the overall management of devices in the SCCM environment.