- Where can I find the various client components?
- Is a reboot required to install the client?
- Help! Computer X has “Client: No” in the console!
- How do we fix failed installs?
- What are the SCCM client distribution methods?
- What is the impact of a client upgrade failing?
- Software cache: C:\Windows\ccmcache
- Log Files: C:\Windows\CCM\Logs — SCCM log file reference
- Software Center: Start Menu / Search for “Software Center (Desktop App)”
- Control Panel Applet: Control Panel\System and Security\Configuration Manager
- For log review, get a copy of “CMTrace.exe”:
Client = Yes in the console means:
- Computer meets Prereqs: WolfTech AD joined, has WolfTech machine certs, in DNS
- Agent installed and has performed first inventory
- Agent contacted Management Point
- Agent has done its first health check
- Collection has updated membership
It is strongly encouraged that the SCCM client install is part of the SCCM imaging task sequence. If a SCCM imaging process is not used, the SCCM client can be installed manually (assuming pre-reqs are met) by opening up an Administrative prompt, and running “\\wolftech.ad.ncsu.edu\files\ncsu\packages\Microsoft-SCCM_Client\Install_Current.cmd”. A reboot is typically not required.
This could be for a number of reasons:
- The dnshostname attribute is not resolvable in DNS. This means the client cannot autoenroll for the machine certificates required for SCCM to function.
- For some reason, the computer has broken client. Verify the certificates are valid, then try a reinstall of the SCCM client.
- In the SCCM Console, you can add a “Last Installation Error” column to help you diagnose installation issues.
- C:\Windows\ccmsetup\*.log for setup related log files. (CMTrace.exe, mentioned above, is useful for log viewing).
The short list:
- Please refer to the Service Now Knowledge Base article KB0015358
The client machine requires an *unexpired* machine cert (certificate issued to the computer from the “NCSU-Computer-Certificate” template) in order to be able to communicate to the SCCM infrastructure.
As of March, 2021, it is expected that the SCCM client is installed via the Windows imaging task sequence. All domain level Windows images will install the client. Any departmental custom Windows images should include the SCCM client install in their task sequence. SCCM is configured to upgrade any earlier versions to the current version as configured in SCCM. As SCCM itself is upgraded, the SCCM core team will determine whether we also perform a client upgrade. These upgrades, both infrastructure and client, will be announced via the activedirectory mailing list.
Manual client upgrades can be performed (assuming pre-reqs are met) by opening up an Administrative prompt on the client machine, and running “\\wolftech.ad.ncsu.edu\files\ncsu\packages\Microsoft-SCCM_Client\Install_Current.cmd”. A reboot is typically not required.
The SCCM agent is about deploying software and patches. If the agent doesn’t get upgraded for some reason, the computer will generally continue functioning as is until an IT person comes along to assist it. If the agent is broken/nonfunctional, then the computer is essentially unmanaged by SCCM at that point. It is nearly impossible for a client upgrade failure to negatively impact the end user with the possible exception of not receiving new software (including monthly security patches).