SCCM - Current Branch - Anyone upgraded yet?

Soldato
Joined
23 Nov 2004
Posts
3,792
Hi,

Many of you upgraded your SCCM from 2012 to the Current Branch release? I'm looking into doing this now but our enviroment is sat on Windows 2008 R2 VM's, so will need to create Fresh VM's with Windows 2012, install Current Branch and then do the Side by Side Migration.

Anyone else gone down this route? If so, how troublesome was it?
 
I too have been looking at the procedures of upgrading.

I'm in the boat where my current SCCM environment is already on 2012R2, so my upgrade path should be easier.
 
I too have been looking at the procedures of upgrading.

I'm in the boat where my current SCCM environment is already on 2012R2, so my upgrade path should be easier.

Yep, much much easier. In place upgrade should be fine. I've done lots of reading on it. I'd recommend running the database pre req check against your SQL DB on a separate server to see what will ans won't work. I can link you up to a walkthrough on this if you want it.

Anyone else made the move yet? Like the new version?
 
I'm holding off until server 2016 is out and a few more updates have been done. I adopted 2012 quite early and got hit by quite a few early bugs that took ages to resolve (mainly relating to OS deployment)

The base OS for mine is still 2008R2 though, so I'm probably going to have a fun time with my upgrade...
 
I just upgraded from R2 SP1 CU2 to 1511. It was quick and simple, but did require restarting the Primary site after. It took down the WDS services on my DPs, but the reboot quickly resolved it.

the new client installs fine on Win10 and Win8.1, but my limited testing shows it prompts for a reboot on Win7. more testing underway this afternoon!

Single Primary, 6 DPs, 1700 clients
 
I'm holding off until server 2016 is out and a few more updates have been done. I adopted 2012 quite early and got hit by quite a few early bugs that took ages to resolve (mainly relating to OS deployment)

The base OS for mine is still 2008R2 though, so I'm probably going to have a fun time with my upgrade...

Similar to me. Mine is run exclusively on VM's so have already got some 2012 ones built. I'll be doing the Side by Side site migration which means a new site code :(

I just upgraded from R2 SP1 CU2 to 1511. It was quick and simple, but did require restarting the Primary site after. It took down the WDS services on my DPs, but the reboot quickly resolved it.

the new client installs fine on Win10 and Win8.1, but my limited testing shows it prompts for a reboot on Win7. more testing underway this afternoon!

Single Primary, 6 DPs, 1700 clients

Blimey, that's a lot of DP's, is it just 6x separate sites? Is your SQL database on the Primary site server?
 
Yes have upgraded our Dev environment, will be doing Production in a couple weeks.

All went smoothly!

All our sccm infrastructure is currently on Srv2008r2 machines. Plan being later in the year to just use the new in-place upgrade feature to take the whole site up from 2008r2 to 2012r2. No side by side migration necessary. (2016 is a little new out the box).
 
Plan being later in the year to just use the new in-place upgrade feature to take the whole site up from 2008r2 to 2012r2. No side by side migration necessary. (2016 is a little new out the box).

You got any information on this? I didn't realise that capability was in the works.

I thought in place upgrades were restricted to 2012 > R2.
 
Currently deploying 1511 side-by-side with our outdated and badly managed 2007 deployment. Got a fair chunk of the WSUS implementation done this week, planning SCEP to be done next week and then we need to look at creating a proper gold image of Windows 10 instead of the base image we have now, and then to refine the task sequences.

We're on 2012 R2 and 1511, will probably upgrade to latest branch before our implementation goes into production as long as there are no critical bugs.
 
Have any of you installed the System Centre Technical Preview 4? I've been playing with it in a lab, just to see how different it is from 2012 R2 - it looks pretty much the same to me, other than the stuff about Windows 10 servicing.

We're using 2012 R2 at work, but we share a site with another business unit so it's not configured the way I would want, and I'm itching to set up our own instance. I just need an excuse as to why we need it, and to be honest, I can't think of a legitimate business case. I was hoping to use SCCM 2016 and it's amazing new features as the reason to push ahead with getting our own. I should probably read the documentation to see what changes they've made :)
 
Fortunately we have a free server arriving over the next few weeks.

I'm wondering if it's would be easier to build a new SCCM server next to the existing one and simply update all the client agents.

That way, I can take my time getting the new server just how I like it rather than upgrade over the top (which I hate doing).
 
Back
Top Bottom