Client Center for Configuration Manager

The Client Center for Configuration Manager tool is mainly used to remotely deploy software to a specific device. The software available for installation depends on which Active Directory groups the device is currently a member of. 

At this time, Service Desk FTEs and Managed Applications use this software. Users must have a Server Administrator Account.

Note: The Installation and use of the CCCM is restricted to IT Personnel and used almost exclusively by Managed Applications and Service Desk. Users without a Server Administrator account will be unable to use this program.
 

1. Add the Node to the following Active Directory (AD) group via HDUtils:  SW_RZander_Client_Center_for_Configuration_Manager_1.0.6.1_Stabl (“Stabl” is not a typo)
2. After the policies have updated, the Client Center for Configuration Manager should be installed on the machine overnight or during the next install window.
3. If the software does not install automatically
   1. Check the Software Center and install from there.
   2. Alternatively, the software may be advertised following the Advertising Software to a Node procedure below. 
4. If the software is unavailable to be installed via the Software Center or advertised, initiate a policy update for the node. 
   1. .Open an elevated Command Prompt, type gpupdate /force, and press Enter. Restart the computer after the policy has been updated.
      1. Verify the policy update was successful by typing gpresult in the elevated Command Prompt and press Enter

1. Go to passman.shsu.edu
2. Check out Administrator password for the target machine.
3. Search and open CCCM (non-elevated) Note: CCCM doesn't exist you have to type in SCCM
4. Click on the blue button from menu bar at the top-left corner of the application
5. Click on Connection Options enter username as .\Administrator and Administrator password
6. In the Target Computer field, enter the target machine as D\L#####.shsu.edu.
7. Click Connect

Note: The software available to install is dependent upon what Active Directory (AD) groups a Node is a part of. NOTE: You are unable to do this for managed laptops off campus. 
 

1. Go to passman.shsu.edu
2. Check out Administrator password for the target machine.
3. Search and open CCCM (non-elevated) Note: CCCM doesn't exist you have to type in SCCM
4. Click on the blue button from menu bar at the top-left corner of the application
5. Click on Connection Options enter username as .\Administrator and Administrator password
6. In the Target Computer field, enter the target machine as D\L#####.shsu.edu.
7. Click Connect
8. Click Software Distribution (Bottom left hand side)
9. Select Applications under Overview (If no Applications load, try selecting Reload Applications)
10. Navigate to the desired software
11. Right-click the Software Name, and select Install
12. The CCCM console should now display that it is initiated an install command
    1. You may verify the installation is successful using the CCCM by selecting Reload Applications
    2. You may also verify the installation is successful by connecting to the client’s computer and opening the Software Center or Programs and Features menu.
13. The installation is complete when the InstallState of the Software is listed as Installed in the Applications Menu of the CCCM
    1. The client may also verify the software is installed by checking their Recently Installed Programs menu or verifying in the Software Center

See KA 90842

Note: These steps are only to be followed 24-hours after the new setup or installation of a Workstation. After a Workstation has been setup, it can take up to 24-hours for the device to communicate with SCCM, update Machine Policies, and/or update Group Policies. 

Step 1: Have an FTE open Microsoft Management Console (MMC) and Access the Active Directory. The FTE will need to search the Node name of the Workstation and confirm that it is in one of the following Security Groups according to the proper setup:

SW_Windows_10_x64_Desktop_Prod

SW_Windows_10_x64_Labs_Prod

Note: If the Node is not in an OSD Security Group, the FTE may add it to the proper group and then you may continue with this process.

Step 2: Open the Control Panel on the Affected Workstation'

Step 3: With the “View by” set to Large or Small Icons, Select “Configuration Manager”

Step 4: At the “Configuration Manager Properties” menu, Select the “Actions” tab, Select “Machine Policy Retrieval & Evaluation Cycle”, and then Click “Run Now”

Step 5: When presented with the “Machine Policy Retrieval & Evaluation Cycle” pop-up, Click “OK”

Step 6: Click “OK” on the “Configuration Manager Properties” menu to close it.

Step 7: Open a Command Prompt Session.

• Type the following command and hit enter: gpupdate /force
• Note: gpupdate is a command that updates the Group Policies for the User and Computer, it does not Update the Machine Policy from SCCM. 

Step 9: Restart the Workstation and have the client open the Software Center after logging into the computer. The Software Center should either be populated with additional software or begin populating software. The full update process could take upwards of 15 minutes or more. 

Step 10: If the Software Center fails to populate or begin populating new software, have an FTE send the Ticket to Managed Applications for Review. Please make sure to document the Steps followed as well as screen captures of any error messages presented during troubleshooting.

It can take up to 24 hours for the applications to populate in Software Center after adding the node to the appropriate AD group. 

From the device, do the following: 

1. Software Inventory Cycle & Machine Policy Retrieval & Evaluation Cycle
   1. Go to Control Panel > Configuration Manager
   2. When the Configuration Manager Properties window appears, go to Actions.
   3. Click on Software Inventory Cycle > click on Run Now.
   4. Machine Policy Retrieval & Evaluation Cycle > Click on Run Now.
   5. The software should appear after 20 minutes.
2. Policy Update
   1. If still not available, initiate a policy update for the node, by opening an elevated Command Prompt
   2. Type “gpupdate /force” without the quotes, and hit “enter”. 
   3. Restart the computer after the policy has been updated.

If the applications do not populate in the Software Center after 48 hrs, the device will need to be brought in for further troubleshooting. 

With SCCM you can manage services directly from the SCCM client without having to access the services via MMC. 
1.Connect to the node in the SCCM client
2.Go to "Monitoring"
3.Select "Services"
4.Here is where you can start, stop, and set startup behaviors for services.