MobileClient.tcf – will contain the Client installation property such as MP, cache size info and other info. ccmsetup.exe – will further be executed at client side for installation. Once Admin$ share is connected, 2 client installation files are copied under c:\windows\ccmsetup.
You can see that SCCM server is trying to connect to Admin$ share of workstation (ie c:\windows) Open ccm.log located under d:\Program Files\Microsoft Configuration Manager\logs. Click on tab “Client Upgrade” and select “Upgrade all clients in the hierarchy using production client” Verify Client push is working (at Server Side) through ccm.log Specify Hierarchy Settings for Client Upgrade With Site selected under “Site Configuration”, select “Hierarchy Settings” on Ribbon bar to open properties. Check the box “Enable automatic site-wide client push installation Under System types, Servers & Workstations are selected while “Configuration Manager site system Servers” is not selected as I don’t wan’t to push the client on SCCM Server.Ĭlick on tab “Accounts”, we need to specify Client Push account here, this account should be part of Local Admin Group account on systems where we are pushing the Client install.
We are going to enable to enable to client push so that any new client which is part of Domain will get client install automatically. Client Push Installation SettingĬlick on “Client Installation Settings” & select Client Push Installation
For this purpose, I am using svc-sccmadmin which is having admin rights. Select the Account which should have access to content on Distribution Points. Under “Software Distribution Component” properties, select tab “ Network Access Account” and select “Specify the account that accesses network locations” and click on burst icon.