Export (0) Print
Expand All

How to Install Exchange 2007 in Unattended Mode

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007

Topic Last Modified: 2007-12-11

This topic explains how to use Setup from a Command Prompt window to install Microsoft Exchange Server 2007 in unattended mode. To perform an unattended setup, you must install Exchange 2007 from the command prompt.

noteNote:
After you install any Exchange 2007 server roles on a computer, you cannot use the Exchange Server 2007 Setup wizard to add any additional server roles to this computer. For more information about modifying an installation, see How to Modify an Exchange Installation.

Before you perform the procedure in this topic, be aware of the following:

  • For e-mail messages to flow correctly, you must install both the Mailbox server role and the Hub Transport server role in each Active Directory directory service server site.

  • For client access to work correctly, you must install a Client Access server in each Active Directory site that has a Mailbox server.

  • You can install the Mailbox server role, the Hub Transport server role, the Client Access server role, and the Unified Messaging (UM) server role on the same computer or on separate computers.

  • Confirm that your organization meets the requirements that are listed in Exchange 2007 System Requirements.

  • To perform the following procedure, the account you use must be delegated membership in the Schema Administrators group if you have not previously prepared the Active Directory schema. If you are installing the first Exchange 2007 server in the organization, the account you use must have membership in the Enterprise Administrators group. If you have already prepared the schema and are not installing the first Exchange 2007 server in the organization, the account you use must be delegated the Exchange Organization Administrator role. For more information about permissions, delegating roles, and the rights that are required to administer Exchange 2007, see Permission Considerations.

    noteNote:
    When you install Exchange 2007, Setup will create a mailbox for the Administrator user account. When Exchange 2007 creates a mailbox, by default, if an alias is not specified, Exchange 2007 uses the user principal name (UPN) and converts all non-ASCII characters to underscore (_) characters. In some languages that use nonstandard character sets, the Administrator user account has by default a non-ASCII value for the UPN. In this case, after you install Exchange 2007, the Administrator account alias will be changed to all underscore characters. To avoid this, confirm that the Administrator account has an ASCII UPN before you install Exchange 2007.

  1. Log on to the server on which you want to install Exchange 2007.

  2. Insert the Exchange 2007 DVD into the DVD drive, and then, at the command prompt, navigate to the DVD drive, or navigate to the network location of the Exchange 2007 installation files.

  3. At the command prompt, run the following command:

    Setup.com [/mode:<setup mode>] [/roles:<server roles to install>] [/OrganizationName:<name for the new Exchange organization>] [/TargetDir:<target directory>] [/SourceDir:<source directory>][/UpdatesDir:<directory from which to install updates>] [/DomainControler <FQDN of domain controller>] [/AnswerFile <filename>] [/DoNotStartTransport] [/EnableLegacyOutlook] [/LegacyRoutingServer] [/EnableErrorReporting] [/NoSelfSignedCertificates] [/AdamLdapPort <port>] [/AdamSslPort <port>] [/AddUmLanguagePack:<UM language pack name>] [/RemoveUmLanguagePack:<UM language pack name>] [/NewProvisionedServer] [/RemoveProvisionedServer] [/ForeignForestFQDN] [/ServerAdmin <user or group>] [/NewCms] [/RemoveCms] [/RecoverCms] [/CmsName:<name>] [/CmsIPAddress:<IP address>] [/CmsIPv4Addresses] [/CmsIPv4Networks] [/CmsIPv6Networks] [/CmsSharedStorage] [/CmsDataPath:<CMS data path>] [/UpgradeCms][/?]
    
    • /mode:<setup mode>, or /m:<setup mode>

      You must use the /mode parameter to specify the setup mode. If you do not specify a mode, Setup uses the default Install mode. Select one of the following modes:

      Install   Use this mode to install a new Exchange 2007 server or to add server roles to an existing Exchange 2007 server.

      Upgrade   Use this mode to upgrade from the release to manufacturing (RTM) version of Exchange 2007 to Exchange 2007 SP1. Setup will upgrade all server roles that are currently installed.

      You cannot perform an in-place upgrade from Exchange Server 2003 or Exchange 2000 Server to Exchange 2007.

      If you are upgrading a clustered mailbox server (CMS), use Setup /m:upgrade to upgrade only the passive node. You must use Setup /UpgradeCms to upgrade the active node.

      Uninstall   Use this mode without parameters to completely uninstall Exchange 2007 from a server. Or use this mode with the /roles parameter to remove specific server roles. To uninstall the active node of a CMS, you must first run Setup with the /RemoveCMS parameter, and then run Setup in uninstall mode.

      RecoverServer   Use this mode to restore Exchange files and local configuration settings on a new server or on a server that experienced a disaster and has been rebuilt. Do not specify the roles to restore. Setup detects the Exchange Server object in Active Directory and installs the corresponding files and configuration automatically. After you recover the server, you can restore databases and reconfigure any additional settings. For more information about recovering a server, see Understanding Setup /M:RecoverServer.

      To run in RecoverServer mode, you cannot have Exchange installed on the server. The Exchange Server object must exist in Active Directory. The recovered server must have the same name as the Exchange Server object in Active Directory.

      To recover a clustered server node, run Setup.com with the /mode:RecoverServer parameter, and then run Setup.com with the /RecoverCms parameter to restore the CMS.

    • /roles:<server roles>, or /role:<server roles> or /r:<server roles>

      You must use the /roles parameter to specify which server roles to install or uninstall. Select from one or more of the following roles, in a comma-separated list:

      ClientAccess (or CA, or C)

      EdgeTransport (or ET, or E)

      noteNote:
      The Edge Transport server role cannot coexist on the same computer with any other server role.
      noteNote:
      You must deploy the Edge Transport server role in the perimeter network and outside the Active Directory forest.

      HubTransport (or HT, or H)

      Mailbox (or MB, or M)

      UnifiedMessaging (or UM, or U)

      ManagementTools (or MT, or T)

      noteNote:
      If you select ManagementTools, you will install the Exchange Management Console, the Exchange cmdlets for the Exchange Management Shell, the Exchange Help file, the Microsoft Exchange Server Best Practices Analyzer Tool, and the Exchange Troubleshooting Assistant Tool. The management tools will be installed automatically if you install any other server role.

      For example, to specify the Client Access and Mailbox server roles, specify the following: Setup /roles:ClientAccess,Mailbox or alternatively, specify the following: Setup /r:C,M.

    • [/OrganizationName:<organization name>, or /on:<organization name>]

      Use the /OrganizationName parameter to specify the name to give the new Exchange organization. This parameter is required if you are installing the first server in an organization, and you have not run Setup /PrepareAD. If you are installing a server in an existing Exchange organization or if you have already run Setup /PrepareAD, you cannot use this parameter.

      noteNote:
      In the Exchange Server 2007 Setup wizard, the default value is First Organization. In the command-line version of Setup, there is no default value.

      The Exchange organization name can contain only the following characters:

      A through Z

      a through z

      0 through 9

      Space (not leading or trailing)

      Hyphen or dash

      The organization name cannot contain more than 64 characters. The organization name cannot be blank. If the organization name contains spaces, you must enclose it in quotation marks.

    • [/TargetDir:<destination folder>, or /t:<destination folder>]

      Use the /TargetDir parameter to specify the location to install Exchange 2007 files. The default location is %ProgramFiles%\Microsoft\Exchange Server. You cannot install Exchange 2007 to a root directory such as C:\. You cannot install Exchange 2007 on a ROM drive, RAM disk, network drive, removable disk, or unknown drive type. You cannot change the installation directory if Exchange is already installed on the server (for example, if you are adding a server role). If the destination folder contains spaces, you must enclose it in quotation marks. If you do not include the quotation marks, Setup will fail with the following error message: "An error occurred while creating the IIS virtual directory."

    • [/SourceDir:<source folder>, or /s:<source folder>]

      Use the /SourceDir parameter to specify the location from which to install Exchange 2007 files when you are adding a server role to an existing Exchange 2007 server and if the source folder is not the folder from which you are running Setup. The default value is the current directory from which you are running Setup. If the source folder contains spaces, you must enclose it in quotation marks.

    • [/UpdatesDir:<updates folder>, or /u:<updates folder>]

      Use the /UpdatesDir parameter to specify the directory from which updates will be installed. If the updates folder contains spaces, you must enclose it in quotation marks. Files in the Updates directory must be either an Updates.exe file, or one or more *.msp files. Setup will install the updates before installing the Exchange server roles specified.

      By default, Setup uses the Updates folder that is in the root folder of the installation media. If you want Setup to search for updates in a different folder instead of in the default Updates folder, use this parameter. You can specify only one folder for updates.

    • [/DomainController:<FQDN of domain controller>, or /dc:<FQDN of domain controller>]

      Use the /DomainController parameter to specify the domain controller to use to read from and write to Active Directory during setup. You can use NetBIOS or fully qualified domain name (FQDN) format. The domain controller that you specify must be in the same Active Directory site as the server on which you run Setup and must be running Windows Server 2003 SP1. If you do not use this parameter, Setup will select a domain controller to use.

      To run Setup /PrepareSchema or Setup /PrepareAD, or to install the first Exchange 2007 server in an organization if you have not run Setup /PrepareAD, Setup must use the schema master domain controller to read from and write to Active Directory. If you specify a domain controller that is not the schema master, Setup will stop and return an error message.

      If you have any domain controllers that are running Windows 2000 Server, when you prepare Active Directory and domains for Exchange 2007 and when you install Exchange 2007, you must run Setup.com from a Command Prompt window, and you must use the /DomainController parameter to specify a domain controller that is running Windows Server 2003 SP1. When you prepare Active Directory and domains for Exchange 2007 SP1 and when you install Exchange 2007 SP1, you do not need to specify a Windows Server 2003 SP1 domain controller.

    • [/AnswerFile:<filename>, or /a:<filename>]

      Use the /AnswerFile parameter to specify the location of a file that contains parameters for Setup. You can use this file to install multiple computers with the same parameters. You cannot use this parameter when installing a CMS. When installing a stand-alone server, you can use the following parameters in the answer file: EnableLegacyOutlook, LegacyRoutingServer, ServerAdmin, ForeignForestFQDN, OrganizationName, DoNotStartTransport, UpdatesDir, EnableErrorReporting, NoSelfSignedCertificates, AdamLdapPort, and AdamSslPort.

      noteNote:
      Do not include the slash mark (/) with the parameters in the answer file.

      The following is an example of the Setup command to use an answer file called AnswerFile01.txt:

      Setup.com /Mode:Install /Roles:Mailbox /AnswerFile:C:\AnswerFile01.txt
      
    • [/DoNotStartTransport]

      Use the /DoNotStartTransport parameter to specify that the Microsoft Exchange Transport service will not start when Setup completes. By default, Setup starts the Microsoft Exchange Transport service after installing either the Hub Transport or Edge Transport server role. If you need to do additional configuration before the Edge Transport or Hub Transport server accepts e-mail messages, for example, configuring anti-spam agents, you should use this parameter. We recommend that you use this parameter when you use the /RecoverServer parameter to recover a Hub Transport or Edge Transport server so that you can move the queue database from the failed server to the correct location on the new server before starting the Microsoft Exchange Transport service.

      noteNote:
      The /DoNotStartTransport parameter cannot be combined with Setup /m:Upgrade.

      noteNote:
      The Microsoft Exchange Transport service runs only on the Hub Transport and Edge Transport server roles.
    • [/EnableLegacyOutlook]

      Use the /EnableLegacyOutlook parameter to specify that you have client computers that are running Microsoft Outlook 2003 or earlier. Exchange 2007 will create a public folder database on the Mailbox server. If all of your client computers are running Office Outlook 2007, public folders are optional in Exchange 2007. If you do not use this parameter, Exchange 2007 will not create a public folder database on the Mailbox server. You can add a public folder database later.

      You can only use this parameter if you are installing the first Mailbox server in an organization.

      When you install the first Mailbox server in an existing Exchange 2003 or Exchange 2000 organization, by default, Setup will create the public folder database on the Exchange 2007 server. You do not need to specify this parameter. Setup will not create a public folder database on subsequent Mailbox server installations in this organization.

    • [/LegacyRoutingServer]

      Use the /LegacyRoutingServer parameter to specify an Exchange 2003 or Exchange 2000 bridgehead server that is located in the routing group to which you will create the initial routing group connector. A routing group connector is required for mail flow between Exchange 2007 and either Exchange 2003 or Exchange 2000 when Exchange server versions coexist in the same organization.

      You can use this parameter only if you are installing the first Hub Transport server in the organization and if you have Exchange 2003 or Exchange 2000 servers in the existing organization. In this scenario, this parameter is required to establish mail flow between Exchange 2007 and Exchange 2003 or Exchange 2000.

    • [/EnableErrorReporting]

      Use the /EnableErrorReporting parameter to enable error reporting during Setup. If you decide to enable error reporting, the Microsoft Error Reporting Service collects information about how you use Exchange 2007 and about any issues you may encounter. This information is used to help Microsoft diagnose problems and provide solutions.

      You can use this parameter only if you are running Setup in Install mode.

      If you enable error reporting, Setup sets the following registry key to 0:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\DisableErrorReporting

      By default, this registry key is 1 and error reporting is disabled.

    • [/NoSelfSignedCertificates]

      Use the /NoSelfSignedCertificates parameter if you do not want Setup to create self-signed certificates in the case where no other valid certificate is found for Secure Sockets Layer (SSL) or Transport Layer Security (TLS) sessions. If you do not have a certificate, communication between clients and the Client Access or Unified Messaging server will be unencrypted.

      You can only use this parameter if you are installing either the Client Access server role or the Unified Messaging server role.

    • [/AdamLdapPort:<port>]

      Use the /AdamLdapPort parameter to specify the Lightweight Directory Access Protocol (LDAP) port to use for the Edge Transport server role Active Directory Application Mode (ADAM) instance. You can specify any valid unused port number. The default value is 50389. Exchange stores the ADAM LDAP port in the following registry key:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\EdgeTransportRole\AdamSettings\MSExchange\LdapPort

      You can use this parameter only if you are installing the Edge Transport server role.

    • [/AdamSslPort:<port>]

      Use the /AdamSslPort parameter to specify the SSL port to use for the Edge Transport server role ADAM instance. You can specify any valid unused port number. The default value is 50636. Exchange stores the ADAM SSL port in the following registry key:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\EdgeTransportRole\AdamSettings\MsExchangeAdam\SslPort

      You can use this parameter only if you are installing the Edge Transport server role.

    • [/AddUmLanguagePack:<UM language pack name1>, <UM language pack name2>, …]

      Use the /AddUmLanguagePack parameter to specify a UM language pack that you want to add. If you add a UM language pack, callers and Outlook Voice Access users can interact with the UM system in another language. For a list of Unified Messaging languages, see Understanding Unified Messaging Languages.

      To install a UM language pack, the Unified Messaging server role must already be installed.

      By default, when Setup installs the Unified Messaging server role, it also installs the en-US language pack and the language pack for the language of the Exchange server.

      When you add a language pack, by default, Setup expects the language pack .msi file to be in the ServerRoles\UnifiedMessaging directory of the installation directory. To specify a different location, use the /SourceDir parameter.

      noteNote:
      Do not include "umlang-" or the .msi extension in the language pack name. For example, the German language pack is umlang-de-DE.msi. To install this language pack, run the following command: Setup.com /AddUmLanguagePack:de-DE.
      noteNote:
      You cannot install a language pack by running the language pack .msi file. You must use Setup.com to install the language pack.
    • [/RemoveUmLanguagePack:<UM language pack name>]

      Use the /RemoveUmLanguagePack parameter to specify a Unified Messaging language pack that you want to remove. For a list of Unified Messaging languages, see Understanding Unified Messaging Languages.

      You cannot remove the en-US language pack. This language pack is required, in addition to any other language packs.

      noteNote:
      Do not include "umlang-" or the .msi extension in the language pack name. For example, the German language pack is umlang-de-DE.msi. To remove this language pack, run the following command: Setup.com /RemoveUmLanguagePack:de-DE.
      noteNote:
      You cannot remove a language pack by running the language pack .msi file. You must use Setup.com to remove the language pack.
    • [/NewProvisionedServer:<server name>, or /nprs:<server name>]

      Use the /NewProvisionedServer parameter to create a placeholder server object in Active Directory so that you can delegate the setup of a server. If you provide permissions to this server object for a user who has Exchange Server Administrators role permissions, that user can install Exchange 2007 on the server. During Setup, additional attributes on this server object will be added. If you do not specify a server name, Setup.com will create a placeholder server object in Active Directory for the local server. You can use the /ServerAdmin parameter with the /NewProvisionedServer parameter to specify the user or group that will have permissions to the provisioned server.

      To run Setup.com with the /NewProvisionedServer parameter, you must be delegated the Exchange Organization Administrators role, you must have an existing Exchange organization in Active Directory, and you must have at least one Exchange 2007 server installed in the organization. The server that you specify must have a machine account in Active Directory.

      After you provision a server with the /NewProvisionedServer parameter, you can view the server in the Exchange Management Console or in the results of the Get-ExchangeServer cmdlet.

    • [/RemoveProvisionedServer:<server name>, or /rprs:<server name>]

      Use the /RemoveProvisionedServer parameter to remove a placeholder server object that was created using the NewProvisionedServer parameter. You can remove the server object at any time before you install Exchange 2007 on that server. After you install Exchange 2007, you cannot use this parameter to remove the server object. You can use this parameter only to remove a provisioned server object. If you run Setup.com with the /RemoveProvisionedServer parameter on a server that has Exchange 2007 installed, Setup.com will complete successfully, but the server object will not be removed.

      If you do not specify a server name, Setup.com will remove the placeholder server object in Active Directory that has the same name as the local server.

      To run Setup.com with the /RemoveProvisionedServer parameter, you must be delegated the Exchange Organization Administrators role.

    • [/ForeignForestFQDN]

      Use the /ForeignForestFQDN parameter if you are in a cross-forest or resource forest scenario and want a user in one forest to administer Exchange 2007 in another forest. For more information, see How to Configure Cross-Forest Administration.

      You must use the /PrepareAD parameter with the /ForeignForestFQDN parameter. You must run Setup.com with the /ForeignForestFQDN parameter from a computer in a forest with an Exchange 2007 organization.

    • [/ServerAdmin:<user or group>]

      Use the /ServerAdmin parameter to specify a user or group account that will have permissions to a provisioned Exchange server. The account that you specify will be delegated the Exchange Server Administrators role for the server that you specify. You can view the Exchange Server Administrators role in the Exchange Management Console or in the results of the Get-ExchangeAdministrator cmdlet. You can use this parameter only if you use the /NewProvisionedServer parameter.

    • [/NewCms]

      Use the /NewCms parameter to create a new Exchange 2007 CMS. This parameter creates the Exchange server object in Active Directory for the CMS. The computer where you run Setup.com with the /NewCms parameter will be the active node of the cluster. You can run Setup.com with the /NewCms parameter on a clustered computer on which you want to install Exchange 2007 or on a computer that is currently a passive node of an Exchange cluster. If you run Setup.com with the /NewCms parameter on the passive node of a CMS, the node will become the active node. If you use the /NewCms parameter, you must also use the /CmsName parameter and one or more of the following IP address parameters: /CmsIPAddress, /CmsIPv4Addresses, /CmsIPv4Networks, /CmsIPv6Networks. To use the /CmsIPv4Addresses, /CmsIPv4Networks, /CmsIPv6Networks parameters, you must be running a Windows Server 2008 cluster.

      noteNote:
      You can install only the Mailbox server role on a cluster.
    • [/RemoveCms]

      Use the /RemoveCms parameter to specify that you want to remove an Exchange 2007 CMS. If you use the /RemoveCms parameter, you must also use the /CmsName parameter. Running Setup.com with the /RemoveCms and /CmsName parameters removes the Exchange server object from Active Directory. When the Exchange server object is removed, that node becomes a passive node in the cluster. If you also use the /mode:uninstall parameter, Setup.com will first remove the CMS, and then completely uninstall Exchange from the server, including uninstalling the Mailbox server role.

      You must run Setup.com with the /RemoveCms parameter on the computer that hosts the CMS. You cannot run it remotely.

    • [/RecoverCms]

      Use the /RecoverCms parameter to specify that you want to recover an Exchange 2007 CMS. Setup.com will use the configuration information for the CMS that is already in Active Directory. The node on which you run this command becomes the active node of the cluster. If you use the /RecoverCms parameter, you must also use the /CmsName and one or more of the following IP address parameters: /CmsIPAddress, /CmsIPv4Addresses, /CmsIPv4Networks, /CmsIPv6Networks. You can specify an IP address that is different from the IP address that was used before the CMS was recovered.

    • [/CmsName:<name of CMS>, or /cn:<name of CMS>]

      Use the /CmsName parameter to specify the name of the Exchange 2007 CMS. The CMS name must be unique. This is not the same name as the name of the Microsoft Windows cluster.

      When you use this parameter with the /NewCms parameter, it specifies the name that you will give to the new CMS. When you use this parameter with the /RemoveCms or /RecoverCms parameter, it specifies the CMS to remove or recover.

    • [/CmsIPAddress:<IP address>, or /cip:<IP address>]

      Use the /CMSIPAddress parameter to specify the static IPv4 address of the Exchange 2007 CMS. The IP address is not the same as the IP address of the Windows cluster, but it must be in the same subnet as the Windows cluster. For clusters that have more than one subnet, if you are running a Windows Server 2008 cluster, use either /CmsIPv4Addresses or /CmsIPv4Networks instead of /CmsIPAddress.

      When you use this parameter with the /NewCms parameter, it specifies the IP address that you will assign to the new CMS. When you use this parameter with the /RecoverCms parameter, you can use it to specify the CMS to recover, or you can use it to specify a new static IP address.

      This parameter does not support IP version 6 (IPv6).

      You cannot use this parameter with any of the following parameters; CmsIPv4Addresses, CmsIPv4Networks, CmsIPv6Networks.

    • [/CmsIPv4Addresses:<comma-separated list of one or two static IPv4 addresses for the CMS>]

      Use the /CmsIPv4Addresses parameter to specify either one or two static IPv4 addresses for the CMS. In Windows Server 2008, a cluster can have dependencies on up to two IP address resources. For more information, see IPv6 Support in Exchange 2007 SP1 and SP2.

      You can use this parameter to configure Exchange on multiple subnets. In this case, each static IPv4 address should correspond to a different subnet.

      This parameter is available only if you are installing Exchange 2007 SP1 on Windows Server 2008.

      /CmsIPv4Addresses and /CmsIPv4Networks are exclusive of each other.

      You cannot use the /CmsIPv4Addresses parameter with the /CmsIPAddress parameter.

    • [/CmsIPv4Networks:<comma-separated list of one or two IPv4 cluster network names>]

      Use the /CmsIPv4Networks parameter to specify that you want to use a Dynamic Host Configuration Protocol (DHCP) IPv4 address for the network that you specify.

      To view the name of cluster network, either use Cluster Administrator, or run cluster.exe network from a Command Prompt window.

      To view the available networks that span multiple networks, use the Cluster.exe command line application in the following command: cluster network.

      This parameter is supported only if you are installing Exchange 2007 SP1 on Windows Server 2008.

      CmsIPv4Addresses and CmsIPv4Networks are exclusive of each other.

      You cannot use the /CmsIPv4Networks parameter with the /CmsIPAddress parameter.

    • [/CmsIPv6Networks:<comma-separated list of one or two public cluster network names>]

      Use the /CmsIPv6Networks parameter to specify that you want to use a Dynamic Host Configuration Protocol (DHCP) IPv6 address for the network that you specify.

      To view the available networks that span multiple networks, use the Cluster.exe command line application in the following command: cluster network.

      This parameter is supported only if you are installing Exchange 2007 SP1 on Windows Server 2008.

    noteNote:
    The /CmsIPAddress parameter, which was a required parameter for /NewCms and /RecoverCms in Exchange 2007 RTM is still used to specify a single static IPv4 address for the CMS. However, in Exchange 2007 SP1, the /CmsIPAddress parameter is optional. If you install Exchange 2007 SP1 on Windows Server 2003, you must use /CmsIPAddress to specify a single IPv4 address. If you install Exchange 2007 SP1 on Windows Server 2008, you can use any of the parameters that are available for specifying static or dynamic IP addresses.
    You cannot use the /CmsIPv6Networks parameter with the /CmsIPAddress parameter.
    • [/CmsSharedStorage, or /css]

      Use the /CMSSharedStorage parameter to specify that this cluster is a Single Copy Cluster (SCC) and the cluster node uses shared storage. By default, the cluster node will not use shared storage. If you specify this parameter, the database and log data are stored on a shared disk. There is a single copy of the data. The shared disk must have a physical disk resource in the cluster.

      If you are creating a single copy cluster, you must use both the /CmsSharedStorage and /CmsDataPath parameters. You can use this parameter only when you are creating a new CMS. If you use this parameter, you must also specify the /CmsDataPath parameter.

    • [/CmsDataPath:<data path>, or /cdp:<data path>]

      Use the /CmsDataPath parameter to specify the path for shared disks. To use this parameter, the data path that you specify must exist, and it must have a physical disk resource in the cluster. If you are creating a single copy cluster, you must use both the /CmsSharedStorage and /CmsDataPath parameters.

    • [/UpgradeCms]

      Use the /UpgradeCms parameter upgrade the active node of a CMS in either a cluster continuous replication (CCR) environment or a single copy cluster (SCC) environment to Exchange 2007 SP1.

      For more information about upgrading the active node in a CCR environment, see How to Upgrade a Clustered Mailbox Server in a CCR Environment to Exchange 2007 SP1 or later.

      For more information about upgrading the active node in an SCC environment, see How to Upgrade a Single Copy Cluster to Exchange 2007 SP1 or later.

    • [/?]

      Use the /? parameter to display Help for the Setup.com command.

  4. Setup copies the setup files locally to the computer on which you are installing Exchange 2007.

  5. Setup checks the prerequisites, including all prerequisites specific to the server roles that you are installing. If you have not met all of the prerequisites, Setup fails and returns an error message that explains the reason for the failure. If you have met all of the prerequisites, Setup installs Exchange 2007.

  6. Verify that the installation completed successfully. For more information, see Verifying an Exchange 2007 Installation.

  1. Log on to the server on which you want to install Exchange 2007.

  2. Insert the Exchange 2007 DVD into the DVD drive. From a command prompt, navigate to the DVD drive.

  3. From a command prompt, run the following command:

    Setup.com [/mode:<setup mode>] [/roles:<server roles to install>] [/OrganizationName:<name for the new Exchange organization>] [/TargetDir:<target directory>] [/SourceDir:<source directory>][/UpdatesDir:<directory from which to install updates>] [/DomainControler <FQDN of domain controller>] [/AnswerFile <filename>] [/DoNotStartTransport] [/EnableLegacyOutlook] [/LegacyRoutingServer] [/EnableErrorReporting] [/NoSelfSignedCertificates] [/AdamLdapPort <port>] [/AdamSslPort <port>] [/AddUmLanguagePack:<UM language pack name>] [/RemoveUmLanguagePack:<UM language pack name>] [/NewProvisionedServer] [/RemoveProvisionedServer] [/ForeignForestFQDN] [/ServerAdmin <user or group>] [/NewCms] [/RemoveCms] [/RecoverCms] [/CmsName:<name>] [/CmsIPAddress:<IP address>] [/CmsSharedStorage] [/CmsDataPath:<CMS data path>] [/?]
    
    • /mode:<setup mode>, or /m:<setup mode>

      You must use the /mode parameter to specify the setup mode. If you do not specify a mode, Setup uses the default Install mode. Select one of the following modes:

      Install   Use this mode to install a new Exchange 2007 server or to add server roles to an existing Exchange 2007 server.

      Uninstall   Use this mode without parameters to completely uninstall Exchange 2007 from a server. Or use this mode with the /roles parameter to remove specific server roles. To uninstall the active node of a CMS, you must first run Setup with the /RemoveCMS parameter, and then run Setup in uninstall mode.

      RecoverServer   Use this mode to restore Exchange files and local configuration settings on a new server or on a server that experienced a disaster and has been rebuilt. Do not specify the roles to restore. Setup detects the Exchange Server object in Active Directory and installs the corresponding files and configuration automatically. After you recover the server, you can restore databases and reconfigure any additional settings. For more information about recovering a server, see Understanding Setup /M:RecoverServer.

      To run in RecoverServer mode, you cannot have Exchange installed on the server. The Exchange Server object must exist in Active Directory. The recovered server must have the same name as the Exchange Server object in Active Directory.

      To recover a clustered server node, run Setup.com with the /mode:RecoverServer parameter, and then run Setup.com with the /RecoverCms parameter to restore the CMS.

    • /roles:<server roles>, or /role:<server roles> or /r:<server roles>

      You must use the /roles parameter to specify which server roles to install or uninstall. Select from one or more of the following roles, in a comma-separated list:

      ClientAccess (or CA, or C)

      EdgeTransport (or ET, or E)

      noteNote:
      The Edge Transport server role cannot coexist on the same computer with any other server role.
      noteNote:
      You must deploy the Edge Transport server role in the perimeter network and outside the Active Directory forest.

      HubTransport (or HT, or H)

      Mailbox (or MB, or M)

      UnifiedMessaging (or UM, or U)

      ManagementTools (or MT, or T)

      noteNote:
      If you select ManagementTools, you will install the Exchange Management Console, the Exchange cmdlets for the Exchange Management Shell, the Exchange Help file, the Microsoft Exchange Server Best Practices Analyzer Tool, and the Exchange Troubleshooting Assistant Tool. The management tools will be installed automatically if you install any other server role.

      For example, to specify the Client Access and Mailbox server roles, specify the following: Setup /roles:ClientAccess,Mailbox or alternatively, specify the following: Setup /r:C,M.

    • [/OrganizationName:<organization name>, or /on:<organization name>]

      Use the /OrganizationName parameter to specify the name to give the new Exchange organization. This parameter is required if you are installing the first server in an organization, and you have not run Setup /PrepareAD. If you are installing a server in an existing Exchange organization or if you have already run Setup /PrepareAD, you cannot use this parameter.

      noteNote:
      In the Exchange Server 2007 Setup wizard, the default value is First Organization. In the command-line version of Setup, there is no default value.

      The Exchange organization name can contain only the following characters:

      A through Z

      a through z

      0 through 9

      Space (not leading or trailing)

      Hyphen or dash

      The organization name cannot contain more than 64 characters. The organization name cannot be blank. If the organization name contains spaces, you must enclose it in quotation marks.

    • [/TargetDir:<destination folder>, or /t:<destination folder>]

      Use the /TargetDir parameter to specify the location to install Exchange 2007 files. The default location is %programfiles%\Microsoft\Exchange Server. You cannot install Exchange 2007 to a root directory such as C:\. You cannot install Exchange 2007 on a ROM drive, RAM disk, network drive, removable disk, or unknown drive type. You cannot change the installation directory if Exchange is already installed on the server (for example, if you are adding a server role). If the destination folder contains spaces, you must enclose it in quotation marks.

    • [/SourceDir:<source folder>, or /s:<source folder>]

      Use the /SourceDir parameter to specify the location from which to install Exchange 2007 files when you are adding a server role to an existing Exchange 2007 server and if the source folder is not the folder from which you are running Setup. The default value is the current directory from which you are running Setup. If the source folder contains spaces, you must enclose it in quotation marks.

    • [/UpdatesDir:<updates folder>, or /u:<updates folder>]

      Use the /UpdatesDir parameter to specify the directory from which updates will be installed. If the updates folder contains spaces, you must enclose it in quotation marks. Files in the Updates directory must be either an Updates.exe file, or one or more *.msp files. Setup will install the updates before installing the Exchange server roles specified.

      By default, Setup uses the Updates folder that is in the root folder of the installation media. If you want Setup to search for updates in a different folder instead of in the default Updates folder, use this parameter. You can specify only one folder for updates.

    • [/DomainController:<FQDN of domain controller>, or /dc:<FQDN of domain controller>]

      Use the /DomainController parameter to specify the domain controller to use to read from and write to Active Directory during setup. You can use NetBIOS or fully qualified domain name (FQDN) format. The domain controller that you specify must be in the same Active Directory site as the server on which you run Setup and must be running Windows Server 2003 SP1. If you do not use this parameter, Setup will select a domain controller to use.

      To run Setup /PrepareSchema or Setup /PrepareAD, or to install the first Exchange 2007 server in an organization if you have not run Setup /PrepareAD, Setup must use the schema master domain controller to read from and write to Active Directory. If you specify a domain controller that is not the schema master, Setup will stop and return an error message.

      If you have any domain controllers that are running Windows Server 2000, when you prepare Active Directory and domains for Exchange 2007 and when you install Exchange 2007, you must run Setup.com from a Command Prompt window, and you must use the /DomainController parameter to specify a domain controller that is running Windows Server 2003 SP1.

    • [/AnswerFile:<filename>, or /a:<filename>]

      Use the /AnswerFile parameter to specify the location of a file that contains parameters for Setup. You can use this file to install multiple computers with the same parameters. You cannot use this parameter when installing a CMS. When installing a stand-alone server, you can use the following parameters in the answer file: EnableLegacyOutlook, LegacyRoutingServer, ServerAdmin, ForeignForestFQDN, OrganizationName, DoNotStartTransport, UpdatesDir, EnableErrorReporting, NoSelfSignedCertificates, AdamLdapPort, and AdamSslPort.

      noteNote:
      Do not include the slash mark (/) with the parameters in the answer file.

      The following is an example of the Setup command to use an answer file called AnswerFile01.txt:

      Setup.com /Mode:Install /Roles:Mailbox /AnswerFile:C:\AnswerFile01.txt
      
    • [/DoNotStartTransport]

      Use the /DoNotStartTransport parameter to specify that the Microsoft Exchange Transport service will not start when Setup completes. By default, Setup starts the Microsoft Exchange Transport service after installing either the Hub Transport or Edge Transport server role. If you need to do additional configuration before the Edge Transport or Hub Transport server accepts e-mail messages, for example, configuring anti-spam agents, you should use this parameter. We recommend that you use this parameter when you use the /RecoverServer parameter to recover a Hub Transport or Edge Transport server so that you can move the queue database from the failed server to the correct location on the new server before starting the Microsoft Exchange Transport service.

      noteNote:
      The Microsoft Exchange Transport service runs only on the Hub Transport and Edge Transport server roles.
    • [/EnableLegacyOutlook]

      Use the /EnableLegacyOutlook parameter to specify that you have client computers that are running Microsoft Outlook 2003 or earlier. Exchange 2007 will create a public folder database on the Mailbox server. If all of your client computers are running Office Outlook 2007, public folders are optional in Exchange 2007. If you do not use this parameter, Exchange 2007 will not create a public folder database on the Mailbox server. You can add a public folder database later.

      You can only use this parameter if you are installing the first Mailbox server in an organization.

      When you install the first Mailbox server in an existing Exchange 2003 or Exchange 2000 organization, by default, Setup will create the public folder database on the Exchange 2007 server. You do not need to specify this parameter. Setup will not create a public folder database on subsequent Mailbox server installations in this organization.

    • [/LegacyRoutingServer]

      Use the /LegacyRoutingServer parameter to specify an Exchange 2003 or Exchange 2000 bridgehead server that is located in the routing group to which you will create the initial routing group connector. A routing group connector is required for mail flow between Exchange 2007 and either Exchange 2003 or Exchange 2000 when Exchange server versions coexist in the same organization.

      You can use this parameter only if you are installing the first Hub Transport server in the organization and if you have Exchange 2003 or Exchange 2000 servers in the existing organization. In this scenario, this parameter is required to establish mail flow between Exchange 2007 and Exchange 2003 or Exchange 2000.

    • [/EnableErrorReporting]

      Use the /EnableErrorReporting parameter to enable error reporting during Setup. If you decide to enable error reporting, the Microsoft Error Reporting Service collects information about how you use Exchange 2007 and about any issues you may encounter. This information is used to help Microsoft diagnose problems and provide solutions.

      You can use this parameter only if you are running Setup in Install mode.

      If you enable error reporting, Setup sets the following registry key to 0:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\DisableErrorReporting

      By default, this registry key is 1 and error reporting is disabled.

    • [/NoSelfSignedCertificates]

      Use the /NoSelfSignedCertificates parameter if you do not want Setup to create self-signed certificates in the case where no other valid certificate is found for Secure Sockets Layer (SSL) or Transport Layer Security (TLS) sessions. If you do not have a certificate, communication between clients and the Client Access or Unified Messaging server will be unencrypted.

      You can only use this parameter if you are installing either the Client Access server role or the Unified Messaging server role.

    • [/AdamLdapPort:<port>]

      Use the /AdamLdapPort parameter to specify the Lightweight Directory Access Protocol (LDAP) port to use for the Edge Transport server role Active Directory Application Mode (ADAM) instance. You can specify any valid unused port number. The default value is 50389. Exchange stores the ADAM LDAP port in the following registry key:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\EdgeTransportRole\AdamSettings\MSExchange\LdapPort

      You can use this parameter only if you are installing the Edge Transport server role.

    • [/AdamSslPort:<port>]

      Use the /AdamSslPort parameter to specify the SSL port to use for the Edge Transport server role ADAM instance. You can specify any valid unused port number. The default value is 50636. Exchange stores the ADAM SSL port in the following registry key:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\EdgeTransportRole\AdamSettings\MsExchangeAdam\SslPort

      You can use this parameter only if you are installing the Edge Transport server role.

    • [/AddUmLanguagePack:<UM language pack name1>, <UM language pack name2>, …]

      Use the /AddUmLanguagePack parameter to specify a UM language pack that you want to add. If you add a UM language pack, callers and Outlook Voice Access users can interact with the UM system in another language. For a list of Unified Messaging languages, see Understanding Unified Messaging Languages.

      To install a UM language pack, the Unified Messaging server role must already be installed.

      By default, when Setup installs the Unified Messaging server role, it also installs the en-US language pack and the language pack for the language of the Exchange server.

      When you add a language pack, by default, Setup expects the language pack .msi file to be in the ServerRoles\UnifiedMessaging directory of the installation directory. To specify a different location, use the /SourceDir parameter.

      noteNote:
      Do not include "umlang-" or the .msi extension in the language pack name. For example, the German language pack is umlang-de-DE.msi. To install this language pack, run the following command: Setup.com /AddUmLanguagePack:de-DE.
      noteNote:
      You cannot install a language pack by running the language pack .msi file. You must use Setup.com to install the language pack.
    • [/RemoveUmLanguagePack:<UM language pack name>]

      Use the /RemoveUmLanguagePack parameter to specify a Unified Messaging language pack that you want to remove. For a list of Unified Messaging languages, see Understanding Unified Messaging Languages.

      You cannot remove the en-US language pack. This language pack is required, in addition to any other language packs.

      noteNote:
      Do not include "umlang-" or the .msi extension in the language pack name. For example, the German language pack is umlang-de-DE.msi. To remove this language pack, run the following command: Setup.com /RemoveUmLanguagePack:de-DE.
      noteNote:
      You cannot remove a language pack by running the language pack .msi file. You must use Setup.com to remove the language pack.
    • [/NewProvisionedServer:<server name>, or /nprs:<server name>]

      Use the /NewProvisionedServer parameter to create a placeholder server object in Active Directory so that you can delegate the setup of a server. If you provide permissions to this server object for a user who has Exchange Server Administrators role permissions, that user can install Exchange 2007 on the server. During Setup, additional attributes on this server object will be added. If you do not specify a server name, Setup.com will create a placeholder server object in Active Directory for the local server. You can use the /ServerAdmin parameter with the /NewProvisionedServer parameter to specify the user or group that will have permissions to the provisioned server.

      To run Setup.com with the /NewProvisionedServer parameter, you must be delegated the Exchange Organization Administrators role, you must have an existing Exchange organization in Active Directory, and you must have at least one Exchange 2007 server installed in the organization. The server that you specify must have a machine account in Active Directory.

      After you provision a server with the /NewProvisionedServer parameter, you can view the server in the Exchange Management Console or in the results of the Get-ExchangeServer cmdlet.

    • [/RemoveProvisionedServer:<server name>, or /rprs:<server name>]

      Use the /RemoveProvisionedServer parameter to remove a placeholder server object that was created using the NewProvisionedServer parameter. You can remove the server object at any time before you install Exchange 2007 on that server. After you install Exchange 2007, you cannot use this parameter to remove the server object. You can use this parameter only to remove a provisioned server object. If you run Setup.com with the /RemoveProvisionedServer parameter on a server that has Exchange 2007 installed, Setup.com will complete successfully, but the server object will not be removed.

      If you do not specify a server name, Setup.com will remove the placeholder server object in Active Directory that has the same name as the local server.

      To run Setup.com with the /RemoveProvisionedServer parameter, you must be delegated the Exchange Organization Administrators role.

    • [/ForeignForestFQDN]

      Use the /ForeignForestFQDN parameter if you are in a cross-forest or resource forest scenario and want a user in one forest to administer Exchange 2007 in another forest. For more information, see How to Configure Cross-Forest Administration.

      You must use the /PrepareAD parameter with the /ForeignForestFQDN parameter. You must run Setup.com with the /ForeignForestFQDN parameter from a computer in a forest with an Exchange 2007 organization.

    • [/ServerAdmin:<user or group>]

      Use the /ServerAdmin parameter to specify a user or group account that will have permissions to a provisioned Exchange server. The account that you specify will be delegated the Exchange Server Administrators role for the server that you specify. You can view the Exchange Server Administrators role in the Exchange Management Console or in the results of the Get-ExchangeAdministrator cmdlet. You can use this parameter only if you use the /NewProvisionedServer parameter.

    • [/NewCms]

      Use the /NewCms parameter to create a new Exchange 2007 CMS. This parameter creates the Exchange server object in Active Directory for the CMS. The computer where you run Setup.com with the /NewCms parameter will be the active node of the cluster. You can run Setup.com with the /NewCms parameter on a clustered computer on which you want to install Exchange 2007 or on a computer that is currently a passive node of an Exchange cluster. If you run Setup.com with the /NewCms parameter on the passive node of a CMS, the node will become the active node. If you use the /NewCms parameter, you must also use the /CmsName parameter and the /CmsIPAddress parameter.

      noteNote:
      You can install only the Mailbox server role on a cluster.
    • [/RemoveCms]

      Use the /RemoveCms parameter to specify that you want to remove an Exchange 2007 CMS. If you use the /RemoveCms parameter, you must also use the /CmsName parameter. Running Setup.com with the /RemoveCms and /CmsName parameters removes the Exchange server object from Active Directory. When the Exchange server object is removed, that node becomes the passive node in the cluster. If you also use the /mode:uninstall parameter, Setup.com will first remove the CMS, and then completely uninstall Exchange from the server, including uninstalling the Mailbox server role.

      You must run Setup.com with the /RemoveCms parameter on the computer that hosts the CMS. You cannot run it remotely.

    • [/RecoverCms]

      Use the /RecoverCms parameter to specify that you want to recover an Exchange 2007 CMS. Setup.com will use the configuration information for the CMS that is already in Active Directory. The node on which you run this command becomes the active node of the cluster. If you use the /RecoverCms parameter, you must also use the /CmsName and /CmsIPAddress parameters. You can specify an IP address that is different from the IP address that was used before the CMS was recovered.

    • [/CmsName:<name of CMS>, or /cn:<name of CMS>]

      Use the /CmsName parameter to specify the name of the Exchange 2007 CMS. The CMS name must be unique. This is not the same name as the name of the Microsoft Windows cluster.

      When you use this parameter with the /NewCms parameter, it specifies the name that you will give to the new CMS. When you use this parameter with the /RemoveCms or /RecoverCms parameter, it specifies the CMS to remove or recover.

    • [/CmsIPAddress:<IP address>, or /cip:<IP address>]

      Use the /CmsIPAddress parameter to specify the static IPv4 address of the Exchange 2007 CMS. The IP address is not the same as the IP address of the Windows cluster, but it must be in the same subnet as the Windows cluster.

      When you use this parameter with the /NewCms parameter, it specifies the IP address that you will assign to the new CMS. When you use this parameter with the /RecoverCms parameter, you can use it to specify the CMS to recover, or you can use it to specify a new static IP address.

      This parameter does not support IP version 6 (IPv6).

    • [/CmsSharedStorage, or /css]

      Use the /CmsSharedStorage parameter to specify that this cluster is a Single Copy Cluster (SCC) and the cluster node uses shared storage. By default, the cluster node will not use shared storage. If you specify this parameter, the database and log data are stored on a shared disk. There is a single copy of the data. The shared disk must have a physical disk resource in the cluster.

      If you are creating a single copy cluster, you must use both the /CmsSharedStorage and /CmsDataPath parameters. You can use this parameter only when you are creating a new CMS. If you use this parameter, you must also specify the /CmsDataPath parameter.

    • [/CmsDataPath:<data path>, or /cdp:<data path>]

      Use the /CmsDataPath parameter to specify the path for shared disks. To use this parameter, the data path that you specify must exist, and it must have a physical disk resource in the cluster. If you are creating a single copy cluster, you must use both the /CmsSharedStorage and /CmsDataPath parameters.

    • [/?]

      Use the /? parameter to display Help for the Setup.com command.

  4. Setup copies the setup files locally to the computer on which you are installing Exchange 2007.

  5. Setup checks the prerequisites, including all prerequisites specific to the server roles that you are installing. If you have not met all of the prerequisites, Setup fails and returns an error message that explains the reason for the failure. If you have met all of the prerequisites, Setup installs Exchange 2007.

  6. Verify that the installation completed successfully. For more information, see Verifying an Exchange 2007 Installation.

importantImportant:
After you install the first Exchange 2007 server in an organization, if you create a new recipient object (such as a mailbox, contact, distribution list, mailbox agent, or mail-enabled public folder), it will have a legacyExchangeDN that corresponds to the new administrative group for the Exchange 2007 server. Because of this legacyExchangeDN, Outlook will request a full offline address book (OAB) download from the Exchange 2007 server for each user in this organization that logs on to a mailbox using Outlook and using OAB version 3 or 2. This could result in many simultaneous OAB download requests, which causes high network utilization.
noteNote:
After you install Exchange 2007, you should verify that the installation was successful. For more information, see Verifying an Exchange 2007 Installation.
importantImportant:
After installing the Unified Messaging server role, you must restart the system to allow the Microsoft Exchange Unified Messaging service to reserve the TCP ports that are required.

The following are examples of using Setup.com:

  • Setup.com /mode:install /role:Mailbox,HubTransport /TargetDir:"C:\Exchange 2007"

    This command installs the Mailbox server role, the Hub Transport server role, and the management tools to the C:\Exchange 2007 directory.

  • Setup.com /r:M,C,U

    This command installs the Mailbox server role, Client Access server role, Unified Messaging server role, and the management tools.

  • Setup.com /mode:Uninstall /role:HT

    This command removes the Hub Transport server role from the server.

  • Setup.com /mode:Uninstall

    This command completely removes Exchange 2007 from the server and removes this server's Exchange configuration from Active Directory.

  • Setup.com /mode:install /role:Mailbox,HubTransport /OrganizationName:MyOrg

    This command creates an Exchange organization in Active Directory called MyOrg, and also installs the Mailbox server role, Hub Transport server role, and the management tools.

  • Setup.com /PrepareAD /on:"My Org"

    This command creates an Exchange organization called My Org and prepares Active Directory for Exchange 2007.

  • C:\Exchange2007\bin\Setup.com /m:install /r:C /SourceDir:d:\amd64

    This command adds the Client Access server role to an existing Exchange 2007 server, using D:\amd64 as the source directory.

  • Setup.com /role:Mailbox,HubTransport /UpdatesDir:"C:\Exchange2007\New Patches"

    This command updates ExchangeServer.msi with patches from the specified directory, and then installs the Mailbox server role, Hub Transport server role, and the management tools.

  • Setup.com /mode:install /role:Mailbox,HubTransport /DomainController:DC01

    This command uses the domain controller DC01 to query and make changes to Active Directory while installing the Mailbox server role, Hub Transport server role, and the management tools.

  • Setup.com /mode:install /role:Mailbox /AnswerFile:c:\ExchangeConfig.txt

    This command installs the Mailbox server role by using the settings in the ExchangeConfig.txt file.

  • Setup.com /mode:install /role:EdgeTranport /DoNotStartTransport

    This command installs the Edge Transport server role and the management tools. After installation, Exchange does not start the Microsoft Exchange Transport service.

  • Setup.com /mode:install /role:Mailbox,HubTransport /TargetDir:C:\Exchange2007 /EnableLegacyOutlook

    This command installs the Mailbox server role, Hub Transport server role, and the management tools into the C:\Exchange2007 directory. This command also creates a public folder database on the Mailbox server.

  • Setup.com /mode:install /role:Mailbox,HubTransport /TargetDir:"C:\Exchange 2007" /LegacyRoutingServer:Ex2003.contoso.com

    This command installs the Mailbox server role, Hub Transport server role, and the management tools into the C:\Exchange2007 directory. This command also creates a routing group connector from the Hub Transport server to the specified legacy Exchange server, and creates a routing group connector from the legacy Exchange server to the Hub Transport server.

  • Setup.com /mode:install /role:Mailbox,HubTransport /EnableErrorReporting

    This command installs the Mailbox server role, Hub Transport server role, and the management tools. This command also enables error reporting.

  • Setup.com /mode:install /role:ClientAccess /NoSelfSignedCertificates

    This command installs the Client Access server role and the management tools and does not create a self-signed certificate.

  • Setup.com /r:Et /AdamLdapPort:50390 /AdamSslPort:50640

    This command installs the Edge Transport server role and the management tools and configures the ADAM instance to use port 50390 for LDAP and port 50640 for SSL.

  • Setup.com /NewProvisionedServer:Exchange03 /ServerAdmin:Contoso\Gerda

    This command creates an Exchange server object in Active Directory called Exchange03 and adds Contoso\Gerda as an Exchange Server Administrator for the server Exchange03.

  • Setup.com /rprs:Exchange03

    This command removes the object Exchange03 from Active Directory.

  • Setup.com /PrepareAD /ForeignForestFQDN:fabrikam.com

    This command creates the Microsoft Exchange security groups organizational unit, creates the three Exchange administrator roles in the root domain of the Fabrikam.com forest, and adds permissions for the Exchange objects in the Exchange forest where you ran the command to the newly created roles in the Fabrikam forest.

  • Setup.com /mode:install /role:Mailbox /NewCms /CmsName:ExchCMS01 /CmsIPAddress:10.212.100.45

    This command installs the Mailbox server role and the management tools. This command also creates a new CMS named ExchCMS01 and IP address 10.212.100.45. After you run this command, the local computer will be the active node of the cluster.

  • C:\Exchange2007\bin\Setup.com /RemoveCms /cn:Cluster01

    This command removes the CMS named Cluster01 from Active Directory.

  • Setup.com /mode:uninstall /RemoveCms /CmsName:Cluster01

    This command removes the CMS named Cluster01 from Active Directory, and then uninstalls Exchange from the server.

  • Setup.com /mode:install /role:Mailbox /NewCms /CmsName:Cluster01 /CmsIPAddress:255.255.255.0 /CmsSharedStorage /CmsDataPath:K:\Exchange\Mailbox

    This command installs a CMS in a single copy cluster (SCC) using shared storage.

  • Setup.com /AddUMLanguagePack:ko-KR

    This command installs the Korean Unified Messaging language pack from the %ExchangeSourceDir%\ServerRoles\UnifiedMessaging directory.

  • <Installation directory>\bin\Setup.com /RemoveUMLanguagePack:fr-CA

    This command uninstalls the French Canadian Unified Messaging language pack from the server.

  • Setup.com /mode:Upgrade

    This command upgrades an Exchange 2007 server to Exchange 2007 SP1.

  • Setup.com /mode:install /role:Mailbox /NewCms /CmsName:ExchCMS01 /CmsIPv4Networks:"Cluster Network 1","Cluster Network 2" /CmsIPv6Networks:"Cluster Network 1","Cluster Network 2"

    This command installs a CMS using cluster continuous replication (CCR) in an environment that has both IPv4 and IPv6 networks.

For information about using the Exchange Server 2007 Setup wizard to install Exchange 2007, see one of the following topics:

For more information about installing a CMS, see the following topics:

For information about tasks to complete after installation, see Post-Installation Tasks.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft