Sccm queries not updating
The state message itself is made up of a few parts – two of the key parts being the Topic Type and State ID.As you look at the logs you will notice in some places the Topic Type seems to already be interpreted for us and in the logs you won’t always see both the Topic Type and state ID together.Even with Profiler you won’t see a great deal – more on SQL stuff in a bit. I’ve pulled some log snips (and at this point thanks go to my colleague – Vinay Pamnani – who had done some of the log gathering leg work for me) that line up the updatesdeployment log and statemessage log on the client – showing how between the two you can get a good idea of what is happening at the various steps along the way simply by looking at the state messages.
OK, cool – so lets resend this data to the MP and track it’s progress.
When state messages are received two things happen – first, state messages are stored in WMI.
Then, on a 15 minute cycle (by default – this can be changed), the state system will scrape WMI for any state message that has not yet been sent and forward up to the MP.
SMX files by the MP_Relay component and placed in the auth\statesys.box\incoming folder on the site server.
From there they are processed into the database to complete the flow.For everything else, traffic goes directly to the MP.