SCCM 2016 Upgrade
We currently use SCCM 2012, I would like to upgrade to SCCM 2016. Is this a in place upgrade? or any complication in this upgrade?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
So what about in the previous version ?
is that advisable to perform the inline upgrade ?
is that advisable to perform the inline upgrade ?
Not known at this time. CB (currently at 1606, not 1511) is only available to those with *active* software assurance. Which is different than windows enterprise, which has historically allowed existing machines to continue running enterprise even after SA expired.
Because it is tied to active SA, it was architected with the idea that it is going into organizations that are current and will stay current. Thus upgrade "jumps" weren't taken into account.
2016 will presumably be sold just as 2012 and 2012 R2 were, as a perpetual license bundled in System Center, and therefore more flexible upgrade scenarios may be considered.
Because CB is tied to SA and has a "stay current" mentality, using CB as a baseline for predicting how 2016 will be handled isn't something I'd be comfortable doing. While there will undoubtedly be some feature overlap, they are effectively diverging as products and have different target markets, with CB leaning mich more heavily into hybrid. Which is why I didn't even bring it up in my initial reply.
In short, nobody who knows about 2016 is publicly talking (likely under NDA) and even if they were, plans can change very quickly very close to RTM. Nobody can safely answer the question you are asking, no matter how it is rephrased.
Because it is tied to active SA, it was architected with the idea that it is going into organizations that are current and will stay current. Thus upgrade "jumps" weren't taken into account.
2016 will presumably be sold just as 2012 and 2012 R2 were, as a perpetual license bundled in System Center, and therefore more flexible upgrade scenarios may be considered.
Because CB is tied to SA and has a "stay current" mentality, using CB as a baseline for predicting how 2016 will be handled isn't something I'd be comfortable doing. While there will undoubtedly be some feature overlap, they are effectively diverging as products and have different target markets, with CB leaning mich more heavily into hybrid. Which is why I didn't even bring it up in my initial reply.
In short, nobody who knows about 2016 is publicly talking (likely under NDA) and even if they were, plans can change very quickly very close to RTM. Nobody can safely answer the question you are asking, no matter how it is rephrased.
ASKER
Currently I am using SCCM 2012 R2 (version 5.0.7958.1401). If I am not wrong this version wont support windows 10 OS. We have many windows 10 clients in our organization. Is there any upgrade available later that this to support windows 10 OS?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks Cliff. I thought that was the case from what you said. It's definitely not something I had realised. Yes, for security change is generally bad and frequent change even worse.
The upgrade path is to get to ConfMgr 2012 R2 first, then go to the "branch" product stream 1511. Once you have that, you get upgrades in the console, as long as you have direct internet access. It also works offline but you have to run a servicing tool on something that has internet. As for 2016, Cliff is correct, you're a bit early. It's due any time now but I'm guessing mid-September.
Mike