Skip to main content

Installation of Exchange 2007 SP2 with Windows 2008 R2 Domain Controllers fails because of outdated Best Practices Analyzer files

When trying to install Exchange 2007 SP2 in a network where all domain controllers are Windows 2008 R2 version, setup fails with following error:

[ERROR] Cannot find at least one domain controller running Windows Server 2003 Service Pack 1 or later in domain 'DC=DCName,DC=com,DC=DCName'. This could be the result of moving domain controller objects in Active Directory. Check that at least one domain controller running Windows Server 2003 Service Pack 1 or later is located in the 'Domain Controllers' organizational unit (OU) and rerun setup.

  1. Download and extract Exchange 2007 SP2 to a local hard drive.
  2. Download the updated ExBPA.PreReqs.xml and ExBPA.Readiness.xml files [click here for download]
  3. Save the files to your local hard drive
  4. Locate ExBPA.PreReqs.xml and ExBPA.Readiness.Xml files which were extracted from the Exchange 2007 SP2 download. The default location is "Setup\ServerRoles\Common\<language>". Rename original XML files to something else or save them to a different location.
  5. Place the ExBPA.PreReqs.xml and ExBPA.Readiness.Xml files which you downloaded into the place of original xml files.
  6. Copy the Exchange 2007 SP2 setup files that you have modified to the non-Internet connected Exchange Server which you are trying to upgrade to Exchange 2007 SP2.
  7. Run Setup on the non-Internet connected computer by using the files you copied as per above.

Related article:

http://msexchangeteam.com/archive/2009/09/15/452494.aspx

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

Restore Time Machine backup from Synology

If you find yourself in a situation where you need to restore your Mac from a Synology NAS, you will find out pretty soon after you enter the recovery mode, that backup disk is not visible in recovery window. Steps need to be executed in order Recovery process to find NAS.

Best practise is to name Time Machine shared folder on Synology without spaces. Second, if you are using a password with spaces, which I strongly suggest from security point of view, always put it between ' ' example: 'This is my password'.

Enter the OS X recovery mode by holding Command +R (when Mac restarts and display is grey)When window with options is presented, select Utilities from the bar and select TerminalIn Terminal use following commands:Cd /Volumesls /laCreate a folder to mount Synology to by typing mkdir synologyNow mount your NAS by entering following commandmount -t afp afp://admin:password@10.10.10.11/TimeMachine synology Where admin is your username with administrative rights, passwo…