Sccm Client Reinstall

SCCM Client Installation
Process & Troubleshooting Guide

Quick Troubleshooting
If the SCCM client seems already to be installed on a system (“Configuration Manager” and “Run Advertised Programs” icons are visible in the control panel), but the system still shows up in the console with “no client installed”, you can first try to de- and reinstall it manually.
There are several ways howyou can do this - here is one approach:
Deinstallation
1. Open a command prompt

2. Navigate to following path:
32bit: %windir%\system32\ccmsetup\ {6A438387-0FF9-4620-947E-39470FB1E2E5}
64bit: %windir%\ SysWOW64\ccmsetup\ {6A438387-0FF9-4620-947E-39470FB1E2E5}
(Please note that the number in the curly bracket varies for each system)

3. Type and run the following command:msiexec /x client.msi (hit the “Yes” button on the upcoming window)

4. Wait for the deinstallation to complete and restart the system
Re-Installation
5. Run the “ccmsetup.exe” which should be located in the following folder on the client system:
32bit: %windir%\system32\ccmsetup
64bit: %windir%\ SysWOW64\ccmsetup

6. Wait for the installation to complete

Now all you can do is waitfor a while and check again if the client is now reporting it´s correct status to the SCCM database.
Please note:
Even though this “quick solution” did solve many problems with SCCM clients in the past, it does not always help.
For this please find below a detailed description of the client installation process and how to troubleshoot it …

Step-by-Step Troubleshooting
This step-by-steptroubleshooting follows the SCCM client installation process in detail and lists the requirements for each of the installation steps. A more detailed version of this can be found here:
http://support.microsoft.com/kb/925282/en-us

Introduction
The installation of the SCCM client consists of the following 3 phases:
1. Pre-installation
SCCM connects to the target client and verifies theclient's operating system and client information. The client installation source files are copied and the setup process downloads the SCCM core components to the client computer.

2. Installation
The SCCM client copies the installation files from the SCCM server and starts the setup.

3. Post-Installation
After the setup program is complete, the SCCM client obtains a site assignment,sends the heartbeat discovery information to the SCCM server and retrieves policies and software package assignments.
This “step-by-step” guide will show you how to troubleshoot issues with the SCCM client following the 3 phases. It describes what SCCM is trying to do at which time and what you can do to check if all requirements are met for each step.

Pre-Installation Phase
First SCCMdiscovers the client computer and then generates a client configuration request (CCR) file on the SCCM server:
1. In Active Directory check if the workstation object is:
a. Present
b. Enabled
c. Located in the OU site structure

2. Check if workstation name can be resolved by DNS/WINS
(Simply ping the computer name and check if you get back an IP address)

3. Check ifsystem is reachable by ping of the FQDN
(e.g.: ping BER001234.eu.pxl.int)

Please note:
If a workstation does not deliver back any IP address it is probably orphaned. In this case you can:
a) Disable the AD workstation object and move it in the respective “Orphaned Workstations” OU
b) Delete the SCCM database entry for that workstation
Then SCCM connects to the ADMIN$ share on the client(based on the information in the CCR file):
(Can be followed here: \\<SCCCM site server>\d$\ConfigManager\Logs\ccm.log)
4. Check if you can access the system´s admin share (e.g.: \\BER001234\admin$)
(Please note: If you cannot access this share you cannot proceed with the next steps. You have to physically go to the system and recreate the shares.)

5. Check if both AD groups...