Hello khan,
I can second Florians suggestion complete. There is no need for a child domain
in your case. Us OUs to separate the offices in AD and this way you can also
use delegate control to have site admins without being domain administrator
to manage the site related tasks. Even if this requires more time to configure
the permissions for them you are able to control the sites setup easier as
with child domains.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> On Mar 27, 9:19 pm, Florian Frommherz
> <flor...@LEAVETHISOUT.frickelsoft.net> wrote:
>> Howdie!
>>
>> Am 27.03.2010 15:48, schrieb khan:
>>
>>> Respected EveryOne
>>>
>>> In my office we have a Primary Server (192.168.0.52) as a Active
>>> Directory server.A secondary server for stand by(192.168.0.198).We
>>> have internal Exchange mail server (192.168.0.53).And a ISA 2004
>>> server is for Edge Firewall(192.168.0.199).There are some
>>> application servers and 150 client computer in our office.
>>> Now what is my questions are follows
>>> 1.We are going to open three brange offices in different locations
>>> which are each contain atleast 50 clients.If that we need to connect
>>> this diffent offices client computers to our main office Server for
>>> Active directory service and application services and internal
>>> exchange mail use. For that we need to create a secondary domain for
>>> this offices
>> No, no - you don't create a seperate domain for that. You stay in the
>> same domain here. You'd need to consider whether you'll place a DC in
>> the branch office or not in case the WAN link between the branch and
>> the head office is down -- and think about the consequences and
>> whether you want a DC there or not.
>>
>> What you - in any case - need to configure is Active Directory Sites
>> and Services and configure the site constellation as it is in real
>> life. That allows AD to tie its replication to a schedule that you
>> create so that bandwidth utilization of replication doesn't chew up
>> all speed available. Sites&Services is the way to go. Stay in one
>> domain as long as possible.
>>
>>> 2.We need to give laptop users to access our Application as well as
>>> active directory from outside of our office promises
>>> So what is the best solution to create this infrastructure
>>> efficiantly .
>> Well, that second requirement runs pretty independently in my
>> opinion. I'd probably try to put a Terminal Server in place and have
>> laptop users connect to the terminal server and use that app from
>> there. If that doesn't work for you (maybe the app isn't built that
>> way), think about a VPN connection from the laptops to the head
>> office.
>>
>> Cheers,
>> Florian
> Hi
>
> Yes,we must place a DC in every branch office.But what i need to know
> means how could we do it in a best manner.So that it is working very
> effectively.any best articals or way to do it .I mean creating a
> chield domain or Sub domain Or connecting it with a VPN or Broad band
> line Or leased line with this offices.How to make this secondary
> domain.
>
> The second think is how do to it in VPN or Terminal Server for
> application users.
>
> Thanks & Regards
>
> Nawas Khan
>
Similar Threads
Linear Mode
