I know that Jason's ConfigMgr Startup script is meant to be run via GPO. Wondering if anyone has had any experience running it via an SCCM Web Console, which we'd like to do. Not sure if it's configurable to do that or not. I'm guessing I'd need to copy it down to the target PC, along with its related XML file, and then trigger via PSExec. Just curious if anyone else had a better solution. Thanks.

Nope, can't say that I have done that. But if you do not want to run it as a startup script, you should consider creating a Windows scheduled task. That way you can trigger the task from the console using a custom right click tool.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

My problem with a scheduled task is... Will it run if WMI is busted? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

I am currently trying to setup the script to use through Group Policy. However, when I boot the system and log in and launch rsop.msc I can see that the script ran. BUT there is no log file in C:\Windows\CCM\Logs (it has a client installed) I also checked C:\Windows\Temp and still not showing the log file. Did I miss something? I edited the XML and set the Error log location and the client install location but I am not seeing the log file. Any thoughts as to what I could have missed? I am really excited to see what this script will do in keeping a healthly active clients in SCCM. :)

Have you checked the Windos Event log to ensure that the script actually ran? Have you looked in the registry to see if the registry key was created (as this is the very first thing the script does)?Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Hi Jason, Do you have any proposed answers off-hand for the "Could not retrieve agent cache size with error code: 70" error"? I have the script and XML config in a GPO as a machine startup script. Each time the machine boots this error is generated in the log file. If I would run the script manually this particular error does not generate but in Event Viewer there is an entry that the Client Check Failed. Are there any timing issues that could be causing this? What is stumping me is that when the script is ran manually the log file generated shows absolutely no errors in it so I am confused as to what is causing the Event Viewer entry that the Client Check has failed? The script seems to do everything as expected wonderfully, i.e. checks Agent version and upgrades successfully, but having a fail log generated for every machine will throw a wrench into the plans on implementing this. Any comments/suggestions will be greatly appreciated!