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

Exchange 2007 Installation Fails and Mixed Mode

I'll try to make this as short as possible.  Here's the history:
1. Had SBS 2003 Server that was moved to Data Center for Exchange purposes.
2. Built a new Domain Controller before moving SBS server , seized FSMO roles etc.
3. Trying to install Exchange 2007 fails because it claims that the organization is in Mixed Mode.

Because SBS server is no longer visible to this domain there is no way to use ESM to switch to Native Mode but apparently there is still a bunch of stuff on the new DC that refer to that Exchange organization that is preventing me from installing 2007 on this domain...

Where can I go to manually fix this issue? I know I could build the Exchange server as a stand alone box and move it to data center to replace existing SBS box but I wanted to capture all of the AD components (users, etc...) before doing so to make the transition more simple and straight forward.  Otherwise I'll have to deal with creating all new users, passwords, and everything else.
0
fredimac
Asked:
fredimac
  • 4
  • 3
1 Solution
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
Go to Admin Tools -> AD Domains and Trusts, right click and select properties.

Change Operations Mode. http://technet.microsoft.com/en-us/library/aa998156.aspx
0
 
fredimacAuthor Commented:
I've read this documment - it refers to changing an Exchange domain - In DOmains and Trusts I can change the Domain Functional Level... it was already set to Windows 2003 so it can't go any higher.  There is no longer an Exchange server in this domain - but AD somewhere thinks there is based on the schema modifications that were made when there was an Exchange server in the domain previously...
0
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
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

 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
If there was an exchange server bfore and you didn't delete it properly, delete all references of that server using adsiedit.
0
 
fredimacAuthor Commented:
An example of the kinds of references I'm looking for in Adsiedit would be helpful
0
 
fredimacAuthor Commented:
I see several references in Adsiedit -
under Domain - DC - CN=Microsoft Exchange System Objects with a bunch of Exchange related stuff in it.  
Also under Configuration  CN=Extended Rights there are a bunch of entries named CN=ms-Exch-xxx-  where X is a variable referring to stuff like ms-Exch-Admin-Role-Administrator  OR  CN=ms-Exch-Modify-etc...  etc..  
Then under Configuration - CN=Configuration,DC=mydomain, DC=com => CN=Services=> CN=Microsoft Exchange ...

And finally - under Schema- CN=Schema, CN=Configuration,DC=mydomain, DC=com there are a bunch of entries like the ones mentioned previously ( CN=ms-Exch-Access-Control-Map / CN=Admin-ACL /  There are  A TON of ENtries like these that refer to Exchange....  which ones get removed?  All of them?  Am I going to blow up AD by doing this?

thanks
0
 
fredimacAuthor Commented:
The answer is to use adsiedit and remove the exchange organization under - cn=configuration => cn=Services => CN=Microsoft Exchange
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

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

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