If you find out please let us know
Does anyone know what the upgrade procedure for the various System Center 2012 R2 products is going to be? We have SCVMM, SCDPM and SCCM 2012 SP1 running at the moment and I'm curious to know how much work is going to be involved in upgrading.
If you find out please let us know
As above! It might mean me having to nuke my half built SP1 server.
(Sorry I can't post anything more constructive!)
It would be moronic for Microsoft to expect everyone to do a swing upgrade again but given their recent behaviour, it would also be completely unsurprising
Coming back to this a few weeks later...
It looks like the upgrade path is 2012 --> 2012 SP1 --> 2012 R2
This applies to all of the system center products apparently
Thoughts on OpsMgr and System Center 2012: Upgrade Paths To System Center 2012 R2
System Center 2012 R2, Upgrade Path |
I'm relieved, an inplace upgrade is possible.
Upgrade Sequencing for System Center 2012 R2
Microsoft has just released information on how to upgrade the System Center 2012 stack. Now BEFORE you start, you need to figure out where to start and what’s to be done in other system center products at the same time. In many cases you will not be able to upgrade the entire stack at the same time, there for all interactions between needs to be taken seriously. As an example, if you do have Orchestrator integration, you need to upgrade the OR server first, but it does not mean all the OIPS should be upgraded, the should of course be upgraded when the corresponding SC2012R2 system gets updated, so there is a lot to think about. (Source)
Johan Arwidmark has posted a very handy guide on how to upgrade to ConfigMgr 2012 R2 (from 2012 SP1) and MDT 2013 (from MDT 2012 Update 1).
A Geeks Guide for upgrading to ConfigMgr 2012 R2 and MDT 2013 « Deployment Research
Before diving into the guide, please note there are a few issues with ConfigMgr 2012 R2 that are currently being researched. For a start, don't be too surprised of the PXE feature doesn't work when using the site server as a DP, or if the network account cannot access the server. See later in this guide for workarounds.
Also, you are very likely to run into that deployment is much slower with WinPE 5.0 (which is used by ConfigMgr 2012 R2). Hopefully these issues will be sorted out quickly, I will be sure to update this post when I have more information.
I did an in place upgrade from 2012 SP1 to 2012 R2 with no problems. I don’t use it for imaging yet, and I’ve not upgraded MDT yet though.
I was sure to take a full system backup beforehand, but the whole process was painless.
KB2905002 - An update is available for the "Operating System Deployment" feature of System Center 2012 R2 Configuration Manager
This update resolves the following issues in Microsoft System Center 2012 R2 Configuration Manager.
After you enable the PXE Service Point role on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running.
Note. This problem affects only distribution points that are installed on site servers.
When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows operating system.
Does anyone know if the hotfix is still needed?
2 thing to note:
SCVMM R2 does not P2V
SCDPM R2 won't backup Server 2003
There are currently 1 users browsing this thread. (0 members and 1 guests)