5.3 agent force inventory from client side
We've recently been instructed to upgrade to 5.3 by support because of a couple of issues we have been having with our K1000. We've noticed that kbscriptrunner.exe is no longer part of the new agent. We're looking for the equivalent that can be run from the workstation that will force an inventory update, and run any managed installs that are in the to install list.
0 Comments
[ + ] Show comments
Answers (17)
Please log in to answer
Posted by:
cblake
13 years ago
runkbot.exe -s runs as LocalSystem. Running runkbot.exe without a -s will run as the logged in user.
Posted by:
GillySpy
13 years ago
runkbot (for those familiar with it) is still there but the script numbers have changed for 5.3. You can call a script like this:
The script for inventory in 5.3 is #4 and for MIs is #6. For version just use 0.
e.g.
runkbot <script#> <version>The script for inventory in 5.3 is #4 and for MIs is #6. For version just use 0.
e.g.
runkbot 4 0
Posted by:
dyee
11 years ago
is there way to invoke runkbot -s 4 0 silently so that it is completely transparant to the user (no second window pops up with the output). like the way inventory is done when you press the Force Inventory from the K1000.
Thanks in advance,
Posted by:
ncsutmf
13 years ago
ORIGINAL: GillySpy
runkbot (for those familiar with it) is still there but the script numbers have changed for 5.3. You can call a script like this:
runkbot <script#> <version>
The script for inventory in 5.3 is #4 and for MIs is #6. For version just use 0.
e.g.
runkbot 4 0
Ok, thanks. So, if I wanted to run inventory first and then run MIs I would call it twice, or does calling inventory also trigger the MIs?
runkbot 4 0
runkbot 6 0
Posted by:
ncsutmf
13 years ago
Ok. I answered my question by testing it. Running the inventory alone does not kick off the managed installs. However, I ran into another problem. Previously we could run KBScriptRunner as any user and the managed installs would run. Now, when I try to run "runkbot 6 0" I get an error that "the requested operation requires elevation" which tells me a user would need to be running as an admin in order for the managed install to run. While this works for anything we can make run with the system account which meets my short term needs, it does not work for an end user initiated update.
Posted by:
ncsutmf
13 years ago
Get the following results when I try that:
C:\Program Files\Dell\KACE>runkbot.exe -s 4 0
KLaunch Could not upload file "C:\Program Files\Dell\KACE\KLaunchSvc.exe" to
"\\127.0.0.1\ADMIN$\System32\KLaunchSvc.exe"
KLaunch Couldn't upload service to '\\127.0.0.1\ADMIN$': Insufficient Access
- Run as administrator?
C:\Program Files\Dell\KACE>runkbot.exe -s 6 0
KLaunch Could not upload file "C:\Program Files\Dell\KACE\KLaunchSvc.exe" to
"\\127.0.0.1\ADMIN$\System32\KLaunchSvc.exe"
KLaunch Couldn't upload service to '\\127.0.0.1\ADMIN$': Insufficient Access
- Run as administrator?
C:\Program Files\Dell\KACE>runkbot.exe -s 4 0
KLaunch Could not upload file "C:\Program Files\Dell\KACE\KLaunchSvc.exe" to
"\\127.0.0.1\ADMIN$\System32\KLaunchSvc.exe"
KLaunch Couldn't upload service to '\\127.0.0.1\ADMIN$': Insufficient Access
- Run as administrator?
C:\Program Files\Dell\KACE>runkbot.exe -s 6 0
KLaunch Could not upload file "C:\Program Files\Dell\KACE\KLaunchSvc.exe" to
"\\127.0.0.1\ADMIN$\System32\KLaunchSvc.exe"
KLaunch Couldn't upload service to '\\127.0.0.1\ADMIN$': Insufficient Access
- Run as administrator?
Posted by:
ncsutmf
13 years ago
I have an admin account, yes, but the point is for an end user to be able to run this like they were able to with KBScriptRunner, not for an admin.
Posted by:
cblake
13 years ago
Not sure I follow what you are trying to accomplish I suppose. If you elaborate the group may have other ideas. Why would an end user need to run an inventory for example?
Assuming you're trying to get something to happen at checkin like an MI or Script: Why not use the user portal UI to deliver software or scripts?
Assuming you're trying to get something to happen at checkin like an MI or Script: Why not use the user portal UI to deliver software or scripts?
Posted by:
RichB
13 years ago
Chris,
I can see the benefit of having a non-admin user account to test software installations. I have a shortcut to kbscriptrunner on the Start menu of all my admin and non-admin accounts in XP and 7 for testing purposes. It doesn't ask for permission and initiates scripts and inventory, installs software as admin, like testing the dialogs a user will see for example. I suppose I could use the "Force Update" button through the web interface or push my "Force Checkin" script to the computer(s) but when right there at the computer or remotely connected to it, it makes things happen quicker when initiated there and it's easy to run. Then I can uninstall, tweak, check-in (kbscriptrunner) to get a smart label for installation again, and then run (kbscriptrunner) from the client for another test of the installation.
I'll miss kbscriptrunner in 5.3.
I can see the benefit of having a non-admin user account to test software installations. I have a shortcut to kbscriptrunner on the Start menu of all my admin and non-admin accounts in XP and 7 for testing purposes. It doesn't ask for permission and initiates scripts and inventory, installs software as admin, like testing the dialogs a user will see for example. I suppose I could use the "Force Update" button through the web interface or push my "Force Checkin" script to the computer(s) but when right there at the computer or remotely connected to it, it makes things happen quicker when initiated there and it's easy to run. Then I can uninstall, tweak, check-in (kbscriptrunner) to get a smart label for installation again, and then run (kbscriptrunner) from the client for another test of the installation.
I'll miss kbscriptrunner in 5.3.
Posted by:
JonHall
13 years ago
ORIGINAL: GillySpy
runkbot (for those familiar with it) is still there but the script numbers have changed for 5.3. You can call a script like this:
runkbot <script#> <version>
The script for inventory in 5.3 is #4 and for MIs is #6. For version just use 0.
e.g.
runkbot 4 0
My agents are currently running v. 5.1.31821, and I have both runkbot and kbscriptrunner. Is there a command I can run to force an inventory and MI? We have the system configured to check in every 4 hours, but I'd like to force it via script.
Posted by:
cblake
13 years ago
@JonHall - kbscriptrunner does this in 5.1
@RichB - I will too, but waves of the future I suppose... Eventually any kinks will work out I think, like you and I have seen over the years.
@ncsutmf
@RichB - I will too, but waves of the future I suppose... Eventually any kinks will work out I think, like you and I have seen over the years.
@
Posted by:
RichB
13 years ago
This page needs to be updated for 5.3:
How to force a client check-in outside the normal run interval
How to force a client check-in outside the normal run interval
Posted by:
dogfish182
13 years ago
This needs a bump, has anyone achieved this?
when we deploy the machines from the k2000 we want to have it scripted install, then check in and run the managed installs right away. Not wait 2 hours :/
this doesnt work. If you make a batch file with
runkbot 4 0
runkbot 6 0
it launches the runkbot 4 0 in another window and carries right on into runkbot 6 0. The effect being that runkbot 6 0 runs before the inventory has finished. therefore it sees nothing waiting to install and installs nothing.
How do I get my 5.3 freshly deployed agents to just do their job?! So frustrated with this 'upgrade'.
when we deploy the machines from the k2000 we want to have it scripted install, then check in and run the managed installs right away. Not wait 2 hours :/
this doesnt work. If you make a batch file with
runkbot 4 0
runkbot 6 0
it launches the runkbot 4 0 in another window and carries right on into runkbot 6 0. The effect being that runkbot 6 0 runs before the inventory has finished. therefore it sees nothing waiting to install and installs nothing.
How do I get my 5.3 freshly deployed agents to just do their job?! So frustrated with this 'upgrade'.
Posted by:
sconstable
13 years ago
Hmmm...
I am trying to EXACTLY the same thing as Dogfish.
I find it redundant to have to manage the install packages in 2 places.
I made a batch file and ran it and had no problems - Im not really sure what might be different-
All of our deployments are 64 bit windows 7 enterprise the batch file is just simply this:
"c:\program files (x86)\dell\kace\runkbot" 4 0
"c:\program files (x86)\dell\kace\runkbot" 6 0
I ran it as a NON admin from a NON elevated cmd prompt and it worked as expected.
I do plan to add this to a runonce registry entry and see if will trigger it when the computer reboots for the first time - Ill let you know what happends.
I am trying to EXACTLY the same thing as Dogfish.
I find it redundant to have to manage the install packages in 2 places.
I made a batch file and ran it and had no problems - Im not really sure what might be different-
All of our deployments are 64 bit windows 7 enterprise the batch file is just simply this:
"c:\program files (x86)\dell\kace\runkbot" 4 0
"c:\program files (x86)\dell\kace\runkbot" 6 0
I ran it as a NON admin from a NON elevated cmd prompt and it worked as expected.
I do plan to add this to a runonce registry entry and see if will trigger it when the computer reboots for the first time - Ill let you know what happends.
Comments:
-
I know this is an old question but it is still relevant in version 6.x.
We address the imaging delay by creating a single script on the K1000 that calls every managed install we require one after another. When we have a new MI we want in our environment we simply create the MI (that takes care of machines currently running) and then add an entry to the end of our single script that calls all MI's back to back. On our k2000 we have a single post install task runkbot 192 1 (where 192 is the script ID for the single script that calls all managed installs). Now when a machine is imaged all the jobs kick off right away!
We also set a registry flag at the end of the script so we can apply a smart label to all machines that have completed their "rush install". Our normal managed installs always exclude machines in that label so we never have collisions. - cnilsson 9 years ago
Posted by:
scottlutz
13 years ago
If you want your commands to run one after the other, just enter them this way in your batch script:
"c:\program files (x86)\dell\kace\runkbot" 4 0 && "c:\program files (x86)\dell\kace\runkbot" 6 0
That way, the 6 0 will run once the 4 0 completes.
"c:\program files (x86)\dell\kace\runkbot" 4 0 && "c:\program files (x86)\dell\kace\runkbot" 6 0
That way, the 6 0 will run once the 4 0 completes.
Posted by:
sconstable
13 years ago
An update to this -
In my testing I have realized that a non-admin and non-elevated commpand prompt cannot run the
"c:\program files (x86)\dell\kace\runkbot" 6 0
if there is actually package to deploy as it runs as the security context of the user who it logged in to actually run the installer(s).
I am trying to put this [batch file] into the k2000 as a post-install task - I have not fully tested yet but I will be soon.
In my testing I have realized that a non-admin and non-elevated commpand prompt cannot run the
"c:\program files (x86)\dell\kace\runkbot" 6 0
if there is actually package to deploy as it runs as the security context of the user who it logged in to actually run the installer(s).
I am trying to put this [batch file] into the k2000 as a post-install task - I have not fully tested yet but I will be soon.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.