Connecting and Basics
In the Client: field, input a target client name. This can be a name or an IP address. Click "Connected" to initiate a connection to the target. If successful, the status bar (at the bottom) will indicate a success message. Additionally, some information about the client will be automatically populated in the Settings and Values in the middle.
The pulldown Client Actions exposes several client actions which can be remotely initiated once a connection has been made. Some client actions are only available to a Configuration Manager (SCCM) Client. These are in a sub-menu at the bottom.
The pulldown Tools offers by default 3 external tools, Cmd Prompt, CompMgmt, and MSTSC. You can customize the Tools pull down with your own applications. An example of how to do so is here: http://myitforum.com/cs2/blogs/rickym61/archive/2009/01/24/128441.aspx
On the far right is the pull down Options. If you work in an environment where you have a production ID (used for Outlook, document editing, etc.) and a Technician ID (used for troubleshooting), under Options is where you would de-select "integrated authentication", and provide an alternate user id and password to use when targetting the client you input in the Client Field. Additionally, if you work in a multi-domain environment, using an alternate user ID may be useful to target clients in other domains.
Register/Unregister Console Extension
In %temp%, a log file of the actions taken are recorded, unless logging is disabled. If you wish to change the defaults for logging, presuming you installed using the MSI, edit %program files%\SCCM Tools\SCCM Client Center\SMSCliCtrV2.exe.config using Notepad. Search for "Logging_Enabled"; you can modify whether logging is on or off by default, the log path, and the LogLevel.
In the lower-left hand corner are several options: Running Executions, Event Monitor, Inventory Actions, Advertisements, and Agent Actions. You can add or remove these options by clicking on the double >>
In the >> are "Show Fewer Buttons", or Add or Remove Buttons.
If you do not have Client Center open to see the fields, use this graphic: ClientCenter Agent Actions
If you do have Client Center open, select the Navigation pane "Agent Actions" in the lower left.
There are several tabs on Agent Actions Pane.
tab contains several settings and values. When you initially connect to a client, some of those values will be automatically populated by the initial connection. For additional values, you can click on the magnifying glass to query the client. If a setting has the potential to be changed there will be a save button next to the magnifying glass. If applicable, a setting may also be "reset to defaults", or if the setting is a remote folder, presuming admin$ is accessible, optionally you can remotely open that folder. In the case of the SMS GUID, at the next service restart you can request a new GUID. (Restart the agent from the Running Executions pane, Services tab)
tab. Click on "List Components" to see which components are installed and enabled by Site Policies and which components might have been modified with a "Local Policy Override". Local Policy Overrides can be set or removed by clicking on a policy, and using either "disable component" or "Remove Local Policy". After using Disable component or Remove Local Policy, click on List Components to refresh the list.
Cache tab. Similar to the Actions tab, query or modify Cache settings. You could also browse to the cache folder, or use the recycle bin icon to clear cache. Click on "Get List" to view cached packages.
Several options for troubleshooting are available. Cleanup Message Queue would be used when troubleshooting an MP, where 'failed to delete message queue' might appear in mp logs; or used on a client when a disk cloning/OSD situation, where a new client may try to download orphaned policies. Delete SMS Certficates ; for an explanation of certificates, see this: http://technet.microsoft.com/en-us/library/cc179731.aspx. In some situations, you might need to have a client get a new certificate. Uninstall, Repair, Install Uninstall and Repair are obvious. For install, browse to select a location for ccmsetup.exe which is accessible to the client to install. Parameters may be modified at the time. Alternatively, if you expect to use this feature often or provide CliCtr to other technicians and want the same settings for consistency, presuming you've installed with the MSI, edit %program files%\SCCM Tools\SCCM Client Center\SMSCliCtrV2.exe.config using Notepad. Seach for CCMCommand to change the value for ccmsetup.exe, to point to (for example) \\ your server name\ccmclient\ccmsetup.exe In CCMInstallationProperties, in that value you could modify the parameters for your environment.
Repair WMI will remotely attempt a repair. If you choose WMIRepair, you can click on the folder icon to access the log file from the WMIRepair action. Delete root\ccm; root\ccm is the namespace utilized by the SMS/ConfigMgr client. If you delete root\ccm, it is recommended to Repair the SMS Advanced Client (or uninstall/install) to recreate the defaults. Recreate Repository; if a WMIRepair was unsuccessful, recreating the repository is another option. In this author's option, recreating the repository would be the last-ditch attempt to remotely fix a computer. If your next step was either reimage or recreate repository, recreate the repository, but you expect that a reimage would be needed if unsuccessful. Microsoft does not recommend recreating the repository. They recommend running WMIDIAG.
Logoff / Restart / Shutdown
Client Health Check
Start Client Health Check to check basic client health. For the Check titled "AdvCheck", you may need to select a valid AdvertisementID/PackageID/Package version which is correct for your environment, which would indicate a client has correctly run that advertisement. Once that is determined, edit the file %programfiles%\Common Files\SMSCliCtr\Client_Health.dll.xml, and modify the value to match your ad/package/package ver
If you do not have Client Center open to see the fields, use this graphic: Advertisements
If you do have Client Center open, select the Navigation pane "Advertisements" in the lower left.
On the initial tab, you can Show Adv to list all advertisement policies. When you highlight a particular advertisement and select ReRun Adv, if the advertisement is a mandatory advertisement, the advert will be queued to rerun. A rerun may not immediately occur; for example, if conditions like "only when no user logged in" or a Maintenance Window are applicable. When all conditions are met, the advert will rerun. Import Policies would be used to import a local policy advertisement.
Show the schedules of Advertisements.
View when a Package/Program last ran, and if successful. If failed, failure code is available. On the far right, pull-down Options to select whether history should be obtained for remote WMI, or remote Registry.
Show ServiceWindow to display any existing Service Windows (also known as Maintenance Windows). You can also Add ServiceWindow... to interactively add a 1 time specific service window for the next xx minutes for the next xx hours. Delete to delete a Service Window.
If you do not have Client Center open to see the fields, use this graphic: Inventory Actions
If you do have Client Center open, select the Navigation pane "Inventory Actions" in the lower left
Inventory Actions (HW delta/full, SW delta/Full, DDR, Collect ID MIFs) are available at any time from the Client Actions pull down. Since HW Inventory is based on WMI, using the Inventory Actions pane, you can view interactively the WMI Classes that would be gathered by a hinv by selecting SMS Inventory. Under AdHoc Inventory select other common details, like last boot time, OS install date, last ddr (heartbeat), last HW/SW inv. Within Inventory Class are other win32 classes. Some may or may not be available on a particular system. For example, 'win32_localadmins' may only be available if you are using a HWInv optional MOF extension to create that namespace.
Get AddRemove Programs to list applications and patches. Uninstall/Repair may be used selectively to uninstall or Repair an application. NOTE: not all applications can be remotely uninstalled. If it is available, the options will not be greyed out.
Security Patch State
Show Patch State to list patch status, including known missing patches. Right click any particular patch to show KB Details, or show bulletin details. Copy Table to Clipboard to copy to clipboard to paste into another application if you need to copy/paste the results elsewhere. You can also open the WindowsUpdate.log, since the WindowsUpdate.log is important to patching, but it is not in the ConfigMgr/SMS client's normal Log folder, a new admin may not realize the log file is in %windir%, and can access the log file here. On the far right Clear Patch List to clear the list.
If you are deeply troubleshooting a specific client, you can enable event monitoring of specific types of events.
If you do not have Client Center open to see the fields, use this graphic: Running Executions
If you do have Client Center open, select the Navigation pane "Running Executions" in the lower left
Show Running Jobs to list jobs in queue. You will also be able to see if a job is waiting for something (content, etc.) Monitoring can be enabled to automatically refresh the list. Kill Running Job would be used if a client were running a particular mis behaving job, and you needed to interactively kill the job prior to the scheduled timeout period, when it would kill itself.
Show Processes to view processes. Right-click to "kill" a process if desired. Create Process... to remotely launch a process. This is only this author's opinion, but if you need to remotely launch something, I recommend using PSExec. Monitoring can be enabled to automatically refresh.
Show all Services to view services. Right-click a service to stop/start/restart or modify startup behavior. Show SMS related services to only display those services specifc to SMS/ConfigMgr client troubleshooting.
The SMSCliCtrV2.exe.config file
The config file has been mentioned elsewhere in this wiki. You could customize additional settings for your environment.
PingRequired True/False. In some environments, ping is not allowed. Change to False.
InvClasses contains the wmi classes as listed in the pull-down on the Inventory Actions pane. If you have additional WMI classes you would like to see interactively, you could add them there, or eliminate ones you don't have. For example, root\cimv2:Win32ComputerSystemProduct:IdentifyingNumber might be useful to see model of specific vendors' model types.
CustCommand/CustArguments you could add additional actions to the Tools menu (see PSexec sample above)
SMSServices contains the list of services which will be displayed when selecting SMS Services from Running Executions, Services, SMSServices. It may be that you determine that the services relating to your Anti-malware applications would be useful to have listed without having to list All Services. You could add those services to that list.
PluginPath If you are a developer for ClientCenter commercial plugins, this is the path where those plugins will be expected to be installed. Depending upon the developer or the environment, this setting may need to be changed by the developer.