This is a bit of a trick so I’m sharing the steps I followed. The problem arises from SCVMM 2012 not supporting SQL Express. This follows the official method as far as I can tell… not that this specific scenario is documented officially in step by step detail. If you find issues or have ideas about these steps please comment below the article. Thanks.

default_VMM_logorightgreenarrow   SCVMM 2012

Step 1 – Backup the SCVMM database

  1. Backup your SCVMM database first.
    1. In Administration view, click General, and then, in the Actions pane, click Back up Virtual Machine Manager.
    2. In the Virtual Machine Manager Backup dialog box, type the path for a destination folder for the backup file. The folder must not be a root directory and must be accessible to the SQL Server.
  2. Keep an eye on this backup file. This is what we use later during the upgrade.

 

Step 2 – Cleanup

  1. Let’s remove everything that will either cause a conflict or otherwise prevents the upgrade.
  2. Uninstall SCVMM 2008 R2 SP1
    1. Uninstall all three components
    2. Choose ‘Retain Database’ during removal of the SCVMM Server service
    3. image
    4. image
  3. Uninstall the WAIK (if it exists) from ‘Programs and Features’ in the Contol Panel.
  4. Uninstall SQL Express
    1. Stop the ‘SQL Server (MICROSOFT$VMM$)’ service under Services
    2. Uninstall SQL Express beginning with the Server component
    3. image
  5. Restart (for good measure)

 

Step 3 – Install

  1. Install SQL Server 2008 R2
  2. Install pre-requisite WAIK 7
  3. Restore the SCVMM database backup to SQL 2008 R2
    1. Open ‘SQL Server Management Studio’
    2. Login
    3. Right click ‘Databases’ on the left and select ‘Restore Database…’
    4. Choose ‘From device:’ then click the ellipse button
    5. On the ‘Specify Backup’ windows click ‘Add’ and navigate in the popup window to your SCVMM database backup. The file will end in .bak
    6. Click OK then OK again
    7. Back at the ‘Restore Database’ window locate ‘To database:’ and type ‘VirtualManagerDB’ as the new name
      1. A different name can be substituted if needed
    8. Place a checkmark in ‘Restore’ and click OK
    9. If you encounter a failure at this point read it carefully. If it refers to overwriting files, go to this location and remove the .mdf and .ldf files. Place them on your desktop. ‘C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\DB’. Then try again.
    10. Click OK to the success popup and close SQL Server Management Studio
  4. Start the install of SCVMM 2012 now. Install all components at this time as needed.
  5. At the ‘Database Configuration’ window select ‘MSSQLSERVER’ from the ‘Instance name:’ dropdown. Select ‘Existing database:’ and choose ‘VirtualManagerDB’ (or whatever name you restored it as) from the dropdown
  6. Click Next. You will see a prompt to upgrade the database. Click Yes
  7. The next screen asks for the ‘Virtual Machine Manager Service Account.’ Keep in mind two things:
    1. This is a good time to change the VMM service account from LocalSystem (if you were running under this) to a domain user
    2. If you do change the service account that will be used in 2012 from what was being used in 2008, you will lose all things that were encrypted by the previous account:
      1. Items encrypted: passwords in templates and profiles
      2. Article explaining this: Choosing Service Account and Distributed Key Management Settings During an Upgrade
      3. Article helping you decide whether to use LocalSystem or a Domain User as service account: Specifying a Service Account for VMM
  8. Having made a heavy decision on the prior step, click Next and finish the installation.
    1. Don’t forget to run the Self Service Portal under port 81!
    2. Use your existing library

Near the last step of the upgrade you are informed that it would be a good idea to follow the article below. I strongly recommend it, especially for the instructions on rebuilding your templates.

‘After System Center 2012 Virtual Machine Manager is installed, additional tasks need to be completed to finish the upgrade to System Center 2012 Virtual Machine Manager. For more information about these tasks, see Upgrading to System Center 2012 Virtual Machine Manager (http://go.microsoft.com/fwlink/?LinkID=214130).’

 

 

  jonjor