SCCM occasionally gets a backlog of Status Message Queries which causes it to freeze and stop processing new entries. This isn't something you'll typically notice right away, but if you go to look at Status Messages you'll notice they stopped at some point in the past.
The first thing you can try is a simple restart of the SMS_STATUS_MANAGER service. Open the Configuration Manager Console and go to Monitoring > Overview > System Status > Component Status. On the ribbon, click on Start and then click Configuration Manager Service Manager.
Once Configuration Manager Service Manager is open, scroll down to the SMS_STATUS_MANAGER and highlight it. Right click on it and Query. Once it shows the status, right click on it and click on Stop. Wait a minute and then right click on it and Query to verify that it stopped. Now right click it again and click Start. If your status messages start showing up again, you're good to go. If not, continue on reading.
If that component service restart didn't fix the issue, you'll need to clear out the oldest pending status message from the folder [Install Directory]\Microsoft Configuration Manager\inboxes\statmgr.box\retry [below sceenshot, step 1]. To clarify, this is on your server that has the SMS_STATUS_MANAGER service on it. Open that folder, cut the oldest entry [below screenshot, step 2) and paste it into a temp folder [below screenshot, step 3,4] like c:\temp just in case you need it. Once you've removed the oldest entry, stop and start the SMS_STATUS_MANAGER service again [below screenshot, step 5] and you should see new messages appearing when you look at the Status Message Queries back in the console. NOTE: It may take several minutes for all status messages to get caught up, but you should slowly see the entries start to get newer and newer.
Popular posts from this blog
Have you ever needed to get a really fast real-time look at if a service is running on a set of servers or workstations? Open CMPivot against a collection, type in your query, and send it. Seconds later you get real-time answers to your query for any online device. Queries for CMPivot run on 42 devices at once, until all devices you're querying have responded. The last time my organization did server updates, I (and a trusty super awesome coworker) had to verify if a couple of SQL services were running on a small collection of servers. As we were manually checking these one by one, I came up with the idea that it would be incredibly helpful to use CMPivot. The below query in CMPivot will return all devices where a SERVICE with the name containing SQL is NOT RUNNING and the service's start type is AUTO. In other words, if a service with SQL in the same is supposed to be automatically running and it's not, this query tells us. Service | where Name contains 'sql'
How do you use Parameters in MEMCM's (R.I.P. SCCM) Run Scripts? How do you use Parameters on the Run Scripts feature? You get three guesses, but the first two don't count. That's right, you create a script with standard PowerShell Parameters and you build it out in MEMCM. In your MEMCM console, navigate to Software Library > Overview > Scripts. If you're not familiar with Run Scripts in MEMCM, check out my previous Blog articles on it. Click on Create Script . In the Create Script Wizard that pops up input a Script Name , pick between PowerShell or PowerShell in your Script Language , import or paste in your script with Parameters, and click on Next . My demo script for this article ( scroll alllll the way down, it's at the bottom ) is about an 8 out of 10 on the cool factor, and about a 3 out of 10 on the usefulness factor. Long story short, the script will make a computer talk. There are two Parameters that you can input, one for "what do y
What is Client Notification? Client Notification in SCCM is one of the most powerful features of SCCM that most people never know they use on a regular basis. In SCCM 2012 SP1, Client Notification was introduced to help get rid of the S low M oving S oftware name and help get SCCM into the business of real-time actions. Client Notification consists of a Notification Manager, a Notification Server, and a Notification Agent which is part of CCMEXEC on the client. The Notification Agent on the client attempts to initiate communication with the Notification Server (your Management Point aka MP) via TCP on port 10123 and it keeps this “conversation” alive checking in every 15 minutes. If TCP on port 10123 isn’t available, the client fails over to using HTTP/HTTPS on port 80/443 and this communication occurs every 5 minutes. DNS Resolution from the MP to the Client is NOT required, because the client is initiating the communication with the MP. As long as the client can resolve