This article covers one of the reasons you might be facing this message. If you want to have a detailed troubleshooting guidance, please read the following article:How to troubleshoot tasks hung with a status of "Client has initiated asynchronous policy execution"

Environment

This message is present in LANDESK Management Suite 9.6    [26.11.14]

Description

When trying to deploy a package, whatever Task settings you use, you might see this message:

Client has initiated asynchronous policy execution

Cause(s)

This message tells you that the Client is trying to pull a policy from the Core Server and does not manage to get it as it looks to get stuck in a loop.

This highlights a communication issue between them.

It can be that:

• The IP Address has changed and has not bee updated which leads to a wrong identification process during Policysync
• The Common Base Agent is not installed / loaded and does not get contacted by the Core
• The Client has the wrong information in its registry that points to another Core Server

There might be other issues that will be reported if recognized.

Resolution

As explained earlier, we have to check these settings in order to ensure our Core and Client are ready not only to see each other, but to exchange data.

To do so, follow the next steps:

I.    Common Base Agent

From the Core Server

Right click on one of the client machine that has the issue and click "Properties"

What is important here is the Common Base Agent status.

If the status is: Not loaded

• You will have to uninstall properly the agent on your device by using the /forceclean parameter as indicated in this article: How to uninstall the LANDesk Agent
• Then delete the device from your Core Server inventory. If you want to be sure that the device is not anymore in the database, you can follow this article: Pending unmanaged client deployments - Devices are deleted but come back when refreshing
• After the device is deleted, double check the settings of your Agent configuration, then rebuild your agents, and schedule a deployment using our Unmanaged Device Discovery feature.
• Once the agent is properly and successfully deployed, check again the Common Base Agent status.

If the status is: Loaded

Go to the next step.

II.  Miniscan

Take note of your Client IP address, in our example:

192.168.1.63

Then go on your Client machine and check your actual IP address:

If the IP address is not the same as the one you had earlier on the Console, go to:

C:\Program Files (x86)\LANDesk\LDClient

And execute as an admin the following executable:

MINISCAN.exe

This will verify and update your IP address to the Core Server.

    This feature is automatically launched when modifying the IP address but an issue has been found and already fixed in the Service Pack 1 for LANDESK Management Suite 9.6 which has a soft release target of Mid to End December

Once this is done and you can see that your device now has the proper inventory data, you will be able able to recreate the scheduled task, target your device and start it:

If you see that your task remains in the "Task Queued at Client for Execution" status after that, please read the following article: How to resolve "Task Queued at Client for Execution"

I ran into an issue with a distribution task that had me a bit stumped.

The task was a simple vbscript to perform some custom developed application upgrades. I created a custom vulnerability definition that scanned for a specific file and version on the client computers. I then used the "create query for affected computers" option to establish the target for the software package and set the scheduled time for the task to kick off at a predetermined time.

All the required steps went according to plan except when the task launched at the specified time, every single client reported "the client has initiated an asynchronous policy execution". Then sat there and did nothing. After waiting nearly 45 minutes for the task to execute, I removed all the targets, then manually dropped them back in from the console and relaunched the task. They immediately started downloading and installing the software package and upgraded normally.

So my question is, why did this task do this and how do I prevent it in the future? Many of our software repairs for custom software require us to roll patches within a specified time window and I can't afford to babysit a task every time we need to update it.

Hi All,

I'm new to the LanDesk tool. I have been trying to resolve package deployment failures but no luck.

We deployed VC++ Runtime 2010 on a test pc where it already has the higher version of VC++ (2012) installed on it and hence the deployment failed.

After this, i tried to deploy other packages like Adobe, Office but the installation never gets triggered on the client PC. When i check the scheduled task for these packages, it shows the status as "Active", Result : "client has initiated asynchronous policy execution" and the Return Code "1354".

The last few lines of the sdclient.log file has these entries:

Wed, 17 Sep 2014 09:53:58 PostInstallInventoryScan: Successfully created inventory scanner task.

Wed, 17 Sep 2014 09:53:58 Sending task status, cmd line -coreandip=coreserver -taskid=198 -retcode=-1918091262 -complete "-log=C:\Program Files (x86)\LANDesk\LDClient\data\sdclient_task198.log" -pkgid=177

Wed, 17 Sep 2014 12:22:09

RunAppMain: command Line :

Wed, 17 Sep 2014 12:22:09

Wed, 17 Sep 2014 12:22:09 Task is not required to send status

Can anyone able to provide any advice on what can be done to overcome this issue?

Thanks,

Gopal

Had a custom script that ran without issue on 9.5 sp1, updated to 9.6 and now Fails.

The scheduled Task results are:

Status:Failed

Result:An invalid parameter was passed

Return Code:16408

The script is simple, it copies files and overwrites existing.

Contents:

[JOBPARAM]

STEPS=1

[MACHINES]

REMEXEC0=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="\\VSIM-LANDESK\ldlogon\Packages\XUpdate\PIN\PIN_ACW-TXT.exe" /dest="C:\XUpdate\PIN_ACW-TXT.exe" /lan=90 /wan=60

REMEXEC1=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="\\VSIM-LANDESK\ldlogon\Packages\XUpdate\PIN\PIN_CDS-TXT.exe" /dest="C:\XUpdate\PIN_CDS-TXT.exe" /lan=90 /wan=60

REMEXEC2=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="\\VSIM-LANDESK\ldlogon\Packages\XUpdate\PIN\PIN_CDL-TXT.exe" /dest="C:\XUpdate\PIN_CDL-TXT.exe" /lan=90 /wan=60

