Manually
Installing the SCCM Client
Note : Fallback status point should be
installed on SCCM server.
Must
have Administrator permissions to the folder to access the client installation
files
This installation method might sound
like a very time-consuming method; however, you will find yourself installing
clients manually for several reasons. You can manually install the client by
running CCMSetup.exe from the site server or from any management point. The file
is located in the Program Files\Microsoft Configuration
Manager\Client folder.
If you prefer the scripty way use:
1.
Copy the client folder from SCCMServer
machine to Client machine
The SCCM 2012 client is stored on your SCCM server (or additional Management
Points) in the Client-folder under SMS_SITECODE
(\\SCCMSERVER\SMS_SITECODE\Client\).You can run the setup using syntax or just simply use the GUI to choose your settings after installation.
2.
Open Cmd prompt using admin rights
3.
Goto the client folder location
4.
Type the following command
ccmsetup.exe /mp:SCCMSERVER /logon SMSSITECODE=AUTO fsp= SCCMSERVERYou can read more about the setup commands at TechNet.
Or
Run ccmsetup.exe, when the client is installed go to Control Panel, press Configuration Manager.
Go to the Site-tab, press Configure Settings to elevate the window and then press Find Site.
Make sure the proper site name shows up and then press OK. The client will now download and apply your client policies.
How to check Client is installed
1. Check The following Logs in location C:\windows\ccmsetup\logs
While
the installation is in progress, you can view the installation program running
within Task Manager or monitor the installation by reading the log files
.
--> Ccmsetup.log— If you
are able to see that the ccmsetup.exe service is created then it clearly
informs us that the server has completed its request to the client and the
client has started installing.
--> ClientIDManagerStartup.log--- you have to get Client is Registered
Also
check the following logs
* CCM.log—Serverside log
* Client.msi.log
2.
Go
to Task Manager --> Processes -->
In Task
Manager you will see ccmsetup.exe
running.
As it completes, you will see ccmsetup.exe
replaced
by the agent host program ccmexec.exe.
3.
Go
to SCCMServer Machine , Open
Configuration Manager-->Assertsand Compliance--> Devices--> Client –YES
NOTE: If Client activity is InActive
Then ,
Goto
Client Machine, open cmd promptàServices.msc --> SMSHostAgent --> restart
then it becomes Active
Client Uninstall
Uninstalling the client is pretty straight forward.Open a command prompt (elevated privileges).
Write: C:\Windows\ccmsetup\ccmsetup.exe /uninstall
Installation Error Codes:
- 2 – The system cannot find the file specified.
- 5 – Access denied.
- 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
No comments:
Post a Comment