Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
2000 Server in 2003 domain with 2012 DC?

Answered 2000 Server in 2003 domain with 2012 DC?

  • Tuesday, February 19, 2013 6:51 PM
     
     
    Sign In to Vote
    0
    One question I have relates to adding a 2012 domain controller into an existing Windows 2003 Native domain (currently 2x 2008R2 DCs and 1x 2003R2 DC).  The end goal is to retire the 2003R2 DC with the addition of the 2012 one.  The catch we have is that we have one legacy Windows 2000 member server (very important, dept drags feet to remove).  If we keep the domain in Windows 2003 mode or even up it to Windows 2008 mode will we be OK having a 2000 member server?

    The Microsoft docs say a 2000 client isn't supported with 2012 DCs, but makes no mention of a mixed OS domain running in 2003/2008 mode.  Would we be able to add the 2012 DC and keep the 2000 member server working?
     

All Replies

  • Tuesday, February 19, 2013 6:57 PM
     
     
    Sign In to Vote
    0

    I'm not aware of the problem you mention.  Actually, another forum list has the same question with my same answer:

    http://social.technet.microsoft.com/Forums/en-US/winserverDS/thread/a6070b2f-827c-4337-81ac-ffa0a1a08bf0/


    C Shane Cribbs
    http://www.georgiatechnologies.com


    • Edited by Shane Cribbs Tuesday, February 19, 2013 6:57 PM
    •  
     
  • Tuesday, February 19, 2013 7:41 PM
     
     
    Sign In to Vote
    0

    Thanks for the link, not sure how I didn't come across that.  According to that post there aren't any issues with Server 2000 in a 2012 level forest, but Microsoft states differently:

    Windows client and Windows Server operating systems that are supported to join Windows Server 2012 domains

    The following Windows client and Windows Server operating systems are supported for domain member computers with domain controllers that run Windows Server 2012:

    • Client operating systems: Windows 8, Windows 7, Windows Vista, Windows XP
    • Server operating systems: Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2, Windows Server 2003

    (technet.microsoft.com/en-us/library/hh994618.aspx#BKMK_WhatsNewAD)

    I read that as Windows 2000 isn't supported in a fully 2012 domain.  Our domain level is 2003 Native so I think we'll be OK but just want to make sure.  I tried testing this but we don't have any Server 2000 CDs around (thankfully, I guess).

     
  • Tuesday, February 19, 2013 7:55 PM
     
     
    Sign In to Vote
    0
    It can join the domain as a member, not as a DC. It's always best to test in a lab beforehand as you mentioned. Use Disk2VHD to create a virtual image of the server 200 and run in in a lab with the 2012.

    Miguel Fra | Falcon IT Services, Miami, FL
    www.falconitservices.com | www.falconits.com | Blog


     
  • Tuesday, February 19, 2013 8:07 PM
     
     
    Sign In to Vote
    0

    That's been my experience as well, but the TechNet article referenced above raises some questions about the official support of that scenario.

    C Shane Cribbs
    http://www.georgiatechnologies.com

     
  • Thursday, February 21, 2013 4:38 PM
     
     
    Sign In to Vote
    0
    I was able to track down a Server 2000 CD and will test this out today and tomorrow.  The scenario will start with a 2003 DC and 2000 member server then join the 2012 server to the domain and promote it.  Hopefully it all goes well.
     
  • Thursday, February 21, 2013 11:06 PM
     
     
    Sign In to Vote
    0

    But, it will not be supported by Microsoft.  The 2000 operating system went out of support almost three years ago.  So nothing has been officially tested.  You are totally on your own should anything not work.  http://support.microsoft.com/lifecycle/?p1=7274

    .:|:.:|:. tim

     
  • Monday, February 25, 2013 9:36 PM
     
     Answered
    Sign In to Vote
    0

    We understand this won't be supported by MS as Server 2000 hasn't been supported for years and should no longer be around.  As one department drags it's feet about replacing an out-dated system, our IT goal is to not let one system hold up the rest of our infrastructure. The key you mentioned is that MS didn't test this configuration, but that's never stopped people before.

    To actually test if having a Windows 2000 client in a domain with a 2012 DC I created a test environment consisting of the 2000 client, a 2003 DC, and a 2008R2 DC.  File shares, DNS, and authentication worked normally so I added the 2012 DC and demoted the 2003 DC.  Everything worked normally except for the listing of users able to access the share on the 2000 box.  The SID was listed and after accessing the share with each user that had access the normal usernames showed back up and the share worked normally.  At this point I don't see anything broken so the test of having a Windows 2000 client in a domain (Windows 2003 level) with a 2012 DC was successful.

    Even though this worked everyone should be pushing to get rid of Windows 2000.

    • Marked As Answer by Erc2007 Tuesday, February 26, 2013 9:52 PM
    •