Article ID: 2267, created on Oct 18, 2007, last review on May 1, 2014

  • Applies to:
  • Operations Automation

Resolution

The HMC re-installation scenario is suitable only if:

  • Customer has existing HMC 3.5 environment without Exchange 2003 deployed.
  • Existing HMC 3.5 environment is used exclusively by PEM.

Advantages:

  • No need in additional hardware for HMC 4.0 installation. The same hardware is used.
  • Existing services and users are not affected.
  • PEM provisioning configuration and customer data are not changed.

HMC re-installation consists of the following steps: 

  1. Disable MPS Provisioning Engine on MPS node
  2. Remove "MPFCustomProviders" package from MPS node
  3. Uninstall PEM Agent from MPS node
  4. Uninstall HMC 3.5
  5. Uninstall SQL Server 2000
  6. AD and System cleanup
  7. Install SQL Server 2005
  8. Configure MPS Security
  9. Install HMC 4.0
  10. Install PEM Agent on MPS node
  11. Install "MPFCustomProviders" package on MPS node
  12. Check and Process Failed Tasks

AdditionalInformation

1. Disable MPS Provisioning Engine on MPS node

To prevent provisioning requests from execution during HMC re-installation MPS Provisioning Engine needs to be disabled on MPS node as following:

1.   Run dcomcnfg.exe and open in the tree Component Services > Computers > My Computer > COM+ Applications, right-click Provisioning Engine icon and click Disable.
2.   Run perfmon.exe and select Report View (Ctrl+R).
3.   Click Add button (Ctrl+I) and in Add Counters dialog, in Performance object select Microsoft Provisioning Engine, in Select counters from list select Process Controllers Executing, and click Add and then Close.
4.   Wait until the value of Process Controllers Executing counter becomes 0, i.e. all currently executing provisioing requests are completed.

2. Remove "MPFCustomProviders" package from MPS node

Because of MPS Engine will be uninstalled, PEM package "MPFCustomProviders" should be removed from MPS node which will be upgraded to HMC 4.0

3. Uninstall PEM Agent from MPS node

To stop MPF request from PEM to MPS node which cause problems during uninstall/ install of HMC, PEM Agent should be uninstalled from MPS node.
1.    Log on to MPS node as a member of the local Administrators group
2.    Open Control Panel > Add or Remove Programs
3.    Select PEM Agent
4.    Click Remove  Important: Do not remove MPS node from PEM. Simply uninstall PEM Agent.

4. Uninstall HMC 3.5

To uninstall HMC 3.5 and all it components:
1.    Log on to MPS node as a member of the Domain Administrators group
2.    Start MPS Deployment Tool
3.    In the Requirements Status pane, expand Hosting Platform, expand Hosted Plans Satabase, expand Plans Database, right-click MPS01,.and than click Uninstall.
4.    Review the information in the Confirm Uninstall on Dependents dialog box, and then click OK.
5.    Click Start Deployment to start the uninstall process.
6.    In the Deployment Completed dialog box, click OK.
7.    In the Requirements Status pane, expand Core Platform, expand Core MPF Install, expand MPF Engine, right-click MPS01, and then click Uninstall.
8.    Review the information in the Confirm Uninstall on Dependents dialog box, and then click OK.
9.    Click Start Deployment to start the uninstall process.
10.  In the Deployment Completed dialog box, click OK.

To uninstall Microsoft Provisioning Resource Kit (if was installed):
1.    Log on to MPS node as a member of the Domain Administrators group.
2.    Open Control Panel > Add or Remove Programs.
3.    Select Microsoft Provisioning Resource Kit.
4.    Click Remove.

To uninstall MPS Deployment Tool:
1.    Log on to MPS node as a member of the Domain Administrators group.
2.    Open Control Panel > Add or Remove Programs.
3.    Select MPS Deployment Tool Build 3.5.x.x.
4.    Click Remove.

5. Uninstall SQL Server 2000

To uninstall SQL Server 2007:
1.    Log on to MPS node as a member of the Domain Administrators group.
2.    Open Control Panel > Add or Remove Programs.
3.    Select Microsoft SQL Server 2000.
4.    Click Change/Remove.
5.    Click Yes in Confirm File Deletion dialog to confirm uninstall.

6. AD and System cleanup

After uninstalling of HMC 3.5 and SQL Server 2000 some cleanup should be performed in AD and on MPS node.
First of all the existing MPS Server Config Entity Active Directory object should be renamed or removed in order to allow a clean installation of HMC 4.0 Deployment Tool. To rename MPS Server Config Entity:
1.    Log on to domain controller node as a member of the Domain Administrators group.
2.    Run the following command: ADSIEDIT.MSC Note: ADSIEDIT.MSC - Active Directory editor MMC snap-in from Windows Server 2003 Support Tools.
3.    Navigate into the following node in left pane: "Domain > [Domain DN] > System".
4.    Delete MPS Server Config Entity object or rename it to MPS Server Config Entity 3.5

Before installing SQL Server 2005 we need to cleanup old SQL Server 2000 data:
1.    Log on to MPS node as a member of the Local Administrators group.
2.    Delete SQL Server 2000 installation directory and data (usually C:\Program Files\Microsoft SQL Server).

To cleanup HMC 3.5 files:
1.    Log on to MPS node as a member of the Local Administrators group.
2.    Remove Sharing from directories C:\ConfigShare and C:\MSIShare.
3.    Delete, Rename or Move to new location directories C:\ConfigShare and C:\MSIShare.

7. Install SQL Server 2005

To install SQL Server 2005 follow the instructions from Windows Infrastructure Deployment Guide listed below.
Note: If MPSSQLService account was already created for HMC 3.5 installation, use this account as Microsoft SQL Server service account during SQL Server installation.
1.    Deploying Provisioning (HMC 4.0) -> Deploying MPS Engine Server -> Install SQL Server 2005. 2.    Deploying Provisioning (HMC 4.0) -> Deploying MPS Engine Server -> Install SQL Server 2005 Service Pack 1.

8. Configure MPS Security

To Configure MPS Security follow the instructions from Windows Infrastructure Deployment Guide listed below.
1.    Deploying Provisioning (HMC 4.0) -> Deploying MPS Engine Server -> Configure MPS Security.

9. Install HMC 4.0

To install HMC 4.0 follow the instructions from Windows Infrastructure Deployment Guide. Begin from instruction Deploying Provisioning (HMC 4.0) -> Deploying MPS Engine Server -> Install the MPS Deployment Tool and process all instruction to the end of Deploying Provisioning (HMC 4.0) -> Deploying MPS Engine Server chapter.
Note: If you receive a Select SQL Server dialog box when you run the Deployment Tool for the first time, select Cancel to prevent the deployment tool from detecting the HMC 3.5 MPS deployment.

10. Install PEM Agent on MPS node

Install PEM Agent on MPS node.
PEM Agent installation performs configuration of MPS node and skip node registration in PEM because MPS node already registered in PEM.

11. Install "MPFCustomProviders" package on MPS node

Install "MPFCustomProviders" package on MPS node From PEM CP.

12. Check and Process Failed Tasks

Some tasks may fail during HMC re-installation. Go to PEM Task Manager and restart failed tasks if any.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF