Maybe you could do a copy as part of a login script instead. Or something with roaming profiles. If you put a copy of the .default profile to your netlogon share, it will be used by the clients for seeding their profile rather than the one on their local machine.
Sent from my iPhone On Jan 15, 2009, at 5:22 AM, Patrick <london31uk@xxxxxxxxx> wrote:
The whole idea is to standardise the staff start menu, what ever pc they log onto. With all the necessary icon nd shortcuts they need.From: Greg Reese <gareese@xxxxxxxxx> To: windows2000@xxxxxxxxxxxxx Sent: Wednesday, January 14, 2009 11:30:50 PM Subject: [windows2000] Re: redirected start menu nightmarewhat are you trying to accomplish by redirecting the start menu. Just curious. There might be some other techniques to get you to the same place.Greg On Wed, Jan 14, 2009 at 5:01 PM, Patrick <london31uk@xxxxxxxxx> wrote: Thanks JimI tried that but did not work, so just like you suggested there might be latency somewhere else. What I did notice though was that browsing the share that held the start menu was very slowFrom: Jim Kenzig http://thin.ms <jkenzig@xxxxxxxxx> To: windows2000@xxxxxxxxxxxxx Sent: Wednesday, January 14, 2009 5:40:41 PM Subject: [windows2000] Re: redirected start menu nightmare There is a start menu key at HKEY_CURRENT_USER \ Control Panel \ Desktop \ MenuShowDelay400 is default and changing to a smaller number might speed it up but it could be that you have latency elsewhere.Jim Kenzig Blog: http://www.techblink.comOn Wed, Jan 14, 2009 at 11:26 AM, Patrick <london31uk@xxxxxxxxx> wrote:Hi Guys,We are redirecting our staff start menu throught group policy and staff are beging to notice a significant delay in the time it takes to have the enitre start menu populated. Any suggestions on how we can improve this.Windows 2003 Domain XP sp2 clients. Thanks Patrick
