Re: slow logon
- From: Goku 316 <aramsajan@xxxxxxxxx>
- Date: Tue, 6 Jan 2009 20:37:01 -0800
Happy new Year and sorry for the late response.
The first day i was involved with handling the GP for this AD environment i
did exactly as you said by disabling the unused sections of GP settings.
i also disabled in the logon and start up scripts the commands to sync the
time with a specific time servers.
will look into the KB315418 article for more tips but so far a few seconds
in the logon time have been reduced so far.
will also look into the sites and services topology setup as well with
microsoft.
thank you all for your help
--
Goku 316
"Jorge Silva" wrote:
Hi.
-Glad to know that part of the problem is already solved.
-Agree, you shouldn't need the net time and w32tm commands unless you're
having problems with time sync.
-Regarding to GPO, you can have settings that may slow down the login
process, run rsop.msc on the client and check what settings are being
aplied, you can also take advantage of the option "Disable computer
configuration settings" or "Disable user configuration settings" for GPOs
that are not using that section. Check KB315418
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Goku 316" <aramsajan@xxxxxxxxx> wrote in message
news:A47B581C-D63E-4D54-81A6-3C785C260BBC@xxxxxxxxxxxxxxxx
we have symantec av 10 and yes the software looks for updates from a local
server within the lan.
i have spoken to the tech support for the virus software and they
suggested
that i tell the software not to restart the services when new virus
updates
have been downloaded upon boot up but wait till a reboot is done.
disabling symantec via msconfig did boost the login but the virus software
is a neccessary bad in corporate companies. looking into other vendors
that
are not memory and cpu hogs. like sophos, viper and panda
i noticed that the login script created by the programmer has:
*********************
verify on
net time \\servername /set /yes
net use x: /del
net use g: /del
net use p: /del
net use x: \\servername\sys /y
net use g: \\servernamex\bellmarc /y
net use p: \\servernamey\public /y
w32tm /resync
***********************
i told the programmer that the domain controller at each site will check
and
update the time for the clients that talk to the dc as the logon server.
there is no need to invoke the net time or w32tm commands.
any suggestions?
also can you elaborate on the point made about GPOs can contribute to slow
logons.
--
Goku 316
"Jorge Silva" wrote:
Hi
Please see answers inline:
We have a native 2000 AD environment with a mixture of Win 2000 and
2003
DCs.
2003 are the majority. DNS is AD integrated and we have dhcp servers
serving
the clients. All clients are XP pro sp2.
Ok.
We have a Start up script and a login script for users as well as
folder
redirection for My Documents.
We have in house programs that the programmer designed and he setup the
start up script in AD to apply updates to the clients machines which is
essentially just overriding some files. Not everyday is updates applied
but
only when the programmer issues updates.
Sounds too many scripting... Note that most problems with slow logons are
related with scripts and GPO settings...
The login script maps 3 drives and one is done automatically for the
home
drive. Along with that an xcopy command is done to copy the program
updates
that will be launched upon reboot if any.
Make sure that the script detects if that update already has been made,
otherwise you may end up repeating the same task over and over...
To me this is not a good method for updating in house software but I
cannot
change this procedure for now or I will face a huge political war.
Ok, I also have no problem with that, as long as the people evolved are
aware of the consequences
Our clients’ machines have windows xp sp2 with just office 2003 and
Symantec
av software.
Is the antivirus checking updates at startup?
Clients complain of slow logon 45 to 90 seconds to see the wallpaper
and
icons.
No event ID errors, hardware errors, spyware errors, virus issues,
service
start up issues or conflicts.
Most problems are related with DNS settings, make sure that the machines
are
using the correct INTERNAL DNS servers, make sure that the machines are
not
attempting to connect to a distant DC else were (check ADSS and subnets),
review the GPO settings (rsop.msc, or gpresult /v), make sure that the
scripts are not doing the same thing over and over, also check Antivirus
definitions and policies (updates at startup, initial system check for
virus
at startup, etc), at last you can enable userenv logging to check any
error
or errors that may be logged.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Goku 316" <aramsajan@xxxxxxxxx> wrote in message
news:532FDA9D-2E25-44A6-8BD8-C15AAF4DD1DC@xxxxxxxxxxxxxxxx
We have a native 2000 AD environment with a mixture of Win 2000 and
2003
DCs.
2003 are the majority. DNS is AD integrated and we have dhcp servers
serving
the clients. All clients are XP pro sp2.
We have a Start up script and a login script for users as well as
folder
redirection for My Documents.
We have in house programs that the programmer designed and he setup the
start up script in AD to apply updates to the clients machines which is
essentially just overriding some files. Not everyday is updates applied
but
only when the programmer issues updates.
The login script maps 3 drives and one is done automatically for the
home
drive. Along with that an xcopy command is done to copy the program
updates
that will be launched upon reboot if any.
To me this is not a good method for updating in house software but I
cannot
change this procedure for now or I will face a huge political war.
Our clients’ machines have windows xp sp2 with just office 2003 and
Symantec
av software.
Clients complain of slow logon 45 to 90 seconds to see the wallpaper
and
icons.
No event ID errors, hardware errors, spyware errors, virus issues,
service
start up issues or conflicts.
The AV software has been tweaked to work faster in xp as well as the OS
itself. Many xp tweaks have been tested and imposed on the clients’
machine.
Profiles have been purged and recreated
Defragging has been automated as well using sysinternals tools to
assist
with other performance issues and maintenance.
Adding 1 GB of ram to a client’s machine can help. Right now they only
have
256MB. (I know the minimum should be 512MB but tell that to the higher
ups).
(XP pro with 512MB is ideal for basic workers that have intense AV
software
to work with.)
Did not do the verbose logging feature yet!!!
All servers involved have been looked at and no errors or faults have
been
discovered.
Here is my assumption:
The client powers on the pc and within 1 minute he or she sees the
logon
screen due to xp’s fast logon. Right away he or she logs in due to
cached
profile on the system. At the same time the startup scripts, Symantec
services are launching in the background, amongst other os related
services
while the user’s profile is being loaded into the registry. This can
cause
a
delay in the user not seeing his or her desktop icons and wallpaper
right
away. Plus upon the logon process the login script is patiently waiting
to
execute and this will add more burden to the client’s patience.
I am sure if the client waited for the startup script to execute then
the
logon process will not take that long.
I am curious if anyone has used the GP “always wait for the network at
computer startup and logon”. I am sure this will remove the xp fast
logon
feature and thus the clients will have no way of login in until certain
functions have been completed.
Are there any negative aspects to expect if I use this GP?
Any suggestions besides upping the ram on the client’s pc?
Sorry for the long intro….
--
Goku 316
- Follow-Ups:
- Re: slow logon
- From: Jorge Silva
- Re: slow logon
- References:
- Re: slow logon
- From: Jorge Silva
- Re: slow logon
- Prev by Date: Allocate static IP to domain User
- Next by Date: DC start up sequence
- Previous by thread: Re: slow logon
- Next by thread: Re: slow logon
- Index(es):
Relevant Pages
|
