Export (0) Print
Expand All

Installing VMM from a Command Prompt

Updated: February 19, 2014

Applies To: System Center 2012 - Virtual Machine Manager, System Center 2012 R2 Virtual Machine Manager, System Center 2012 SP1 - Virtual Machine Manager

You can install Virtual Machine Manager (VMM) by using a command prompt. Installing VMM features involves saving installation settings in an .ini file and using the setup.exe command with that file.

ImportantImportant
For all of these procedures, use the Run as administrator option to open an elevated command prompt.

Installation files

Your installation media contains .ini files for each VMM feature:

  • VMServer.ini

    Settings for the VMM management server.

  • VMClient.ini

    Settings for the VMM console.

  • VMEUP.ini

    Settings for the VMM Self-Service Portal.

    noteNote
    As of System Center 2012 Service Pack 1 (SP1), the VMM Self-Service Portal has been removed.

  • VMServerUninstall.ini

    Uninstallation settings for the VMM management server.

The files contain key/value pairs that have default values. These entries are commented out. To edit the file, remove the comment symbol (#) and change the value.

Installing a VMM management server by using a command prompt

To install a VMM management server, edit the VMServer.ini file and then run the setup.exe command.

noteNote
When you install a VMM management server, the VMM console is automatically installed.

Configuring options for a VMM management server in the installation file

 

Option Values Default

ProductKey

Product key in the format: xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

UserName

Optional display name for the user who is installing the features.

noteNote
This is not the user account for the installation.

Administrator

CompanyName

Optional display name for the organization that is installing the features.

Microsoft Corporation

ProgramFiles

Location for VMM files.

C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager

CreateNewSqlDatabase

0: Use an existing Microsoft SQL Server database.

1: Create a new SQL Server database.

1

SqlInstanceName

Name of the new or existing instance of SQL Server.

MICROSOFT$VMM$

SqlDatabaseName

Name of the new or existing SQL Server database.

VirtualManagerDB

RemoteDatabaseImpersonation

0: Do not impersonate the administrator account for SQL Server.

ImportantImportant
The user that runs setup.exe must be an administrator for the server that is hosting SQL Server.

1: Impersonate the administrator account for SQL Server by using the provided credentials.

ImportantImportant
The user who runs setup.exe must provide values for the SqlDBAdminName, SqlDBAdminPassword, and SqlDBAdminDomain parameters.

0

SqlMachineName

Name of the server that is hosting SQL Server. Do not specify localhost. Instead, specify the actual name of the computer.

<sqlmachinename>

(various ports)

For information about ports, see Ports and Protocols for VMM.

IndigoTcpPort: 8100

IndigoHTTPSPort: 8101

IndigoNETTCPPort: 8102

IndigoHTTPPort: 8103

WSManTcpPort: 5985

BitsTcpPort: 443

CreateNewLibraryShare

0: Use an existing library share.

1: Create a new library share.

1

LibraryShareName

Name of the file share to be used or created.

MSSCVMMLibrary

LibrarySharePath

Location of the existing file share or the new file share to be created.

C:\ProgramData\Virtual Machine Manager Library Files

LibraryShareDescription

Description of the share.

Virtual Machine Manager Library Files

SQMOptIn

0: Do not opt in to the Customer Experience Improvement Program (CEIP).

1: Opt in to CEIP.

For more information about CEIP, see Microsoft Customer Experience Improvement Program.

For CEIP privacy information, see Privacy Statement for the Microsoft Customer Experience Improvement Program.

0

MUOptIn

0: Do not opt in to Microsoft Update.

1: Opt in to Microsoft Update.

For more information about Microsoft Update, see Frequently Asked Questions.

For Microsoft Update privacy information, see Update Services Privacy Statement.

0

VmmServiceLocalAccount

0: Use a domain account for the VMM service (scvmmservice).

1: Use the Local System account for the VMM service.

noteNote
To use a domain account, when you run setup.exe, provide values for the VMMServiceDomain, VMMServiceUserName, and VMMServiceUserPassword parameters.

For more information about service accounts, see Specifying a Service Account for VMM.

0

TopContainerName

Container for Distributed Key Management (DKM); for example, “CN=DKM,DC=contoso,DC=com”.

For more information about DKM, see Configuring Distributed Key Management in VMM.

VMMServer

HighlyAvailable

0: Do not install as highly available.

1: Install as highly available.

For information about highly available installations, see Installing a Highly Available VMM Management Server.

0

VmmServerName

Clustered service name for a highly available VMM management server.

ImportantImportant
Do not enter the name of the failover cluster or the name of the computer on which the highly available VMM management server is installed. For more information, see How to Install a Highly Available VMM Management Server.

<VMMServerName>

VMMStaticIPAddress

IP address for the clustered service name for a highly available VMM management server, if you are not using Dynamic Host Configuration Protocol (DHCP).

noteNote
Both IPv4 and IPv6 are supported.

<comma-separated-ip-for-HAVMM>

Upgrade

0: Do not upgrade from a previous version of VMM to System Center 2012 – Virtual Machine Manager.

1: Upgrade from a previous version.

1

Installing a VMM management server by using a command prompt

After you edit VMServer.ini, open an elevated command prompt, and then run setup.exe by using the following parameters:

  • /server

    Specifies installation of the VMM management server.

  • /i or /x

    Specifies whether to install (/i) or uninstall (/x) the server.

  • /f <filename>

    Specifies the .ini file to use.

    ImportantImportant
    Be sure that this parameter points to the correct .ini file. If setup.exe does not find an .ini file, it will perform the installation by using its own default values.

  • /VmmServiceDomain <domainName>

    Specifies the domain name for the account that is running the VMM service (scvmmservice). Use this parameter only if you set VmmServiceLocalAccount to 0 in VMServer.ini.

  • /VmmServiceUserName <userName>

    Specifies the user name for the account that is running the VMM service (scvmmservice). Use this parameter only if you set VmmServiceLocalAccount to 0 in VMServer.ini.

  • /VmmServiceUserPassword <password>

    Specifies the password for the account that is running the VMM service (scvmmservice). Use this parameter only if you set VmmServiceLocalAccount to 0 in VMServer.ini.

  • /SqlDBAdminDomain <domainName>

    Specifies the domain name for the administrator account for the SQL Server database. Use this parameter if the current user does not have administrative rights to SQL Server.

  • /SqlDBAdminName <userName>

    Specifies the user name for the administrator account for the SQL Server database. Use this parameter if the current user does not have administrative rights to SQL Server.

  • /SqlDBAdminPassword <password>

    Specifies the password for the administrator account for the SQL Server database. Use this parameter if the current user does not have administrative rights to SQL Server.

  • /IACCEPTSCEULA (as of System Center 2012 SP1)

    Notes acceptance of the Microsoft Software License Terms. This is a mandatory parameter.

For example, to use a VMServer.ini file that is stored in C:\Temp with a SQL Server administrator account of contoso\SQLAdmin01 and a VMM service account of contoso\VMMadmin14, use the following command:

setup.exe /server /i /f C:\Temp\VMServer.ini /SqlDBAdminDomain contoso /SqlDBAdminName SQLAdmin01 /SqlDBAdminPassword password123 /VmmServiceDomain contoso /VmmServiceUserName VMMadmin14 /VmmServiceUserPassword password456 /IACCEPTSCEULA

Uninstalling a VMM management server by using a command prompt

To uninstall a VMM management server, edit the VMServerUninstall.ini file and then run the setup.exe command.

Configuring options for uninstalling a VMM management server

 

Option Values Default

RemoteDatabaseImpersonation

0: Local SQL Server installation.

1: Remote SQL Server installation.

When you run setup.exe, provide a value for the SqlDBAdminName, SqlDBAdminPassword, and SqlDBAdminDomain parameters unless the user who is running setup.exe is an administrator for SQL Server.

Replaces the OnRemoteServer setting in VMM 2008 R2.

0

RetainSqlDatabase

0: Remove the SQL Server database.

1: Do not remove the SQL Server database.

ImportantImportant
To remove the SQL Server database, when you run setup.exe, provide a value for the SqlDBAdminName, SqlDBAdminPassword, and SqlDBAdminDomain parameters unless the user who is running Setup is an administrator for SQL Server.

0

ForceHAVMMUninstall

0: Do not force uninstallation if setup.exe cannot verify whether this node is the final node of the highly available installation.

1: Force the uninstallation.

For more information about uninstalling a highly available VMM management server, see How to Uninstall a Highly Available VMM Management Server.

0

Uninstalling a VMM management server by using a command prompt

To uninstall a VMM management server by using a VMServerUninstall.ini file that is stored in C:\Temp, with a SQL Server administrator account of contoso\SQLAdmin01, use this command:

setup.exe /server /x /f C:\Temp\VMServerUninstall.ini /SqlDBAdminDomain contoso /SqlDBAdminName SQLAdmin01 /SqlDBAdminPassword password123

Installing or uninstalling a VMM console by using a command prompt

To install a VMM console, edit the VMClient.ini file and then run the setup.exe command.

To uninstall a VMM console, run the setup.exe command. There is no separate .ini file for uninstalling the VMM console.

noteNote
Do not attempt to uninstall the VMM console from a system that includes a VMM management server. You must first uninstall the VMM management server.

Configuring options for a VMM console

 

Option Values Default

ProgramFiles

Location for VMM files.

C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager

IndigoTcpPort

Port that is used for communication between the VMM management server and the VMM console.

8100

MUOptIn

0: Do not opt in to Microsoft Update.

1: Opt in to Microsoft Update.

For more information about Microsoft Update, see Frequently Asked Questions.

For Microsoft Update privacy information, see Update Services Privacy Statement.

0

VmmServerForOpsMgrConfig

This setting is not used. For more information, see Configuring Operations Manager Integration with VMM.

<VMMServerName>

Installing a VMM console by using a command prompt

After you edit VMClient.ini, use an elevated command prompt to run setup.exe by using the following parameters:

  • /client

    Specifies installation of the VMM console.

  • /i or /x

    Specifies whether to install (/i) or uninstall (/x) the console.

  • /f <filename>

    Specifies the .ini file to use.

    ImportantImportant
    Be sure that this parameter points to the correct .ini file. If setup.exe does not find an .ini file, it will perform the installation by using its own default values.

  • /opsmgr

    Specifies whether to configure a preinstalled instance of System Center Operations Manager 2007.

    CautionCaution
    Do not use this parameter. For more information, see Configuring Operations Manager Integration with VMM.

For example, to use a VMClient.ini file that is stored in C:\Temp, use this command:

setup.exe /client /i /f C:\Temp\VMClient.ini

Installing the VMM Self-Service Portal by using a command prompt

noteNote
In System Center 2012 SP1, the VMM Self-Service Portal has been removed.

To install the VMM Self-Service Portal, edit the VMEUP.ini file and then run the setup.exe command.

To uninstall the VMM Self-Service Portal, run the setup.exe command. There is no separate .ini file for uninstalling the VMM Self-Service Portal.

Configuring options for the VMM Self-Service Portal installation

 

Option Values Default

ProgramFiles

Location in which to store program files.

C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager

VmmServerName

Name of the VMM management server that this VMM Self-Service Portal connects to.

<machineName>

IndigoTcpPort

Port that is used for communication between the VMM management server and the VMM Self-Service Portal.

8100

SelfServicePortalTcpPort

Port that users use to connect to the VMM Self-Service Portal.

80

SelfServicePortalHeader

If other websites on this server are using the same port, specify a header for the VMM Self-Service Portal.

For more information about headers, see How to Install the VMM Self-Service Portal.

<headerName>

MUOptIn

0: Do not opt in to Microsoft Update.

1: Opt in to Microsoft Update.

For more information about Microsoft Update, see Frequently Asked Questions.

For Microsoft Update privacy information, see Update Services Privacy Statement.

0

Installing or uninstalling the VMM Self-Service Portal by using a command prompt

After you edit VMEUP.ini, use an elevated command prompt to run setup.exe by using the following parameters:

  • /eup

    Specifies installation of the VMM Self-Service Portal.

  • /i or /x

    Specifies whether to install (/i) or uninstall (/x) the VMM Self-Service Portal.

  • /f <filename>

    Specifies the .ini file to use.

    ImportantImportant
    Be sure that this parameter points to the correct .ini file. If setup.exe does not find an .ini file, it will perform the installation by using its own default values.

To use a VMEUP.ini file that is stored in C:\Temp to install the VMM Self-Service Portal, use this command:

setup.exe /eup /i /f C:\Temp\VMEUP.ini

To uninstall the VMM Self-Service Portal, use this command:

setup.exe /eup /x

See Also

-----
For additional resources, see Information and Support for System Center 2012.

Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.
-----
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft