Problem

User can not deploy a task because the download fails. In the tasklockfile you can find that the files with the extension .config can not be found.

Cause

Some files are not served off of IIS because they are typically part of the building blocks of the website itself.
You can find a list of them tied up in the IIS management setting "Request Filtering".

Solution

1. Open Internet Information Services (IIS) Manager on the Core Server.
2. Click on the LANDESK website under Sites or Default Web Site
3. Open 'Request Filtering' in the center panel.
4. Inside the 'Request Filtering' in the 'File Name Extensions' tab, right-click the file extensions that is failing to download (.config) and select 'Remove...' option.
5. Start 'command prompt' tool (cmd) and enter following command to restart IIS services: IISRESET

Issue

• You have created a new software distribution task in the Ivanti EPM console.
• The software package is hosted in a web share on your core server and contains one or several files with no extension.
• Your distribution policy allows the target computers to only download the install file(s) through the HTTP protocol.

When run on the client computers, the distribution task fails with error code:

processing of package is complete, result -1918107543 (0x8dac0069 - code 105)

Additionally the SDClient_taskID.log file shows the following entries:

Fri, 15 Jan 2016 09:15:52 DownloadFileFromPeer: DOWNLOAD_ERROR_GENERAL_FAILURE

Fri, 15 Jan 2016 09:18:28 Download failed file not found at source(1): http://core-server/depository/file_name1

Fri, 15 Jan 2016 09:18:28 Download Error: err=11, path=http://core-server/depository/file_name1

Fri, 15 Jan 2016 09:18:29 DownloadFileFromPeer: DOWNLOAD_ERROR_GENERAL_FAILURE

Fri, 15 Jan 2016 09:18:29 Download failed file not found at source(1): http://core-server/depository/file_name2

Fri, 15 Jan 2016 09:18:29 Download Error: err=11, path=http://core-server/depository/file_name2

Cause

The software distribution task fails because the target computers can't find these files on the core server even if proper permissions and path have been configured.

Actually, this issue occurs because, by default, IIS server doesn't know how to handle files with no extension.

As a result, when a client computer queries the core server to download these files,IIS replies with a "404 - NOT FOUND"

The same error is displayed if you open a web browser on one of the target computers and try to manually download these files.

Resolution

Before running the task, you need to configure IIS so that it knows how to serve files with no extension.

1. Log into your core server and go to the IIS server view
2. Select "Default Web Site" and then click "MIME types".
   
3. In the MIME types screen, click "Add"
   
4. Type "." as file name extension and "application/octet-stream" in the MIME type field. Select OK to save.
   
5. Restart IIS

Now the distribution task should be successful with target computers being able to download files with no extension.

Has anyone been able to create a distribution package for Skype 2016? Looking for some pointers because I am having a hard time.

Preferred Servers can be enabled in the Ivanti EPM Console.  It now includes the ability to authenticate to a UNC share or a web share using the credentials configured for the preferred package server.  That way, when the share is accessed by an Agent workstation's Local System account, it will be able to access the share using the credentials specified instead of simply trying to authenticate as Local System.

1. In the Ivanti EPM Console, click Tools | Distribution | Content Replication/Preferred Servers.
2. Click Add to add a new server, or click an existing entry and click Edit.
3. Enter the server information.
4. Click Test credentials to make sure the credentials you provided work.
   
   (Optional) If you want to use IP address ranges to limit which clients you want using this server as a preferred server, click on "IP address ranges" enter the IP addresses and click Add.
   
   
5. If you will be writing files to this preferred server as well as reading files from it (for capturing images during provisioning for example), enter credentials with read and modify permissions in the "Write" section of the template.
6. Click Save.

For example, if the packages on the core server can be found here:

CoreServer\packages\

Then on the package server called PackageServer, they should be found here:

PackageServer\packages\

For web it is similar:

For how to set up a web share

http://community.landesk.com/support/docs/DOC-6986

EN

Hello professionals! We have a little problem with the replication. We have over 100 locations and each location has a server. The replication runs overnight and seems to be clean, all green and at 100%, but appearances are deceptive. Some software packages report "105 Download Fail". I compared the packages and found no difference. Number of files, time, HASH values match. Time differs sometimes, but that's only because the replication ran later. When I delete the software folder and replicate it, everything works fine. In addition, there is a problem that some software packages have not been changed for months and out of the blue download no longer works. The procedure is the same with the problem only I still reset the HASH values. With 100 servers, it's very costly. Did you have a problem like that? MfG

DE

