[gptalk] Re: always wait for network at computer startup or logon
- From: rpo <rpo8373@xxxxxxxxx>
- To: gptalk@xxxxxxxxxxxxx
- Date: Mon, 15 Sep 2008 11:21:03 +1000
hi guys,
thanks for the replies.
so do you guys recommend this setting be used or not? i am seeing some
slight speed improvements by disabling "always wait for network at
computer startup or logon", and it's apparently the default windows xp
settings. but i'd be interested to know what the majority are doing
with this setting.
additionally, scrutinising the userenv.log further this morning i've
noticed that between the machine policy determining the link speed and
the gpos beginning processing there is a huge gap of timing passing
(anywhere between 30 and 100 seconds) where it is loading the system,
nt authority, etc profiles and running processes that need to run as
the system user, including our mcafee antivirus services and sms 2003
(ccmexec) service.
i have tested removing these from a local machine and can see a
considerable speed increase. is there something i can do to reduce
these processes' impact on the system startup?
daniel.
On 11/09/2008, Florian Frommherz <florian@xxxxxxxxxxxxxxx> wrote:
> Howdie!
>
> > in trying to reduce startup/logon times. i'm reviewing a policy that
> > has "always wait for network at computer startup or logon" set to
> > enabled. in my testing ou, i've disabled it and startup times have
> > decreased by around a min. apparently the default setting is disabled,
> > but i'd like to hear about people's opinions on this setting? should
> > it be on or off.
>
> "Always wait for the network" basically makes XP machines wait for the
> network to be fully loaded before going on further and showing the user the
> logon screen as a result. With that policy you can make sure that users (and
> the machine) have access to the network and DCs at the time they log on.
> Policies get applied right-away without having to wait for the background
> refresh (some policies don't become "active" if they're applied in
> background).
>
> > additionally, in regards to the startup slowness, i notice there seems
> > to be a long wait at "applying computer settings". what exactly occurs
> > here? i've used policy reporter and it shows that during machine
> > policy refresh, establishing the link speed and determining it is a
> > fast link takes less than a second, there is then a 20-30 sec delay in
> > the log before anything else starts happening, can anyone shed some
> > light on this?
>
> How are those machines connected? Is your DNS config on the client healthy?
>
> Cheers,
>
> Florian
>
> ***********************
> You can unsubscribe from gptalk by sending email to
> gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by
> logging into the freelists.org Web interface. Archives for the list are
> available at //www.freelists.org/archives/gptalk/
> ************************
>
***********************
You can unsubscribe from gptalk by sending email to
gptalk-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field OR by
logging into the freelists.org Web interface. Archives for the list are
available at //www.freelists.org/archives/gptalk/
************************
Other related posts:
