KACE Product Support Question
K2000 3.6 Questions
So I updated my test box to version 3.6. I had a couple of questions about the new version. As a disclaimer I would like to say I've been using Kace for years now, and glad to see some of these new features implememted.
Now here comes my gripe...
1. It appears that .cmd files no longer work. Which is a problem for those of us that use .cmd files primarily. I know this was also an issue with the K1000 which is the main reason I waited for the hotfix for version 5.5.90546. Which repaired that. I see no mention of this in the "Known issues" section of the release notes. I think this should be included since they all worked in 3.5. I'm assuming this has something to do with the new task engine and error level checking? I am one of the fortunate ones that has a test box though, and was able to test my images prior. For those people that do not this could be a problem. Should I be using .bat files in both my K1 and K2 since this seems to be more "supported" with Kace? If so is there any documentation anywhere that says use .bat files because of "X"?
2. I was fortunate enough to attend a few classes on 3.6 in Austin in December. I learned there that this version would no longer be using "start /wait", and the "call" when calling a cmd file within a zipped file. For the users that did not get a chance to go how are they supposed to know this? Page 149 (mentioned twice), page 152, and page 154 of the admin guide still say to use the "call" command to run another batch script.
3. What is the correct syntax for using a powershell script now? What I had in 3.5 worked. I uploaded my .ps1 file and used "powershell.exe -nologo -executionpolicy bypass -noprofile -file <name>.ps1" as my command line.
I know you guys make changes. I would just appreciate a heads up if what I'm currently using will break after a patch. Especially for those that would be scrambling to make these changes in a production environment.