KACE Product Support

I had come across the get-set-computername several times in my searching, but seemingly the only official reference that says it can prompt for a computer name is on the page you referenced, which says, "Major features include ... -dialog prompting". But that page also says that complete instructions are in the README.txt, which doesn't mention dialog prompting in the main portion of the text. Now that you tell me it's there, I looked a little harder and found it in the Appendix and later in the Version Information. I would encourage the writers of that documentation to update it to put the dialog information in the main text itself, along with the other methods for how the app can be used.

Granted, it's my fault I didn't find that reference, but learning KACE on my own without proper training presents a HUGE learning curve, and digging in appendices for what I would have expected to be in the main text wasn't in my mindset.

But thank you for making me aware that this app has the possibility to save me some work.

=====

Yes, I understand that the scripts can be created/edited elsewhere, and then rolled into a pre/post-install task. But that means I now have to remember how to do all the KACE stuff, as well as the off-board stuff - what scripting language/tool did I use last year to create this? where did I store that work? did I have to move the scripts elsewhere after packaging them? Further, if someone comes behind me to take on my role, they will have no idea of what these hidden scripts do, or where they are, or how to change them, or how to make them apply. None of this is a show-stopper, but it'd be *so* much easier to be able to edit the scripts right there within the K2000 web interface, just as I can edit BAT scripts right there in the K2000 web interface.

=====

We *could* do images/scripting the way you do it, copying and modifying the standard image as needed, but that doesn't fit our culture as well as having a standard image with checkboxes at the start of the install to determine what apps get installed. Much of our tech workforce consists of temps who are here at best three or four years, usually two at most, who come and go, and neither need to be bothered with the intricacies nor the responsibility of tinkering in the KACE system with our images.

=====

I have tried looking at the KBE Manipulator, but that's just one more thing I have to add to the basic system, and one more thing to learn in order to make this system work. I know I've looked at it several weeks ago, but I could not tell you one single thing about it at this moment, other than I don't remember anything about it except that I couldn't get it to do what I needed at the time for it to do. (I have WAY more responsibilities in my job than making KACE work the way I need it to work.) At this moment, when you suggest it as a solution to putting Powershell into the KBE, and gave me a link, I was more than willing to go see what was involved, but that link doesn't seem to indicate where I need to go next to get Powershell into a VBE, which means I'd be spending another morning doing research instead of doing my job. I'm all for research, and learning how to use the tools that will best serve my purposes, but this morning, like most, I have fires to put out that don't leave me time for fixing a problem that Microsoft should have already had in place, if they really want Powershell to be the de facto tool for sysadmins.

=====

I apologize if I sound like I'm whining; I'm just frustrated. I thought the KACE was supposed to make my life easier (and I think eventually it will); it's just not at a mature state where it actually does at the moment. - kentwest 7 years ago