Once packages are exported and off-boarded from the your K1000 or K2000, it can be difficult identifying or finding a particular package unless you made sure to document the files. They can be even harder to find if the exported item was already removed from the K2000, or in a disaster recovery scenario where you only want to import packages that you need right away.

This script will gather identifying information from all of the exported K1000 and K2000 packages in a specified folder and deliver the information in HTML format.
Please bear in mind that it will not work if you have only .pkg files from your K2000, as it reads the data from the .xml files that are exported with those .pkg files.
With K1000 it will extract the .XML file from the .kpkg and then keep it stored for faster reading the next time the report is run.

Only tested with version 3.3 and higher .pkg (K2000) files and 5.2 and higher .kpkg (K1000) files.

You can download the script here.

Feedback is very welcome, please let me know what you think or if it helps you.

Version History

-Fixed a bug that kept the script from running unless you had .kpkg files in your target directory

-Added gui progress bar while waiting for kpkgs to extract

-Added code from Corey Serrins that would extract XML information from a K1000 .kpkg and allow us to report from it
-Fixed issue with x64 systems not closing GUI properly when script was finished
-Changed behavior so that the final report opens in the default web browser instead of opening in Internet Explorer

-Added the ability to check for K1000 package xmls and display them in the report.
-Added check to ensure that there were K1 or K2 package .xmls in a directory before continuing with the report

-First public release
-Added check to skip .XML files not generated from the K2000
-Kept the GUI up with previous values if there was an issue with the package directory specified rather than exiting.

-Added checks to make sure that the target package directory existed and contained .XML files
-Added the ability to create the destination directory for the report if it did not already exist

-Added the ability to sort the table based on File Name, Title, or Type
-Corrected an issue where Scripted Install files were showing as Postinstall Tasks
-Added a graphical window to run through the process
-Added a message if you tried to start the report without specifying both the target package directory and report destination

-Generated a stylized html table with the package results
-Listed the date generated and the source package directory in the report

-Generated a plain .html table instead of a .CSV

-Added the ability to browse for the directory that the packages were contained in
-Added the ability to save the .CSV report with a custom name and location

-Added in a .CSV header

-initial release
-Generated a .CSV report

Answer Summary:
You can download the script here: https://downloads.kace.com/support/downloads/k2000/scripts/k-series_pkg_report.zip
1 Comment   [ + ] Show Comment


  • Feature request: Option to rename existing files to the title of the exported object.
    • I'll have to add that in, good request!
Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Answer this question or Comment on this question for clarity