Hallo Profis! Wir haben ein kleines Problem bei der Replikation. Wir haben über 100 Standorte und jeder Standort hat einen Server. Die Replikation läuft über Nacht und scheint sauber zu sein, alles grün und bei 100%, aber der Schein trügt. Manche Software Pakete melden „105 Download Fail“. Ich habe die Pakete verglichen und habe kein Unterschied gefunden. Anzahl der Dateien, Zeit, HASH Werte stimmen überein. Die Zeit weicht manchmal ab, aber das ist nur, weil die Replikation später gelaufen ist. Wenn ich die Software Ordner lösche und neu Repliziere, dann funktioniert alles wunderbar. Zusätzlich dazu kommt ein Problem, dass manche Software Pakete wurden seit Monaten nicht geändert und aus heiteren Himmel funktioniert Download nicht mehr. Vorgehensweise ist bei dem Problem das gleiche nur setze ich noch die HASH Werte zurück. Bei 100 Servern ist es sehr aufwendig. Hattet Ihr so ein Problem? MfG

SDMCACHE ist auf der gleicher Partition#

SDMCACHE is on the same partition

There is no provision to install a package as the current user for MacOS packages. Does anyone know of a workaround? Packages like Microsoft Office 365 Teams can't be installed as root or else their internal auto-update feature stops working.

Thanks,

Charles

We are looking to automated software installs such that adding a user to an ad group installs software on their computer (not every computer they log into).  Long story short, we decided to go with a template with the software install steps which all have 'if' statements around user ad group membership (thanks to some scripting).  However, every time we run the template, it reinstalls the software whether its there or not.  So my question:

Is there a way to make LD check to see if something is installed before executing a package?  I would hate to script this for all packages.

Sorry for the noob question; I'm an SCCM guy and this stuff is all native functionality in that tool so I am assuming there is native functionality in this one????

• Introduction
• Agent State: What It Does And How To Enable It
• Troubleshooting Agent State Issues

Introduction

Ivanti EPM 2018.1 introduced a new addition to Self-Electing Subnet Services - Agent State. This changes the how device availability is determined when targeting devices in a scheduled task . Self-Electing Subnet Services will need to be enabled alongside at least 1 device on the subnet that has Agent State enabled in the Client Connectivity Agent Settings for managed devices:

If you want to utilize Agent State, make sure that the network is enabled and the Agent State service is enabled in the agent settings on at least one of the devices on that network. The network also needs to be shown as enabled in the SESS - Agent State tool.

Agent State: What It Does And How To Enable It

When Agent State based targeting is enabled on the core, devices are no longer pinged from the core to see if the agent responds when a scheduled task is started. Instead, the core does a lookup in the database to view the value of the inventory value "Agent State - Available":

Even though this is a value that is viewable in the devices inventory, this entry is not sent up with an inventory scan. This information is queried by the Agent State rep on that devices network. The Agent State representative on that network receives information from EPM managed devices on that network and then relays that information to the core server (and then is updated in the database). The Agent State inventory menu will only show up on machines that are running an agent that is on version 2017.3+.

The 3 different available status of an agent's state are:

0 - Offline and not available:

If a device is listed as Offline, the core will not attempt to push the scheduled task on the machine. It will immediately set the task to "Policy has been made available" and wait for the machine to come online and perform a policy sync.

1 - Online and available:

If a device is listed as Online, the core will immediately begin the scheduled task process on the device. Since the core knows that the device is available, it doesn't need to ping the device from the core and it can immediately start the scheduled task process.

Unknown - Status of the agent is unknown.

If the status is Unknown, the scheduler will revert to the old method of determining device availability (pinging the machine and waiting for a response). This status indicates that there may be an issue with the Agent State representative on the network. If many of your devices are showing as "Unknown" you should view the status of agent state in the Self Electing Subnet Services window to see if the network has agent state enabled.

Troubleshooting Agent State Issues

While Agent State is a great addition to EPM (it lowers the time it takes to start a task on a group of devices by roughly 3-7 seconds per device!) that also means that there are network considerations that need to be made. Agent state uses multicast to communicate with devices on the network. If multicast is being filtered or is not working correctly, you will run into issues. Some common issues that have occurred are:

Devices in a scheduled task are not able to be pushed and revert to "Policy has been made available".

If you are receiving that message for your devices when starting a task, spot check the "Agent State - Available" value on some devices. If they are showing as "0", verify the status of the network in the Self Electing Subnet Services window. If it is disabled, enable it by right-clicking the network and selecting "Enable". Refresh the window and wait a few minutes for a device to be elected as the Agent State representative and the "Current State" to be enabled.

Once is shows as enabled and a device is successfully elected, check the availability status in the inventory. When it shows as "Available - 1", push the task again to the machine and verify that it is working.

