- Task Property Enhancements
- Core Server Changes
There are many new features for Software Distribution in LDMS 2016. Some are very noticeable but other are enhancements that take place behind the scenes to improve performance and usability. Below you will find a list of the most important and exciting changes.
Task Property Enhancements
1. Custom Targeting
LDMS 2016 now has the ability to target from with the properties of the task. There is no longer a need to drag and drop the target devices from the network view to the task. All targeting types are supported. This includes the following:
- Targeted Devices
- Targeted LDAP objects
- Targeted Queries
- Targeted LDAP Queries
- Targeted Device Groups
- Targeted Scopes
- Targeted Time Zones
In the below listed example you see a view of a Targeted Device (Win7-Device Name) added from the task properties.
|Select Targets||List of Available Targets||View of Selected Targets|
2. Task Templates
We have introduced Task Templates in LDMS 2016. We currently have defaults for two types, Software Distribution (SWD) and Patch Management. The Accelerated Push Task Template is enabled by default for both task template types. Task templates give you the ability to custom target devices from within the template itself. Any devices added within a task template stays with the template until manually removed. You cannot associate SWD packages to your default SWD task template but can with any non-default SWD task template.
In the below listed example you see a view of a Default Accelerated Push - Template
|Task Templates||Custom Targeting|
|Task Template Overview||Task Settings|
3. Ability to Skip Previous Successful Targets
From within the properties of the task you now have the ability to "Ignore subsequent request on successfully targeted clients". This is NOT enabled by default. When selected the package won't download or run on devices that were previously successful. This activity is calculated at the client level by viewing the .stat file associated to the successful task. This is a handled on a per task basis and not per package.
|Ignore Subsequent Request|
4. Accelerated Wakeup
Accelerated Wakeup has actually been included in LDMS 9.6 SP2. This feature does not conduct a device discovery. When selected, we simply send out magic packets in at attempt to wake up the device. Unlike the standard "Wake up device" option included in the task properties, "Accelerated Wakeup" will not return the device to a shutdown state.
*Note - In order for Wake on Lan (WOL) to properly work, the Bios and/or Network Adapter of the desired client has to be capable and configured to take advantage of the WOL technology.
5. New Package Menu
The Package Menu has been reorganized as depicted in the display below.
|Windows Package Options||Universal Package Options|
6. Windows Action
The Window Action types is now included in LDMS 2016. This action makes use of Powershell cmdlets and contains the following features:
- 18 Canned actions
- 1 Custom (allows you to use your own powershell syntax)
- Chained with error checking
- Cmdlet preview
- Custom ordering
Macro expansion (i.e. %ld_client_dir%, %windir%) is also supported and these variables are resolved client side. With error checking embedded, any Powershell failures are gathered and appended to sdclient_task log files on the client.
In the display below, there's an outline of what a "Connect to UNC Share" action type looks like.
|Windows Action Type||Action Type List||Connect to UNC Share|
Note* Any passwords for connecting to UNC shares are encrypted, only visible by the owner and disabled if the owner is public
7. Android and iOS
There are now Mobile package types for Android and Apple iOS. We currently only allow for free versions to be obtained from the various App stores, however, we do support the use of Manifest URLs and Hosted Apps.
|Mobile Package Types||App Search||App Preview|
8. Inter-Package Actions (Bundles Only)
This feature allows you to inject "reboot" and "continue on install failure" actions in to Bundle packages. The reboot action does not use the Landesk reboot settings.
Note* The reboot action is hard coded with a non-configurable 30 second count down. The user cannot defer this reboot action.
Core Server Changes
9. Enhanced General Push Option
A new option to control how long a task spends actively pushing out to clients has been added. "Maximum Task Run Time" allows you to choose how long you want a task to keep actively pushing out to devies before failing the task. This allows you to run a push, but ensure that it stops rolling out to machines after a certain amount of time to not overlap any other tasks that may need to run. By default the task will stop pushing out after 15 Minutes, this is also the smallest amount of time that you can set the Maximum amount to (option can range from 15-240 minutes), if the task finishes running before this, it is done and will move to a completed status. This setting only controls how long the core will actively try to contact machines to run the task, the minimum time of which is 15 minutes and if you have a task that takes longer than that to contact all the machines, you can allow up to 240 (4hrs) for the core to contact all the devices in the task.
To access this option go to the Console and click on Tools | Distribution | Scheduled Tasks, click on the cog icon in the Scheduled Tasks toolbar, and select "Default Scheduled Task Settings". Look at the General Push settings to see the slider bar to set the Maximum Task Run Time.
|Enhanced General Push Option|
10. Bulk Package Credentials Updater
In LDMS 2016, we've included a Bulk Package Credentials Updater. This feature allows you to update any package that has user credentials loaded in the package properties. From this view you can multi-select your desired packages and change the credentials currently loaded. This toolbar option is not available for non-administrators.
|Bulk Package Credentials Updater Toolbar Icon||Bulk Package Credentials Updater|