Client agent version is returned by the heartbeat discovery (called the data discovery cycle in the list of client side actions). If this truly is not updating the values in your DB, you've got much bigger issues. Have you followed the log trail?
When did you update the clients? Note that I always recommend setting the heartbeat discovery interval to a frequency of every 1 day or even more frequently up to 3-4 time per day for this reason amongst others. J From: [email protected] [mailto:[email protected]] On Behalf Of Mawdsley R. Sent: Thursday, May 28, 2015 7:23 AM To: [email protected] Subject: [mssms] RE: Client Version Number Wrong Every 7 days. Running it manually doesn't help. Nor do running any of the client side actions. Rich From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Garth Jones Sent: 28 May 2015 13:18 To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Client Version Number Wrong What is your Heartbeat Discovery Cycle seup to? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mawdsley R. Sent: Thursday, May 28, 2015 8:08 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Client Version Number Wrong Afternoon Chaps, I have an issue where clients are running R2 CU4 (5.00.7958.1501), but in System Center, they are showing as base R2 (5.00.7958.1000). This is oddly only about a third of the total machines tho, the others show fine. See attached dodgy paint job, Any Ideas? Thankyou Rich
