Manually Fixing a Broken Client

By -
Just because the client is installed doesn't mean it is working correctly. When you notice a device isn't reporting back correctly. There are a few things to look at first in your configuration manger console. Go to the client and look at the client activity if any of your scans or request are more then a week old that is a good indication the client is have an issue with either connection to the server or running these actions


Next go to log into the client and go to Control Panel > System and Security > Configuration Manager and on the actions tab and run the Machine Policy Retrieval & Evaluation Cycle, Software update Scan Cycle and the Hardware Inventory Cycle. Try to wait a few moments between each action running one right after the other can cause the client to stop one action an run another. If you get an error on any of these actions uninstall the SCCM client and reinstall it.


last on the client having the issue open powershell as an administrator and run the following

Get-WmiObject -Namespace root\ccm -Class sms_client

If you get an error or you do not get anything back reinstall the SCCM client, this means SCCMs part of WMI is not working and needs to be repaired reinstalling the client will do this.

You can do this all manually or you can use my SCCM Client Health Check login script to help automate the process.  

Comments

Post a Comment

Popular posts from this blog

SCCM Task Sequence GUI - How to set up the TS to work with a GUI

By -
Image
Before I have posted how you can create a TS for windows 10 , add a GUI to your TS and run a script to configure your windows 10 install . However all of this has become out dated and so I wanted to update all of that. This how to will walk you through how to create a TS that will allow you to choose a windows 10 or windows 7 image, name the computer, add the computer description to AD, Choose form a list what applications you want to install, Choose to enable BitLocker and set the PIN as well as create a local account. Prerequisites: MDT integrated to SCCM A boot image with the following components added Windows Powershell(WinPE-DismCmdlest) HTML(WinPE-HTA) Microsoft .NET (WinPE-NetFx) Windows Powershell (WinPE-Powershell) A windows 10 and windows 7 image  1. Download the package I have put together containing the scripts you will need https://github.com/sccmtst/SCCM-Management-Scripts/tree/master/TSGUI 2. If you have not already done so download and in...
Read more

SCCM Applications vs. SCCM Packages: Understanding the Key Differences

By -
Microsoft System Center Configuration Manager (SCCM) is a versatile and powerful tool for managing devices, applications, and updates in an organization's IT environment. Among its many features, SCCM allows you to deploy software to your end-users in two primary ways: Applications and Packages. Although both methods have a similar goal, they have some key differences that IT administrators should understand when choosing the appropriate deployment method. In this blog post, we will explore these differences and help you decide which option is best for your organization. Definition and Deployment Scenarios SCCM Applications: An SCCM Application is a high-level, user-centric deployment method that focuses on providing the desired user experience. Applications are designed to be state-based, meaning they can detect if the application is already installed and only perform the necessary actions if the application is not present or if a newer version is available. Applications are suita...
Read more

Faster PXE boot times in SCCM 1606 and later

By -
Image
A new feature introduced with SCCM 1606 was being able to modify the boot times for PXE. This is done by modifying the TFTP block and window size of the boot image RamDisk. This was originally implemented to help a admin over come network requirement. This allows us to make the PXE boot times much faster for my self this meant taking a 10 minute boot time all the way down to 30 second boot time. In order to make this change you need to create 2 registry keys on your PXE enabled DP. Location : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP Name: RamDiskTFTPWindowSize Type : REG_DWORD Value : <customized window size> The default value is 1 (1 data block fills the window)  Location : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\DP Name: RamDiskTFTPBlockSize Type : REG_DWORD Value : <customized block size> The default value is 4096 (4k).  once you have added the registry keys you will need to restart  the Windows Deployment Service for the ch...
Read more