Machines are showing that they are offline ("Available" - 0) but they are online and can be pinged from the core.

If the machine is not showing as available in inventory but you are able to ping the machine from the core, there may be an issue with the Agent State representative or multicast communication on that network. Ping the DNS name of the machine and make sure that the IP that is responding is the same one that is listed in inventory. If the IP is accurate, check for errors in the C:\ProgramData\LANDesk\Log\TMCSVC.log on the Agent State representative. If you see message similar to the errors below, multicast is most likely being filtered on that network and causing our problems with Agent State:

To test the functionality of multicast, use either of the 2 following testing methods:

Method One:

Create a policy-supported push task and start it on a machine that is having issues. I use the package "Clear Preferred Servers" or "Remove Streamed Documents" since it has a low overhead and doesn't impact the agent device or network as much. From the device, run a policy sync to pull the task down onto the test device. Once that one task is successfully pulled down to a machine, duplicate the previous task, set the task to only allow "Peer to Peer Download" by using an agent setting that only allows peer download:

Distribution and Patch Setting:

Scheduled Task setting:

Since you successfully ran that task on a machine on that subnet, clients "should" be able to use multicast and successfully share resources locally to copy the file(s) from the machine that already downloaded and ran the software distribution package. Machines that are unable to communicate with multicast will error out and not to able to run that task.

Method Two:

Use the steps in the following document to test multicast functionality on that network: Troubleshooting multicast communication with MulticastNetworkTest.exe

Conclusion:

Regardless of what you use to test multicast functionality, you will need to work internally with your network team to resolve multicast issues that are discovered.

Troubleshooting multicast communication with MulticastNetworkTest.exe

OVERVIEW:

EPM can be configured to use multicast in many different ways.  The most obvious are distributing files during patching, software distribution, OS Provisioning, and Agent State communication.  Multicast packets are also used for Peer to Peer or Preferred Server downloads.  The nature of Multicast packets are such that they can easily be lost in a 'noisy' network environment and this can impact the successful implementation of LANDesk multicast functionality.  This utility will help you test multicast communication and determine if High Priority multicast packets are being lost in transit.

More information about Peer to Peer downloading can be found here:

STEP BY STEP:

Option 1:

You can test multicast functionality from one device to another, or from one device to multiple others.  This is a helpful test when peer to peer downloading is not working as expected.

1. Download the attached MulticastNetworkTest utility and unzip it
2. Place the utility in the ldclient folder on two or more test devices; one will be the sender and the others will be listeners
3. Stop the LANDesk Targeted Multicast service on both devices
4. On the listener, run "MulticastnetworkTest.exe listener” from an admin command prompt.
5. On the sender, run “MulticastnetworkTest.exe sender”.  It will look like this:
   
6. The sender will broadcast 10000 packets, 500 of which will be high priority. The listener will record receipt of these packets and the numbers should look like this:
   
   
   

As you can see in this example the listener received all 500 high priority packets although it dropped a few of the low priority.  That is considered normal.  If you find that High Priority packets are being dropped, that indicates a network issue that must be addressed before Multicast features within LDMS can work reliably.

Option 2:

You can cause one device to send out multicast packets and then listen to see if it receives back the same packet.  This is more of a general test.

1. Download the attached MulticastNetworkTest utility and unzip it
2. Place the utility in the ldclient folder on a test device
3. Stop the LANDesk Targeted Multicast service
4. Run MulticastNetworkTest.exe with no arguments

In this mode it will send out a multicast packet once per second. It will also print out a line for each of these messages it receives.  It includes a count in the message, so you can see if any are missed.  So if you run it on one machine, then you should see that it receives a message from itself once per second.  If you run it on 3 machines, you should see that each machine receives the 3 messages from each machine every second.

Hello,

Does anyone have any experience or have an idea on how to properly package and distribute Eclipse IDE for Java Devs? Link: Eclipse Packages | The Eclipse Foundation - home to a global community, the Eclipse IDE, Jakarta EE and over 350 open so… I've looked and looked and it doesn't seem like they have an msi or a way to perform silent installs.

Thanks

Have been using Endpoint Manager 2017.3.3 for a few weeks now with no issues until today when we are now unable to work with 'Distribution Packages'. When  we choose 'new -> windows -> exe' (or anything else) it returns "The remote server returned an error: (500) Internal Server Error", hitting ok clears the message and the executable properties window appears but if we then try to change the primary field option the same error then appears.

Likewise when trying to check the properties of an existing package this error appears.

Pasting the web path into browser results in this;

Have tried using the console directly on the server but get the same results. Looking about the community it would appear it is likely something to do with IIS permissions on the package share.

Within IIS the share details appear and can be accessed.

