Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
One more time! Server 2003 AD to Server 2012 AD

Answered One more time! Server 2003 AD to Server 2012 AD

  • Wednesday, November 14, 2012 7:10 PM
     
     
    Sign In to Vote
    0

    Current network is 32 bit Server 2003 running AD.  new DC will be 2012.  My high level understanding of the process to date is:

    Run AD prep /Forest prep from the 2012 disk.  I've read that there's no 32 bit adprep.  Might this be an issue and is there a workaround?

    Then join 2012 to existing domain

    Add DNS to the mix (and let that replicate

    Promote to a DC

    Demote the old 2003 DC after replication has occurred.

    Also, I've seen several posts here with various issues encountered relating to DNS replicating properly and promotion failing due in part to the other DC having a 32 bit OS.  Before I get knee deep in this, can someone share their experiences and offer some guidance?

    Thanks to all who post,

     

All Replies

  • Thursday, November 15, 2012 6:16 AM
    Moderator
     
     
    Sign In to Vote
    1

    Hello Steve,

    You might want to follow the steps below to introduce 2012 as DC in your existing setup.

    1. Install a new server with WS 2003 64bit ( may be on a virtual machine )

    2. Promote WS 2003 64bit as an additional domain controller

    3. Transfer the FMSO roles to to newly introduced domain controller (WS 2003 64bit)

    4. Once FSMO role transfers are complete, make sure AD is replicated.

    5. Run adprep and forestprep on WS 2003 64bit DC

    6. Introduce WS 2012 as a additional DC

    7. Transfer the FSMO roles from WS 2003 64bit DC to newly introduced WS 2012 DC.

    8. Allow replication to occur and then you may demote the WS 2003 DCs as appropriate.

    Also, go through following articles for more details

    Adding first Windows Server 2012 Domain Controller within Windows 2003/2008/2008R2 network (by Krzysztof)

    http://kpytko.wordpress.com/2012/09/07/adding-first-windows-server-2012-domain-controller-within-windows-200320082008r2-network/

    Introducing the first Windows Server 2012 Domain Controller 

    http://blogs.technet.com/b/askpfeplat/archive/2012/09/03/introducing-the-first-windows-server-2012-domain-controller.aspx

    Upgrade Domain Controllers to Windows Server 2012

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

    Thanks

    Regards, Santosh

    I do not represent the organisation I work for, all the opinions expressed here are my own.

    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    Whenever you see a helpful reply, click on Alternate Text Vote As Helpful & click on Alternate Text Mark As Answer if a post answers your question.

     
  • Thursday, November 15, 2012 11:12 AM
     
     
    Sign In to Vote
    0
    So, I have to tell my client that he has to buy a 64 bit WS2003 just to use for a few days during the upgrade? I guess this means this Microsoft has abandoned users of 32 bit operating systems.
     
  • Thursday, November 15, 2012 11:26 AM
    Moderator
     
     
    Sign In to Vote
    1
    So, I have to tell my client that he has to buy a 64 bit WS2003 just to use for a few days during the upgrade? 
    Unfortunately Yes.

    Regards, Santosh

    I do not represent the organisation I work for, all the opinions expressed here are my own.

    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    Whenever you see a helpful reply, click on Alternate Text Vote As Helpful & click on Alternate Text Mark As Answer if a post answers your question.

     
  • Thursday, November 15, 2012 12:54 PM
     
     
    Sign In to Vote
    0
    Totally unacceptable Microsoft.  I will have Dell ship the server with WS 2008 64 and wait for the next hardware refresh for a more current OS.
     
  • Thursday, November 15, 2012 1:30 PM
     
     
    Sign In to Vote
    2
    I think you misunderstood what Santosh suggested.  You can created a 64-bit virtual machine - you don't need to buy 64-bit hardware in order to install Windows Server 2003 and make it a domain controller.  Microsoft told customers before Windows Server 2008 even came out that 32-bit server operating systems were going to go away.  One reason for that was because the hardware vendors were no longer selling any 32-bit servers - people were installing 32-bit operating systems on 64-bit servers.  Windows Server 2008 R2, released in 2009, was 64-bit only.  Kinda hard to blame Microsoft for things that were happening in the hardware space. <grin>

    tim

     
  • Thursday, November 15, 2012 1:36 PM
     
     
    Sign In to Vote
    0
    i certainly don't blame them for EOL the 32 bit OS but leave an upgrade path.
     
  • Thursday, November 15, 2012 1:42 PM
    Moderator
     
     
    Sign In to Vote
    1

    Steve,

    I can understand your concern however, that's how the things are ( unfortunately ).

    Tim,

    Thanks for the elucidation.

    Regards, Santosh

    I do not represent the organisation I work for, all the opinions expressed here are my own.

    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    Whenever you see a helpful reply, click on Alternate Text Vote As Helpful & click on Alternate Text Mark As Answer if a post answers your question.

     
  • Thursday, November 15, 2012 1:50 PM
     
     
    Sign In to Vote
    0
    WS 2008 will do until the next hardware refresh and will bridge them to a 64 bit OS so I'll just go sit in my corner and behave.  <grin>
     
  • Thursday, November 15, 2012 2:20 PM
     
     Answered
    Sign In to Vote
    1

    On Thu, 15 Nov 2012 06:16:07 +0000, Santosh Bhandarkar wrote:

    1. Install a new server with WS 2003 64bit ( may be on a virtual machine )

    Steve, you may want to hold up here as I really don't understand why
    Santosh is telling you that this step is required as it is not required. As
    long as your domain is at 2003 functional level, there is nothing at all
    preventing you from adding a 2012 DC to the domain.

    As far as there not being an x86 version of ADPREP available that is
    irrelevant. With 2012 you no longer have to manually run ADPREP at all.
    When you configure the AD role on the new 2012 computer, it will determine
    if ADPREP needs to be run and if so will do it for you.

    The bottom line here is that there is no requirement that all of your DCs
    be x86 or x64.

    Paul Adare
    MVP - Forefront Identity Manager
    http://www.identit.ca
    Congratulations!  You are the one-millionth user to log into our system.

    • Marked As Answer by Steve R Thursday, November 15, 2012 2:21 PM
    •  
     
  • Thursday, November 15, 2012 2:23 PM
     
     
    Sign In to Vote
    0
    AWESOME!!    This is the best news ever.
     
  • Thursday, November 15, 2012 2:32 PM
     
     Answered
    Sign In to Vote
    1

    On Thu, 15 Nov 2012 14:23:06 +0000, Steve R wrote:

    AWESOME!! ? ?This is the best news ever.

    You're easily pleased. :-)

    If you look about 1/2 way down this page (search for Adprep) you'll see a
    screenshot of what I mentioned in my previous post:

    http://blogs.technet.com/b/askpfeplat/archive/2012/09/03/introducing-the-first-windows-server-2012-domain-controller.aspx

    Paul Adare
    MVP - Forefront Identity Manager
    http://www.identit.ca
    Semi-conductor:  A person hired to lead an orchestra before he has
    graduated
    from director's school.

    • Marked As Answer by Steve R Thursday, November 15, 2012 2:44 PM
    •  
     
  • Thursday, November 15, 2012 2:44 PM
     
     
    Sign In to Vote
    0

    Yes, this quote from the web page sums it up nicely:  "As you can see in the below screenshot if you have not already prepared the forest/domain the Domain Controller promotion process will do this for you."  I guess I was confused because elsewhere I read that there was no AD / Forest Prep that would run on 32 bit OS's  I (mistakenly) drew the conclusion that this step would fail.

    Many thanks for your help.

     
  • Thursday, November 15, 2012 2:59 PM
    Moderator
     
     
    Sign In to Vote
    1
    Looks like my understanding was incorrect. In my test lab I had followed the traditional way of upgrading the schema hence, I had suggested the steps mentioned in my previous post. Sorry for the confusion.

    Regards, Santosh

    I do not represent the organisation I work for, all the opinions expressed here are my own.

    This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

    Whenever you see a helpful reply, click on Alternate Text Vote As Helpful & click on Alternate Text Mark As Answer if a post answers your question.

     
  • Thursday, November 15, 2012 3:00 PM
     
     
    Sign In to Vote
    0
    No worries, you had the best of intentions.