Skip to main content

SCCM How to deploy a client

Overview

Within Config manager the client is within the "All Systems" collection however, under the column 'Client' the answer is NO.

Stage 1

First thing to do is click on "Client installation methods"  located under Site Settings.  Then right click on "Client Push Installation" and select properties.  On the general tab if you click on "Enable Client Push Installation to assigned resources" any system discovered throug AD (or other) will have a client automatically installed.  Depending on you environment consider this tick box.

On the Accounts tab you must input account credentials that will have administrative access to the admin$ share of the client system.  The account that can access desktops may be different to domain controllers so you can put multiple accounts in here and it will try them in order.

On the Client tab you can specify the Site code.  It is also possible to define SMS cache size rather than the 5gb default. See Microsoft for additional properties http://technet.microsoft.com/en-us/library/bb680980.aspx

Client agents under Site Settings will list the agents that will be pushed out with the SCCM client.
The computer client agent is critical.  On the properties tab is important you have set a Network access account.  This agent will connect back to the SCCM server looking installation folders so it must have suitable access delegated.

Stage 2

Now SCCM is configure correctly and agents have the appropriate account setup for connection.  Right click the system without the client, Then "Install Client".  This will bring up a wizard, i like to select include only clients in this site's boundaries and Always install (repair ...). Finish the wizard.

Stage 3

Check the log files for errors! c:\Prgram Files\Microsoft Configuration Manager\Logs

Using Trace32 open the CCM log on the SCCM server.  Which will show the client deployment process so we can see if it is succeeding.



On the client system you can open the CCMSetup log file to monitor the client installation (this can take a while to complete (located admin$\system32\ccmsetup\ccmsetup.log)

On the client there are three key log to know that your client install was successful (located dmin$\system32\ccm\logs)

"Clientlocation.log" confirm the current management point is correct.
"Location services.log" Confirm the current AD site of machine is "" correct
"Execmgr.log"  This log reads policy from the management point. So advertisements creates a policy which the client reads .  "Software distribution agent was enabled" will not be in red.

Stage 4

Within the control panel there will now be three additional icons.  The Configuration Manager, Run Advertised Programs, Remote control Properties, and Program Download monitor.

There are two services installed on the client system.
SMS Agent Host
SMS Task Sequence Agent

Comments

Popular posts from this blog

SCCM Unknown computer not able to see Task Sequences after installing Current Branch 1702

Soon after installing SCCM CB 1702 we were unable to see Task Sequences deployed to the unknown collection. This issue was identified as a random system taking the GUID of the 'x64 Unknown Computer (x64 Unknown Computer)' record. As a result it was now a known GUID; as we were only deploying Task Sequences to the Unknown collection none were made available. 'x64 Unknown Computer (x64 Unknown Computer)' record 'x86 Unknown Computer (x86 Unknown Computer)' record To get the GUID of your unknown systems open SQL management studio and run the following command: --Sql Command to list the name and GUID for UnknownSystems record data select ItemKey, Name0,SMS_Unique_Identifier0 from UnknownSystem_DISC Using the returned GUID (SMS_Unique_Identifier0) we can find the hostname that has been assigned the 'x64 Unknown Computer (x64 Unknown Computer)' GUID by running the query below. --x64 Unknown Computers select Name0,SMS_Unique_Identifier0,Decommissioned0 from Sys...

Windows 7 Offline files will not go Online when connected to network

Issue Several laptop users move between networks, domain, home, etc and when they attempt to access DFS shares explorer status is working offline.  The issue only resolves it self after a reboot. Connecting directly to the share works and i am able to ping network resources.  This behavior occurs for VPN users as well. Possible Causes "slow-link mode". In win7 (with default settings) a client will enter slow-link mode if the latency to the server is above 80ms. In slow-link mode all writes are made to the local cache and a background sync only happens every 6 hours.  Depending on your connection the default slow link detection speed is 64,000 bps On client computers running Windows 7 or Windows Server 2008 R2, a shared folder automatically transitions to the slow-link mode if the round-trip latency of the network is greater than 80 milliseconds, or as configured by the "Configure slow-link mode" policy. After transitioning a folder to the slow-link mode, Offline Fil...

SCCM Software Update - Job error 0x80004005 Failed to Add Update Source for WUAgent

SCCM Software Updates - Failed to Add Update Source for WUAgent  Today I have been looking at a range of servers (Server 2008 /R2 2012 /R2) that were failing to communicate with the Software Update Point (SUP) in SCCM and retrieve deployment policy. The UpdateDeployment.log was reporting the Job error 0x80004005 Job error (0x80004005) received for assignment ({af7a48e6-d550-4070-dd9b-ecc234567584}) action UpdatesDeploymentAgent 12/6/2017 10:32:27 AM 2096 (0x0830) The WUAHandler.log  was reporting "Unable to read existing WUA Group Policy object" and "Failed to Add Update Source for WUAgent " Unable to read existing WUA Group Policy object. Error = 0x80004005. WUAHandler 12/6/2017 3:41:00 AM 2828 (0x0B0C) Failed to Add Update Source for WUAgent of type (2) and id ({3AAB6A76-CE2D-4E8A-9F11-123AE69612A1}). Error = 0x80004005. WUAHandler 12/6/2017 11:03:31 AM 2276 (0x08E4) Until the agent can report back to the SUP, SCCM will not be able to summarize Software Update sta...