setup

All posts tagged setup

According to the Technet documentation you should be able to install Exchange 2010 in an environment where Exchange 2007 is running. A while ago I got a question from a customer who had an issue when trying to install Exchange 2010. The problem occured running the setup.com /ps to extend the schema for Exchange, the following error message was displayed:

The schema version of Exchange 2007 SP3 is higher than the one from the Exchange 2010 setup. This makes it impossible to install Exchange 2010.

When you have installed Exchange SP3 you will have to wait for a service pack which will extend the schema. Because a lot of people will probably install Exchange 2007 SP3 this may be included in SP1 for Exchange 2010.

Below an overview of the Exchange versions and which schema version they use:

ExchangeSchema
Exchange 2000 RTM4397
Exchange 2000 SP34406
Exchange 2003 RTM6870
Exchange 2003 SP36936
Exchange 2007 RTM10628
Exchange 2007 SP314625
Exchange 201014622
Exchange 2010 SP114726

If you would like to know how you can find out which version of AD schema you are using then take a look at the site below:

open

Today I had a nice issue at a customer site who tried to install Exchange in a test environment. First I will give a short introduction. Let’s say you have an AD forest which contains a child domain where you want to host Exchange in. You first will need to do some things in the forest before you can install Exchange in the child domain. You will start with the schema upgrade followed by the forest prep. As last step you will prepare the child domain and you could start the Exchange setup to install Exchange.

Normally you will use the same media for all servers, but in Exchange 2007 this can be different. This because Exchange 2007 had a 32-bit version which could be used in test environments or to prepare the schema/forest on a 32-bit DC.

You may think aaahhh that happened ?? Everything was done via the correct steps but when starting the Exchange installation via the GUI the following errors were displayed in the log:

[2/7/2010 11:30:46 PM] [0] Setup has chosen the local domain controller dc.ota.company.corp for initial queries
[2/7/2010 11:30:46 PM] [0] PrepareAD has either not been run or has not replicated to the domain controller used by Setup. Setup will attempt to use the Schema Master domain controller dc.company.corp
[2/7/2010 11:30:46 PM] [0] The schema master domain controller is available

So first checked if the servers can connect to eachother which was no issue. After trying some things we decided to move the schema master to the child domain to look if that would help. But this was also a no go and gave the following warnings:

[2/8/2010 3:32:34 PM] [1] [ERROR] PrepareDomain for domain ota has partially completed. Because of your Active Directory site configuration, you must wait for forest-wide replication to occur, and then run PrepareDomain for ota again.
[2/8/2010 3:32:34 PM] [1] [ERROR] Active Directory operation failed on dc.ota.company.corp. This error is not retriable. Additional information: The specified group type is invalid.
Active directory response: 00002141: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0

Waiting for 15 minutes didn’t fix the issue so we reversed all changes and I decided to start the Exchange setup via the GUI on the schema master. Then I saw the issue immidiatly the files used on the schema master were files for Exchange 2007 RTM and not for Exchange 2007 SP1. After using that files it worked without any issues.

It was a nice jigsaw after all.

Setup.com /M:RecoverServer

Last week I have been working on an Exchange 2007 migration. After preparing the server for installation I installed the CAS/hub role. Everything went fine till we wanted to modify the settings of the virusscanner. For some strange reason it was not possible to add some exclusions and it was not possible to remove the virusscanner.

The decission was quickly made, so we started from scratch and so we started with installing Windows 2008. After this we installed the software that is needed as a requirement for Exchange 2007.

We didn’t change much on the configuration and we could use:

setup.com /m:recoverserver

It’s a nice option I have to admit, de setup will search the AD for the configuration of Exchange 2007 for the specific server. This command will ensure that the roles that were installed previously will be installed again, and ready you are.

But what are the contitions you must meet and what are the things you should keep in mind when using this option:

  • the name of the server must be exactly the same
  • the server must be a member of the domain
  • the computeraccount in the Active Directory may not be removed. By removing it all configuration settings for Exchange  2007 will be deleted for this server. You need to reset the computeraccount so you can add the computer to the domain again
  • the configuration of the volume’s must be exactly the same as the old server
  • the same OS needs to be installed on the new server
  • when using a 3rd Party certificate ensure that you have a copy of the certificate
  • every customization which is made, for example changing the OWA login page, need to be documented/backuped. This is not restored by using the option recoverserver
  • extra added virtual directories, for example creating an extra Offline Address Book, will not be restored. Also this needs to be restored via a restore of the backup.

Such as most products have, the setup from Exchange 2007 can be made unattented. This can partitially be done by specifying parameters after the setup command.

The first parameter, if you have your forest and domains prepped, is mode, with this parameter you can specify the mode setup will be running in: install, uninstall, upgrade or recover.

/mode:install

/mode:uninstall

/mode:upgrade

/mode:RecoverServer

The next parameter is role, with this parameter you can specify which rol(es) need to be install(ed) on the server:

/role(s):HubTransPort, HT, H installs the HUB Transport role

/role(s):ClientAccess, CA, C installs the Cient Access role

/role(s):MailBox, MB, M installs the HUB Transport role

/role(s):UnifiedMessaging, UM, U installs the Unified Messaging role

/role(s):EdgeTransport, ET, E installs theEdge Transport role

/role(s):ManagementTools, MT, T installs the Management Tools

It is possible to combine the parameters, for example:

/roles:H,C,M,T

The parameters above will install the Hub Transport, Client Access and Mailbox rols + the management tools.

Besided  the parameters already mentioned you can give up several other parameters for example to change the install directory, below an overview of a few of them:

  • /OrganizationName, /on with this parameter you can specify an Exchange organization, this parameter is needed when no Exchange environment is currently active.
  • /TargetDir, /twith this parameter you can specify the install directory, default it is %programfiles%\Microsoft\Exchange Server.
  • /DomainController, /dcwith this parameter you can specify the domaincontroller which is used for gathering the information that is needed and for writing some config issues in the Active Directory.
  • /UpdatesDir, /uif you don’t want to install all updates manually after the setup you can use this parameter to install them automatically.

Besides the already mentioned parameters there are parameters for preparing the forest and domain for Exchange 2007:

  •  /PrepareLegacyExchangePermissions, /pl when you have installed an earlier version of Exchange you can’t adjust the Active Directory for Exchange 2007. You should use this parameter to ensure that the previous Exchange versions will be working together with Exchange 2007. When you don’t use this parameter it could be that the Recipient Update Service doesn’t work OK anymore.
  • /PrepareSchema, /ps this parameter is used to prepare the schema for Exchange 2007. You should run the Exchange setup with this parameter on the Schema Master This parameter doesn’t need to be specified when using PrepareLegacyPermissions, when using that it will be automatically done.
  • /PrepareAD, /p with this parameter you will prepare the forest. This parameter will also run the PrepareDomain parameter/action.
  • /PrepareDomain, /pd  will ensure that the domain will be prepared for Exchange 2007.
  • /PrepareAllDomains, /pad  this parameter is the same as the previous one, only this one will prepare all domains and subdomains.

Besides all the parameters mentioned there are a lot of more parameters that you can use, a full overview can be found on this site.