sfsdtc
asked on
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!
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!
Please provide logs/error or Exchangesetup logs to analyze it further.
ASKER
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
ExchangeSetup.log
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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!
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!
If server does not exist then there will not be an issue, but still take AD full backup for safer side.
ASKER
Is there a better way to do an AD full backup other than backing up all the DCs?
ASKER
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!
OK! then go through with this article and also attached PDF .
WindowsServer2012ADBackupandDisasterReco
WindowsServer2012ADBackupandDisasterReco
ASKER
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!
ASKER
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!!!
Great to know, hope you can accept my suggestions as solutions...
ASKER
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.
MooseSupport