I have a SCCM 2012 R2 pilot site that I have upgraded to 1511 and then to 1602. I am trying to understand how the client upgrade /update process will work. I know I can tell the site to automatically update all of the clients and that seems to be working okay for those machines that are already installed (<100). I have 2 other scenarios that I need to make sure that have client consistency across the environment when deploying.
I have about 3000 SCCM 2007 clients that I need to move to this new site, I have a package that has worked well during the pilot but that was to 2012R2 not 1511>1602. I also have a desktop team that builds new systems using MDT currently so I need to have a similar package for those new or reconfigured machines. I assumed it would be as easy as going to \\siteserver\SMS_xx\Client\<file://siteserver/SMS_xx/Client/> and copying the files from there and adding them to my deployment package. But I see that I have a client folder, client upgrade folder, staging client folder all with different source files. To further complicate it I see that there is a hot fix for SCCM 2007 clients that get upgraded to resolve a reboot during the deployment. https://support.microsoft.com/en-us/kb/3140781 So I guess my question is can I go from SCCM 2007 straight to SCCM 1602 client or do I need to do 2007 to 1511 and then to 1602? My next question would be similar but can I go from fresh built to 1602 ? or do I have to do 1511 and then patch to 1602? And finally what folder should I be getting the latest client install files from? Thanks Carl
