Skip to main content

How to uninstall System Center Virtual Machine Manager

Should you have the need to uninstall SCVMM, or on of its components, the process is very easy.  You simply need to determine if you want to retain the database or not.

 

The below instructions were provided by Microsoft.  You can see how simple each one is.  Below is a screen shot of my VMM server’s Programs and Features before the uninstallation.

image

Below is the uninstallation screen for the Administration console.

image

 

This one is for the removal of the VMM Server.  Remember that if you delete the database, you lose everything.  Do this only if you do not plan on continuing to utilizes your current VMM configuration.

To uninstall the VMM Server
  1. In Control Panel, double-click Programs and Features, select Microsoft System Center Virtual Machine Manager 2008 Server (x64), and then click Uninstall.

  2. On the Uninstallation Options page, do one of the following:

    • Select Retain data if you plan to reinstall VMM server and want to resume managing virtual machines in the same host environment.
    • Select Remove data if you do not plan to reinstall VMM server and want to permanently remove the VMM database.

To uninstall the VMM Administrator Console

    1. In Control Panel, double-click Programs and Features for Windows Server 2008 or Windows Vista, or Add or Remove Programs for all other supported operating systems.

    2. Click Microsoft System Center Virtual Machine Manager 2008 Administrator Console (x64) for 64-bit operating systems orMicrosoft System Center Virtual Machine Manager 2008 Administrator Console for 32-bit operating systems, and then clickUninstall or Remove, depending on the operating system.

    3. On the Confirmation page, click Uninstall.

To uninstall the VMM Self-Service Portal
  1. In Control Panel, double-click Programs and Features for Windows Server 2008 or Add or Remove Programs for Windows Server 2003.

  2. Click Microsoft System Center Virtual Machine Manager 2008 Self-Service Portal (x64) for 64-bit operating systems or Microsoft System Center Virtual Machine Manager 2008 Self-Service Portal for 32-bit operating systems, and then click Uninstall or Remove, depending on the operating system.

  3. On the Confirmation page, click Uninstall.

To manually uninstall the VMM agent
  1. In Control Panel, double-click Programs and Features for Windows Server 2008 or Add or Remove Programs for Windows Server 2003.

  2. Click Microsoft System Center Virtual Machine Agent (x64) for 64-bit operating systems or Microsoft System Center Virtual Machine Manager Agent for 32-bit operating systems, and then click Uninstall or Remove, depending on the operating system.

  3. In the Confirmation dialog box, click Yes.

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...