Explanation

There are many new features to Software Distribution in LDMS 9.6 SP1. Some are visible, and some are enhancements that took place behind the scenes to improve performance. Below you will find a list of the most important and exciting changes.

Distribution Package Changes

1. Signed PowerShell Scripts

  LDMS 9.6 SP1 has the ability to deploy signed PowerShell scripts adding another layer of security to PowerShell deployments. However this requires that the environment be configured correctly ahead of time to allow the signed scripts to run. Basically put you have to be able to run them securly outside of LANDESK before you will be able to deploy a signed PowerShell script inside of LANDESK. For this you have to import your PowerShell certificate into each client that will be running the scripts.

  Also to control whether LANDESK is going to handle the script as signed or not we have added PowerShell Security Options to the Package UI. By default this value is unchecked, making no change for existing PowerShell packages. The default value can be changed to always pre-check this box in the Distribution Package Properties by clicking on the Default Package Settings cog icon in the toolbar. Select PowerShell security, check or uncheck the box as desired, click Save.

2. Metro App Distribution Packages

  Also new in LDMS 9.6 is the ability to deploy Metro Apps for Windows 8.1. Due to the security constraints placed on Metro Apps by Microsoft, the apps are only able to be "sideloaded" by LANDESK, and thus it requires your clients be configured to allow sideloading apps. You can find more information on this process here (Sideloading Requirements).

  To create a new Windows Metro Application package, in the console go to Tools - Distribution - Distribution Packages, in the toolbar click on "New Distribution Package", and select "New Windows Metro Application package." Point to the .APPX file as your primary file, and add any necessary additional files. Then schedule and deploy as you would any other software distribution task.

3. Link Package Icons

  In line with changes made in LDMS 9.6 to allow you to use JPG and PNG files for your Portal Manager and Fuse icons, we have now extended that capability to Link Packages. Current packages with the standard .ICO files will continue to function the same, however any NEW Link Packages will require the link icon be provided as a JPG or a PNG file. For the best result please use a PNG that is formatted as 320x200 pixels in size.

Core Server Changes

4. SchedQry.exe and SchedLDAPResolver.exe improved, what took hours may only take minutes.

  The processes for resolving queries when tasks are started, and also in charge of running once an hour (Default schedule) to re-resolve those queries and add or remove machine from tasks as necessary has been improved with Multi-Threading and also Results Caching. With the Multi-Threading the processes are able to resolve queries much more rapidly, also we have implemented very strict logic to control how many threads are used to ensure the best use of resources. Likewise, we also employ results caching so that we avoid re-resolving the same query for each task it is targeted at, improving resolution time, and taking some of the load off of the database.

