/build/static/layout/Breadcrumb_cap_w.png

K1000 Managed Install v.s. Scripting

Hey everyone.

Searched this subject before, seems like nothing new on it for a while and with several appliance updates maybe things are a bit different than they used to be.

I wanted to open up discussion of Managed Install vs Scripting, and explain/explore the main difference between the two as well as how they can be similar.

I myself am a scripts guy, I like the extreme flexibility of what I can push this way especially as a heavy AutoIT user I often have my entire install/task/automation pre-compiled and just use scripting as a deployment method.

The other main scripts guy does not do automation like I do, but he has built all the managed installs.

From what I can tell the Managed Install ties to a Software Catalog item, this is so the K1000 can know what registry/file is checked to determine if the software is installed.  It then gets a deployment schedule and during probably inventory check in.  Should the computer be on the distribution list via label/name it will determine if the software is installed.  

If not, follow the specified install instructions using the dependency files attached.
If yes already installed?  I know it wont re-install but does it deliver the payload first?

That would be +1 to managed install as I know with scripts all the dependencies get copied over no matter what (well at least with offline scripts, perhaps online scripts do not)

I feel I can very closely emulate this same behavior by making a script and putting in on a schedule.
Have my verify step check something that would determine if the software is already installed, and if it is then do not try to install it again.

However how is the overhead and efficiency in this?   Is there some inherent methods that managed installs use that make this better to do via managed install?

To bring the gap even closer, smart labels.
Designing a label that in itself is placed on a computer based on software being on the computer or missing.  Then the script can run on a schedule and apply only to computers that have the label on them, and the label will automate based on current inventory database queries. 

I think as a result I have been able to emulate managed installs completely in the scripts side, but I wanted to hear some thoughts/opinions on the pros/cons and obvious differences I may be missing.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: chucksteel 3 years ago
Red Belt
1
Yes, you can emulate the managed install process, but I'm not sure why you necessarily want to put in the extra work. You can continue to leverage your AutoIT scripts, just upload them to the MI instead of a script. The K1000 will handle the rest of the logic. 

To answer your question, the installer for the managed install is only downloaded if the computer needs the software, so if storage/bandwidth is a concern then using a managed install is preferable.
Posted by: five. 3 years ago
Second Degree Green Belt
1
You covered most of the differences. The others I can think of: with a scripted install, everything hits at once. So it can slow down the network. And if it causes reboots or issues they all go at the same time. Whereas the MI will go staggered over time. You can go to Settings - Provisioning - Communication Settings to see the time frame.

Also, I believe with MI it runs as system account. Whereas scripting you can runas. Helpful in my environment because I have UAC enabled and local users are not admins.
 
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