It sounds like sdclienthandler. Does this happen with different Windows 10 versions? Are you installing a "provisioning" agent an agent with a distribution and patch setting configured to never run policy sync or vulscan during provisioning? I recommend opening a ticket with Ivanti Support to troubleshoot this :. So I do the following and works Distribute software. I have what I call "Master Templates" and my tech's use this template. We are trying to develop that base Master Template that we can add on to for specific needs.
All the apps but Adobe DC install properly in this base template. I've verified the Adobe DC distribution package works to deploy Adobe DC via a policy-supported push, but for some reason the OS provisioning doesn't run the installer. I've made sure there aren't other active installs and that the PC rebooted before trying to install Adobe, but it still doesn't start the installer.
Seems like you are on to something. Looking at the ldprovision log seems to show that the sdclienthandler. I'll try creating a provisioning agent that delays policy sync and vulscan to see if that makes a difference.
Since the other apps were installing without issue i figured that wasn't the problem. I'll open a ticket after this test if the issue persists. Seems strange to be that consistent on just one app. Most of the time its more random as the local scheduler runs the other tasks with randomizing by default.
If you just deploy Abobe DC as single step in a provisioning template does it work? Rather than a provisioning agent the other option is install your normal agent then use the change setting action to change the distribution and patch setting to one with policy and vulscan off.
Then you can set this back towards the end of your template to your prod setting. The sdclient logs show an error stating that ldrunner. When a vulnerability is repaired as a policy LANDesk will automatically create a software distribution package out of the repair task. Right click on the software distribution package and select the option to Reset package hash. There is no message dialog box that will pop up, but the hash has been cleared.
Restarting the repair task at this point should result in a success. To resolve this, create a new repair task that utilizes the Policy method. Skip to Main Content. Home All Products Forum Groups. Getting Started. If there is a match the file will be retrieved. A hash value will only be contained on the preferred server if the files were replicated over via Ivanti EPM Content Replication.
If content Replication was not used, the downloader will download the entire file, calculate the hash and compare the hash it has to the hash found in the database.
When selecting the source network option, the downloader will be allowed to traverse your network back to the network path specified in your package primary and additional files in efforts to download the file. In this event, the hash is written to the Ivanti EPM database and will not be pulled from a preferred server or peer. More information related to the use of this tool can be found in the following location:.
How to use PEDownloader. In order for the targeted device to be able to perform a file download, it must first gather information from the core to know what information is contained in the package.
The client policy xml file CP. For more detailed information on how the core publishes information to IIS and how clients retrieve this information from IIS please reference the following articles:.
How to troubleshoot Policy Sync. Skip to Main Content. Home All Products Forum Groups. Getting Started. Expand search. Log in Account Management. Ask a Question. Applies to. Software Distribution. Created Date. Apr 14, PM.
0コメント