New SBS domain - Adprep / Domainprep on the current Win2003

Discussion in 'Windows Small Business Server' started by Henrik \(Hear\), Mar 17, 2008.

  1. Hi all,


    Have a domain with a Win2000 srv as DC together with a Win2003std as a DC.
    Adding a SBS2003R2 according to
    Win2003Srv will be kelpt as a second DC in the new SBS domain.

    Regardles If the Win2K srv is kept or not (another issue, not discussed
    here), when installing the SBSR2 , are there any needs to make a adprep /
    domainprep on the Win2003 server above?

    Henrik \(Hear\), Mar 17, 2008
    1. Advertisements

  2. Henrik \(Hear\), Mar 17, 2008
    1. Advertisements

  3. Henrik \(Hear\)

    kj [SBS MVP] Guest

    Run only once on the forest schema master (if using the latest adprep).
    kj [SBS MVP], Mar 17, 2008
  4. Many Thanks KJ, thats what I thought/read ;-)
    Then Im on the right track for the client environment.
    Henrik \(Hear\), Mar 17, 2008
  5. SBS2003 is, at heart, a Windows Server 2003 DC. Since you've already
    introduced a WS2003 DC to the domain, it's likely that you already ran the
    required ADPREP steps. OTOH, you can't do any harm by running ADPREP from
    the SBS disk 1.

    IIRC, The R2 disc does another ADPREP step (to support WS2003 R2), but
    that comes late in the process anyway.
    Steve Foster [SBS MVP], Mar 17, 2008
  6. Anytime Henrik. Good luck with the project.
    /kj [SBS MVP}, Mar 17, 2008
  7. Thanks Steve,

    This domain is nativly a Win2000 Domain with an added Win2003std.
    Now they want to add the SBS2003R2 to the domain.

    My addvise have been to plan to remove the t2K machine (wich holds the
    schemas) and transfer them to the Win203 machine.

    After that, add the SBS2003 to th domain according one of the KB that
    handles this scenario.
    Sfter tha add of the SBS tarnsfer the roles to the SBS, adprep/domainprep
    the Win2003 server to support R2.

    Im trying to figure out why the client needs a second DC.

    To be honest, Im not the tech guy here Im asking the questions for another
    technician that has the client.
    So thats why there are some unanswered questions :) Helping a collegue out
    puts me here..
    Henrik \(Hear\), Mar 17, 2008
  8. LOL, didnĀ“t check my spelling before posting :-D
    Henrik \(Hear\), Mar 17, 2008
  9. Henrik \(Hear\)

    kj [SBS MVP] Guest

    While SBS2003 is akin to Windows 2003, *R2* is *not*.

    I know, sounds weird. SBS 2003 R2 does not implement the features that
    Windows 2003 R2 does when *it* is a domain controller. Specifically, Schema
    update V31 is not implemented in, not included in, nor required for SBS2003

    Schema V31 is required for a Windows 2003 R2 server to be promoted to a
    domain controller in any forest/domain, *including* a SBS2003 one.
    kj [SBS MVP], Mar 18, 2008
  10. Haha, yes, confusing, right back at me :)
    Thanks for that clarification. I need to read this thru a couple of times
    before trying to pass It on to my friend.
    LOL, even more confusing for him.

    I know that many has questions regarding the R2 update and what It brings in
    comparison with the "normal" R2 for Win2003 Std/Ent server. I new about many
    differences but not all. At least some important features are included for
    the SBS R2.
    Henrik \(Hear\), Mar 18, 2008
  11. Henrik \(Hear\)

    kj [SBS MVP} Guest

    Yes, there are several valuable new SBS R2 features. But none of them
    require (or use) the schema version 31 upgrade.

    Only regular Windows 2003 standard, enterprise, or datacenter R2 servers in
    a domain need or use the schema upgrade.
    kj [SBS MVP}, Mar 18, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.