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…
The link is here http://technet.microsoft.com/en-us/library/dn521010.aspx
Some highlights:
Orchestrator: http://technet.microsoft.com/en-us/library/jj628201.aspx
- If Orchestrator is part of your environment, then Orchestrator will be the first component that you upgrade.
Service Manager: http://technet.microsoft.com/en-us/library/jj628207.aspx
Data Protection Manager: http://technet.microsoft.com/en-us/library/jj628208.aspx
- There are some new features that are available with Data Protection Manager (DPM) that are only available when using Windows Server 2012.
Operations Manager: http://technet.microsoft.com/en-us/library/jj628193.aspx
After you upgrade Operations Manager, you might have to install the Operations Manager console on some of the down-level components.
- There are some new features that are available with Operations Manager that are only available when using Windows Server 2012.
Configuration Manager: http://technet.microsoft.com/en-us/library/jj628195.aspx
Virtual Machine Manager and App Controller: http://technet.microsoft.com/en-us/library/jj628212.aspx
Categories: Deployment, System Center 2012 R2