How Automatic Client Upgrade Hammered Our Primary Server

[pxedave]

Folks,

 

My first experience with Automatic Client Upgrade (post R2 SP1) is not a good one...

 

After enabling this in live, even with the maximum 31 day upgrade window, our Primary server jumped to 95% network utilisation - things returned to normal shortly after disabling it. Following a brief investigation this morning I think I know why... OK, we were expecting Scheduled Tasks to be created across all our clients on day one. What we didn't expect was that client source would be pre-staged to the PCs at the same time! To add insult to injury, as this deployment doesn't employ the usual caching methods the 1E Nomad software we use to reduce server load was bypassed too... For now we are going to use the old right-click-a-collection-and-reinstall-client method to deploy it gradually ourselves.

 

What's the point in being able to increase the window to 31 days if the server is going to push client executables to every PC on day one? I still find it hard to believe it works like this but this is what I'm seeing. Note, only ccmsetup.exe is mentioned in the log but I saw an up-to-date 27Mb MSI in the same folder... Anyway, see the log snippet below.

 

 

 

 

'Configuration Manager Client Upgrade Task' is scheduled to run at 06/27/2015 12:10:38 PM (local) 06/27/2015 11:10:38 AM (UTC) time with arguments ' /AutoUpgrade /UpgradePackageVersion:14 /UpgradeWinTask'. ccmsetup 17/06/2015 14:29:38 5656 (0x1618)
ITaskService::GetFolder failed with 0x80070003 ccmsetup 17/06/2015 14:29:38 5656 (0x1618)
Params to send '5.0.8239.1000 Deployment Scheduled Time(UTC): 06/27/2015 11:10:38 AM' ccmsetup 17/06/2015 14:29:38 5656 (0x1618)
Sending message with STATEID='102' via the existing client. ccmsetup 17/06/2015 14:29:38 5656 (0x1618)
Adding client deployment state message. ccmsetup 17/06/2015 14:29:39 5656 (0x1618)
<ClientDeploymentMessage ErrorCode="0"><Client Baseline="1" Platform="1"/><Packages><Package ID="{DC61B2DE-E38E-498E-95B3-4BEF3657482E}"/></Packages><Additional><UpgradeSchedule Value="06/27/2015 11:10:38 AM"/></Additional></ClientDeploymentMessage> ccmsetup 17/06/2015 14:29:39 5656 (0x1618)
Successfully deleted existing ccmsetup.exe ccmsetup 17/06/2015 14:29:40 5656 (0x1618)
Downloading file C:\WINDOWS\ccmcache\8j\ccmsetup.exe ccmsetup 17/06/2015 14:29:40 5656 (0x1618)
Downloading C:\WINDOWS\ccmcache\8j\ccmsetup.exe to C:\WINDOWS\ccmsetup\ccmsetup.exe ccmsetup 17/06/2015 14:29:40 5656 (0x1618)
File download 15% complete (262144 of 1738424 bytes). ccmsetup 17/06/2015 14:29:41 5656 (0x1618)
File download 30% complete (524288 of 1738424 bytes). ccmsetup 17/06/2015 14:29:41 5656 (0x1618)
File download 45% complete (786432 of 1738424 bytes). ccmsetup 17/06/2015 14:29:41 5656 (0x1618)
File download 60% complete (1048576 of 1738424 bytes). ccmsetup 17/06/2015 14:29:41 5656 (0x1618)
File download 75% complete (1310720 of 1738424 bytes). ccmsetup 17/06/2015 14:29:41 5656 (0x1618)
File download 90% complete (1572864 of 1738424 bytes). ccmsetup 17/06/2015 14:29:41 5656 (0x1618)
File download 100% complete (1738424 of 1738424 bytes). ccmsetup 17/06/2015 14:29:41 5656 (0x1618)
Download complete. ccmsetup 17/06/2015 14:29:41 5656 (0x1618)
CcmSetup is exiting with return code 0 ccmsetup 17/06/2015 14:29:41 5656 (0x1618)

 

 

[pxedave]

... Even if it was only a 2Mb pre-stage, across our 10,000 PC's... 2 x 10,000 = 20,000Mb = 20Gb...