D
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
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