Windows Vista Forums

Getting New Server - Coming from SBS2003 domain

  1. #1


    PorBar Guest

    Getting New Server - Coming from SBS2003 domain

    I posted this to the wrong group..sorry for any cross-post:

    We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
    going to replace a SBS2003 Server. The Client OSs are a mixture of
    2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
    install the new Server.

    We assume on the clients we will just have to join them to the "new"
    domain, and we can either keep the same computer name or change it.

    Does anyone foresee any issues with connecting these clients? For
    instance what will happen to the user profiles (desktops,
    Favorites,etc) when they connect to this new Server.

    Or, would we be better off using a new domain name? Pros/Cons??

    Thanks!

      My System SpecsSystem Spec

  2.   


  3. #2


    Lanwench [MVP - Exchange] Guest

    Re: Getting New Server - Coming from SBS2003 domain

    PorBar <compsosinc@newsgroup> wrote:

    > I posted this to the wrong group..sorry for any cross-post:
    Correction: that would be a "multipost" ..but that's ok as you've confessed
    and apologized. ;-)

    >
    > We have purchased a new 2003 R2 Server (Hardware, OS & CALs) that is
    > going to replace a SBS2003 Server. The Client OSs are a mixture of
    > 2kPro, XP SP2 & SP3.We want to keep the same Domain name when we
    > install the new Server.
    >
    > We assume on the clients we will just have to join them to the "new"
    > domain, and we can either keep the same computer name or change it.
    >
    > Does anyone foresee any issues with connecting these clients? For
    > instance what will happen to the user profiles (desktops,
    > Favorites,etc) when they connect to this new Server.
    >
    > Or, would we be better off using a new domain name? Pros/Cons??
    >
    > Thanks!
    There are really very few "pro" arguments re creating a new domain unless
    your old one is named MYBOSSSUCKS.local and said boss has no sense of humor.

    Since you won't have Exchange after you get rid of SBS (I assume) you will
    need to get the mail dumped out to PST files.

    You can join the new server to the domain and make it a DC, but you will
    have to use a new name. Migrate your data over and change your login
    scripts. When you've made it a DC and global catalog server you can
    disconnect the old SBS box from the domain and sieze the FSMO roles to the
    new server ... and then you'll need to do some cleanup in AD to remove all
    traces of the SBS box. ADSIEdit is your friend here.
    http://support.microsoft.com/kb/216498 You're also going to have traces of
    Exchange in AD which you will need to clean up if you ever want Exchange
    again.

    Mind you, I have never done this with an SBS box but it should work.




      My System SpecsSystem Spec

  4. #3


    Ace Fekay [MCT] Guest

    Re: Getting New Server - Coming from SBS2003 domain

    "PorBar" <compsosinc@newsgroup> wrote in message
    news:c774dda8-1d40-4184-9118-2782546f0b4f@newsgroup

    >I posted this to the wrong group..sorry for any cross-post:
    >

    I saw your post in the other group. I cross-posted it to this group, before
    I saw this one.

    And yes, you multi-posted it, as Lanwench said. Cross-posting is when you
    select multiple groups at the same time when posting it. You posted it with
    two separate postings.

    Ace


      My System SpecsSystem Spec

  5. #4


    PorBar Guest

    Re: Getting New Server - Coming from SBS2003 domain

    On Sep 1, 2:03*pm, "Ace Fekay [MCT]" <ace...@newsgroup>
    wrote:

    > "PorBar" <compsos...@newsgroup> wrote in message
    >
    > news:c774dda8-1d40-4184-9118-2782546f0b4f@newsgroup
    >

    > >I posted this to the wrong group..sorry for any cross-post:
    >
    > I saw your post in the other group. I cross-posted it to this group, before
    > I saw this one.
    >
    > And yes, you multi-posted it, as Lanwench said. Cross-posting is when you
    > select multiple groups at the same time when posting it. You posted it with
    > two separate postings.
    >
    > Ace
    Ok -thanks for the input. With the new server, since this is just a 15-
    user network, and we did not "use" Exchange (meaning the users have no
    email and they did not send internally either), and some employees
    have left, etc..we plan on recreating the user & computer accounts.
    Had just the default GPO, default login scripts with SBS. Printers
    installed manually etc..very little if any "automation".

    Just curious if the SBS clients would have to "rejoin" the domain the
    new Server (ie run the network connection wizard on each) if the
    domain name is kept the same? Also the SBS clients have static IP
    addresses and we are thinking of letting the new sever be a DHCP & DNS
    Server. Any advice here?

    We do not intend to join the new server to the current domain. Just
    get it ready with its roles (DC, DNS, DHCP) then shutdown the SBS and
    start connecting the clients. We figured the client/user profiles will
    have to be recreated-they were not roaming, etc.

    Thanks again..await your feedback.

      My System SpecsSystem Spec

  6. #5


    Ace Fekay [MCT] Guest

    Re: Getting New Server - Coming from SBS2003 domain

    "PorBar" <compsosinc@newsgroup> wrote in message
    news:821d3060-6f2a-4806-a90e-60639e32247c@newsgroup
    On Sep 1, 2:03 pm, "Ace Fekay [MCT]" <ace...@newsgroup>
    wrote:

    > "PorBar" <compsos...@newsgroup> wrote in message
    >
    > news:c774dda8-1d40-4184-9118-2782546f0b4f@newsgroup
    >

    >>

    >>> I posted this to the wrong group..sorry for any cross-post:
    >>
    >> I saw your post in the other group. I cross-posted it to this group,
    >> before
    >> I saw this one.
    >>
    >> And yes, you multi-posted it, as Lanwench said. Cross-posting is when you
    >> select multiple groups at the same time when posting it. You posted it
    >> with
    >> two separate postings.
    >>
    >> Ace
    >
    > Ok -thanks for the input. With the new server, since this is just a 15-
    > user network, and we did not "use" Exchange (meaning the users have no
    > email and they did not send internally either), and some employees
    > have left, etc..we plan on recreating the user & computer accounts.
    > Had just the default GPO, default login scripts with SBS. Printers
    > installed manually etc..very little if any "automation".
    >
    > Just curious if the SBS clients would have to "rejoin" the domain the
    > new Server (ie run the network connection wizard on each) if the
    > domain name is kept the same? Also the SBS clients have static IP
    > addresses and we are thinking of letting the new sever be a DHCP & DNS
    > Server. Any advice here?
    >
    > We do not intend to join the new server to the current domain. Just
    > get it ready with its roles (DC, DNS, DHCP) then shutdown the SBS and
    > start connecting the clients. We figured the client/user profiles will
    > have to be recreated-they were not roaming, etc.
    >
    > Thanks again..await your feedback.
    If you want to keep the same name, but not the same domain, meaning to start
    fresh, then all the workstations will need to be disjoined first prior to
    unplugging the current machine, because you can't have the current one up
    and running when you install the new one. So it's better off disjoining them
    first. Just make sure you know the local admin password prior to the
    dis-joining. Once the new domain is up and running, then you can join them
    to the new domain.

    As far as keeping current GPOs, they will be part of the old domain, so they
    will no longer exist in the new domain. However, you can copy them over, but
    they must be saved to a file first before unplugging the old DC.

    Migrating GPOs Across Domains
    You can use a copy operation to transfer settings to a new GPO in the same
    domain, another domain in the same forest, or a domain in another ...
    http://technet.microsoft.com/en-us/l...43(WS.10).aspx

    Copy a Group Policy object using GPMC
    http://technet.microsoft.com/en-us/l...87(WS.10).aspx

    Some tips and guidelines:

    1. Before disjoining the workstations, copy all user data (My docs, Outlook
    PSTs if any, data they may have saved on their desktops, etc, to a thumb
    drive, your laptop, or somewhere else.
    2. Make sure you don't select a single label name
    2. DCPROMO will install DNS for you. Make sure you have a copy of the i386
    folder on c: drive to make it easier. Make sure the copy of i386 is of the
    same SP level or you will need to re-run the service pack after you install
    a non-same level SP source to a greater SP level installation. This goes for
    any other services such as WINS, DHCP, etc.
    3. Since this is a non-SBS DC that you are creating, it is highly advised,
    and recommended, to NOT multihome it nor install RRAS on it. SBS can handle
    multihoming perfectly with the wizards. With non-SBS, it introduces
    complications that will pull your hair out. Allow your firewall/router to
    handle internet access. If there are two NICs on the new server, either
    disable one of them, or team them, but do not use both on separate networks.
    There are registry changes you can make, along with a handful of other
    changes to make it work (I can provide a multipage step by step if you want)
    to make a multihomed DC work, but it vastly changes a DC's default behavior.
    4. Once dcpromo has changed, change the DNS address from the loopback
    (127.0.0.1) to the actual IP of itself.
    5. Make sure to not use the ISP's DNS, the router as a DNS address, or any
    other external DNS server that has no reference to your internal AD DNS
    domain name.
    6. If you need VPN services, install RRAS on a non-DC, or use your robust
    firewall (such as a Cisco ASA, Netscreen, etc) to provide these services.

    I hope that helps.

    Ace


      My System SpecsSystem Spec

  7. #6


    Kerry Brown Guest

    Re: Getting New Server - Coming from SBS2003 domain


    "PorBar" <compsosinc@newsgroup> wrote in message
    news:821d3060-6f2a-4806-a90e-60639e32247c@newsgroup

    > On Sep 1, 2:03 pm, "Ace Fekay [MCT]" <ace...@newsgroup>
    > wrote:

    >> "PorBar" <compsos...@newsgroup> wrote in message
    >>
    >> news:c774dda8-1d40-4184-9118-2782546f0b4f@newsgroup
    >>

    >> >I posted this to the wrong group..sorry for any cross-post:
    >>
    >> I saw your post in the other group. I cross-posted it to this group,
    >> before
    >> I saw this one.
    >>
    >> And yes, you multi-posted it, as Lanwench said. Cross-posting is when you
    >> select multiple groups at the same time when posting it. You posted it
    >> with
    >> two separate postings.
    >>
    >> Ace
    >
    > Ok -thanks for the input. With the new server, since this is just a 15-
    > user network, and we did not "use" Exchange (meaning the users have no
    > email and they did not send internally either), and some employees
    > have left, etc..we plan on recreating the user & computer accounts.
    > Had just the default GPO, default login scripts with SBS. Printers
    > installed manually etc..very little if any "automation".
    >
    > Just curious if the SBS clients would have to "rejoin" the domain the
    > new Server (ie run the network connection wizard on each) if the
    > domain name is kept the same? Also the SBS clients have static IP
    > addresses and we are thinking of letting the new sever be a DHCP & DNS
    > Server. Any advice here?
    >
    > We do not intend to join the new server to the current domain. Just
    > get it ready with its roles (DC, DNS, DHCP) then shutdown the SBS and
    > start connecting the clients. We figured the client/user profiles will
    > have to be recreated-they were not roaming, etc.
    >
    > Thanks again..await your feedback.
    Why not keep the SBS server as is, join the new server to the domain, and
    use the new server only for the new application? This way the application
    will be running on a server dedicated to it. If the vendor is recommending
    to not install the app on an SBS server why are they happy installing it on
    a DC with several roles?

    --
    Kerry Brown
    MS-MVP - Windows Desktop Experience: Systems Administration
    http://www.vistahelp.ca/phpBB2/





      My System SpecsSystem Spec


Getting New Server - Coming from SBS2003 domain
Similar Threads
Thread Forum
restore windows 2000 domain controller to SBS2003 domain Server General
Possible domain name problem coming SBS Server
New Server -Coming from SBS2003 domain Server General
Re: New Server -Coming from SBS2003 domain SBS Server
Replace 2003 domain server with SBS2003 Vista Forums