Moving from SCE2010 to SC2012, best practices

Forum: Essentials (SCE)
Viewing 3 posts - 1 through 3 (of 3 total)
  • #94540
    Profile photo of James Hodgkinson
    JasonA
    Member

    I’m looking at upgrading my employers SCE2010 to System Center 2012, and want to know what would be the suggestion to go about this.  I know I’m going to need to load several SC2012 products to get similar functionality to SCE.  It looks like what I’ll need, at a minimum are:
    Operations Manager
    Config Manager
    Virtual Machine Manager

    As we’ve also recently had our Forefront Client Protection server die, I figure to also add this component (part of OpsMgr)

    My question is, what is the best method to move from SCE to SC?  I’m going to have to use the same physical server, which does meet the requirements for SC.  Based on something I found elsewhere, I’m going to need to remove the SCE clients from the workstations / servers, then load up SC and install its client.  Is there an easy way to remove the SCE client without going to each monitor system?  Ditto for the Forefront, I’m presuming I’ll need to remove both its agent (MOM of all things) and the Forefront client before the new client gets installed.

    Any help would be appreciated,
    Jason

    #94960

    Did you end up moving forward with your migration?  If so, are there any pointers you could share to make life easier for those of us who have yet to make the change?

    #94979

    Hi Jason,

    As I understand you have System Center Essentials 2010 in your environment and you want to upgrade to System Center 2012.

    With the new license schema probably Essential product will decommissioned. There is no inplace upgrade from SCE 2010 to SC 2010 so I suggest to make a parallel upgrade. To make such upgrade I suggest to follow these general steps:

    1. Make high level designs for your System Center 2012 components.

    2. Write down a plan for migration.

    3. Install System Center 2012 components in your environment. If you have resources you can use all components as one license grants you rights to use all products. Refer to your software supplier for valid license schema.

    4. After install the components configure them on basic level. For example to do not rush to import all management packs in Operations Manager.

    5. Pick a small number of your servers (if you have test and development servers it will be best). If you have 100 servers 10 will be a good number.

    6. Trough SCCM you can create a task sequence to uninstall SCE 2010 agents on these servers and install SCCM, SCOM, DPM agents on them. You can target that task sequence to a collection of these servers and advertise it.

    7. As you have these agents install on them you can start to fine tune SCOM management packs one by one based on these servers.

    8. When you finish with the configuration of SCOM, SCCM, DPM, VMM or the other components you will use you can migrate all your other servers on different waves. During the migration you can still continue to fine tune SCOM and the other components.

    9. After the migration is over you can decommission SCE 2010 environment. Make sure before wiping SCE to have backup of your SCE 2010 servers and database because your company may be obligated to contain data for certain period of time.

    These are only general steps but I suggest to have more detail plan and design plans for the different components. Depending on how big is your environment you may have to hire some System Center consultants to help you with the designs.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.