Re: GPO for slow network detection not reliable
- From: "Darren Mar-Elia" <dmanonymous@xxxxxxxxxxxxx>
- Date: Tue, 10 Jul 2007 07:52:57 -0700
Franz-
Slow link detection for Group Policy is different than slow link detection for user profiles. Slow link detection for user profiles *does* ping the user profile server for the user, not the authenticating DC. Hope that helps.
--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policy
Simplify Group Policy Troubleshooting with the NEW GPExpert Troubleshooting Pak 1.0 at http://www.sdmsoftware.com/products.php
Visit the GPOGUY: http://www.gpoguy.com -- The Windows Group Policy Information Hub:
FAQs, Training Videos, Whitepapers and Utilities for all things Group
Policy-related
"Franz Schenk" <franz.schenkNOSPAM@xxxxxxxxxxxxxxxx> wrote in message news:e7FP$VswHHA.4588@xxxxxxxxxxxxxxxxxxxxxxx
Hi
Thanks to your blog, I know now why it doesn't work: Slow link detection runs against the authenticating DC, and there are DC's available at each location, so the link speed is always considered as fast even if the user roaming profile is stored at the remote location.
What we need is that the client's don't load roaming profiles from remote locations, and especially do not save the profiles to a server at a remote location (because saving the user profile takes much more time than loading).
So what we need is something like slow link detection to the server where the roaming profiles are stored. The "best" solution we have so far is to instruct the users to plug out the network cable before logging off at a remote location. If you or anyone else has a better idea to solve this problem, I'm looking forward to know about it.
Thanks a lot
regards,
Franz
"Florian Frommherz [MVP]" <florian@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> schrieb im Newsbeitrag news:eCJWhYrwHHA.1208@xxxxxxxxxxxxxxxxxxxxxxxHowdie!
Franz Schenk schrieb:Have a customer whose clients are roaming between two locations which are connected over a VPN with a 5 to 10 MBit/s Link. LAN speed is 100MBit/s. The customer wants that the clients load and save the server roaming profile only when they are on the location with the home server, and using the local cached profile when working at the remote location.
Have configured at computer- admin templates - system - logon - "slow network connection timeout for user profiles" to a value of 20000 (20MBit/s) and a timeout of 3ms (a ping to the remote location takes about 5 ms). Despite of these settings, the computer sometimes still tries to save the profile to the remote server when logging off.
Well, the Slow Link Detection works with ping commands - you could either try to figure out the threshold by when the slow link detection comes to work or - if possible - block the ping command from the outside VPN clients. That would result in an automatic "slow link".
http://support.microsoft.com/kb/227260
http://www.frickelsoft.net/blog/?p=33
cheers,
Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
.
- Follow-Ups:
- Re: GPO for slow network detection not reliable
- From: Franz Schenk
- Re: GPO for slow network detection not reliable
- References:
- GPO for slow network detection not reliable
- From: Franz Schenk
- Re: GPO for slow network detection not reliable
- From: Florian Frommherz [MVP]
- Re: GPO for slow network detection not reliable
- From: Franz Schenk
- GPO for slow network detection not reliable
- Prev by Date: Drive mapping
- Next by Date: Re: GPO Error 1030 - Help Please!
- Previous by thread: Re: GPO for slow network detection not reliable
- Next by thread: Re: GPO for slow network detection not reliable
- Index(es):
Relevant Pages
|