I did a similar test, configured everything to run from a local directory,
ran it while logged in as admin, launched the script from the command prompt
(Run as administrator), below is the command line I used, and the
ConfigMgrStartup.xml. I love that it does the Auto Hotfixes, big thanks to
Jason Sandys!
WScript.exe C:\CM2012\ConfigMgrStartup.vbs
/config:C:\CM2012\ConfigMgrStartup.xml
<?xml version="1.0"?>
<Startup>
<Option Name="CacheSize">8120</Option>
<Option Name="AgentVersion">5.00.7804.1400</Option>
<Option Name="ClientLocation">C:\CM2012</Option>
<Option Name="MaxLogFile">2048</Option>
<Option Name="ErrorLocation">C:\CM2012\Logs</Option>
<Option Name="AutoHotfix">C:\CM2012\Hotfix</Option>
<Option Name="Delay" >5</Option>
<InstallProperty Name="SMSMP">CM01.SMS.LOC</InstallProperty>
<InstallProperty Name="SMSSITECODE">PS1</InstallProperty>
<InstallProperty Name="FSP">CM01.SMS.LOC</InstallProperty>
<ServiceCheck Name="BITS" State="Running" StartMode="Auto"
Enforce="True" />
<ServiceCheck Name="winmgmt" State="Running"
StartMode="Auto" Enforce="True" />
<ServiceCheck Name="wuauserv" State="Running"
StartMode="Auto" Enforce="True" />
<ServiceCheck Name="lanmanserver" State="Running"
StartMode="Auto" Enforce="True" />
<ServiceCheck Name="RpcSs" State="Running" StartMode="Auto"
Enforce="True" />
</Startup>
From: [email protected] [mailto:[email protected]]
On Behalf Of Atkinson, Matt T
Sent: Thursday, June 11, 2015 10:24 AM
To: [email protected]
Subject: RE: [mssms] Error with SCCM Client Startup script
Latest and greatest, 1.6.8
I plan to run it as GPO, but I want to make sure it is working first so that
is why I'm testing with psexec as the local system account.
From: [email protected] [mailto:[email protected]]
On Behalf Of Jason Sandys
Sent: Wednesday, June 10, 2015 5:58 PM
To: [email protected]
Subject: RE: [mssms] Error with SCCM Client Startup script
Also, what version of the script are you running?
J
From: [email protected] [mailto:[email protected]]
On Behalf Of Art Flores
Sent: Wednesday, June 10, 2015 6:22 PM
To: [email protected]
Subject: RE: [mssms] Error with SCCM Client Startup script
Howdy Matt, I am using it and it works great. Are you running it as a GPO
in a startup script? Did you assign read rights to the Domain Computers
group on the client share? If memory serves, I had to assign read
permissions on both tabs, Sharing and Security/NTFS. When using the GPO
startup script, the script will run under the context of the local
computer's system account.
From: <mailto:[email protected]>
[email protected] [ <mailto:[email protected]>
mailto:[email protected]] On Behalf Of Atkinson, Matt T
Sent: Wednesday, June 10, 2015 10:43 AM
To: <mailto:[email protected]> [email protected]
Subject: [mssms] Error with SCCM Client Startup script
Hi All,
I've started testing Jason Sandy's client startup script, but it gives me an
error message and terminates prematurely:
*Could not retrieve agent cache size with error: Invalid procedure call or
argument (5)
I'm using psexec to run it as my local system as a test. I've configured the
xml file to set the cache size to 10gb: <Option
Name="CacheSize">10240</Option>.
Anyone out there using this that can point me in the right direction? Sadly,
my VBScript skills are non-existent, I started scripting with Powershell and
haven't run in to anything that I couldn't do with PS.
Thanks!!
Matt
_____
This message is intended for the sole use of the addressee, and may contain
information that is privileged, confidential and exempt from disclosure
under applicable law. If you are not the addressee you are hereby notified
that you may not use, copy, disclose, or distribute to anyone the message or
any information contained in the message. If you have received this message
in error, please immediately advise the sender by reply email and delete
this message.
_____
This message is intended for the sole use of the addressee, and may contain
information that is privileged, confidential and exempt from disclosure
under applicable law. If you are not the addressee you are hereby notified
that you may not use, copy, disclose, or distribute to anyone the message or
any information contained in the message. If you have received this message
in error, please immediately advise the sender by reply email and delete
this message.
