Advanced Deployment Approaches

Mike Saladino - Sr. Sales Engineer Phil Crosby - Sales Engineer

Agenda
Advanced Distribution Building Blocks
4 Ways to Install Software Labels and Filters Custom Inventory Rules and Custom Data Fields Understanding Event Scheduling

Use Cases
Standardize your population - custom inventory + filter Uninstall/Install Example - MI vs. Script with multiple tasks Alt. Download Locations - Network installs (no uploads to KBOX) Staging Patch Feed

Building Blocks - Managed Installs

Payload Advantages
Tied to Inventory - Only run if needed Load balanced User interaction - prompt/snooze Simple scheduling - tied to Inventory, Deploy Window Alternate Download Locations

Limitations
Can order, but not dependent on success Tied to Inventory Schedule Single Command Line No pre-requisite verification
3

Managed Install Interface

Managed Install Interface (cont)

Building Blocks - Scripting

Payload (Dependencies) Advantages
Pre-flight Verification Multi-step processes Dependent Tasks Flexible Scheduling - one off, repeating Built in staging of payload for future execution

Limitations
Requires manual verification of need No Alternate Download UI Manual end-user notification - no snooze

Scripting Interface

Scripting Interface (cont)

Scripting Interface (cont)

Building Blocks - Patching and Kontainers

Application Installers in Patch Feed
Pre-packaged 3rd Party Apps Flexible detection and scheduling No work needed but no control over install options Example at the end

Virtual Kontainers
Repackaging the KBOX way Execution Control Label-driven, so same concepts apply Not covered in this presentation

10

Patch Module Installers

11

Building Blocks - Labels and Filters

Manual vs. Filter vs. LDAP/AD Calculated at Inventory Nesting

12

Filters
Identifying groups of machines using computer inventory details like IP address, computer name, OS type, etc.

13

LDAP/AD Integration

14

Building Blocks - Custom Software/Fields

Software Family Example ie version < 8 Chassis or Flag drop out of label

15

Custom Software Item / inventory rule

16

Custom Inventory Rule Syntax

17

General use
Manually construct logic for software package detection within a custom software item
FileExists(C:\WINDOWS\notepad.exe) FileVersionEquals(C:\Program Files\Internet
Explorer\iexplore.exe, 6.0.2900.2180) RegistryValueEquals(SOFTWARE\Microsoft\Internet Explorer\Version Vector,IE,6.000)

18

Advanced Use
Detect ranges of software versions(or combinations)
RegistryValueGreaterThan
(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Co mmon\ProductVersion,LastProduct,11.0.0.0) AND RegistryValueLessThan (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Co mmon\ProductVersion,LastProduct,12.0.0.0)

19

Building Blocks - Scheduling

When are labels calculated
Ordering of labels for nesting

When do MIs run When do Scripts run

Online vs. Offline (Server vs. Agent time) AMP queuing vs. All at once

20

Filter Orders and Nested Labels

21

Use Cases - Custom Inventory Rules

22

Use Cases - Custom Filter for Installs

Identify machines missing software
Filter identifies and automatically labels machine based on
missing software

Create a Managed Install for that label to install software Software is installed to this label to machines within it

23

Use Cases - Automated Uninstall/Install

Standardize your software population
Custom inventory rule to identify outdated software

Put those machines into a label for outdated software Assign an uninstall script to that label that removes it Create a Managed Install for that label to install the new version Any future outdated software found will automatically be updated

24

Use Cases - Alternate Locations

Used to offload software packages from the KBOX to an alternate network location on a smaller scale (configured per MI)

25

Use Cases - Staging

Use to copy large installation files out to clients ahead of coordinated deployment. Deploy install file with File sync or Script Trigger with Script or Managed install.

26

Use Cases - Patch Feed

Create a patch label for installers you wish to deploy Assign that patch label to a machine or group of machines Put it on a patch schedule Anytime a new version is available through the patch feed, it can be deployed automatically and without the need to create MIs or scripts.

27

Keep the Konversation Going!

Visit appdeploy.com/kace Ask Questions, Get Answers, Share your Expertise!

28