Set Logon Server

I have a 2003 domain with 2 DC's and they are both in the Default First Site.
1 in the main office holds all the roles and the other one is in a branch
office is basically for logon purposes to cut WAN traffic. I did a SET
command on a computer in the branch office and noticed that the logon server
reported the one in the main office. I also have a remote office with 3
computers in it with no server and they come all the way back to the main
server when they are closer to the branch office. IS there a group policy I
can set to make them login to the closet server or do I have to create sites?
If so - how do I get the remote office with 3 computers to log into the
branch site?
--
Thanks in Advance - Marcus

Danny
Thu May 01 08:46:38 PDT 2008

You have to create sites.


> If so - how do I get the remote office with 3 computers to log into the
> branch site?

Add them to the branch site.


hth
DDS

"mcrow7" <mcrow7@discussions.microsoft.com> wrote in message
news:F5D164A0-3BC5-47DC-AB20-E25E5F0C6F68@microsoft.com...
>I have a 2003 domain with 2 DC's and they are both in the Default First
>Site.
> 1 in the main office holds all the roles and the other one is in a branch
> office is basically for logon purposes to cut WAN traffic. I did a SET
> command on a computer in the branch office and noticed that the logon
> server
> reported the one in the main office. I also have a remote office with 3
> computers in it with no server and they come all the way back to the main
> server when they are closer to the branch office. IS there a group policy
> I
> can set to make them login to the closet server or do I have to create
> sites?
> If so - how do I get the remote office with 3 computers to log into the
> branch site?
> --
> Thanks in Advance - Marcus

Marcin
Thu May 01 09:11:00 PDT 2008

Marcus,
create separate AD sites for your branch and remote office and associate
each with IP subnets at those locations. Create site links that reflect your
network connections between these locations and ensure that the cost of the
one between the remote and branch offices is lower than the one to the main
office.
Alternatively, if you don't expect any near term expansion of your remote
office, you might want to consider including it in your branch office
site...

hth
Marcin

mcrow7
Thu May 01 09:48:34 PDT 2008

Thanks for you imediate reply -

The remote office does not have a domain controller. From what you replied -
will this still work for the remote office with just 4 Workstations logging
into the closest DC?

Once I create the sites - the workstation will just auto login to there new
DC? I dont have to do do anything else except create the sites and the
subnets?

--
Thanks in Advance - Marcus


"Marcin" wrote:

> Marcus,
> create separate AD sites for your branch and remote office and associate
> each with IP subnets at those locations. Create site links that reflect your
> network connections between these locations and ensure that the cost of the
> one between the remote and branch offices is lower than the one to the main
> office.
> Alternatively, if you don't expect any near term expansion of your remote
> office, you might want to consider including it in your branch office
> site...
>
> hth
> Marcin
>

Marcin
Fri May 02 17:23:07 PDT 2008

As long as the site link costs reflect your intention and DNS is working
properly... Site coverage mechanism is automatic - even in absence of local
DC...

hth
Marcin

"mcrow7" <mcrow7@discussions.microsoft.com> wrote in message
news:BEB93AEA-6D50-4E9D-800A-9B035820D969@microsoft.com...
> Thanks for you imediate reply -
>
> The remote office does not have a domain controller. From what you
> replied -
> will this still work for the remote office with just 4 Workstations
> logging
> into the closest DC?
>
> Once I create the sites - the workstation will just auto login to there
> new
> DC? I dont have to do do anything else except create the sites and the
> subnets?
>
> --
> Thanks in Advance - Marcus
>
>
> "Marcin" wrote:
>
>> Marcus,
>> create separate AD sites for your branch and remote office and associate
>> each with IP subnets at those locations. Create site links that reflect
>> your
>> network connections between these locations and ensure that the cost of
>> the
>> one between the remote and branch offices is lower than the one to the
>> main
>> office.
>> Alternatively, if you don't expect any near term expansion of your remote
>> office, you might want to consider including it in your branch office
>> site...
>>
>> hth
>> Marcin
>>