/build/static/layout/Breadcrumb_cap_w.png

K2000 - Install default software from K1000 during deployment

Update: Added Version 2.0 which includes the new konea path. DOWNLOAD Version 2.0 

Within the K1000 you'll have all your managed installation. If you want to install your software during the deployment within the K2000 during a special task here is how:

  1. Create a K1000 Script which calls all of your software you want to install in a single task (note: you can create different scripts for different K2000 deployment sets)
  2. Call the K1000 script(s) as a postinstall task in your K2000 deployment.
When you create the K1000 scripts take note about the scriptid (see screenshots).
uslTQL.png
xkLpQp.png
lFl5wa.png
9LHpgj.png
y123iC.png


After that you have to create a post install task which calls the script id:
4H8SBB.png

The executable is a autoit script created by myself. You can use and modify it the way you like. 

Screenshots during deployment:
If there is no connection to the K1000 this warning will show until a connection is established.
SWS70t.png 

During the deploy...
fThnyL.png


Comments

  • Awesome. I am also a AutoIT user and love how well it intergrates with the K1000 & K2000.

    In our environment the K1000 scripts are more of breakfix, update, and very scripty type things.

    My K2000 has all the software installs, but I still like this idea a lot and it could prevent use from doubling up jobs in some situations.

    Looking at the code, I assume the KBOT client has to be installed on the computer for this to work. That could be my only issue as we install it after we name the devices by hand.

    Our naming convention is too random to be automated.

    Best thing I learned is I see how you passed the script ID to the autoit.exe and then to runkbot.
    I have always use the runkbot 4 0 and runkbot 6 0 without really knowing what they did.

    Now I can see, it was calling script #4 and script #6 what ever those are, and that I can manually call my other scripts the same way! That is awesome when I am waiting for deployments in a pinch. - ViciousXUSMC 3 years ago
    • Hi ViciousXUSMC,
      thanks for your feedback! You are right. You can use this tool to run every Script id you like as postinstall task :)

      Regards
      Timo - Timokirch 3 years ago
      • Just got to use this today, works well!

        Only suggestions I came up with is add #RequireAdmin to the script.

        When running from the K2000 as system it is not needed, but for using it local & testing unless I ran it from a pre-elevated cmd it would not work.

        The other thing you could do is add @SW_HIDE to your RunWait() commands so that the command windows do not show on screen.

        Last MsgBox() freezes execution while it is up and of course keeps popping up with sounds and top priority. This could be changed to a GUI or a SplashTextOn() message so that it can stay up while waiting for connection.

        I also added the ability to pass multiple parameters at once so you can call the .exe just one time but launch multiple K1000 script jobs.

        Thanks again for the share, I learned a few great things about the K1000 and the agent by looking at it.

        With your permission I can post the modified source code. - ViciousXUSMC 3 years ago
      • That's why i love to share ideas :)

        Thank you very much for these information's. I would love if you can post / send the modified code. I would update the downloads afterwards :) - Timokirch 3 years ago
This post is locked
 
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