Offline KScripts not running
I'm new to KACE, I have a great understanding of Managed Installations and have deployed everything from Flash to packaging and pushing Microsoft Office. However I'm a little confused as to why my Offline KScripts aren't running based on my configurations.
I understand that Offline KScript are run based on the client's scheduling or an event (so the system doesn't have to be connected to the K1000 box for the script to run and that Online KScript are pushed based on the server's schedule and thus only machines connected with run the script. My enabled Offline KScript aren't even running when set to rule at a scheduled time on the client machine(s), simple tasks like setting the administrative pass or changing registry values. My scripts work with no problem when they are run using the "Run Now" option. Last, but not least, for whatever reason, I can't get kscripts to work that refer to resources on server shares, shares even kbox samba shares that are enable in the samba share settings, example: \\kbox\clientdrop_x for that specific organization within the K1000 box.
My Main Questions are:
1) Does "Also Run Once at next Client Checkin" mean that it will run at the next Client Checkin and never again, unless there is a schedule set?
2) Does "Also Run at Machine Boot Up" mean EVERY boot up the script should run?
3) Does "Also Run at User Login" mean EVERYTIME a user logs in the script will run?
4) Why can't I access a server share (in an offline script) to i.e. copy an application to the local drive, run it and then delete it? Does this required an Online KScript to do?
I have been checking the manual (it's very vague behavior scheduling offline kscripts) and on the web and these questions are hard to find answers to.
Thanks in advance.
I understand that Offline KScript are run based on the client's scheduling or an event (so the system doesn't have to be connected to the K1000 box for the script to run and that Online KScript are pushed based on the server's schedule and thus only machines connected with run the script. My enabled Offline KScript aren't even running when set to rule at a scheduled time on the client machine(s), simple tasks like setting the administrative pass or changing registry values. My scripts work with no problem when they are run using the "Run Now" option. Last, but not least, for whatever reason, I can't get kscripts to work that refer to resources on server shares, shares even kbox samba shares that are enable in the samba share settings, example: \\kbox\clientdrop_x for that specific organization within the K1000 box.
My Main Questions are:
1) Does "Also Run Once at next Client Checkin" mean that it will run at the next Client Checkin and never again, unless there is a schedule set?
2) Does "Also Run at Machine Boot Up" mean EVERY boot up the script should run?
3) Does "Also Run at User Login" mean EVERYTIME a user logs in the script will run?
4) Why can't I access a server share (in an offline script) to i.e. copy an application to the local drive, run it and then delete it? Does this required an Online KScript to do?
I have been checking the manual (it's very vague behavior scheduling offline kscripts) and on the web and these questions are hard to find answers to.
Thanks in advance.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
cmccracken
13 years ago
Welcome to the KBOX.
I've had varying degrees of success with the scripts, but I believe the reason for #4 is the script is running as the local system; it doesn't have any rights on the server share.
Casey
I've had varying degrees of success with the scripts, but I believe the reason for #4 is the script is running as the local system; it doesn't have any rights on the server share.
Casey
Posted by:
rmeyer
13 years ago
1) good question, I'm not sure, I think it's will run at each check in, but I'm not sure
2) I understand it as every boot up
3) I understand it as every login aswell
4) it is because the agent is running as the user "SYSTEM", it doesn't have any access to a share unless "Everyone" have access to the share, and I doubt that is the case.
You can how ever map the drive with a user's credentials then it will work, but also show up as a drive in KACE ( net use x: \\server\share /user:domain\user Passw0rd ) and then delete it at the end of the script ( net use x: /d )
2) I understand it as every boot up
3) I understand it as every login aswell
4) it is because the agent is running as the user "SYSTEM", it doesn't have any access to a share unless "Everyone" have access to the share, and I doubt that is the case.
You can how ever map the drive with a user's credentials then it will work, but also show up as a drive in KACE ( net use x: \\server\share /user:domain\user Passw0rd ) and then delete it at the end of the script ( net use x: /d )
Posted by:
diverdaveman1
13 years ago
#1 - I've had hit and miss with this - Create some VM's and test then retest!!!
#2 - I've seen this work just as described
#3 - I've seen this work just as described
#4 - Create the Online Script and choose 'Run As User' then supply domain admin user credentials. You may even want to create a 'KACE_Admin' domain admin for just this purpose. We created a 'KACE' only domain admin account that is strictly for KACE scripts. Works perfect every time!!!
Once again VM's will become your best friend when attempting new scripts and/or MI's.
Dave
#2 - I've seen this work just as described
#3 - I've seen this work just as described
#4 - Create the Online Script and choose 'Run As User' then supply domain admin user credentials. You may even want to create a 'KACE_Admin' domain admin for just this purpose. We created a 'KACE' only domain admin account that is strictly for KACE scripts. Works perfect every time!!!
Once again VM's will become your best friend when attempting new scripts and/or MI's.
Dave
Posted by:
ncsutmf
13 years ago
#4 also, \\kbox\clientdrop_x requires authentication using the share admin password and gives read-write access. If you want to use the shares on the kbox, try \\kbox\client_x instead for access within the script, and use the clientdrop_x share for when you upload the files that will be used by the script.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.