Being quite new to this any assistance would be appreciated.

To deploy software to PCs within my environment I have always used the LANDESK Management Console GUI to schedule a task for any software listed under "Distribution Packages" such as below image. This requires logging into the server, scheduling a distribution package and then choosing the PC.

I am looking for a way to schedule a task from command line, powershell, vbs, etc from a workstation that will reach out to the server and create a scheduled task to start the install for audit

My end goal is so that IT employee who is imaging a PC can choose which software to install post deployment via checkboxes in a homemade gui. This will allow the deployment to be more agile than just having the apps listed in my Operating System Provisioning Template or needing to login to the server GUI to schedule. I would like to be able to walk through the following steps:

1. Create a Bare Metal Object in LANDESK Management GUI on the server
2. Schedule Operating System Provisioning through the GUI on the server
3. Launch PC via PXE and Deploy OS from Template scheduled in Step 2
4. PC being Provisioned will prompt user to select software to install via a home made script*/gui (all client side PC)
   1. * This script will then send the needed commands back to the LANDESK server (or web gateway?) to schedule the tasks to start individual distribution packages. The LANDESK Management GUI will show the tasks just as if they were scheduled from the LANDESK Management Console itself.

All in all I am trying to replicate something very similar to Microsoft Deployment Toolkit which allows you to specify which apps you want to install during a deployment

Bonjour,

Je n'arrive pas à déployer un paquet pour l'installation de Microsoft Visio 2003.

Voici l’erreur.

Hasherize: failed to calculate hash for file

HasherizeSha256: Failed to calculate the hash for file

J'ai déjà fait une réinitialisation des hash du paquet.

Merci

Hi there

Pushing tasks has always been OK but since last week when I send a task, whether individually or as part of a task sequence, it has started to fail.

Or more accurately when finished it says Stage = Completed, Status = Failed.

However, the task appears to be successful, the software is installed and all appears fine.

I wondered why this is happening and how to fix it so a successful task appears as successful like it used to?

Cheers

Phil

Hiya

I am wanting to installing Microsoft Teams as part of my OS deployment task sequence.

There are install files as an EXE or an MSI

The EXE installs only to the local user app data folder.

The MSI will install it for each user when they log in for the first time so it is this i want to use.

It installs successfully during the build but when I then log in as a user it doesn't appear to run and install.

Has anyone successfully installed it so it appears for users when they log into their device?

Cheers

Phil

I'm running on 2017.3 SU3.

I have a software package that deploys from the portal. 1300 total users, ~300 successful so far, and ~20 failed.

Most of the failures have been from the user clicking on the package in the portal, then the portal never downloads the package or progressing. It just sits at 0% downloading and does nothing.

I don't see any errors in the policy sync logs. (Plus it's already in the portal so I think policysync has done it's job.)

There is no sdclient task log.

I do see the .xml and .stat file for the task in c:\ProgramData\LANDesk\Policies

Rebooting doesn't help.

What are my next steps? I hate to reinstall the agent as that is a pain.

We are looking to configure Ivanti replication for a large number of sites over 500.

How many replication tasks run at  once?

Is this configurable?

What is the limit for how many replicators can use the same source?

Problem:

During Inventory scan or Software Distribution task LDAPWhoami.exe triggers smartcard reader dialog box (on the devices with smartcard reader installed).

Example 1:

Example 2:

Cause:

Changes implemented in the product in version EPM 2017.3 within ldapinfo.dll code (used by ldapwhoami.exe). Ldapinfo.dll is part of the agent package so the issue is client-oriented.

Solution/Workaround:

Replace ldapinfo.dll with the file from a previous version of EPM (attached to this document) on affected devices. If you encounter this issue in your environment, please raise a case with Ivanti.

The engineering team is currently working on fixing this issue (DSI 232949). If you have any additional questions, please contact Ivanti Support.

Hello,

I have created a scope called "OS reinstall" and I setup certain updates to be autofixed for all devices in this scope (global patch settings - do not autofix). This scope selects systems based on device group called "OS reinstall". Another words - I move my systems manually to group "OS reinstall" and I expect these systems to autofix all patches for "OS reinstall" scope. Problem is that for some reason after I move system to group this system is still not able to apply patches - it acts like these patches do not have "Autofix" enabled. Do I need to do something like "wake up agent" or "update agent settings" so agent knows it is inside "OS reinstall" scope?

Issue

Sometimes the drive can run out of space quickly due to patching.  This guide will walk you through altering the retention of files within the SDMCache Folder

Resolution

Within your Agent Settings tool locate the Client Connectivity options. Go to the Download Tab and alter the Number of days files stay in cache to whatever value you would like.