AD question

  • Thread starter Thread starter Auddog
  • Start date Start date
A

Auddog

Just so that I get this straight I thought that I would ask. I have created
my AD for my company name company.local. We have a remote office that I
want to add to the directory and I was thinking about adding them as a child
domain named sales.company.local. I'm doing this mostly for admin purposes,
but also because the office are located a couple of hours from each other
and I don't want to tie up the connection. Now for my questions.

Will my users be able to login at either location without having to do
anything different? Will their script files (network drives, printers, etc)
follow them when they login? In my lab I setup a dumb server just like
this, but I'm unable to browser the network shares (is this due to dns)?

A
 
Auddog,

You would be better off creating the other location as a site in the same
domain and scheduling the replication in off hours or at a longer interval.
This will give you many fewer problems and will let your users roam between
locations.

Network drives and printers would follow then in either scenario due to the
fact that they would be logging into their own domain -- its just that in
the multiple domain scenario, they would always have to talk to the DC on
the other site rather than seeing the speed of the local connection.

As to the network shares... it could be due to DNS, but you haven't really
given us enough information. It could also be permissions or that you have
different networks and NetBIOS broadcasts don't cross routed boundaries.
What do you mean... can't see the computers, can't see the shares, all of
the shares, specific files?

Let me know if you have other questions?
 
Back
Top