FN-GM

For those who have just upgraded to the final release of SP1 you will have found the client needs an upgrade. You can do this my one if these methods:

1. Auto upgrade SCCM 2012 Clients
2. Use the client upgrade package

Step 1 would be easier, but for devices that go offline for long periods will not upgrade as well. If you use the deployment package and let the software install outside of maintenance windows it will get to all your machines better. Also step 1 will not give to the reporting step 2 will allow you.

This query will allow you to create a collection for devices that do not have the new updated client. You can then deploy the upgrade package to this collection.

Code:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ClientVersion < "5.00.7804.1000"

You may find that deploying the package returns as failed and reporting "unexpected restart" but the application has installed just fine. This is because the package the stops the ccmexec service which kills the execution manager making it think it got rebooted or interrupted.