Upgrade to SCCM 2012 R2 SP1 - Clients Communication

Hello All,

I am planning to upgrade my existing SCCM 2012 R2 to SP1.

My concern is that many of the computers are offline during the summer months and will not be back on the network until September.  Will this cause a problem with the client communication?  As the client will be of an older version after upgrade of the server, will the difference in version break the connection/communication with SCCM?

July 21st, 2015 10:14am

No SCCM client will still be compatible. Once they are online they will report back and will be upgraded if you select the auto upgrade option.

Info taken from the Technet: 

After you upgrade a primary site, plan to upgrade clients that are assigned to that site. Although a Configuration Manager primary site or secondary site can support communication from clients that have a lower service pack version, this communication should be a temporary configuration. Clients that run a previous service pack version of Configuration Manager cannot use the new functionality that is available with the new service pack version of Configuration Manager

Free Windows Admin Tool Kit Click here and download it now
July 21st, 2015 10:16am

No the clients will not break. You can create collections and target the upgrade of the clients or you can switch on automatic upgrade of clients.

Check out the Updating the Clients and Consoles section of this upgrade guide

http://www.systemcenterdudes.com/sccm-2012-r2-sp1-upgrade/

You can set a time frame for upgrades so you can spread the client deployment.

July 21st, 2015 10:20am

Because the machines are offline in the summer months, do I set the "Automatically upgrade clients within days" to 45 days?  The 45 days will bring us to September time frame.

Other than the auto upgrade option in hierarchy settings, is there other ways to push client upgrade to workstations?

Free Windows Admin Tool Kit Click here and download it now
July 21st, 2015 10:22am

Ann,

You can leave this at 7 days. What the process does is create a scheduled task on the client that will run every 7 days. So at some point the machine will upgrade.

July 21st, 2015 10:25am

Ann - the article show you other options such as creating a collection and targeting the client install at that collection. 

Another option is a client push from the console. Bit tedious though

Free Windows Admin Tool Kit Click here and download it now
July 21st, 2015 10:26am

You could make a collection and deploy the package that will be created when you do the upgrade (just like any CU before)

But for the ease i would use the auto upgrade. No need to set the date that far this is for SCCM to slowly upgrade all the client. When a client come online that is not upgraded SCCM will start the upgrade even if the time frame is pass.

Here you will find the info about the option 

  • Automatically upgrade clients within days  Specify the number of days in which client computers must upgrade the client after they receive client policy. The client will be upgraded at a random interval within this number of days. This prevents scenarios where a large number of client computers are upgraded simultaneously.

July 21st, 2015 10:26am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics