Thursday, April 7, 2011

Exchange Server 2010 unattended mode

Prepating Active Directory and Domains
If you have any computers in your organization running Microsoft Exchange Server 2003, enter the following command to let Exchange Server 2010 prepare coexistence exchange environments.

Setup.com /PrepareLegacyExchangePermissions or setup.com /pl

Remark: To run this command in the forest, you must be a member of the Enterpeise Admins group.

Remark: If there is no Exchange Server 2003 in your organization, you don't need to enter the above command.

Then, you have to prepare the schema supporting Exchange Server 2010. Enter the following command to update the schema.

Setup.com /PrepareSchema or setup.com /ps

Remark: To run this command in the forest, you must be a member of the Enterprise Admins group.

Enter the following the prepare installing Exchange Server 2010.

Setup,com /PrepareAD /OrganizationName:<organization name> or Setup.com /p /on:<organization name>

Remark: If there is a previous Exchange Server in your organization, you don't have to perform "/OrganizationName:<organization name>".

Assuming needing to setup Exchange Server in a new domain, you have to perform the following command.

At the new domain, log in as Domain Administrator.
Enter Setup.com /Preparedomain or Setup.com /pd

Remark: To run this command in the domain, you must be a member of the Domain Admins group.

Or, enterprise administrator can perform the following command.

Setup.com /PrepareAllDomains or Setup.com /pad

Install Exchange 2010 in unattended mode
You can use Setup from a Command Prompt window to install Microsoft Exchange Server 2010 in unattended mode. Performing an unattended setup, you must install Exchange 2010 from the command prompt.

Enter the following command to install typical Exchange Server roles.

Setup.com /mode:Install /roles:ClientAccess,Mailbox,HubTransport or Setup.com /m:install /r:c,m,h

Remark: If all of your client computers are running Microsoft Outlook 2003, you have to add "/EnableLegacyOutlook" parameter which can be installed the public folder database.

Installing Exchange Server 2010 from the command prompt, the options are more flexible.

/NoSelfSignedCertificates parameter is used to disabling the exchange to create self-signed certificates.

/LanguagePack parameter is used to specifying an Exchange language pack that you want to add.

Example: Setup.com /mode:Install /languagepack:<"C:ExchangeLanguagePack"> /role:Mailbox,HubTransport

/ExternalCASServerDomain:<domain> parameter is used to providing external Client Access Server FQDN.

/MdbName:<mailbox database name> parameter is used to modifying the mailbox database name, By default, when the Exchange server is being installed, it will create a mailbox database with a random name. Using this parameter, let you provide the name of the mailbox database.

/DbFilePath:<Edb file path> parameter is used to modifying the default path of the edb file.

Example: Setup.com /r:m /Dbfilepath:d:\Mailbox\MailboxDatabase01.edb

/Logfolderpath:<log folder path> parameter is used to modifying the default path of the log file.

Example: Setup.com /r:m /Logfolderpath:d:\Mailbox\LogFolder

/LegacyRoutingServer parameter is used to specifying an Exchange 2003 bridgehead server that’s located in the routing group to which you’ll create the initial routing group connector.

Example: Setup.com /mode:Install /role:HubTransport /LegacyRoutingServer:Ex2003.contoso.com

/InstallWindowsComponents parameter can help you to install the required Windows role and features for each selected Exchange 2010 SP1 server role.

Example: Setup.com /m:install /r:m,c,h /InstallWindowsComponents

Remark: Before running this command, you have to install Microsoft .Net Framework 3.5.1 features by yourself.

/NewProvisionedServer:<server name> or /nprs:<server name> is used to creating a placeholder server object in Active Directory so that you can delegate the setup of a server.
Remark: You also need to add the specify user in the Delegated Setup managenent role group for set Exchange.


For Edge transport server
/AdamLdapPort:<port> parameter is used to specifying the LDAP port to use for the Edge Transport server role Active Directory Lightweight Directory Services (AD LDS) instance.
/AdamSslPort:<port> parameter is used to specifying the SSL port to use for the Edge Transport server role Active Directory Lightweight Directory Services (AD LDS) instance.
 
For recover server
Setup.com /m:RecoverServer parameter is used to recovering a catastrophic failure of a server.

Reference:


http://technet.microsoft.com/en-us/library/bb125224.aspx

This posting is provided “AS IS” with no warranties, and confers no rights!

No comments:

Post a Comment