Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Migration from Exchange 2003 to 2010.  FFL IS set at 2003.  Error at Setup ... Forrest NOT set at 2003 .

Posted on 2014-09-05
6
Medium Priority
?
265 Views
Last Modified: 2014-09-05
Hi Guys,

Got a weird problem.  

Migrating from Exchange 2003 to Exchange 2010 to achieve a co-exisiting situation on the domain.  However, I am hitting a bit of a problem.  My Domains and Trusts prog. states my Forrest Functional Level is 2003 -  I have a minimum spec of Ent. Servers of 2003 SP2 on the domain.  However, when I run :  setup /PrepareLegacyExchangePermissions on the new proposed EXCH 2010 server ... I get an error stating that the Forrest Functional Level needs to be at 2003  ... which it is.   Anyone came across this before.

Any comments would be appreciated.

IM
0
Comment
Question by:ianmclachlan
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 37

Expert Comment

by:Neil Russell
ID: 40305611
Are you sure you have raised BOTH Domain level AND Forest level to 2003?
Use the following to check.

http://www.techgalaxy.net/Docs/Win2003/Verifying_functional_levels_by_using_ADSIEdit.htm
0
 

Author Comment

by:ianmclachlan
ID: 40305614
Hi,

Yes, Both Domain and Forrest are indicating "Windows Server 2003".

IM
0
 
LVL 37

Accepted Solution

by:
Neil Russell earned 2000 total points
ID: 40305620
Checked with ADSIEdit yes? only Sometimes it can show in error in AD
0
NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

 

Author Comment

by:ianmclachlan
ID: 40305666
Hi,

Thanks for your email.

Ran ADSIedit

Domain was set properly at 2.  However, the Forrest was set at 0.  Have changed to 2 and ran the setup /prep.  again.

Working fine now.  Obvious blip when the Forrest was originally changed.

Thanks

IM
0
 

Author Closing Comment

by:ianmclachlan
ID: 40305669
Excellent pointer to obtain answer
0
 
LVL 37

Expert Comment

by:Neil Russell
ID: 40305771
Glad to have been of help.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question