Exchange Server 2013 Installation Fails due to Exchange Server 2003 Installed

I have an Exchange Server 2007.  I'm trying to install Exchange Server 2013 on another server so I can then migrate mailboxes, etc from 2007 to 2013 and remove the 2007 server.

My install fails because it says I still have an Exchange Server 2003.  I had 2003 originally but it was uninstalled a couple years ago.  I saw items regarding using ADSIEDIT to remove but when I go into it, under CN=Servers, I only see my current Exchange 2007 server listed.

Any suggestion on how I can fix this?  Thanks!
sfsdtcAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott GorcesterCTOCommented:
If Exchange was previously unisntalled from the server you are installing to then you may need to manually remove all traces from the drive and the registry. If not then there is some remanent that is lingering in the AD.

MooseSupport
0
Amit KumarCommented:
Please provide logs/error or Exchangesetup logs to analyze it further.
0
sfsdtcAuthor Commented:
The Exchange Server 2013 is on a new server.  Exchange was not installed on it before.  I've attached the Exchange Setup Log.  I'm working on installing the MS Unified Communications piece.  Biggest issue is how to get rid of it thinking Exchange 2003 is still installed.  Thanks!
ExchangeSetup.log
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Amit KumarCommented:
Please verify ADSIedit.msc once again, seems there is a legacy server entry.

Try this powershell:

Get-ExchangeServer | ft

If you find any server which is not in your knowledge then run below powershell:

Get-ExchangeServer OLDSERVER | fl DistinguishedName

You will be able to get details of culprit server.

Or if you want to check from ADSIEdit.msc

use ADSIedit and see if there are still remnains of old Exchange objects in Active Directory.

Do the following
- Open ADSIEdit
- Configuration -> Services ->
- Microsoft Exchange -> ExchangeOrgName ->
- Administrative Groups -> First Administrative Group ->
- Servers

Change and make sure that you do not have any old Exchange objects listed in there. If you do delete them.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sfsdtcAuthor Commented:
Under Administrative Groups via ADSIEdit I have the following:
  CN=Exchange Administrative Group - This has settings for existing Exchange 2007 Server
  CN=ABCD - Replaced actual value with ABCD.  Under CN=Server here, it shows the old Exchange 2003 server that doesn't exist.  Should I delete the whole CN=ABCD tree?  If so, is there a way to backup first in case deleting it causes problems?

Thanks!
0
Amit KumarCommented:
If server does not exist then there will not be an issue, but still take AD full backup for safer side.
0
sfsdtcAuthor Commented:
Is there a better way to do an AD full backup other than backing up all the DCs?
0
Amit KumarCommented:
See if this article works for you suggested by MS.

Hope you have Windows 2008 as DC.
0
sfsdtcAuthor Commented:
I'll take a look at that.  All my DCs are at least Windows Server 2012.  I do have Windows Server Backup installed on all of them.  Thanks!
0
Amit KumarCommented:
OK! then go through with this article and also attached PDF .
WindowsServer2012ADBackupandDisasterReco
0
sfsdtcAuthor Commented:
I backed up my AD.  When I go into ASDIEdit and right click the legacy server that no longer exists, there is no option to Delete or Remove.  Is there something else I need to do?  Thanks!
0
sfsdtcAuthor Commented:
Nevermind, I was able to start ADSIEdit on another DC and it has the Delete option.  Looks like I was able to remove the legacy server - Exchange Server 2013 Installation has gotten past that point.  Thanks for the help!!!
0
Amit KumarCommented:
Great to know, hope you can accept my suggestions as solutions...
0
sfsdtcAuthor Commented:
Using ADSIEdit to remove the old server under CN=Server fixed this issue.  Thanks!  Note: appears ADSIEdit must be used on DC that has the Schema Master or there is no Delete option when you right click an object.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.