SCCM Client Installation

and Troubleshooting
Author Akshar Kapaganty, 5045391

20 January 2019
© Atos | Syntel - For internal use
Learning Objectives

▶ By the end of the module, participants will be able to learn as follows:

▶ To Install/Uninstall SCCM Agent and troubleshooting the different communication issues.
▶ Required Services and there importance for SCCM Agent.
▶ Reading Log file for troubleshooting.
▶ Different components and Actions of SCCM Agent.
▶ Windows Management Instrumentation (WMI) and their basics.
▶ SCCM Remote Control Troubleshooting.

2 | © Atos | Syntel - For internal use

SCCM Agent Installation Methods

▶ There are different methods of SCCM Agent installation and here in this training material
will be concentrating on Manual installation.
Client Installation Method Description
Automatically Upgrade Use this method to automatically upgrade client when it identifies that a client that is assigned to the site is below a
version that you specify. This Configuration is already set in our SCCM Environment

Client push installation Use this method to automatically install the client to assigned resources and to manually install the client to resources
that are not assigned, This method we are using as and when require.

Software update point installation Used to install the client using the Configuration Manager software updates feature(Patching).

Group Policy installation Used to install the client using Windows Group Policy.
Logon script installation Used to install the client by means of a logon script

Manual installation Used to manually install the client software

Upgrade installation Uses Configuration Manager application management to upgrade Configuration Manager clients to a newer version.

Client Imaging Used to pre-stage the client installation in an operating system image. All Atos Syntel Desktops/Laptops will consist of
SCCM Client on it except Servers.

3 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation

▶ There are several scenarios where we would need to install/Uninstall the SCCM Client manually.
▶ These are Mandate to install SCCM Agent , admin$, Firewall Should disabled , Administrator rights, Communication
to SCCM Server(XXXXXX.abc.com).
▶ Go to path \\XX.XXX.XX.XX\patches\SCCM Agent and Copy the folder Client and paste on any location. In Below
example we have copied on C drive and executed with specific switches.
Switches :-
SMSSITECODE= This Client.msi property specifies that the client tries to locate the Configuration Manager site code to use.
MP= Management Point where Client will get the required installation files
FSP = This Client.msi property specifies that the fallback status point named SMSFP01 is used to receive state messages
sent from the client computer.

▶ MPSERVER: XXXXXX.abc.com
▶ FSPSERVER: XXXXXX.abc.com
▶ ABC: site code of Primary SCCM Server.
▶ Syntelorg.com: Domain name

4 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation

▶ With help of Command prompt we are going to install the SCCM Agent.
▶ Start > Search for CMD > Right click Command Prompt and Run as Administrator.

5 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation

▶ C:\client\ccmsetup.exe MP= XXXXXX.abc.com SMSMP= XXXXXX.abc.com SMSSITECODE=abc FSP=

XXXXXX.abc.com Copy above command in CMD and enter. Now client installation starts progress can be viewed in
log file(C:\Windows\ccmsetup\logs\ccmsetup.log) step by step.

6 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation

▶ Below is the snippet of CCMsetup.log to check whether agent installation is successful or not.
▶ C:\windows\ we can see three folders belongs to SCCM Agent CCM, CCMSetup, CCMCache

7 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation
Installation error codes

▶ Installation Error Codes:

▶ 2 – The system cannot find the file specified.
▶ 5 – Access denied.
▶ 7- Reboot require for machine
▶ 52 – You were not connected because a duplicate name exists on the network. Make sure there is not a duplicate name in DNS and that 2 machines don’t have the same IP in DNS.
▶ 53 – Unable to locate – http://support.microsoft.com/kb/920852 – cannot connect to admin$ – Computer Browser not started – add File/print sharing to Exceptions in Firewall – turn file and print on.
▶ 58 – The specified server cannot perform The requested operation
▶ 64 – The specified network name is no longer available. Source: Windows
▶ 67 – network name cannot be found.
86 – network password is not correct? Machine Name <> resolved name.
▶ 112 – Not enough disk space
▶ 1003 – Cannot complete this function.
▶ 1053 – The service did not respond to the start or control request in a timely fashion.
▶ 1068 – The dependency service or group failed to start
▶ 1130 – Not enough server storage is available to process this command. Source: Windows
▶ 1203 – The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator.
▶ 1208 – An extended error has occurred. Source: Windows
▶ 1396 – Logon Failure: The target account name is incorrect. (NBTSTAT -a reverse lookup, duplicate IP address)
▶ 1450 – Insufficient system resources exist to complete the requested service. Source: Windows
▶ 2147749889 – Generic WMI failure (Broken WMI)
▶ 2147749890 – not found – Source: Windows Management (WMI) – try repair WMI
▶ 2147749904 – Invalid class – Source: Windows Management (WMI)
▶ 2147749908 – Initialization failure – Source: Windows Management (WMI)
▶ 2147942405 – Access is Denied (Firewall rule? / MacAfee-HIPS?)
▶ 2147944122 – The RPC server is unavailable. (Dcom is miss-configured for security . http://support.microsoft.com/kb/899965 )
▶ 2148007941 – Server Execution Failed
.

8 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation
Checking Agent installation and required components

- Open Control panel to check SCCM Agent(Configuration Manager) installed or not.

- Double click on Configuration manager to open the properties and check the required data is populated for healthy agent installation.
- Assigned Management Point should be XXXXXX.abc.com.
- In Some cases in Actions tab we could see only 2 actions 1. Machine Policy And 2.User Policy try to run both and wait for 10mins to
populate all actions list below.

9 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation
Checking Required Services are running or not

- Open Services.msc to check whether required services are up and running or not.
- Points to remember for successful communication with SCCM Server SMS Agent Host should up and running.
- Bits ( Background Intelligent Transfer Service) is not required to run but its should present.

10 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation
Checking WMI is working as expected or not?

- Open Run and type WBEMTEST to check the WMI(Windows Management Instrumentation) connectivity.
- WMI is nothing but windows internal Data base like ( Oracle, SQL, MSSQL).
- WMI query language is called WQL ( Windows Query Language).
Connect and provide the Namespace ( Nothing But Database) in our case it is CCM, If its connected successfully means DB is working as
expected. You can exit.

11 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation
Logs files (C:\Windows\CCM\Logs\)

- If you feel there is problem with agent communication and not able to see all the actions mentioned in slide 9.
- Then look for the log file clientlocation.log from the path (C:\Windows\CCM\Logs\ClientLocation.log) and check its properly
populating the information like below.

Current AD forest name is SYNTELORG.COM, domain name is SYNTELORG.COM ClientLocation 1/21/2019 3:28:36 PM 7124 (0x1BD4)
Domain joined client is in Intranet ClientLocation 1/21/2019 3:28:36 PM 7124 (0x1BD4)
Assigning client to site 'SNT' ClientLocation 1/21/2019 3:29:01 PM 24476 (0x5F9C)
Getting Assigned Site ClientLocation 1/21/2019 3:29:01 PM 24476 (0x5F9C)
Client is currently not assigned to any site ClientLocation 1/21/2019 3:29:01 PM 24476 (0x5F9C)
Removing client site assignments ClientLocation 1/21/2019 3:29:01 PM 24476 (0x5F9C)
Removed pending site assignment to 'SNT' ClientLocation 1/21/2019 3:29:01 PM 24476 (0x5F9C)
Raising event:
instance of CCM_RemoteClient_Reassigned
{
DateTime = "20190121095901.334000+000";
LastAssignedSite = "";
NewAssignedSite = "SNT";
ProcessID = 26424;
ThreadID = 24476;
};
ClientLocation 1/21/2019 3:29:01 PM 24476 (0x5F9C)
Client is now successfully assigned to site 'SNT' ClientLocation 1/21/2019 3:29:01 PM 24476 (0x5F9C)
Setting current Management Point as VPS2CSCCMPRI01.SYNTELORG.COM ClientLocation 1/21/2019 3:29:01 PM 24476 (0x5F9C)

12 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation
Logs files (C:\Windows\CCM\Logs\)

- If you found client is not assigned properly to the MP check below links whether client able to communicate or not.
- If its communicating try to uninstall and Install the SCCM Agent to fix the issues.
- If its not communicating check the all requirements are properly met or not like stated earlier.

▶ http:// XXXXXX.abc.com/sms_mp/.sms_aut?mplist
▶ http:// XXXXXX.abc.com /sms_mp/.sms_aut?mpcert
▶ http:// XXXXXX.abc.com /sms_mp/.sms_aut?MPKEYINFORMATION

13 | © Atos | Syntel - For internal use

SCCM Agent Manual Installation
Uninstallation of SCCM Agent

- Using CCMSetup.exe we can uninstall the SCCM Agent. Please follow below.
- Command Ccmsetup.exe /uninstall
- Whether the execution is completed or not we can check from the path (C:\windows\ccmsetup\log\ccmsetup.log)

14 | © Atos | Syntel - For internal use

SCCM Remote Control Troubleshooting

- Make sure below service is up and running.

- Check the log file (C:\Windows\CCM\log\CmRcService.log) for further troubleshooting’s. By Default No remote control access is provide to
any Team. With Proper ticket and justification from Manager will have the access. If access is not there below error can be visible in the log
files.
====== Starting service CmRcService ====== CmRcService 1/21/2019 4:37:58 PM 17788 (0x457C)
Restoring Windows hardware acceleration settings. CmRcService 1/21/2019 4:37:58 PM 27584 (0x6BC0)
Registering Media Disconnect WMI Event was done successfully CmRcService 1/21/2019 4:37:59 PM 27584 (0x6BC0)
Configuring listeners on TCP port 2701. CmRcService 1/21/2019 4:37:59 PM 27584 (0x6BC0)
Binding to Ip v6 protocol success CmRcService 1/21/2019 4:37:59 PM 27584 (0x6BC0)
Binding to Ip v4 protocol success CmRcService 1/21/2019 4:37:59 PM 27584 (0x6BC0)
=== Listening for remote control requests === CmRcService 1/21/2019 4:37:59 PM 27584 (0x6BC0)
======> A connection has been established. (OnConnectionEstablished) CmRcService 1/21/2019 4:39:57 PM 8848 (0x2290)
Ready to start the security handshake. CmRcService 1/21/2019 4:39:57 PM 8848 (0x2290)
=== Starting security handshake === CmRcService 1/21/2019 4:39:57 PM 8848 (0x2290)
=== Security handshake completed [0x00000000] === CmRcService 1/21/2019 4:39:57 PM 8848 (0x2290)
The viewer is a member of the Local Administrators group who are allowed to use Remote control. CmRcService 1/21/2019 4:39:57 PM 8848 (0x2290)
The user(SYNTELORG\AK5045391) is not authorized for Remote Control CmRcService 1/21/2019 4:39:57 PM 8848 (0x2290)
Session denied: The remote user is not authorized to perform remote control on this system. CmRcService 1/21/2019 4:39:57 PM 8848 (0x2290)

15 | © Atos | Syntel - For internal use

References

▶ https://blogs.technet.microsoft.com/smartinez/2013/09/27/top-3-configmgr-2012-client-
installation-methods/
▶ https://docs.microsoft.com/en-us/sccm/core/clients/manage/remote-control/remotely-
administer-a-windows-client-computer
▶ https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/log-files
▶ https://docs.microsoft.com/en-us/sccm/core/clients/deploy/deploy-clients-to-windows-
computers

16 | © Atos | Syntel - For internal use

Thank You
For more information please contact:
Internal 022 333733
Mobile +91 9949470591
[email protected]
[email protected]

Atos, the Atos logo, Atos Codex, Atos Consulting, Atos Syntel, Atos Worldgrid, Bull, Canopy, equensWorldline,
Unify, Worldline and Zero Email are registered trademarks of the Atos group. September 2018. © 2018 Atos.
Confidential information owned by Atos, to be used by the recipient only. This document, or any part of it, may not
be reproduced, copied, circulated and/or distributed nor quoted without prior written approval from Atos.