Description:
Product to Package Mapping and Installed Mapped Software are powerful new components that were introduced in LDMS 9.5 SP2 and are used in LDMS 9.6.
Product to Package Mapping allows you to use a template system or a previous inventory scan for the same system and automatically install software based on the template.
This is very useful for old to new migrations and even in-place migrations. Also it saves time in customizing individuals computers whose old computer failed or those who are getting new systems when paired with machine to machine mapping and profile migration.
This document will walk you through how to set this up so you can start using it in your environment.
Configuration:
1. Configure Products in Software License Monitoring
Open Reporting/Monitoring in the Toolbox and open Software License Monitoring. (Note: You need Silverlight installed to see the webpage.)
Next select Products and Discovered.
In Discovered you will find Software discovered on your systems by LANDESK.
(Note: If you don't see the software you are expecting, you can add custom products here How to add a Custom Product to Software License Monitoring
Also if you want to set up License tracking and other options please review the following landing page as it is not covered in this document:
Software License Monitoring (SLM) Landing Page)
While in Discovered right click on the software you would like to use in Product to Package Mapping and go to Move to -> Monitored.
Once you have set all of the items you want to Monitored, click on the Monitored tab to ensure they are all there.
Close the Software License Monitoring window.
2. Set up Product to Package Mapping in Provisioning
Open the toolbox in Distribution and then OS Provisioning/OS Deployment (LDMS 9.6/9.5 SP2) and click on the Product to Package Mapping icon.
If you skipped or didn't configure Software License Monitoring this is what you'll see.
If you did configure Software License Monitoring you should see the packages you've set to Monitored.
You can now begin mapping your install packages to the software. To do this simply click in the SWD Packages box and then double click the desired Distribution Package.
(Note: If you don't have any distribution packages please start here. Software Distribution .)
(Important: You don't have to map Chrome -> Chrome or 7-zip -> 7-zip. As you can see in the screenshot you can map the install packages to anything. I mapped Office 2013 to 2003, 2007, and 2013 because I want any old systems that had an inventory of of 2003 or 2007 to get the new 2013. This is extremely useful in old to new migrations or system replacements. I have also mapped Silverlight to install on all of my virtual machines with VMware tools and I want Firefox on everything that has Microsoft Visual C++).
Once you have finished mapping click Assign and Close.
3. Add Provisioning Action Template Install Mapped Software
Everything has been configured, the final piece to get this working is to add the Install Mapped Software template action to your provisioning template.
(9.6 users, this action is added automatically if you create your template with the provisioning wizard.)
Final Notes
This feature is mostly to be used in conjunction with Machine to Machine Mapping in LDMS 9.6 How to use Machine Mapping in LDMS 9.6
In LDMS 9.5 SP2 and later it still works for in place migrations. (I.E. XP to Windows 7 or Windows 7 to Windows 8 on the same system.)