5. Enhanced Accelerated Push options

  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 30 Minutes, this is also the smallest amount of time that you can set the Maximum amount to (option can range from 30-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 30 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 Accelerated Push settings to see the slider bar to set the Maximum Task Run Time.

6. New option for when users are logged off their machine.

  We now have the option that if a user is logged off their machine, the task can be automatically delayed to Run at Next Logon. This allows flexibility in controlling when tasks are run on client machines. Also of note, is even if a user is logged on, you can also automatically defer the task until the next logon to ensure a cleanly logged in machine for installing packages. This is great for tasks that require programs to be closed when installing, as the install happens before the user opens their programs to begin their work.

  These options are found in the Distribution and Patch settings. In the console go to Tools - Configuration - Agent Settings, expand All Agent Settings and click on Distribution and Patch. Select the settings you would like to alter from the list or create a new setting. Once inside the Distribution and Patch setting Properties do the following:

• Logged Off User, Run at Next Logon option
  1. Expand Distribution Only Settings
  2. Select Logged Off User options
  3. Set the behavior to Run at Next Logon.
• User Logged On, Automatically Defer Until Next Logon option
  1. Click on Distribution-Only Settings
  2. Check the option "Defer Until Next Logon"

7. Task Visibility - Stages

  One of the most informative new features of LDMS 9.6 SP1 is the ability to see at a glance what stage machines are in while running a task. The stages from beginning to end are:

1. Core Initiated - Core is processing task, and contacting clients.
2. Starting - Client has received task and is preparing to run it.
3. Downloading - Client is downloading files.
   • During this stage, if "Send Detailed Task Status" is enabled, a progress bar showing the download percentage is visible in the task progress view.
4. Installing - Installation is running on client.
5. Completed - Task is done running on client machine (regardless of failed or successful status)

8. Scheduled Tasks and Diagnostics Utility

Learn more about it here:

Scheduled Tasks and Diagnostics Utility

9. Package Relationships UI

Learn more about it here:

Package Relationships new in LDMS 9.6 SP1

Overview

New to LDMS 9.6 SP1 we have replaced the Scheduled Tasks and Policies utility with a more functional and robust Scheduled Tasks and Diagnostics utility.

Opening the Scheduled Tasks and Diagnostics utility

There are two main ways to access the Scheduled Tasks and Diagnostics that will provide slightly different views.

1. Right click on the device(s) and select "Scheduled Tasks and Diagnostics"
2. Drill into the "Top Failure Codes" chart in Scheduled Tasks. Instead of getting a list of the tasks a particular machine is part of, you will get a list of all machines from all tasks that have returned a specific error code.
   1. In the Management Suite Console go to Tools - Distribution - Scheduled Tasks.
   2. Click on the top node of the Task Tree, above My Tasks.
   3. Locate the chart titled "Top Failure Codes"
   4. Double click on the failure code you would like to investigate.

* Note: The Top Failure Codes chart shown here was moved to be the first chart shown, by default it is actually the 5th chart in the list.

The Scheduled Task and Diagnostics View

Shown Above: Scheduled Tasks and Diagnostics as opened by drilling into the Top Failure Codes chart (method 2 explained above) showing all machines from all tasks that returned a specific error code. You may notice that the same machines appear 3 times, this is because those machines gave the same failure code on three different tasks.

So what am I seeing here?

  In the screenshot above you can see the list of machines that returned the same error code, in this case an error code of "1." Also you notice there are some new icons in the toolbar, and a tool for displaying log files which also highlights information of interest in the log. Lets go into each of these views a bit deeper.

Toolbar

1. Logs - From this drop down menu you call pull up logs into the viewer, in real time, from both the client and the core server. If selecting logs based on a task, it will automatically pull the logs for the task that is highlighted in the machines and tasks list. Also, under client logs there is the option to "Get All and Zip" which zips up ALL client side LANDESK logs, and ask where you would like to save them on your console machine.
2. Export - CSV Export of the machines and task list.
3. Real Time Discovery - Allows user to discover the device in Real Time and verify that it is available on the network and that LANDESK can communicate with it. This uses the same Discovery method as when a task is started to assist in troubleshooting.
4. Inventory - Open the Inventory of whichever machine is highlighted in the list.
5. HTML5 Remote Control - With a single click you can open a HTML5 Remote Control window into whichever machine is selected in the list.
6. Remote Event Viewer* - Displays the selected machine's Event Viewer for simplified troubleshooting.
7. Remote File System* - Opens Windows Explorer to the C$ share of the selected device.
8. Synchronize Policies - Manually kick off a policy sync on the client machine with quick click.
9. Highlighted Text Web Search - Whatever text you have highlighted yourself in the log file displayed below will be automatically entered into a web search to help find more information. This is helpful when investigating return codes from common program like Microsoft Office, or an MSI install that uses standard MSI return codes.
10. Find - Search based on information in the list of machine and tasks.

* = Authenticates based of the user that is signed into the OS of the computer running the Console, and not with the credentials used to log into the console. Local and Domain security policies may not allow remote access.

Machines and Tasks List

• From this list you are able to see the Machine names, and Task IDs and Names along with the final Return Code from the task, along with other identifying information to assist in troubleshooting.
• As mentioned earlier, whichever machine\task is selected in this list will dictate which logs will be shown and what machine is on the receiving end of the action initiated from the toolbar.
• All the actions in the toolbar are available in a right click menu, by right clicking on any machine\task in this list so that you do not have to move the mouse cursor back and forth.

Log Viewer

• The Log Viewer will only show the last 50k of data in the log file. If you need to see more than this it will prompt you and ask if you would like to open the log in an "Editor", which generally would be Notepad.
• The log is automatically parsed and pertinent information highlighted upon opening.
  • Red - Possible failure
  • Orange - Possible warning
  • Blue - Possibly informative
• Search results from the Log Search utility is highlighted in yellow. Once a search term is entered pressing enter repeatedly will automatically cycle through the results.
• Highlighting any information with your cursor and pressing the Web Search button on the toolbar will automatically open a browser and search the web for that highlighted text.

Conclusion

   The Scheduled Tasks and Diagnostics utility is one of the most exciting new features of Software Distribution as it will facilitate the use and troubleshooting of Software Distribution and Patching tasks across the board. Please take the time to familiarize yourself with its features and see how they can most benefit you in your day to day activities.

Software Distribution for LANDESK Management Suite

• This is a list of highly recommended documents for increasing overall knowledge of this component.
• The article's listed below are applicable to LANDesk Management Suite 9.0 and may apply to 8.8.
• If you want to review additional content regarding this component, please use Documents or Discussions buttons on the overview page.

Changes in Software Distribution for LDMS 9.6 SP1

• Whats new for LDMS 9.6 SP1 Software Distribution

• Scheduled Tasks and Diagnostics Utility

• Package Relationships new in LDMS 9.6 SP1

Initial Install and Configuration

• Video: Software Distribution Fundamentals: Creating Distribution Packages
• Video: Software Distribution Fundamentals: Delivery Methods
• Video: Software Distribution Fundamentals: Scheduled Tasks
• Software Distribution (LDMS) Desktop Manager Configuration Guide
• How to Configure a Preferred Package Server
• How to set up a HTTP share for a Preferred Package Share
• Using LANDesk Content Replication
• Deploying a Virtualized Application via LaunchPad Quickstart Guide
• AdminStudio 2013 Limited Edition for LANDesk® Management Suite
• Quick Start Guide for using AdminStudio to repackage a software installation into an MSI package.
• Best known methods to configure and use Fuse

Additional Options and Information

• How to keep files in the SDMCACHE directory for a longer period of time
• SDCLIENT.EXE Command Line Switches
• Understanding Batch File Distribution Packages
• Working With Registry Keys in a Batch File
• How to use Reboot Settings
• Time Zone Aware Targeting for Distribution Tasks

Troubleshooting this Component

• How to quickly troubleshoot a Software Distribution job.
• Policy Tasks Run on Clients After Tasks Have Been Deleted From the Core Server.
• The Scheduler Service stops after each completed task
• Troubleshooting "Failed to download additional files"
• Advanced Install and troubleshoot Fuse
• ClientDBUtil.exe Application Error

Notice: Any E-Learning content is available by default to Members who have a minimum support agreement at Professional level.

NOTE:This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to Software Distributionif this page hasn't helped.

good morning,

I have a new core server 9.6. I configured the différent items.

I create a new distribution package. The source of package is in the different server with IIS . (The source is the same that the old core server in 9.0)

When i try to distribute a package i have a error message "The extended attributes are inconsistent"  with RunPackageInstall: stop on returncode=8db500ff of package=Bélux - Filezilla client (v3.5.0)

Mon, 22 Dec 2014 11:52:25 ******* sdclient starting to process task *******

Mon, 22 Dec 2014 11:52:25 Task id to process: 28

Mon, 22 Dec 2014 11:52:25 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.28.RunNow._+IKN5GV5vP1p+oDwfYN3rtvdjKU=.xml"

Mon, 22 Dec 2014 11:52:25 File (http://landesk-packages.match.eu/02_DSI/Filezilla (v3.5.0)/Onefile/Filezilla (v3.5.0).exe) is cached locally

Mon, 22 Dec 2014 11:52:25 The nostatus flag has NOT been set.

Mon, 22 Dec 2014 11:52:25 Core name 'SLAM0015.match-supermarket.com' obtained from active task list

Mon, 22 Dec 2014 11:52:25 Sending task status, cmd line -coreandip=SLAM0015.match-supermarket.com -taskid=28 -retcode=229392444 -pkgid=14

Mon, 22 Dec 2014 11:52:26 About to call DownloadFiles (1 files) with these settings:

Mon, 22 Dec 2014 11:52:26 m_allowedBandwidthWAN: 50

Mon, 22 Dec 2014 11:52:26 m_allowedBandwidthLAN: 75

Mon, 22 Dec 2014 11:52:26 m_maxDiscoveryThreads: 1936020028

Mon, 22 Dec 2014 11:52:26 m_discardPeriodSeconds: 604800

Mon, 22 Dec 2014 11:52:26 m_preserveDirectoryStructure: 1

Mon, 22 Dec 2014 11:52:26 m_bUseWanBWForPush: 0

Mon, 22 Dec 2014 11:52:26 m_bSynchronize: 0

Mon, 22 Dec 2014 11:52:26 Allowed download methods(m_downloadControl):

Mon, 22 Dec 2014 11:52:26 PeerOneSource

Mon, 22 Dec 2014 11:52:26 Peer

Mon, 22 Dec 2014 11:52:26 Source

Mon, 22 Dec 2014 11:52:26 m_preferredServerControl: AttemptPreferredServer

Mon, 22 Dec 2014 11:52:28 The nostatus flag has NOT been set.

Mon, 22 Dec 2014 11:52:28 Core name 'SLAM0015.match-supermarket.com' obtained from active task list

Mon, 22 Dec 2014 11:52:28 Sending task status, cmd line -coreandip=SLAM0015.match-supermarket.com -taskid=28 -retcode=229392258 -pkgid=14

Mon, 22 Dec 2014 11:52:30 ExpandEnvironmentVariables Result:

Mon, 22 Dec 2014 11:52:30 The nostatus flag has NOT been set.

Mon, 22 Dec 2014 11:52:30 Core name 'SLAM0015.match-supermarket.com' obtained from active task list

Mon, 22 Dec 2014 11:52:30 Sending task status, cmd line -coreandip=SLAM0015.match-supermarket.com -taskid=28 -retcode=229392406 -pkgid=14

Mon, 22 Dec 2014 11:52:31 ClientThread

Mon, 22 Dec 2014 11:52:31 PackagePath:     [http://landesk-packages.match.eu/02_DSI/Filezilla (v3.5.0)/Onefile/Filezilla (v3.5.0).exe]

Mon, 22 Dec 2014 11:52:31 PackageGUID:     []

Mon, 22 Dec 2014 11:52:31 PackageParam:    [/Ah- /Ab ]

Mon, 22 Dec 2014 11:52:31 File is cached, the local location 'C:\Program Files (x86)\LANDesk\LDClient\sdmcache\02_DSI\Filezilla (v3.5.0)\Onefile\Filezilla (v3.5.0).exe' will be used

Mon, 22 Dec 2014 11:52:31 Installing 'C:\Program Files (x86)\LANDesk\LDClient\sdmcache\02_DSI\Filezilla (v3.5.0)\Onefile\Filezilla (v3.5.0).exe' with the following options '/Ah- /Ab '

Mon, 22 Dec 2014 11:52:45

Mon, 22 Dec 2014 11:52:45 InstallProc returned 255

Mon, 22 Dec 2014 11:52:45 AiExitCode = 255

Mon, 22 Dec 2014 11:52:45 RunPackageInstall: stop on returncode=8db500ff of package=Bélux - Filezilla client (v3.5.0)

Mon, 22 Dec 2014 11:52:45 processing of package is complete, result -1917517569 (0x8db500ff - code 255)

Do you know a issue of this problems.?

Thank's

Arnaud.

Environment :

LDMS 9.6 :

Added in LDMS 9.6-SP1 :

If you migrate to a new LANDESK Core server, one of the challenges can be getting all of the SWD packages updated with the new server name.

If using CoreSync is not an option, then this query will help to update the package paths that are defined in the individual SWD packages.

As always, before running any query that could negatively impact your environment ensure the following.

1.  You have a verified backup of your database.

2.  Test in a non production system before applying any changes to a production environment.

/****** Query to update package paths in all SWD packages  ******/

UPDATE dbo.PACKAGE_FILES_HASH SET FULL_PATH = replace

(FULL_PATH, 'OldServerName', 'NewServerName') WHERE FULL_PATH LIKE '%OldServerName%'

This query will update all of the paths for the Primary File in the SWD package as well as all Additional Files.

Here is the package after running the sql command.

Hi All,

I wonder If someone can help me with the following issue.

Visual studio 2013 pro got failed when I pushed from landesk.

When I tried the package manually in the system,It got failed in 4 system and it got succeeded in 2 system out of 10.

Downloaded the new package and tried nothing helped, I gave full internet access not helped.

Error: Visual Studio core features fatal error during installation.

Thanks & regards,

Dinesh

Hi All,

can anyone help me with the script to remove the admin rights from the group. I am trying to push this from software distribution that got failed.

When I try to run manually, it works fine, please help me

@ECHO OFF

REM Adding a local group
net localgroup Administrators dinesh /delete

exit /b

HI Friends,

Can some help me with the batch script or shell script to uninstall visual studio 2013.

Thanks

Hi All,

Please help me with; how to remove local admin rights using LANDesk.

Thanks & Regards,

Dinesh

I created a package and a scheduled task (I set to Policy Task Type), to put an Icon (that opens a URL Link) to Launchpad on 22 PCs. The process completed successfully and users are able to open the Web Site.

Then I deleted the Schedule Task thinking I don't need it anymore. That Icon I put on all those PCs disappeared the following day.

I had to redo the entire process. This time I did not delete the Scheduled  Task.

May I please ask if it is necessary to not delete the Scheduled Task in order to keep the Icon in place, and why. I would like to please have a documentation on this type of process to keep as my notes. Would anyone have some notes to share please?

Thank you so very much.

Ernie Biala

Purpose

Method for remote unprovisioning of vPro clients, for troubleshooting and correcting issues that may require the client to be unprovisioned.

The Intel(R) AMT Unprovision Utility is a simple command line utility that allows users to remotely unprovision an Intel(R) AMT system without requiring a

separate management console.

Steps

1. Download the Intel UnprovisionEx.exe tool.
2. Unzip the files to your Software Distribution Storage.
3. In the Management Suite Console, create a new Software Distribution Executable package.
4. In the Package Information section use the UnprovisionEx.exe as the primary file.
5. In the Install/Uninstall Options section add the following switches into the install/uninstall options: -hostname %computername% -user admin -pass P@ssw0rd -full
   • For the password please use the admin password for your vPro machines .
   • The -hostname can be either the listed variable, FQDN or IP address.
6. Save the package and schedule it out to the vPro devices you would like to unprovision.
7. Once these machines are in the pre-provisioned state attempt to zero-touch provision these devices.

(To verify the provisioning state of the machine please reference https://community.landesk.com/support/docs/DOC-31903)

Hi Friends,

I hope some of you might also have come cross with the following issues, Kindly suggest or help me.

Our ERP oracle application tool will only work with JRE6u27, But the latest JRE is JRE8u25.the following  KB files blocks outdated java in IE. But we have pushed these patches already using the LANDesk  patch manager and we are trying to uninstall the same. But I wonder after recreating a profile in the system , application started working with JRE6u27 but still the system has following KB files installed in it. Recreating profile in 1000 pc is highly impossible in the domain network. Kindly suggest us.

KB2987107

KB3008923

KB3013126

KB2976627

Wish you happy new year,

Thanks,

Hi All.

I have been set a challenge to standardise the version of Skype that is deployed over our network.

After some "Goggling", this seems like a challenging task.

From what I can tell, the specific version of the ".MSI" needs to be ran with various switches. This could prove time consuming as there are alot of different version installed.

Can anyone help me accomplish this task with LANDesk??

Any help would be appropriated.

Thanks.

Adam.

In some of client ,it's show this error when open the landeskportalmanager of LDMS  , click yes is still Pop up this box,and it can't used.anyone have solution for this error?

Hi All,

In my environment, few device’s policy.sync.exe log is showing the below given error . After performing the local DB cleanup task (stopping policy related task/exe ,clear xml files , deleting the DB files (it was having size 0 KB) , creation and validation of new local DB , starting the policy service/exe. ) , the policy sync started working fine.

Can you please help me on identifying the root cause  and preventing this error. Thanks in advance

: Version 9.5 without SPs. 

Regards ,Joby

{

Fri, 19 Dec 2014 09:13:57 Sending policy request to core server.
!!!!!!--------removed user and computer informations-------!!!!!
Fri, 19 Dec 2014 09:13:58 Web request returned 0 The web request was successful.
Fri, 19 Dec 2014 09:13:58 Has Policy downloaded from core
Fri, 19 Dec 2014 09:14:58 LdcDbMutex::Lock mutex lock timeout
Fri, 19 Dec 2014 09:15:58 LdcDbMutex::Lock mutex lock timeout
Fri, 19 Dec 2014 09:15:58 Failed to persist the inventory id to the managed node database.
Fri, 19 Dec 2014 09:15:58 In WriteServerResponse
Fri, 19 Dec 2014 09:15:58 Out WriteServerResponse
Fri, 19 Dec 2014 09:15:58 Policy request has been processed.
Fri, 19 Dec 2014 09:15:58 Checking for rescheduled policies
Fri, 19 Dec 2014 09:16:58 LdcDbMutex::Lock mutex lock timeout
Fri, 19 Dec 2014 09:16:58 [STOP] Policy Synchronization application complete.

Fri, 19 Dec 2014 09:42:49 Checking if we have a valid local database file before attemp to start policy.sync.exe
Fri, 19 Dec 2014 09:42:49 [START] Policy synchronization started.
Fri, 19 Dec 2014 09:43:49 LdcDbMutex::Lock mutex lock timeout
Fri, 19 Dec 2014 09:43:49 Error: failed FixLastPolicyResponseAndClientOperations.

!!!!!!--------removed user and computer informations-------!!!!!

Mon, 05 Jan 2015 10:19:06 Checking if we have a valid local database file before attemp to start policy.sync.exe
Mon, 05 Jan 2015 10:19:06 Do not start policy synchronization yet since the local database file size is zero

}

Hi,

I have a client, which one will be reinstalled (OSD). The client is content of a scope. For this scope (query) there are several policies running. The client, which I want to reinstall has executed all policy successful (before the reinstallation ).

Will this client pull this policies again, after the installation of the client completed? Or will the client never reexecute the task (because was successful one time) until I reschedule the task? (Policy is set to run once)

I'm running LDMS 9.6

Regards,

I have been testing out some of the new features of 9.6 SP1 and was looking at the new Task Visibility Stages specifically the Download stage where is shows the download percentage in the progress bar.  Send Detailed Task Status is enabled in our agent settings but what I am seeing is that the percentage that is reported back doesn't appear to be correct.  As a test I built an Office 2013 executable distribution package and added all of the office files as additional files after selecting the setup.exe as the primary file.  After scheduling the task and doing a push to the machine the percentage immediately started at 43% when the stage changed to Downloading.  Within a few seconds the percentage was at 100% but was still downloading files.  Since I knew it wasn't possible for it to be finished downloading all of the files that quick I looked in the sdmcache folder on the client to see the size of the Office 2013 folder that was being downloaded and it was only at 135 MB which isn't anywhere near 100%.  It almost makes me wonder if the percentage is only based on the primary file and does not take into account the additional files that need to be downloaded.

I realize that calculating time remaining and percent completed is never that accurate but is anyone else seeing similar things?

I cannot find a preferredserver.dat on any agents as documented on the HELP file.

The only details i can find are in reference to what server was used "CurrentDownloads.log" which shows incorrect server files be downloaded from.