going from Altiris 6.9 to Kace
I'm moving from Altiris to Kace. But how do I resolve these challenges. I do a lot of "post image tasks" after imaging, and some tasks are conditional on the computer name prefix. Maybe that's not the best way to do it.
Kace client is 32k-bit. So for example calling reg.exe in a .bat script will be 32-bit.
No hierarchical folders for computers or scripts. (Wish I could drag and drop too.)
No way to script a reboot action and wait for the action to finish.
If you're looking to replace altiris 6.9 you may want to look into leveraging the K2000 for imaging as post-imaging tasks can be flagged as requiring a reboot which the k2000 will gracefully facilitate. As for the conditional tasks, I'm currently in the same boat and trying to determine the most scalable method for doing this. It will likely involve software collections and labels. I'm currently unsure how i want to do the label targeting whether heirarchal Active Directory OU based targeting for the majority of the packages.
We made that transition about five years ago, here are some tips I can share:
Conditional Tasks - Use smart labels for these. You create smart labels in the device inventory based on given criteria. When computers run their inventory the label will be applied if the machine meets the criteria.
32bit client - Use the /reg:64 flag to import keys into the 64bit area of the registry.
Folders for devices and scripts - This is a hard one to lose, especially the folders for scripts. A robust naming scheme for your scripts is the best advice I can give. As for devices, labels can be nested, so that does help, i.e. We have a label hierarchy for our computer labs, building, lab.
Scripts that require reboot - The script scheduling in the SMA is not as robust as Altiris, that is true. I really miss being able to schedule a script to run tomorrow morning at 5:00am. Surviving restarts is also an issue. There is at least one post on UserVoice for that functionality (https://kace.uservoice.com/forums/82699-sma-k1000/suggestions/16829452-add-a-reboot-in-the-middle-of-a-script) and there are probably more.
Some other helpful advice...
Brush up on your SQL skills. If you don't have any, then start learning or get someone on your team to learn. The appliance is much more powerful if you can create queries, this applies to complicated smart labels and other parts of the appliance.
If you aren't using the service desk, remember that it can still be used to automate tasks. Here is an example of adding data from the device inventory to the associated asset: https://www.itninja.com/question/is-sql-query-for-data-field-possible