Sign in
 
Exchange Server TechCenter > Exchange Server Forums > Migration [Exchange Server] > 2003 and 2007 Exchange functioning on a multi mode 2008 2003 domain infrastructure
Ask a questionAsk a question
Search Forums:
 

Answer2003 and 2007 Exchange functioning on a multi mode 2008 2003 domain infrastructure

  • Wednesday, October 14, 2009 7:57 PMPete Nisler Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I just recently started a position with a company who just installed whatever they wanted.  When I got here the previous admin installed 2007 Exchange running with 2003 Legacy for testing.  The domain was 2003 Servers.  They then upgraded the DC's to 2008.  When realizing that there was no way to manage the users they promoted a new 2003 server.  I currently am unable to add new users to the legacy (production) 2003 exchange environment.  (can add through ad on the exchange server but the mailbox never gets created) Also users in exchange are unable to see updates to distribution lists or free/busy time.  I checked adsiedit and it seems there are missing entries that should be created when you install Exchange 2007 to function with Exchange 2003.  Any help would be greatly appreciated.  I was able to find a backup of one of the old dc's
     

Answers

All Replies

  • Friday, October 16, 2009 4:05 AMAndy Webb Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Sounds like your RUS isn't running correctly for starters.

    I don't think I'd recommend just doing an AD restore at this point given what you've said about it.

    How many users are you dealing with? Perhaps consider flattening the org (export to PST) and build clean Exchange 2007 into the forest?

    Otherwise, you've got to peel the onion one problem at a time.  make sure RUS is working (affects DL and AB updates, affexts MBX creation on 2003).  make sure the public folder store is functional and free busy is gettinc maintained.  make sure the OAB is getting updated and distributed to the clients (also test with OWA because it avoids OAB issues).

    What's an ExBPA report say about the health of the domain controllers that Exchange is trying to use and the rest of the health of Exchange?
     
  • Friday, October 16, 2009 5:57 AMXiu Zhang - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

     

    First let me clarify the issue with you:

     

    1.    Windows Server 2008 domain level.

     

    Note: If we raise functional level to Windows Server 2008, Domain Controllers that are running Windows Server 2003 cannot be added to that domain.

     

    2.    Exchange 2007 with Exchange 2003

     

    Note: Exchange Server 2003 Service Pack 2, Exchange 2007, and Exchange 2007 SP1 (when released) are supported in environments that either partly or entirely use writeable Windows Server 2008 directory servers.

     

    So please verify if you have sp2 for Exchange 2003.

     

    Besides, user from Exchange 2003 cannot obtain free/busy information for user from Exchange 2007 ? Or user from Exchange 2003 cannot obtain free/busy information for Exchange 2003 users? Or User from Exchange 2007 cannot obtain free/busy for exchange 2003 users? Or all the Exchange users cannot obtain free/busy information?

     

    Please check the article below and then verify if you have public folder on Exchange 2003 and OAB generate on CAS server.

     

    How Exchange 2007 OAB Files are replicated to a Client Access Server for download

    http://blogs.msdn.com/dgoldman/archive/2006/08/25/How-Exchange-2007-OAB-Files-are-replicated-to-a-Client-Access-Server-for-download.aspx

     

    Troubleshooting Free/Busy Information for Outlook 2007

    http://technet.microsoft.com/en-us/library/bb397225.aspx  

     

    What does Exchange 2007 Availability Service do?

    http://msexchangeteam.com/archive/2006/10/23/429296.aspx

     

    Free Busy generation process

    http://msexchangeteam.com/archive/2006/08/04/428597.aspx

     

    Regards,

    Xiu

     

     
  • Tuesday, November 03, 2009 7:30 PMPete Nisler Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Looks like I was able to resolve the issue.  I moved all mailboxes off of Exchange 2007 that were there.  I then uninstalled exchange 2007 by moving all of my public folder replicas back to 2003 exchange.  Once I decommissioned the Exchange 2007 server I had to remove the ExhangeAB record from the 2003 Exchange server (must have been a domain controller before) to the 2003 domain controller using setspn.exe.  Looks like everything is running fine for now.  Once I can get the 2007 server installed properly and the infrastructure correct I will migrate to 2007.
    Pete Nisler Systems Administrator