KACE Product Support

This is what I would do, but with Kace there's always about 8 ways to accomplish your task.

Run an Offline Kscript.

Make sure to check mark "Enabled"

Select your new label under "Limit Deployment to Selected Labels". 

Select your OS.

Select your Schedule options. I would probably use "run at next client check in" in your case. I also usually set to run every 8 hours.

Dependecies:

(upload your vbsscript)

Verify:

(This step checks for a reg key, file, version number. Since I haven't seen your script I'm going to assume it's changing a reg key. If your script does not set anything obvious then have it create a reg key.)

Verify a registry Value is exactly...

Key: HKLM\Software\Kace

Name: Test

Equal To: 1

On Success

Log Message.... Reg key is already set.

Remediation

(This is the step that is taken if the verify step is not equal to in this case the reg key does not exist.

Launch a program...

Directory :$(KACE_SYS_DIR)

File: csript.exe

Parameters: $(KACE_DEPENDENCY_DIR)\script.vbs

On remediation Success

Log message ..... Script is successful.

On remediation Failure

Log message ..... Script has failed.

Once the reg key is set by your script then the next time the machine checks in it will verify that key is "whatever" and if it is it will just log a message, and not run again.

You can add a RunOnce key in registry which will execute your vbscript only one time..

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce

They have answered this but for the future:

If you are all Dell machines, think about adding the CCTK to your pxe boot and your images.  That will allow you to make changes to the bios during imaging and when the OS is up and running.  Allows quick fixes when a oops happens, I had a tech leave a classroom booting nic 1st then hdd, I was able to do a push to the machines and change the boot order via CCTK commands.