TechSupp Posted October 8, 2008 Posted October 8, 2008 Just had a mare of an afternoon with the system on meltdown as PC' were down to a crawl, accessing the network server etc. Just had a look and found the server was running at 100% and checking the processes found it was wscript at 98%. Killed this process and system seems to have settled somewhat. Any ideas what is causing wscript.exe and can I leave it stopped?
strawberry Posted October 8, 2008 Posted October 8, 2008 wscript is usually called from the command line. could be anything,
Geoff Posted October 8, 2008 Posted October 8, 2008 wscript is responsible for executing VBS scripts.
Mcshammer_dj Posted October 8, 2008 Posted October 8, 2008 snd like you have a script that is not completing or is hanging. I would look at the event logs and check any scipts that you have running on the server
TechSupp Posted October 8, 2008 Author Posted October 8, 2008 Ah well...wscripts does not seem to be the culprit after all although it was at 100%. The network access is still slow (checked the event logs and can't see anything untoward). Any ideas what to check next?
meastaugh1 Posted October 8, 2008 Posted October 8, 2008 Could it be a loop/broadcast storm on the network?
TechSupp Posted October 8, 2008 Author Posted October 8, 2008 I presume a loop storm is just a looped cable connection? Don't think so as I am using the server to type this and the internet comes up fine, but when trying it from a client PC linked to the same switch as the server its very slow to get a web page. Tried other switches that are linked to the server switch and they are the same as well. Can't understand why the server is OK and other PC's have slow acces to the server itself and the internet?
meastaugh1 Posted October 8, 2008 Posted October 8, 2008 That's right. Just a relatively simple thing to rule out. Wasn't sure whether the wscript running at 100% was the cause or a symptom.
TechSupp Posted October 9, 2008 Author Posted October 9, 2008 Right, heres the update...wscript.exe is the culprit. After exahustive testing the network is OK but here where I can see the problem. wscript.exe seems to be run at logon and hogs the processing so everthing slows down. Kill that process and all is OK. Client PC's when logging on the domain seem to start wscript.exe, when I kill it at the PC browsing the internet and server folders etc is OK. Log back off and back on without killing it and all slows down to a standstill. I have amessage that pops up in a dos box telling me that cmd.exe was started in the scripts directory but UNC paths are not supported. Took all scripts off logon and logoff but still appears. Checked in the directory specified and can't see any file's. Any suggestions. Can I block wscript run ning from the server as it seems to be triggered when the gpo is loaded as a laptop that logs on as a workgroup only connects and browses fine. Any suggestions welcome
Geoff Posted October 9, 2008 Posted October 9, 2008 You have a login script thats broken. Check what login scripts are running using the GPMC reporting/modelling. Run the scripts manually and see if there are any errors. Failing that remove them one by one until the problem goes away.
matt40k Posted October 9, 2008 Posted October 9, 2008 Normally login scripts are kept in \\domain\netlogon I think there is another way too. Run a GP report for the affected user.
TechSupp Posted October 9, 2008 Author Posted October 9, 2008 You have a login script thats broken. Check what login scripts are running using the GPMC reporting/modelling. QUOTE] How do I do the GPMC repoprting/modelling? Manually removed all scripts to run at logon as far as I can see.
matt40k Posted October 9, 2008 Posted October 9, 2008 Over 4months since i touch AD. If I remember, you need v.2 (another thing to install over the admin tools, look on ms download) then for each ou click on the gp policy and theres a option to report (to html) look for something that ends in .vbs You can do it for a user over all... I think there is a tool too, to check your current users policy, see whats overriding what etc... can't remember the command, would be best to run this.... oh what's it call!! i hate not admin a domain! I'm already forgetting stuff!
TechSupp Posted October 9, 2008 Author Posted October 9, 2008 I'm at home now so can't look in to the reporting etc but would running GPRESULT on the client or on the server specifying the pc/user give me a result that says what scripts are trying to be run as I think that is what the problem is. The wscript.exe is a slight red herring I think. Two dos cmd boxes appear at logon telling me thay can't run with network UNC paths so I think the clients are trying to run two scripts from somewhere in their GP hence why I'm asking about gpresult but I can;t seem to find out which or where they are. Should I delete any local profiles first and try a gpupdate on the clients first to see if that makes any difference.
SYNACK Posted October 10, 2008 Posted October 10, 2008 @TechSupp - You should be able to use gpresult or the RSoP mmc snap-in to get this information off a client machine.
SteveLaw Posted October 10, 2008 Posted October 10, 2008 If you install the Group Policy Management Console it has the reporting built into it (down the bottom somewhere). you run the wizard choose a PC and a user and it will tell you every policy that is applied to each and what the settings are.
TechSupp Posted October 10, 2008 Author Posted October 10, 2008 Thanks I'll try that when I get in today.
matt40k Posted October 10, 2008 Posted October 10, 2008 (edited) GPRESULT wasn't what I was thinking.... really bugging me now! Brainwave Rsop.msc!! Edited October 10, 2008 by matt40k Brainwave
TechSupp Posted October 10, 2008 Author Posted October 10, 2008 Went in this moring and used the GPMC add inn and what a fantastic tool! Found the rouge scripts I was looking for no problem. Thanks to all who offered help. Disabled all the scripts it highlighted, logged on and hey presto strainght on the internet and browsing network resources fine..and no wscript.exe holding it all up. So in the end it seems like I had a couple of bad scripts for some reason (not changed them so will check whats happened) and thats what was causing wscript not to finish and clog each client pc up. So wscript wasn't the problem just and effect. Thanks to all, saved by the forum once again!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now