Jump to content


We use cookies to let you log in, for ads and for analytics. OK

Photo

Upgarde SCCM 2012 R2 SP1 to SCCM Current Branch 1610





  • Please log in to reply
1 reply to this topic

#1 StewieHendrix

StewieHendrix

    Newbie

  • New Members
  • Pip
  • 2 posts
  • Gender:Male

Posted 09 January 2017 - 03:19 PM

Hi,

 

My appologies if I post this in the wrong forum.
Also, appologies for the very long post.

 

Our environment:
SCCM 2012 R2 SP1
One Primary Site server (no secondary sites)
Site version: 5.00.8239.1000
SQL is on the same server (SQL 2012)
Server version: Windows Server 2012 R2
11 Distribution Points worldwide
MDT: 2013 Update 2 (6.3.8330.1000)
Windows 10 ADK: 10.1.10586.0
 
I am new in the company and I have inherited an SCCM 2012 R2 SP1 server.
I am not an SCCM expert at all. I am still learning.
 
However, they are requesting to upgrade the SCCM server the latest version.
I want to make sure that everything will work after the upgrade. Hence the questions.
 
Currently, we are deploying Windows 10 build 1511. (as well as Win 7 and 8.1 in some cases)
We want to deploy Windows 10 1607 after the upgrade (and Win 7 and 8.1 on some devices)

 

1) Do I have to upgarde ADK to version 1607 (10.1.14393.0)?

If yes, before or after the uprade of ConfigMgr?

I remember a while ago there was a problem with a certain version of ADK 1511 and we had to skip that version.
I suppose the latest version is working fine?

 

 

2) Do I have to update MDT?

If yes, before or after the upgrade of ConfigMgr?

 

3) I did a lot of research. So I can now first upgrade to the latest baseline version 1606 and then do an in-place upgrade to 1610?

Please correct me if I'm wrong.

Also, can I do the upgrade to 1610 immediately or will I have to do/test something before proceding?

 

4) How about the update of ConfigMgr clients on our devices?

At the moment, automatic update is turned on: "Upgrade client automatically when new client updates are available".
Should I turn this off before I start with the Site upgrade to avoid automatic client updates in case something goes wrong and I have to restore backup?
 
5) Does anybody know of a good backup and restore guide for CM?
I want to create a backup first and be able to restore it if anything goes wrong.
As the server is on VMWare, can I take turn off the server, take a snapshot, upgrade. And if something goes wrong I restore the snapshot?
Is that sufficient?
 
 
Thank you




#2 StewieHendrix

StewieHendrix

    Newbie

  • New Members
  • Pip
  • 2 posts
  • Gender:Male

Posted 11 January 2017 - 08:47 AM

Anyone?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users