Blog Posts tagged with KACE 5.4

Ask a question

K1000: Simple Scripted File Copy

Though there are many ways to do this including a file sync I see a lot of users wanting to use a bat file to do this and running into issues. Probably because of the familiarity with DOS commands and not scripting syntax, especially KScripting.

The simple script below will let you create a DOS syntax script tfor use with kace to copy a file. 

Create a Online Shell Script

Attach a dependency and give the commands like below in the script text

A couple of notes here. 

Because the kscript runs as local system you wont run into any permoissions caused by launching your own batch file.

We have simply attached the file to copy as a dependency (in this case AgentErr.png)

Using xcopy withthe path to the script (you can find this by attaching your dependency and saving the script) Find you script in the list you are returned to and hover over it. The link to the script shows the ID, it should aslo be visible inthe address bar like. 


The part after ID= will be the number you use in your script.

lastly /y says yes to make sure there is no user interaction required and the /D tells XCOPY that our destination is a directory.

View comments (1)

K1000: Updating Agent Software

PROBLEM: Kace fails provisioning your client with the newest Agent budle

REASON: You cannot provision an already provisioned client. 

RESOLUTION: You must use the upgrade feature of the KACE Agent. 


First we need to make sure you have the latest agent version loaded on your appliance.

Go to K1000 Settings --> Server Maintenance --> Currently Downloaded Agent Bundle Version:
Check for the current version number.

If it doesnt then download and load the newest agent bundle at https://www.kace.com/support/Customer/downloads

Once this is verified then proceed to check the settings below:

Settings --> K1000 Agent --> Agent Updates from KACE

Make sure the boxes for
Update Broken Agents:
are both checked and then you will need to either check Deploy to all machines or deploy to certain labels.

This will automatically upgrade the agents as they check in.

View comments (5)

K1000: All Queue Default Owners

The below SQL report will return all the default queue owners of all your helpdesk desk categories along with the settings.


And the results look like the below

Be the first to comment

K1000: Mac: Deploy Silverlight through a managed install

Please note: This install of Silverlight was tested on OS X 10.8.1 with agent version 5.4.5315 and server version 5.4.70402. It should work with any supported version of OS X and the K1000.

Problem: Silverlight needs to be installed. 

Solution: Deploy Silverlight to Macs through a managed install. The version used in this blog is 5.1.10411.


Steps to create a managed install for Silverlight:

1. Install Silverlight on a test system that has the KACE agent installed and force an inventory update.

This can be done from the computer's inventory page, or it can be done through terminal on the system:  sudo /Library/Application Support/Dell/KACE/bin/runkbot 2 0

2. Once the system checks in, there will be an entry in Software Inventory for SLLauncher, but not one for Silverlight.  This could be used, but it may not be unique for other versions of Silverlight. This means a custom Software Inventory item for Silverlight will need to be created and a custom inventory rule will need to be applied.

a. Click on Inventory>Software>Choose Action>Add New Item.  

b. Title and describe the entry as needed for Silverlight.

c. Add the operating system(s) that Silverlight will be deployed to.

d. Add the custom inventory rule (see screenshot below for location): 

PlistValueEquals(/Library/Internet Plug-Ins/Silverlight.plugin/Contents/Info.plist,CFBundleVersion,TEXT,5.1.10411.0) 

e. Upload the Silverlight.dmg file obtained from Microsoft to the software inventory item.

f. Add licenses and Metadata as needed.

g. Save the software inventory item.

Please note:  All the available options for custom inventory rules can be found by clicking on the gold question mark box next to Custom Inventory Rule.


3. To create the managed install, go to Distribution>Choose Action>Add New Item.

a. Select Silverlight from the software drop down. The name may vary based on what the software inventory item was named.

b. Do not change the default installation commands as Silverlight will install with no changes.  This is the case for some if not most .dmg files as the K1000 will mount and extract the installer automatically.

c. Changed Managed Action to one of the Execute options.

d. Add individual machines or labels to target machines that need Silverlight installed.

e. Change Deploy Order, Max Attempts, Snooze, Pre-Install/Post-Install messages as needed.

f. Save the managed install.

So long as the MI is set to one of the Execute options, it will attempt to deploy the next time a targeted client machine checks into the K1000. This can be forced this on a client machine using the check-in steps provided earlier.

Be the first to comment

Workstation Uptime > 24 hours Smart Label

Today I set out to create a script that would automatically reboot workstations (not servers) at midnight following 24 hours of uptime. This is to facilitate patching and software deployment. The problem was the syntax for Uptime in the smart label wizard didn't seem to work any way I tried to enter it. With some help from IT Ninja and KACE support this is what I found works. 


For non-server windows based machines.

For Servers it shoud look something like this.

With additional limits on the Workstation Label

With the first smart label and reboot script, we're hoping to have this in place once it's tested and approved. I hope this helps!

View comments (4)
Showing 1 - 5 of 7 results

Top Contributors

Talk About PowerShell