Roaming profiles and slow network detection

[Dussan Pirc]

In "How a Slow Link Is Detected for Processing User Profiles and
Group Policy" (http://support.microsoft.com/kb/227260), writes that slow
network is calculating from

C:\>ping -l 2048 remote-domain-controller.domain.tld


I'm interesting in what "remote-domain-controler.domain.tdl" stands for!

If it is pinging first domain controller than it is useless for my purpose.
Some of my users are traveling with their laptops to other offices, which
have DC, but their roaming profiles are on server, which is in the main
office. Avg. ping between branch and main office is 100 to 200 ms.

I was trying to set different values for "slow network" (from 100 to
50.000) but no success, only at last parameter (50.000) I get the remark
about slow network.

I thing it laptop is pinging local DC not the server where roaming profiles
are stored.


Can anyone confirm that?

Any other suggestions for saving problems with roaming profiles and
laptops. Folder redirection have the same problem.

With regards,
Dussan

 

[Guest]

Hi,


I think that you are looking for slow connection for roaming user profiles
under Computer Configuration | Administrative Templates | System | User
Profiles
That setting is specific to roaming profiles.

Regards,

VMM

 

[Dussan Pirc]

Yes, I have already change that, but, like I wrote, it is using the
closest AD controller, not the server with roaming profiles...

With regards,
Dussan

 

[Florian Frommherz]

Howdie Dussan!

Yes, I have already change that, but, like I wrote, it is using the
closest AD controller, not the server with roaming profiles...

Active Directory and clients are designed to always use the closest
(fastest answering) domain controller as the %logonserver% to
authenticate with.

I don't understand why this is an issue for you, since the roaming
profile is given in the form \\servername\share ?

cheers,

Florian

 

[Dussan Pirc]

Please, read my original post - I have problems with roaming profiles when
users are on different location where AD is "near", but server with roaming
profiles is "far".

With regards,
Dussan