Slow log in on XP workstations

[markesmith]

Hello All

Many thanks for all your help and support on this one. We start at the school on Monday so I'll let you know how we get on. Cheers.

[Guest]

For remote install you could use psexec

 

http://www.sysinternals.com/Utilities/PsExec.html

 

Just tried it and seems to work fine

[Geoff]

The license has changed on the sysinternals free tools preventing them from being used in a school enviroment (amongst others).

[spc-rocket]

HI all,

 

We designed a vbscript to deploy the patch via the startup script. The problem we are having is that the script runs when you double-click on it but doesn't work when used as a startup script. Any ideas as to why this may be, i have give the domain computers read and execute access to the hotfix files etc.

 

I'll post the script here on Monday when i'm back at work again.

 

The script first checks to see if the hotfix is installed and if it isn't then it installed it otherwise it just skips it.

 

Ashok.

[spc-rocket]

Hi all,

 

Here's the script that will install the patch:

 

 

 

'sExePath = "\\admin_server\packages$\XPHotfixes\kb899409.exe" 

'sSwitches = "/quiet /norestart" 

Set oShell = CreateObject("WScript.Shell") 

sRegKey = "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" 

' suppress error in case values does not exist 

On Error Resume Next 

' check for marker 

sRegMarkerValue = "" ' init value 

sRegMarkerValue = oShell.RegRead( sRegKey & "\Hotfix899409Installed") 

On Error Goto 0 

' to be sure update is installed only once, test on marker 

If sRegMarkerValue <> "yes" Then 

oShell.Run("\\admin_server\packages$\XPhotfixes\KB899409.exe /quiet /norestart"), 1, True 

' create marker 

oShell.RegWrite sRegKey & "\Hotfix899409Installed", "yes" 

End If

Set oShell = Nothing

 

You need to replace the patch referenced in this code:

 

oShell.Run("\\admin_server\packages$\XPhotfixes\KB899409.exe /quiet /norestart"), 1, True

 

to the path where you patch is located - UNC path will do.

 

The /quiet and /norestart will cause the patch to install silently and will not restart the computer.

 

HTH,

 

Ashok.

 

Credit goes to someone, don't know where i found this script, somewhere from the net.

[tarquel]

Nice

 

Stick it in the Domain Computers policy - Start Up script - will that do?

 

vb script i assume?

 

Can you edit your post and put the code in code tags for readability for others if ya would pls?

 

Thx

Nath.

[CM786]

Just a quickie if I may?

 

Do we need this if the server is running Server2003 R2?

 

I'm experiencing slow logins too- around 3 -4 mins on a XPSP2/Server2003R2 network via a 100Mbps connection.

 

All group policies/software installation is working great - the logins is are just so slow.

 

I might have a DNS issues, but I'm not sure what I should look for?

I had a look at Event viewier both on the server and the client PC I logged into and couldn't see any red circles with crosses on. :oops:

 

The login itself is actually quick, its when the PC gets to the "applying personal settings" bit that it takes ages. This is a new network, so their are very few saved profiles on the local client.

 

I am applying a few user group policies at login:

 

Folder Redirection,

Student LockDown,

Proxy Settings,

Startup Scripts

 

and just an Install Office Computer Policy.

 

Any help appreciated.

[Guest]

The patch fixes slow logins at the "applying personal settings" part of logon casued by Folder Redirection.

 

Just stick the patch on the server that holds the redirected folders and on a single work station and see if it cures your problem.

[CM786]

Thanks SYSMAN

 

I just thought that it would have been integrated in Server2003 R2 anyway.

[DMcCoy]

Why on the server? Surely that is only if you are logging in to the server console itself with redirected folders? The Slow down was instroduced with XP SP2, well before 2003 SP1 came out.

[woody]

Can I just ask? Has any one applied the patch on a client but not on a server? We started applying the patch to xp sp2 worksations last night but I didn't apply it on the server because I didn't want it to restart at that point and chuck everyone out.

 

However this morning, we have come across a problem where if a user doesn't have a profile already in documents and settings, they log on without group polices applying. I'm just wondering if the server needs the patch to apply as well?

[sidewinder]

I didnt put it on any servers, didnt see the point, and Ive had no problems

 

I cant see why you would need it on the server

[woody]

It's ok, I've just found out the problem we have had isn't related to this Patch. I can see what you mean about not needing it on the server. The server patch is if it is slow logging onto the server itself.

[sidewinder]

just out of interest, what was causing it? im just nosey

[woody]

Well, it was actually AB tutor, our classroom control software. I've spoken about it on other posts - it allows teachers to set policy restrictions in place for internet access. Well, the teacher had 3 seperate policies in place before the class logged on. For some reason, these policies were blocking the applying of group policy at logon. I havene't figured out which of the three was doing it or perhpas it was the combination. But I'm also going to contact the authors of the software to ask their take on matters.