Auto-upgrade is a hierarchy wide setting so it doesn’t matter where you enable it. Yes, it works fine for larger enterprises. Microsoft uses it internally for all of their upgrades — since they dogfood interim builds, they’ve deployed many for their 200,000+ managed client infrastructure.
What’s better is up to you, but yes, auto-upgrade works well and is my first choice even for larger hierarchies. J From: <[email protected]<mailto:[email protected]>> on behalf of Liam Doyle <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Wednesday, March 9, 2016 at 11:30 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [mssms] Hey Jason, thanks for your respone. Pls find below comments. Que :Knowing why you don’t want to use auto-upgrade would be helpful in answering this question. My hirerarchy is having 2,35,000 clients. So I am confused whether enabling auto upgrade is a good option or not, as I am not sure how will be failure rate. If enable it, where should I enable. Is that on CAS or on the respective primaries. Que :Also, is you are simply upgrading your site hierarchy to 1511, then there is no client “migration”, so not sure what you mean by your last sentence. Yes, we finished upgrading the site servers to 1511. But SCCM clients should be migrated to the latest 1511 client version rite. Que:For an in-place site hierarchy upgrade, upgrading the clients is also done in place. This is done by running the latest version of ccmsetup on the client. This does not change any of the configuration of the system, just upgrades the bits and bytes to 1511. Running ccmsetup can be done in many ways and is ultimately all that auto-upgrade does. We, did a in-place upgrade. But clients didnt get upgraded yet. Do u think enabling auto-upgrade on CAS is a better option. Que:All item of knowledge that could be helpful is knowing why you have a CAS and three primary sites. Majority of our SCCM machines are at US. So we had CAS and one primary there. one primary for EU, and one for APAC. We had app 2,40,000 clients Many thanks for ur response, Regards, Liam On Thu, Mar 10, 2016 at 5:22 AM, Liam Doyle <[email protected]<mailto:[email protected]>> wrote: Que : Knowing why you don’t want to use auto-upgrade would be helpful in answering this question. Answer : My hirerarchy is having 2,35,000 clients. So I am confused whether enabling auto upgrade is a good option or not. Also, is you are simply upgrading your site hierarchy to 1511, then there is no client “migration”, so not sure what you mean by your last sentence. For an in-place site hierarchy upgrade, upgrading the clients is also done in place. This is done by running the latest version of ccmsetup on the client. This does not change any of the configuration of the system, just upgrades the bits and bytes to 1511. Running ccmsetup can be done in many ways and is ultimately all that auto-upgrade does. All item of knowledge that could be helpful is knowing why you have a CAS and three primary sites. On Sat, Mar 5, 2016 at 11:59 PM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: Knowing why you don’t want to use auto-upgrade would be helpful in answering this question. Also, is you are simply upgrading your site hierarchy to 1511, then there is no client “migration”, so not sure what you mean by your last sentence. For an in-place site hierarchy upgrade, upgrading the clients is also done in place. This is done by running the latest version of ccmsetup on the client. This does not change any of the configuration of the system, just upgrades the bits and bytes to 1511. Running ccmsetup can be done in many ways and is ultimately all that auto-upgrade does. All item of knowledge that could be helpful is knowing why you have a CAS and three primary sites. J From: <[email protected]<mailto:[email protected]>> on behalf of Liam Doyle <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, March 4, 2016 at 12:39 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [mssms] Hello experts, Need a suggestion: we are planning to upgrade our environment to 1511. We have a CAS with three primaries. What is the best way to migrate our present clients to 1511 other than auto upgrade. Regards, Liam On Sat, Mar 5, 2016 at 11:59 PM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: Knowing why you don’t want to use auto-upgrade would be helpful in answering this question. Also, is you are simply upgrading your site hierarchy to 1511, then there is no client “migration”, so not sure what you mean by your last sentence. For an in-place site hierarchy upgrade, upgrading the clients is also done in place. This is done by running the latest version of ccmsetup on the client. This does not change any of the configuration of the system, just upgrades the bits and bytes to 1511. Running ccmsetup can be done in many ways and is ultimately all that auto-upgrade does. All item of knowledge that could be helpful is knowing why you have a CAS and three primary sites. J From: <[email protected]<mailto:[email protected]>> on behalf of Liam Doyle <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, March 4, 2016 at 12:39 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [mssms] Hello experts, Need a suggestion: we are planning to upgrade our environment to 1511. We have a CAS with three primaries. What is the best way to migrate our present clients to 1511 other than auto upgrade. Regards, Liam
