when I run my script it does nothing
I have a SCCM 2007 client health check script that I downloaded from MyITForum (written by Jerry Sandys) It comes with an .xml file that, from what I've read, is the only thing you need to modify. So I updated this .xml file with the required information. I also added a few print statements to the vbs script. I run the script like this: C:\Temp> CScript c:\temp\ConfigMgrStartup.vbs c:\temp\ConfigMgrStartup.xml it prints this to the screen. Microsoft (R) Windows Script Host Version 5.7 Copyright (C) Microsoft Corporation. All rights reserved. Hello Line 122 after all the declaration The very end of the script But it does Not do anything. It does not install the SCCM client and it does not write anything to the log file that is specified in the .XML file. It does dump out a log file that has this inside of it. <![LOG[---------- Beginning Execution]LOG]!><time="7:33:2.000+0" date="2-7-2012" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs"> <![LOG[Configuration file not specified on command-line with config switch]LOG]!><time="7:33:2.000+0" date="2-7-2012" component="ConfigMgrStartup.vbs" context="" type="3" thread="" file="ConfigMgrStartup.vbs"> <![LOG[Finished Execution ----------]LOG]!><time="7:33:2.000+0" date="2-7-2012" component="ConfigMgrStartup.vbs" context="" type="1" thread="" file="ConfigMgrStartup.vbs"> So what am I doing wrong? How do I run this and make it actually work? We need a SCCM client health check to run via login scripts. Thanks.
February 7th, 2012 10:54am

Hi, You should ask the author of the script. Unfortunately we didn't write it and this isn't an SCCM support forum. Bill
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2012 10:55am

I guess another way I could ask it..... is the way I ran the script correct? why do I see that error in the log file that says config file not specified? What causes that log file error? Thanks.
February 7th, 2012 11:08am

I guess another way I could ask it..... is the way I ran the script correct? why do I see that error in the log file that says config file not specified? What causes that log file error? Thanks.
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2012 11:08am

Hi, Your command line will indeed start the script using the CScript host, and you are also passing a command-line argument (an XML file name) to the script. What the script actually does when you run the above command is up to the script. You need to ask the author about that. (Please note that it's impossible for us to guess what is happening, because we don't have the script you're running, and we also can't see your screen.) Bill
February 7th, 2012 11:23am

Hi, Your command line will indeed start the script using the CScript host, and you are also passing a command-line argument (an XML file name) to the script. What the script actually does when you run the above command is up to the script. You need to ask the author about that. (Please note that it's impossible for us to guess what is happening, because we don't have the script you're running, and we also can't see your screen.) Bill
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2012 11:23am

It's Jason Sandys not Jerry. The script won't run from SCCM since it is used to fix broken SCCM clients. The script is to be ran from a GPO. Havign said that, this is not an SCCM issue and should not be in this forum. Of course Jason answers a ton of questions here so he will likely reply. If not you should be able to contact him through his blog. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
February 7th, 2012 12:12pm

The script uses named parameters; to specify one you include the name of parameter on the command-line. Thus, the proper command-line is: CScript c:\temp\ConfigMgrStartup.vbs /config:c:\temp\ConfigMgrStartup.xml (the very last line of the included doc mentions this)Jason | http://myitforum.com/myitforumwp/community/members/jasonsandys/ | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2012 12:18pm

Jason, thank you. I did discover I was running it wrong. I've noticed that on a machine that has no SCCM client it installs the client fine. But on a Windows XP x86 machine I deleted many SCCM files from the \CCM folder. I then ran your script and it never seem to repair anything nor did it write a log to the path I specified in the .xml file. My .XML line looks like this: <Option Name="ErrorLocation">\\US-SCCM-PRI01\logfiles$\clientcheck</Option> I made sure that Domain Computers have "write" access to this location. And one last thing.....if the WMI is corrupted will your script fix it or only report that it's broken? Thank you.
February 7th, 2012 5:42pm

Jason, thank you. I did discover I was running it wrong. I've noticed that on a machine that has no SCCM client it installs the client fine. But on a Windows XP x86 machine I deleted many SCCM files from the \CCM folder. I then ran your script and it never seem to repair anything nor did it write a log to the path I specified in the .xml file. My .XML line looks like this: <Option Name="ErrorLocation">\\US-SCCM-PRI01\logfiles$\clientcheck</Option> I made sure that Domain Computers have "write" access to this location. And one last thing.....if the WMI is corrupted will your script fix it or only report that it's broken? Thank you.
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2012 5:42pm

hello, so unless I misunderstand what this script does it does not repair any broken sccm clients. it only seems to install the sccm client on a machine that does not have it. is that all it does or should it fix broken clients as well?
February 14th, 2012 10:45am

hello, so unless I misunderstand what this script does it does not repair any broken sccm clients. it only seems to install the sccm client on a machine that does not have it. is that all it does or should it fix broken clients as well?
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2012 10:45am

I am still having issues with this. as I said on a machine with no SCCM client it will install it. But if you have SCCM and you delete many of the core files in %sys32%\ccm and run it nothing happens. It does not repair anything. Should it? I thought this was a fix script? it also does not write anything to the server for logging. Any help would be great.
February 21st, 2012 12:33pm

I am still having issues with this. as I said on a machine with no SCCM client it will install it. But if you have SCCM and you delete many of the core files in %sys32%\ccm and run it nothing happens. It does not repair anything. Should it? I thought this was a fix script? it also does not write anything to the server for logging. Any help would be great.
Free Windows Admin Tool Kit Click here and download it now
February 21st, 2012 12:33pm

still no progress on this script.... it only seems to install on machines that never had SCCM. Should it repair broken client installs as well?
February 29th, 2012 11:24am

still no progress on this script.... it only seems to install on machines that never had SCCM. Should it repair broken client installs as well?
Free Windows Admin Tool Kit Click here and download it now
February 29th, 2012 11:24am

So, simply deleting a handful of files from the ccm directory doesn't necessarily compromise the client. The script checks for a handful of baseline requirements (as detailed in the accomanying documentation) and if any of these fails, then it is either corrected or the script kicks off a reinstall of the client if you've specified the proper location for ccmsetup. The intention of the script is not to be an all encompassing health script as there are other tools out there for that; however, the script does detect and remedy most common issues (randomly deleted files from ccm is not a common issue) some of which do require a reinstall of the client. The main intention of the script is to "pull" the client agent to systems and ensure it is running on as many system as possible. Thus, please review the documentation as it should answer your questions.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
April 29th, 2012 1:24pm

So, simply deleting a handful of files from the ccm directory doesn't necessarily compromise the client. The script checks for a handful of baseline requirements (as detailed in the accomanying documentation) and if any of these fails, then it is either corrected or the script kicks off a reinstall of the client if you've specified the proper location for ccmsetup. The intention of the script is not to be an all encompassing health script as there are other tools out there for that; however, the script does detect and remedy most common issues (randomly deleted files from ccm is not a common issue) some of which do require a reinstall of the client. The main intention of the script is to "pull" the client agent to systems and ensure it is running on as many system as possible. Thus, please review the documentation as it should answer your questions.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2012 1:24pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics