We are currently using UNC paths for all of our software packages. We have setup the permissions on the UNC paths so that only the client systems have access to that particular folder. This is to help protect our software repos from unauthorized access. I would like to move to using HTTPS so that I can get around firewalls to clients that are not on our home network. Is there a way to use HTTPS to distribute software that requires the system to authenticate?
Best known methods are only intended to be a starting point while finding what works best in any given environment. This guide will assist Ivanti Administrators with creating a software distribution package for Microsoft Office 365 Click-to-Run and deploying it with Ivanti EPM. When distributing Microsoft Office to multiple computers it is important to obtain the volume license for that product version. This document does not make reference to volume licensing. For more information on Microsoft Volume licensing please go direct with Microsoft.
Installing Office 365 Click-to-Run
Download Office Deployment Tool (ODT) to a Network Share
There are (2) Deployment tools available. If you are managing Office 2016 product please use the 2016 version. For this example, the 2013 version was used.
The server this Network share is on does not have to be your Ivanti EPM Core server as long it has the correct NTFS and Share permissions. If you elect to use a server other than your Ivanti EPM Core you will need to ensure you have that server configured as an Ivanti EPM Preferred Server (How to configure a Preferred Package Server)
For this example, the Core's LDLogon share was used and I created an Office sub-folder.
Microsoft now offers a Configuration XML Editor which presents you with a GUI assisting in the creation of the xml file.
Below is an example of what the Configuration file will look. You can modify the attributes to your liking through the Configuration XML Editor tool or by manually editing the file.
may be someone else out there had the same issue than me and knows how to solve it. I`m deploying Win10 upgrade from Win7 to clients via UEM. That normally works fine, but now there`s a client which don`t wants to upgrade. The Job starts and the download of the ISO file works fine, but when the Installation starts there`s Always this errorcode:.
this is a part of the log for that Job in Ivanti UEM:
Tue, 07 Aug 2018 09:49:12 Processing generic executable Tue, 07 Aug 2018 10:00:31 Launched application 'C:\Program Files (x86)\LANDesk\LDClient\sdmcache\Softwareverteilung\Microsoft\Win10upgr\deWin10ProX64\setup.exe'('/auto upgrade /noreboot /quiet') result -1047526944 Tue, 07 Aug 2018 10:00:31 Installation result 8DB501E0 Tue, 07 Aug 2018 10:00:31 RunPackageInstall: stop on returncode=8db501e0 of package=W10Ver1803upgr Tue, 07 Aug 2018 10:00:31 processing of package is complete, result -1917517344 (0x8db501e0 - code 480)
The Problem is I can`t find anything about errorcode 8db501e0, what does it mean?
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.
I'll be the first to admit I have no idea what I'm doing when it comes to Macs so if you can help you may need to use small words
I've got a couple of Macs in my environment and have been able to package and deploy various applications without any issues.
Adobe Creative Cloud on the other hand seems to be a different beast entirely, as much as it says it's a .pkg file my windows server sees it as a folder as well as Ivanti.
When attempting to create a package I get the following error:
The package is indeed available at that address if you manually navigate to it. I'm presuming it's just something simple I'm missing but all the other forum posts regarding this package that I have found seem to indicate that the package should be detected like any other package and using the Adobe Packager, which is what I used, is all that is required. If I run the installer manually on a Mac all works as expected.
This was added to allow software distribution to not be beholden to the maintenance window on the agent. For Patch tasks, the "Ignore Maintenance Agent Settings" from the main properties window to the new "Overrides" section.
Solution:
If you want your tasks to respect the maintenance windows of the devices Patch and Compliance agent setting, make sure that you uncheck the "Ignore Maintenance Agent Settings" on your existing and new scheduled tasks.
In some high secure environments, users can encounter an issue with PowerShell scripts distribution via Ivanti Endpoint Manager. This issue occurs mainly for Windows 10 build 1709. Error message in log file (sdclient_task{taskID}.log - C:\Program Files (x86)\LANDesk\LDClient\Data \ C:\Program Files\LANDesk\LDClient\Data):
Thu, 15 Mar 2018 11:39:58 PowerShell file Client Thread
Thu, 15 Mar 2018 11:39:58 Powershell install value is: [0]
Thu, 15 Mar 2018 11:39:58 Powershell version is: []
Thu, 15 Mar 2018 11:39:58 PowerShell is not installed in the client system
I have setup a preferred server with a share same name as share on the source
All the credential tests worked during setup of Preferred Server, Sources,
When I select "Start content replication now" i get "Content Replication" "Requesting" then it changes to "Content Replication" "Failed" "No response from agent on target device"
Hardware and Software Scans work
Remote control works
Scheduled tasks to send update to device works.
I wanted to put this in "Online Support Discussion Group" but I don't have access.
We have configured a distribution package to deploy office applications on some Apple IOS Iphone.
Now when launching the task, we would like these applications to be grouped together in a single folder on the Iphone screen. The task must therefore install applications on the mobile and create a folder and add icons in the new folder.
Is it possible?
See attached file for screenshot (Landesk-Folder-icon.docx)
Use Windows package actions to perform custom operations during package installation. Actions you create in the action interface then get combined into a package that runs a single PowerShell script on targeted devices. Available actions include the following:
Copy, rename, delete, or move a file
Create or delete a directory
Stop, start, or restart a Windows service
Add, delete, or update a registry entry
Connect or disconnect a UNC share
Launch an executable
Pop up a window
Custom PowerShell commands that you've created
Example
In this example we are going to use a situation where you are deploying a Software Package that has many files and is very large. If you zip the Software Package files, this will make the package size smaller, but also process quicker as each individual file will not have to go through the file hashing process, just the single zipped file will be hashed.
Files added as "Additional Files" are by default copied to the SDMCache directory of the Client. The SDMCache default location can be changed in your Agent Settings. Reference - https://community.ivanti.com/docs/DOC-32702
During Inventory scan or Software Distribution task LDAPWhoami.exe triggers smartcard reader dialog box (on the devices with smartcard reader installed).
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.
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:
Create a Bare Metal Object in LANDESK Management GUI on the server
Schedule Operating System Provisioning through the GUI on the server
Launch PC via PXE and Deploy OS from Template scheduled in Step 2
PC being Provisioned will prompt user to select software to install via a home made script*/gui (all client side PC)
* 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
I manage Ivanti End Point Manager 2017.3 for a customer.
I have a task for uninstalling three software from the customer's workstations. This task just invokes a batch file which performs three steps.
1) uninstall the first software, then send a message to the Core Server console with sdclient.exe;
2) uninstall the second one, then send a message to the Core Server console;
3) uninstall the third one, then send a message to the Core Server console.
I can say that the task is working, but it has a little strange behaviour.
In the Scheduled Task console, I see that the task goes quickly in the Successful tab, showing Status Done and Stage Completed.
Actually, the batch is still working; if I refresh (F5) the Scheduled Task console, I can see the messages coming from the batch (uninstalled the first software, then later uninstalled the second one, then later uninstalled the third one).
I would expect that the task should stay in the Active tab (until the batch completes its execution), instead of going immediately in the Successful tab.
Anybody has the same issue (and possibly a solution)?
To make this configuration a permanent part of the default Agent configuration, do the following.
Browse to the LDLOGON share on the core server. Open the ntstacfg.in# file with notepad.exe. Search for ldap, which should take you to this section:
; LDAP groups can be enumerated on the client, this provides more information in the inventory
; database and faster targeting of LDAP groups. This also generates network traffic between the
; client and the LDAP server, the following registry value can be used to disable this option
REG54=HKEY_LOCAL_MACHINE, SOFTWARE\LANDesk\ManagementSuite\WinClient\DisableLdapGroupEnumeration, 0, , REG_DWORD
The default value is 0 which is Disabled. Change this to 1, and save the file.
On the Ivanti EPM Core server, go to Configure | Services | Inventory and restart the Inventory Service. This will run stamper.exe, which builds the ntstacfg.ini file from the ntstacfg.in# file.
Next, in the Ivanti EPM Console, go to Tools | Configuration | Agent Configuration and click the "Rebuild All" button. This will rebuild the Agent_Name.ini file from the ntstacfg.in# file.
After doing this all of the Ivanti EPM Windows Agents will have LDAP enumeration enabled when the agent is installed.
2. Configure the Directory Manager plugin
In the Ivanti EPM Console, go to Tools | Distribution | Directory Manager. Click the Key icon, and then the Add button. Enter the credentials of a domain administrator or a user that can browse the domain.
The following window will come up, prompting for the kind of LDAP objects to find. Depending on the type of query and what is going to be targeted (users or machines), this will change. For this example, both types are selected.
Your schedule task will be stay active status and never finish.
Error message and Logs needs to check:
1. In C:\ProgramData\LANDesk\Log\LANDesk.Scheduler.GlobalScheduler.Skeleton.log
You may see the following exception:
Line 10767: 08/20/2013 15:17:12 INFO 14776:1 RollingLog : <MachineName> : Exception in GlobalSchedulerSkeleton: '', hexadecimal value 0x02, is an invalid character. Line 5, position 22.
Line 10768: 08/20/2013 15:17:12 INFO 14776:1 RollingLog : <MachineName> : at System.Xml.XmlTextReaderImpl.Throw(Exception e)
2. In the global scheduler log you may see the following:
<MachineName> has completed task with status 8 (An exception occured processing the delegated task.)
3. There is a .pmf file that is created for the scheduled task. It can be found in managementsute\landesk\file named corename-task-#.pmf. Where corename is the corename, and # is the task ID. Review that file to see if there are invalid characters looks like this:
<targets>
<target deviceId="xxxx" computerIdn="xxxx" />
</targets>
Reason:
The schedule task stacked at active status because of the exception, the task will not continue. The exception was because there was some invalid charicters contains in the "device ID"
Solution:
1. Delete the machine from All device list.
2. Then follow the steps in this document to clear the device ID on the machine.
And the policy.invoker.exe should always be running in task manager. The policy.invoker.exe will check the for policy client files every 3 seconds to launch the task.
If it is not running, you can go to Services and start the LANDesk Policy Invoker.
You can collect the following log files for the support team: