Domain Design

[Rob]

I have a Windows 2003 Server at my first location. I want to set up a new
server at a second location. I want the first location to be able to access
all the files on the server at the second location but the second location
should have no access to first location. Should I just set up the second
server as child domain and give people from the first location access to the
child domain but no vice versa?

Thanks.

Rob

 

[Ace Fekay [MVP]]

In

I have a Windows 2003 Server at my first location. I want to set up
a new server at a second location. I want the first location to be
able to access all the files on the server at the second location but
the second location should have no access to first location. Should
I just set up the second server as child domain and give people from
the first location access to the child domain but no vice versa?

Thanks.

Rob

You could do this, but a child domain is always additional administrative
overhead. If you don't want the users to access any files or printers, etc,
you can still make another DC in your current domain, but just do not allow
users to access those resources. It's up to you to allow/prevent resource
access by user accounts. Unless I'm missing something in your intentions...

--
Regards,
Ace

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================

 

[Enkidu]

I have a Windows 2003 Server at my first location.
I want to set up a new server at a second location.
I want the first location to be able to access
all the files on the server at the second location
but the second location should have no access to
first location. Should I just set up the second
server as child domain and give people from the
first location access to the child domain but no
vice versa?

Like Ace says. Set up the second location as a second SITE,
same domain.

The permissions thing is a separate issue. I don't think
that you have given quite enough information. It would be
useful to know why you want to do this.

Cheers,

Cliff