So, finally I have finished upgrading all of our clients to the latest version and CU of the SCCM client.
To say it has been a challenge is an understatement.
You would think that given what SCCM is used for that it would be easy and quick to do, but no.
There were just over 400 machines and once I upgraded the server form SP1 to R2 and then updated it to the latest CU I had to deploy the R2 client and then deploy the update to CU4.
The R2 client seemed to get deployed quiet easy, there were a few machines that for some reason had really really old SP1 version on them. For those, there were a few that didn’t like the upgrade, so I had to uninstall the old client and then deploy the new one.
I then set about deploying the CU4 update to all machines. There was a bunch that wouldn’t update, no matter how long I left it and no matter how many times I forced an Application Deployment Evaluation Cycle it stayed on the old version.
I had a SQL query listing all the machines on the old version, the started off about 49.
I found it easier to remote on and manually uninstall the client, wait for all processes to terminate, rename the old SCCM directory and then reboot the machine. I figured that out after a bit of trial and error trying to get things off and on again!
So, thinking I had it sussed out, I was somewhat surprised when I refreshed my query one morning to find the number of machines had increased. Looking closer it was a few machines from the Labs.
RDPing on showed that the version was indeed the old version. I really couldn’t be bothered to see what the hell was going on as it had been a good few weeks that I had been trying to do this and people not logging off! and machines in locked rooms that didn’t work with WOL were doing my nut in.
So for each of those I applied my fix – remove the old client, wait for processes to terminate, rename the old CCM directory, reboot the machine, deploy the new client via SCCM and then deploy the update. That seemed to work for every computer that somehow managed to downgrade its client version on a reboot!?
Now to package and deploy the growing list of application updated that are needed.