Re: Child domain?
- From: <paul_lemonidis@xxxxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Fri, 2 May 2003 14:11:34 +0100
Hi Doug
From what you say you would be best off with two separate AD forests combined
using some sort of Meta Directory Service. Something like Simple Sync
(http://www.cps-systems.com/) may well give you what you need.
Be aware that splitting them off from you altogether is no small job.
Rebuilding an AD domain from scratch will break virtually everything that of
theirs that is in your current domain.
Hope that helps.
Bye for now.
Paul.
----- Original Message -----
From: Stelley, Doug
To: [ExchangeList]
Sent: Friday, May 02, 2003 1:45 PM
Subject: [exchangelist] Re: Child domain?
http://www.MSExchange.org/
You see? That's why I wanted to begin planning early!
We will have to maintain their servers & software for them here
at the main site, but from a user standpoint, they will be split into a new
organization. New Addressing / naming convention et.al.
Logically, a completely new AD with E2k would be best, but we
need to be the Enterprise admin overall.
-----Original Message-----
From: paul_lemonidis@xxxxxxxxxxx [mailto:paul_lemonidis@xxxxxxxxxxx]
Sent: Friday, May 02, 2003 8:30 AM
To: [ExchangeList]
Subject: [exchangelist] Re: Child domain?
http://www.MSExchange.org/
Hi Doug
SBS will only allow to you to create a new Forest with the server being the
root of it. Thus I am farid what you are propsoing isn't possible with SBS.
However, you could install a Windows 2003 server in to a workgroup and then
install AD and create a child Domain within the smae Forest. Do remember that
if they subsequently wish to install E2K or E2K3 on the server or another
server in their child Domain they will be using your Global Address List as
they will still be in your Domain forest. would that be a problem? If it is the
best long term solution, although rather laborious to say the least, may be to
create them their own independent AD strcuture.
Hope that helps.
Regards,
Paul Lemonidis.
----- Original Message -----
From: Stelley, Doug
To: [ExchangeList]
Sent: Friday, May 02, 2003 1:07 PM
Subject: [exchangelist] Child domain?
http://www.MSExchange.org/
My organization has to spin off some of our clinics in a few months; I'd
like to run this by you all.
Currently the users there are in our domain, and use our exchange for mail
etc.
Can I buy them a new server with SBS(Small Business Server), create a new
child domain in our existing forest using SBS?
Or maybe a server with Windows Server 2003, promote to a domain controller
in its own child domain, with exchange 2000 standard (I have an unused
license). There are only about 50 users there. I'm looking for the best
solution, and need to plan for it now.
Doug Stelley
Network Admin.
Olean General Hospital
(716)375-7320
Absence is to love what wind is to fire; it extinguishes the small, it
enkindles the great. - Comte de Bussy-Rabutin
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
paul_lemonidis@xxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
_______________________
Confidentiality Notice: The information contained in this message may be
legally privileged and confidential information intended only for the use of
the individual or entity named above. If the reader of this message is not the
intended recipient, or the employee or agent responsible to deliver it to the
intended recipient, you are hereby notified that any release, dissemination,
distribution, or copying of this communication is strictly prohibited. If you
have received this communication in error please notify the author immediately
by replying to this message and deleting the original message. Thank you.
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
dstelley@xxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
ISA Server Resource Site: http://www.isaserver.org
Windows Security Resource Site: http://www.windowsecurity.com/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSExchange.org Discussion List as:
paul_lemonidis@xxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
_______________________
Confidentiality Notice: The information contained in this message may be
legally privileged and confidential information intended only for the use of
the individual or entity named above. If the reader of this message is not the
intended recipient, or the employee or agent responsible to deliver it to the
intended recipient, you are hereby notified that any release, dissemination,
distribution, or copying of this communication is strictly prohibited. If you
have received this communication in error please notify the author immediately
by replying to this message and deleting the original message. Thank you.
Other related posts:
