Install ConfigMgr Client Using Client Push Installation Method SCCM

9
ConfigMgr Client Push Installation

Let’s understand the process of the ConfigMgr Client Push Installation Method. The installation of the client is one of the important parts of the ConfigMgr manager environment. So, client push is the easiest method to install the client.

As you know, the client installation strategy is very important for every organization. The following are the client installation methods. But, I prefer the Logon script installation method using Jason Sandys script.

  • Client push installation (From SCCM Console)
  • Software update point-based installation (GPO GPEDIT.MSC)
  • Group policy installation (GPO – GPEDIT.MSC)
  • Using Microsoft Intune (Intune/Azure Console)
  • Package and program installation (SCCM Console)
  • OSD Task Sequence (SCCM Console)
  • Logon script installation (AD)
  • Workgroup computers (Manual)
  • Internet-based client management (SCCM/Manually ?)
  • Provision client installation properties (GPO)
  • Manual installation (Manual via command prompt?)

Personally, I like the Client Push Installation method and that is what we are going to learn through this post. Let’s jump into the step by step guide to ConfigMgr Client push installation method.

Requirements

  • Admin$ share should present
  • Admin$ SMB access to Windows 10 devices.
  • Client Push Account should have administrator access on Windows 10 client device
    • Or the SCCM site server should be part of the Administrators group on the Windows 10 device.
  • Devices should be discovered and Device record should be available in SCCM console.
  • Make sure Client Push firewall ports and defender settings are ok before the start of the following process.
  • Connectivity to Management Point.
DescriptionUDPTCP
SMB between the site server and the client computer.445
RPC endpoint mapper between the site server and the client computer.135135
RPC dynamic ports between the site server and the client computer.49152-65535
Hypertext Transfer Protocol (HTTP) from the client computer to a management point when the connection is over HTTP.80/443
Client Push Firewall Ports

NOTE! – Configuration Manager tries to install the client on all discovered resources. It retries any failures for up to seven days.

Step #1 – Initiate Client Install

  • Right-click on one of the devices or device collections. Install ConfigMgr Client Using ClientPush Installation Method.
  • Select Install Client.
Install ConfigMgr Client Using Client Push Installation Method SCCM
Install ConfigMgr Client Using Client Push Installation Method SCCM
  • Click the Next button.
Client Push Installation Method Guide | SCCM
SCCM Client Push Installation Method Guide | ConfigMgr
  • Select the two options below to install the client on Windows 10 device.
  • Enable the option called Always install SCCM client.
    • Repair or upgrade it if the client is already installed.
    • Uninstall the SCCM client before installing its option is to have clean installation of the client.
ConfigMgr Client Push Installation Method Guide | SCCM
ConfigMgr Client Push Installation Method Guide | SCCM
  • Click Next, Next, and Close to complete the ConfigMgr Client Push Installation Wizard.
Client Push Installation Method Guide | SCCM
SCCM Client Push Installation Method Guide | ConfigMgr

Server Side Log CCM.log

  • Let’s check CCM.log from site server F:\Program Files\Microsoft Configuration Manager\Logs.
  • The following are the important log file entries.
    • Search for the following entry in ccm.log Started service “ccmsetup” on machine “HTMDWin10.htmd.com”.
    • Once you have this entry for the client then everything is OK from the server-side.
Install ConfigMgr Client Using Client Push Installation Method SCCM
Install ConfigMgr Client Using Client Push Installation Method SCCM
---> Trying each entry in the SMS Client Remote Installation account list
---> Warning: no remote client installation account found
---> Attempting to connect to administrative share '\HTMDWin10.htmd.com\admin$' using machine account.
---> Connected to administrative share on machine HTMDWin10.htmd.com
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0xFFFF)
---> Attempting to make IPC connection to share <\HTMDWin10.htmd.com\IPC$> 
---> Searching for SMSClientInstall.* under '\HTMDWin10.htmd.com\admin$\'
---> System OS version string "10.0.19041" converted to 10.00
---> Unable to connect to WMI (root\ccm) on remote machine "HTMDWin10.htmd.com", error = 0x8004100e. $$<06-27-2020 14:09:29.685+00>
---> Creating \ VerifyingCopying existence of destination directory \HTMDWin10.htmd.com\admin$\ccmsetup.~
---> Copying client files to \HTMDWin10.htmd.com\admin$\ccmsetup.~ 
---> Copying file "F:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf"
---> Copying file "F:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe"
---> Created service "ccmsetup" on machine "HTMDWin10.htmd.com".
Submitted request successfully
Getting a new request from queue "Incoming" after 100 millisecond delay. \Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). 
---> Started service "ccmsetup" on machine "HTMDWin10.htmd.com".
---> Deleting SMS Client Install Lock File '\HTMDWin10.htmd.com\admin$\SMSClientInstall.HT1
Execute query exec [sp_CP_SetLastErrorCode]
---> Completed request "2097152002", machine name "HTMDWIN10".
Deleted request "2097152002", machine name "HTMDWIN10"
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152002
Execute query exec [sp_CP_SetLatest] 2097152002

Client-Side Log File – CCMSetup.Log & Client.MSI

  • Let’s check the Log Files from the client-side related to the Client Push method.
    • Go to C:\Windows\ccmsetup\Logs
    • ccmsetup.log
    • Client.Msi.log to confirm the installation status
      • Make sure there is NO entry called “Return Value 3“.
Product: Configuration Manager Client -- Installation operation completed successfully.
Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.8968.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.
Install ConfigMgr Client Using Client Push Installation Method SCCM
Install ConfigMgr Client Using Client Push Installation Method SCCM

Results – Client Push Installation

  • The client got installed and it showing as online in Configuration Manager console.
  • The ConfigMgr client push installation was successful.
ConfigMgr Client Push Installation Method Guide | SCCM
ConfigMgr Client Push Installation Method Guide | SCCM

Resources

Video Recording

9 COMMENTS

  1. Anoop,

    Love the blogs, really informative. QUick question, when running client upgrades, we still need the client push account(computer or user) to do the upgrade via push right? I know we can deploy via Software distribution, but to do it in an automated fashion, my assumption is that it’s the same process for upgrade as it is for clint push, meaning we need local admin rights?

    Thanks

  2. Hi Anoop, I am struggling to find out why my account is getting locked on our 2010 SCCM even after I removed my account. I rebooted it after that and still when I check the security logs on the DC, it is still saying I was locked from the sccm server on an hourly basis. Not sure what to do at this point, and I know I have to upgrade but we are very limited with our budget for years now.

  3. Oh, I think i figured it out. It was still using my credentials to push the client. Thanks for your post, it gave me an idea where to look further.

  4. Hi. Very clear style and detailed. Thank you. Question: I have sccm 2012 environment. unstable. I am planning fresh install of current branch 2002. How to handle old clients? Will the 2002 client push option properly uninstall old and install new?

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.