Quantcast
Channel: Ivanti User Community : All Content - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 1803

How to deploy software packages using run from source during provisioning in LDMS 9.6

$
0
0

Environment

 

LANDESK Management Suite 9.6

 

Review Date

 

October 2014

 

Issue

 

  • Provisioning is not aware of the scheduled task settings available for software distribution such as the the option to run the package installation from source.
  • A device installing a software during a provisioning process will always try to download the distribution package locally before running the installation.
  • Delivery methods are not used any more in LANDESK Management Suite 9.6.

 

How to


To avoid the target device downloading the installation files locally, we can set up a script that will run the package from a mapped network drive rather than from a UNC share.

Setting up our provisioning template to map a drive with a correspondent letter associated before running the software distribution will make the target device downloading a few bytes script and running the installation without downloading the package locally.

 

Step by Step


1. Define a drive letter suitable for both the Core Server and the target devices to be used for the network drive mapping

2. On a test client device, map the drive letter pointing to the software source or to a preferred server that has the same content replicated

3. On a test client device, verify that the installation of the package manually running the installer while pointing to the network drive just mapped, using the options you defined for your distribution package


map_drive.png


4. On the Core server, create a script using the same command tested on the client device


create_script.png

 

5. On the Core server, create a batch file distribution package pointing to the script just created

 

batch_package_run_from_source.png

 

6. On the Core server, while configuring your provisioning template, set up an action to map drive to preferred server, using the same letter defined at point 1

 

map_preferred_server.png

 

7. In the same provisioning template, after having mapped the designed drive letter to a preferred server, distribute the software package created at point 5

 

distribute_batch.png

 

8. Schedule the provisioning template targeting a test device and verify that the package installation succeed without the client device downloading the files on the local file system


Viewing all articles
Browse latest Browse all 1803

Trending Articles