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

Exchange 2010, raise forest functional level

I have a single Windows 2003 server running Exchange 2003 and it is healthy.  I setup a second server with Windows 2008 on one virtual machine and a second windows 2008 for a second vm.  The first vm I added as a Domain controller and setup this as the FSMO.  Next I am trying to add Exchange 2010 to the second VM.  I have been following all kinds of posts here but I keep coming back to the problem that Exchange will not install until I get the forest functional level up.  Now I can see where my forest level is Windows 2003 but I guess I am missing something.  

Here is what I continue to see.

To update the domain functional level, the Active Directory Domain Controllers in the domain must be running the appropriate version of windows.

domain Name
iris.local

Current domain functional level
Windows Server 2003

The following Active Directory Domain Controllers are running earlier versions of windows:
domain Name      AD DC      Version of Windows
iris.local      mail-svr.iris.local      Windows Server 2003 5.2 (3790)



As for the uprgrade path I am trying to follow this.  
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html

Can anyone help?
0
bhgewilson
Asked:
bhgewilson
2 Solutions
 
PenguinNCommented:
I understand that both forrest and domain are 2003, is that correct.
What servicepack level is your old exchange.
0
 
bhgewilsonAuthor Commented:
Service pack 2

as per exeadmin.dll
0
 
Kash2nd Line EngineerCommented:
http://technet.microsoft.com/en-us/library/dd638130.aspx

first thing, you need to make sure your exchange 2003 (windows 2003 is in native 2003 mode).

go to AD and check there. Right click and Raise functional level.

once that is done then you need to prepare the domain (schema) for it. the above link will explain it to you step by step.

http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/

make sure you have all the latest patches installed on win sbs 2003
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
bhgewilsonAuthor Commented:
I have tried a ton of things including running all updates.  No matter what it does not allow me to install exchange 2010 because it says "the forest functional level of the current active directory forest is not windows 2003 native or later".  

I am not sure what else to do here.  I think FSMO is set but I can't be absolutely positive.  

No matter I am still having the same problems.  
0
 
bhgewilsonAuthor Commented:
So I have been following articles for close to two days now.  

I have a single Windows 2003 server with Exchange 2003.  I have installed two more servers.  One for Windows 2008 R2.  I have added this as a DC and changed the FSMO roles (assured this is done).  I stood up a member server Windows 2008R2.  I am trying to install Exchange 2010 but keep getting an error that the forrest fuctional lever of the current active directory forest is not windows 2003 native or later.  I have read and re-read and it should be right.

Can I demote the current Windows 2003 box to a member server without killing exchange 2003?  Can I just demote this and then rum exchange 2010?

Thanks,
0
 
AwinishCommented:
You need to upgrade schema for adding exchange 2010 in your environment & yes,it has to be Native mode in Exchange 2003.

http://technet.microsoft.com/en-us/library/bb691354%28EXCHG.140%29.aspx#WS08R2

I think Exchange deployment assistant is a good tool which will help you.

http://technet.microsoft.com/en-us/library/bb691354%28EXCHG.140%29.aspx#WS08R2
0
 
bhgewilsonAuthor Commented:
I have gone through all of these steps but still suck on upgrading forest fuctional level.  
0
 
bhgewilsonAuthor Commented:
Well guys I have been battling this for days.  This morning I took both domain controllers down and turned them off.  I brought up the new one and then the old one.  I started it again and it went through.  Seems I was having some replication issues.  
0
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.

Join & Write a Comment

Featured Post

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

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