Nothing to worry about, it just means there is an agent update to push.
However, you will need to work through the fabric in the GUI, checking the Library Servers, PXE Servers, Update Servers etc etc.
You'll probably want to add the extra columns to each view of the console as you go to make it easier to check. Add these columns:
- Agent Version
- Agent Version Status
- Updated Date
Or alternatively, you could always drop to a PowerShell Prompt and run this to check your entire estate very quickly:
Get-SCVMMManagedComputer | FT ComputerName,Role,VersionStateString,AgentVersion,UpdatedDate -AutoSize
This will show you the current state of your VMM Agent deployment status.
If you wanted to just see those servers requiring an update, add a filter:
Get-SCVMMManagedComputer | Where VersionState -eq UpgradeAvailable | FT ComputerName,Role,VersionStateString,AgentVersion,UpdatedDate -AutoSize
And just to finish, you "could" (I wouldn't to this on mass!!) update all of those pending agents with a couple of lines:
$Credential = Get-SCRunAsAccount | Out-GridView -PassThru
Get-SCVMMManagedComputer | Where VersionState -eq UpgradeAvailable | Update-SCVMMManagedComputer -Credential $credential -RunAsynchronously
See the failed one? That's the Cluster Object Name of my library file server cluster and VMM (although it shows as having an Agent Status etc) won't allow direct update of that, only the nodes that are part of the cluster.