• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 369
  • Last Modified:

migrating from exchange 2007 to 2013 issue

i am trying to upgrade from exchange 2007 to 2012. in the prerequisites it says i cannot go any further unless exchange 2000 or 2003 servers are removed. ive located the old 2003 server in adsi but im not sure if i should delete it or what would happen if i delete it. i was told that it needed to be left there when migrating from 2003 to 2007, but i have no clue why. can someone shed some light on why that was the case and what would happen if i go ahead and get rid of it? is there some sort of work around? am i even looking in the right place?
0
rjunk
Asked:
rjunk
  • 3
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
The only bit that has to be left in place is the admin group, not the server. If the server had been removed correctly then the server entry would have gone.

Do you have Exchange 2003 media? Do you have a Windows 2003 server you could install the management tools only on? If so you could do that and check the migration was completed successfully. You can also then delete the server through ESM and that will clean up the domain better than using adsiedit.

Simon.
0
 
RadweldCommented:
if you follow the advice from Sembree make sure you move the RUS and Move the Public Folder Hierarchy to Exchange 2007 at the same time.

The following is for 2010 although most of it applies to 2010 https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010---part-ii/
0
 
rjunkAuthor Commented:
Thanks for responding both of you. I do not have the exchange 2003 media or a Windows 2003 Server. I will go ahead and delete the remaining entry in asdi edit and hope for the best. I will let you guys know if it worked or $h!t the bed.
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

 
RadweldCommented:
0
 
rjunkAuthor Commented:
I removed the only server from ADSI edit and that did the trick. I can now move forward with the installation of 2013. I installed exchange, rebooted the server and when i launch the exchange toolbox i get an error "MMC has detected an error in a snap-in and will unload it."
0
 
rjunkAuthor Commented:
Removing the old server from ADSI edit didnt cause anything bad to happen. FYI.
0

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now