Can the K2000/SDA see scripts from the K1000/SMA?

Is it possible for the K2000 to see scripts from our K1000 if they are linked and then run them as post-install tasks during deployment? 

1 Comment   [ + ] Show comment
  • No, only SMA's managed installs, not scripts - Channeler 10 months ago

Answers (2)

Posted by: Nico_K 10 months ago
Red Belt

You cannot see the scripts in the SMA.
To run them you have  few possibilities which need an agent:

The easiest one would be:
create a smart label with newly built machines and attach the scripts to it so they will run as soon as the clients checks into the appliance, this is also the suggested since it is the basic functionality and does not need much effort to maintain

The more complex one would be: run the scripts over the runkbot as post install task.
1. find out the script id.
a) mouseover the script in Scripting|Scripts and note the message: sma/adminui/kbot.php?ID=103 then 103 is the script id
b) open the script under Scripting | Scripts and look into the title: sma/adminui/kbot.php?ID=103 then 103 is the script id

2. run the script using the scripting engine like c:\program files (x86)\quest\kace\runkbot.exe 103 0

Repeat this for all scripts
This could be problematic in maintaining if a script id changes due to replaced scripts.
Also this makes the SDA part of the process longer instead of using the SMA part where the SMA is built for.

Posted by: JasonEgg 10 months ago
Red Belt
Here's a feature request in uservoice for easier hand-off between SDA->SMA by applying labels as post-install task: https://kace.uservoice.com/forums/82717-sda-k2000/suggestions/1214277-ability-to-apply-k1-labels-from-the-k2-as-postinst
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