Re: Windows 2003 Enterprise and SBS 2003 Domain Coexistence

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Seay (seay_at_mail.com)
Date: 09/16/04

  • Next message: Larrycoe: "Re: DHCP Has Blue exclamation mark" 
    Date: Thu, 16 Sep 2004 00:10:26 -0500

    Just curious, can I during this period ALSO move my mailbox from Exchange
    2003 Ent (Exchange in the domain I want to move FROM) into the Exchange 2003
    SBS Edition (destination domain - SBS domain of course) - while I have this
    coexistence - Again, I have licensing issues I need to comply with and we
    are below 50 users.

    BTW, do you have your own site for these kind of info - very good info you
    have!

    "Javier Gomez [SBS MVP]" <javier_gomez@remove.this.engineer.com> wrote in
    message news:%23mypJT5mEHA.3100@TK2MSFTNGP10.phx.gbl...
    > You are correct. However, I didn't mention that you have 7 days to
    > complete this... if at that time the SBS install is not finished you will
    > start getting warnings and eventually the server will shutdown within the
    > hour. So, it is imperative that you dcpromo it, transfer all fsmo roles
    > and continue the integrated setup.
    >
    > Cheers,
    >
    > --
    > Javier [SBS MVP]
    >
    > << SBS ROCKS !!! >>
    >
    > "Seay" <seay@mail.com> wrote in message
    > news:eVr13s3mEHA.3480@TK2MSFTNGP09.phx.gbl...
    >> Thx Javier...to confirm with you...what you are saying is install SBS
    >> 2003 as a normal server and join to domain...then DCPROMO it in the new
    >> domain to function as a DC in the existing domain and transfer roles?
    >> So it really functions as "normal" server that can be DCPROMO as "normal:
    >> standard W2K3 server! WOW if thats correct.
    >>
    >>
    >>
    >>
    >> "Javier Gomez [SBS MVP]" <javier_gomez@remove.this.engineer.com> wrote in
    >> message news:O$zLOnxmEHA.3684@TK2MSFTNGP10.phx.gbl...
    >>> With SBS2k3 you can just install the OS portion (first part of the
    >>> installation) and join it to the existing domain. You would have to
    >>> DCPromo manually and transfer all FSMO roles and then continue with the
    >>> integrated setup. If you are just starting... I suggest you start over,
    >>> this looks much more simple than what it really is.
    >>>
    >>> BTW-> SBS does not have SharePoint Portal Server (SPS), it has Windows
    >>> SharePoint Services (WSS). Two differente beasts :-)
    >>>
    >>> BTW2-> The NG for SBS2k3 is microsoft.public.windows.server.sbs
    >>>
    >>> --
    >>> Javier [SBS MVP]
    >>>
    >>> << SBS ROCKS !!! >>
    >>>
    >>> "Michael Jenkin [SBS-MVP]" <michael.jenkin@mvps.org> wrote in message
    >>> news:ufMtsswmEHA.596@TK2MSFTNGP11.phx.gbl...
    >>>> Hello Seay,
    >>>>
    >>>> Sbs needs to be the root of the forest hence top level domain
    >>>> controller. It can not join another domain. An SBS network can have
    >>>> many
    >>>> domain controllers but they are all in the same domain (Again with SBS
    >>>> being the root). SBS can not form trusts.
    >>>>
    >>>> There are a number of things you could do.
    >>>>
    >>>> One item I have done a few times (Just to get the data etc over)
    >>>>
    >>>> Turn off DHCP on the SBS server, make sure it has an IP valid on the
    >>>> existing network, make an aco*** with the same username/password on
    >>>> both networks as administrators, link network drives to any data
    >>>> needed,
    >>>> dump accross any data, extract out user account info with any of the
    >>>> vbs
    >>>> tools out there then break all links with the current domain and build
    >>>> the SBS box as it's own network with the view to never join to the old
    >>>> network (it now serves as a backup of your data until your first good
    >>>> backup). Turn on DHCP again.
    >>>>
    >>>> The vbs scripts can migrate all user data out as a CSV file and then
    >>>> import again with other vbs scripts. (if all you need is the user
    >>>> acocunts you go forgo all this and do it to a usb key or floppy disk).
    >>>>
    >>>> I am not aware of any way to dirrectly connect the AD's and migrate the
    >>>> data over. SBS cannot act as a bridgehead in this way.
    >>>>
    >>>> There will be other ways. I know my way (which might be allot of work
    >>>> compared to another way). There will be more advice from others so hang
    >>>> in there and someone who might know more than my expeariance might
    >>>> reply
    >>>> to you !
    >>>>
    >>>> Seay wrote:
    >>>>
    >>>>> I have initially created a Windows 2003 Enterprise AD network - 2 DC
    >>>>> and 2
    >>>>> Enterprise FS
    >>>>>
    >>>>> I realized this was an overkill so what I want to do is go to SBS 2003
    >>>>> Domain - 2003 AD
    >>>>>
    >>>>>
    >>>>> Question:
    >>>>> ----------
    >>>>> Can I join an SBS 2003 server into my current Windows 2003 Ent based
    >>>>> domain?
    >>>>> <-- THIS is the MAIN question
    >>>>>
    >>>>> I am wanting to copy my users and computers into the SBS 2003 and take
    >>>>> advantage of the 'budled' softwares - Exchange 2003 and SPS 2003.
    >>>>>
    >>>>>
    >>>>> Please do not discuss the "better" or "cheaper" etc option - I would
    >>>>> simply
    >>>>> like to know if you can to transfer objects over.
    >>>>>
    >>>>> Thank you.
    >>>>>
    >>>>>
    >>>>
    >>>> --
    >>>> Michael J. Jenkin MVP - SBS, Senior Systems Engineer , Millennium
    >>>> Business Solutions
    >>>> Microsoft Most Valued Professional, Microsoft's Windows Server
    >>>> Systems -
    >>>> Small Business Server
    >>>> MVP's do not work for Microsoft. If this email was generated in a
    >>>> newsgroup, please reply only to the newsgroup.
    >>>> Note: The contents of my postings and responses here represent my
    >>>> personal opinions and do not necessarily reflect the views, thoughts or
    >>>> feelings of Microsoft or any of its employees.
    >>>> http://mvp.support.microsoft.com
    >>>>
    >>>>
    >>>
    >>>
    >>
    >>
    >
    >

  • Next message: Larrycoe: "Re: DHCP Has Blue exclamation mark"
    • Quantcast