REMEXEC3=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="\\VSIM-LANDESK\ldlogon\Packages\XUpdate\PIN\PIN_CDG-TXT.exe" /dest="C:\XUpdate\PIN_CDG-TXT.exe" /lan=90 /wan=60

REMEXEC4=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="\\VSIM-LANDESK\ldlogon\Packages\XUpdate\PIN\PIN_DDD-TXT.exe" /dest="C:\XUpdate\PIN_DDD-TXT.exe" /lan=90 /wan=60

REMEXEC5=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="\\VSIM-LANDESK\ldlogon\Packages\XUpdate\PIN\PIN_DDL-TXT.exe" /dest="C:\XUpdate\PIN_DDL-TXT.exe" /lan=90 /wan=60

REMEXEC6=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="\\VSIM-LANDESK\ldlogon\Packages\XUpdate\PIN\PIN_FLL-TXT.exe" /dest="C:\XUpdate\PIN_FLL-TXT.exe" /lan=90 /wan=60

REMEXEC7=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="\\VSIM-LANDESK\ldlogon\Packages\XUpdate\PIN\PIN_IRL-TXT.exe" /dest="C:\XUpdate\PIN_IRL-TXT.exe" /lan=90 /wan=60

REMEXEC8=<qt/>%LDMS_CLIENT_DIR%\sdclient.exe<qt/> /f /o /p="\\VSIM-LANDESK\ldlogon\Packages\XUpdate\PIN\PIN_LOL-TXT.exe" /dest="C:\XUpdate\PIN_LOL-TXT.exe" /lan=90 /wan=60

Please help and thanks in advance.

This video tutorial will show the basics of creating an executable distribution package, in this case Firefox.

If you have found this video helpful please like of bookmark.

I'm trying to deploy Symantec SEP 12 to out users, and I am getting the following error on a few of the machines:

"You were not connected because a duplicate name exists on the network.  Go to System in Control Panel to change the computer name and try again/"

I assure you, there is NOT a duplicate computer name on the network.  This is an AD domain, so you can't have duplicate computer names.

Could this be caused by someone cloning an OS with the LD Agent already installed, and not resetting the specific hardware ID in the registry?

Was curious on how to clear a selection in Portal Manager once you choose a background and want to go back to default.  Also if there is a way to not have any text involved in the name. If you clear it uses a default text also would be nice if instead of text it could be an image.

Hi everyone,

We encountered a problem while using Powershell Packages.

We set all our computers with an executionpolicy to Unrestricted.

Nonetheless when we use Landesk to execute a powershell script through a Powershell Package at the end of it the execution policy is set back to Restricted.

Our computers are Windows 7 SP1 x64 enterpise Edition and we are using Landesk 9.5 SP1

Does anyone encountered this issue? Do you know is Landesk SP2 or SP3 might fix this?

Best regards,

Charles.

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)

Issue:

How to change the time that files remain in the SDMCACHE directory.

The SDMCACHE directory is where LANDesk products store files that were downloaded during Software Distribution or Patching tasks. By default, this folder is purged every 7 days on normal agents and every 14 days on subnet representative agents.

Solution:

1. Change the following registry values on the client:

32bit

HKLM\Software\Intel\LANDesk\LDWM\Distribution\Multicast\Discard Period

HKLM\Software\Intel\LANDesk\LDWM\Distribution\Multicast\Subnet Rep Discard Period

64bit

HKLM\Software\Wow6432Node\Intel\LANDesk\LDWM\Distribution\Multicast\Discard Period

HKLM\Software\Wow6432Node\Intel\LANDesk\LDWM\Distribution\Multicast\Subnet Rep Discard Period

Defaullt Data for Discard Period is set to (604800) in seconds = 7 days

Defaullt Data for Subnet Rep Discard Period is set to (1209600) in seconds = 14 days

Increase the data value in seconds.

Note: When updating the registry, this will update the *.info files located in ldcacheinfo directory for the discard date.

2. Restart the LANDesk Targeted Multicast service on the client.

Note: This does not change the time for files that are already in the SDMCACHE directory. To change the time for existing files in Management Suite 9.0 SP2 or higher, delete the LDCACHEINFO subfolder from each directory containing files needing the longer discard period before restarting the service.

To verify that the files have been cached the intended amount of time, run "TMCsvc.exe /F|more" from a command prompt in the \LDClient directory. This command will output cached files "time to live" values to screen.

Unexpected error in custom script source.  See agent log for details for two MS patches its affecting mos of systems ..i need help ?

This is probably a simple question but I cannot find the answer anywhere. We're moving to 9.6 from 9.0, and we use push tasks. Here in 9.6 testing, everything defaults to a policy (In the scheduled task properties, under Task Settings). Is there a settings to change to make the default a push?

Thanks in advance.

Explanation

A new feature we have added to LDMS 9.6 SP1 is the Package Relationships tool to allow you to quickly view all the relationships that Packages and Bundles have to other Bundles, Packages, and Tasks.

Overview

From this new window you can see the following information, in this case I selected a bundle named Bundle2:

1. Parent Bundle, you can see here the selected bundle is inside of "Bundle1."
2. Child Bundle, "Bundle3" is located inside of the selected bundle.
3. Child Packages, The LANDESK.com Link Package shown above is inside of the selected bundle, however the package located in "Bundle3" does not show in this view as it is not directly associated to the selected bundle.
4. Tasks, The last two items show Tasks that will deploy this bundle "Bundle1" and "Bundle2" are both scheduled and ready for deployment.

Summary

This new Relationship utility will help you to quickly resolve any relationship issues that arise when try to delete packages or bundles or simply trying to organize them effectively.

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.