Greetings,

  We have a large VDI environment and to date these machines have not joined the ConfigMgr world as the 2007 agent was far too noisy.

  We are now doing a test using the CM2012 client as we can have different client settings. So we've turned off nearly everything. There are only a couple of dozen fields collected by hardware inventory once a week. We installed the clients using ccmloglevel=3. Sadly there is not much that can be done about the client health scheduled task.

  The amount of noise is still a concern. When we run PROCMON we discover that the agent is reading the registry CONSTANTLY and writing a ".msg" file every minute. What on earth is this thing doing and why? Does anyone know?

Thanks

David Z

When we run PROCMON we discover that the agent is reading the registry CONSTANTLY and writing a ".msg" file every minute. 

Is it true that there is nothing specific in the client log files about this activity of the agent? What is there is that .msg files? One suggestion, what if you disable all the inventories for some time and check?

The is nothing in the client log files as they are rarely updated due to ccmloglevel=3.

I dont know what the .msg files are and why they would be constantly generated.

I dont think disabling the once a week hardware inventory has anything to do with this activity.

Curious. Have you tried opening one of these .msg files? What folder are they created in?

Constant registry reads is pretty typical for most system applications though.

Note that you can configure ccmevel to "notify only": http://blog.coretech.dk/kea/configure-client-remediation-in-configmgr-2012-to-monitor-only-using-settings-management/

Im thinking maybe the .msg files are status messages, but why be so active reporting status when Ive configured the client to do stuff all?

Essentially im looking to quieten down the client as much as possible. Id be interested if others have a VDI environment and how they tune things.

It writes every minute to the following location:

C:\windows\ccm\servicedata\messaging\endpointqueues\statemessagemanager

It writes both .msg and .que messages

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.

It's a very long time ago and Im no longer working there.

No we didnt solve the problem.