/build/static/layout/Breadcrumb_cap_w.png

Blog Posts by DaveMT

Ask a question

Basic Scripted Installation Deployment For Windows 10 Example

Here is a basic script built installation for those needing an example to start from:



That should give you a good example for a scripted (Non-UEFI) built for Windows 10.  I hope this helps you out.


 



View comments (1)

Basic Software Distribution Example

I've had a lot of positive feedback on my example of how I do a managed software distribution, so I thought I would share my instructions.  Feel free to contact me if you have any questions.


KACE Software Distribution

First Step is to creating a Software Distribution package is to gather up all the installation files required and zip them up into a since zip file.  Be careful the files are at the root of the zip and not in a folder at the root of the zip file (This could cause failures).

Save the zipped file to a location accessible when uploading to the KACE web interface.

Now, log into your KACE environment and pull up a current inventoried PC that already has that software installed.  Expand the Installed Programs field under Device Inventory.  Find the software and click on the hyperlink for it.  Please note that this must be the exact same version of the zipped package.

Under the Manage Operating Systems, ensure all OS versions you plan to distribute this to are selected (Note that with version 8 release of KACE, you can select entire OS Versions instead of individual versions as an option.)

Click on the Browse button, browse to and select the zipped file you have saved.

After selecting the file, change the Category and Threat Level as needed.  Click Save button when finished.

Navigate to Home>Label Management, then click Labels

Under Labels, click Choose Action and select New Manual Label.

Complete Name, Description and selections for Restrict Label Usage To.  Click Save when finished. Note: I start Software Installation Labels with SIL (Software Installation Label) for Best Practices

Navigate to Distribution>Managed Installations.  Under File, click New.

Configure Name, Execution; choose the software from the drop down options (Choose the one you uploaded earlier)

Note that with Version 8 you can choose Cataloged Software or Software from the Software list.  Your uploaded zip file will be associated under Software.


Now choose the installation commands.  Most often you will choose Override Default Installation to include switches such as silent installation.

Under Deploy, click Manage Associated Labels and select the label you created for this distribution and apply it.

Configure Notifications to give the user warnings and completion messages.

Configure Schedules as needed (What times it is permitted to install and how many attempts until it reports failed, etc.)  Click Save when complete.


Now, to have software install apply to devices, you will need to Apply the new Label to any device you wish to install it on.  After the device inventories next, it will install per configured settings.


NOTE: If device has a local KACE Repository, this may not work until the repository has obtained a local copy of this distrubtion (sometimes up to 24 hours)




http://www.itninja.com/refer/DaveMT




View comments (1)

TeamViewer/KACE Integration

I found looking over several different forums and sites how to get the TeamViewer integration for simple click and remote in KACE.  I put together a process how I got it to fully automate the obtaining of the TeamViewer ID and simple two click connection to remote the remote device.  I hope you find this helpful.


TeamViewer/KACE integration


This is done with a few different tasks to do in KACE.  These are the steps I completed after creating and deployed our own custom Host MSI package of TeamViewer with our settings and password built in, however the support technician needs to have the full TeamViewer support client installed.


First step is to add a custom field in KACE to identify the TeamViewer Support ID.

 

Task 1 (This is for creating custom inventory field for TeamViewer 11 Support ID)


  • Under Inventory>Software, choose New under the Choose Action drop down menu.

  • Give it a name TEAMVIEWERID           

  • Version is 11.x

  • Publisher is TeamViewer

  • Add notes (Captures ID for TeamViewer 11)

  • Select all Windows based operating systems under Supported Operating Systems

  • The Custom Inventory Rule is asking what to look for.  In this case, we are look for the TeamViewer ID in the registry.  Copy and paste:

    • RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TeamViewer, ClientID, NUMBER)

  • Click Save. (After systems begin to inventory, they will populate this field if they have TeamViewer 11 Installed.  This is located under Software>Custom Inventory Fields in Device Inventory.

     

     

    Task 2 (This is for adding the TeamViewer Device Actions to the inventory fields)


  • Under Settings>General Settings scroll down to the bottom until you see Device Actions

  • Click Add New Action

  • In the name box, type TeamViewer Remote

  • In the Action drop down, choose Custom Action

  • In the Command Line box, copy and paste this line:

    • "%ProgramFiles%\\TeamViewer\\TeamViewer.exe" -i KACE_CUSTOM_INVENTORY_TEAMVIEWERID --Password P@ssw0rd

  • Click Save and Restart Services (This will cause the K1000 to go offline for a few seconds)

     

     

    NOTE: This is only designed to work with Internet Explorer (If you wish to use Firefox or Chrome, you will need to add the IE Tab plugin)

You will also need to have the full TeamViewer Program installed onto your PC.  Several settings need to be applied to the IE Settings for it to work.  These settings can be applied via GPO or manually directly on the support PC.  Here are the security settings that must be done in IE for this to work.:


Tools Internet Options | Security Select Trusted Sites Icon | Sites Button
    -Add the KACE server to the zone (should be in the top box if you have KACE open actively)
    -Require Server Identification (Uncheck)
    -Click Close Click on Custom Level button ActiveX Controls  Plugins
    -Allow previously unused ActiveX controls Enable
    -Allow scriptlets > Enable
    -Automatic Prompting for ActiveX controls > Enable
    -Download unsigned ActiveX controls Enable
    -Initialize & script ActiveX controls not marked safe for scripting > Enable
    -Run ActiveX controls and plugins > Enable Click OK to close Security Settings Window Click OK to close Internet Options Window


View comments (3)
Showing 1 - 4 of 4 results

Top Contributors

Talk About Application Packaging