MDT Package Mapping Relationship Tool
Home made tool for creating relationships in the MDT database PackageMapping table. Used to maintain relationships between Add/Remove programs Display Name values and PackageID/Program Name. There are several things to bear in mind when using it:
- I am not a developer, therefore what I’ve put together is probably poorly coded and full of bugs, but it seems to do the job.
- It requires a precise design for the PackageMapping table (shown below), including the addition of a ‘Comments’ field which isn’t there as standard.
- It requires .Net Framework 3.5 client on the machine that’s running it, but a database server/instance and database can be specified for remote execution.
- The user running the program will require Connect, Select, Update, Insert and Delete permissions on the MDT Database to perform all functions.
- Always make a full backup of the database before using any third-party tools on it, especially mine.
- I provide the tool free of charge in the case that others can benefit from it, but cannot be held responsible for any loss of data that results from its use.
PackageMapping table design required:
- ARPName [Primary Key] : nvarchar(255) : Allow Nulls – False
- Packages : nvarchar(255) : Allow Nulls – True
- Comments : nvarchar(MAX) : Allow Nulls – True
Interprets the Sender.log file to display accurate details about active package transfers. Shows the Request ID, Destination, Data Transferred, Total Amount to transfer, % transferred, % remaining and where possible, the package ID of the package being transferred.
- Again, I’m not a developer and so I apologise for bugs and functionality.
- It requires .Net Framework 3.5 client on the machine that’s running it.
- The user running the program will require WMI access to a site server if Package Lookup functionality is desired.