Introducing SCCM Package Conversion Manager
By Paul Heuring So you’ve recently deployed Microsoft System Center 2012R2 Configuration Manager to replace an older implementation. But you had any number of tried and true packages that users and administrators have relied on. Rather than manually recreating them in the new environment, you could export them and import them into the new system. Still, the new application deployment model offers some useful features missing from using Packages and Programs to deploy software. You might like to try using the Microsoft System Center Configuration Manager Package Conversion Manager, PCM, to bring those older packages into the new system. Here is an overview of the PCM and some high level planning advice in using it. Microsoft System Center Configuration Manager Package Conversion Manager is feature pack download for Microsoft System Center 2012 Configuration Manager that allows you to convert Configuration Manager 2007 packages into System Center 2012 Configuration Manager applications. A Configuration Manager application contains files and programs that can be deployed to client devices. However, unlike Configuration Manager 2007 packages and programs, an application provides additional user-centric functionality. For example, an application might contain deployment types for a local installation of a software package, a virtual application package, or a version of the application for mobile devices. Upon conversion, you can use the new features in applications such as dependencies, requirement rules, and user device affinity. To effectively use the Package Conversion Manager it is best to plan your implementation. In a perfect world, you have a test environment wherein you can test the tool against packages imported from your production environment. After completing testing of the converted applications, you can then export the converted applications from the test environment and then import them to the production environment. Your package conversion plan would look like the following. 1) Select the packages that you want to convert Not all packages are suitable for conversion into applications. The best types of package for conversion to applications are those that contain user-facing software, for example:
- Windows update files: .msi and .msu.
- Microsoft Application Virtualization (App-V) programs.
- Windows executable files: .exe
- System maintenance tools; for example, scripts or backup utilities.
- Packages that are at End-of-Life.
- The location specified for source files is a full UNC path, for example \\Server\Volume\File.
- Windows update files, .msi and .msu, use only one unique Product Identification Locator (PID).
- At least one test package with a readiness state of Automatic.
- At least one test package with a readiness state of Manual.
- Packages that you know well.
- Packages that are the most important to your business.
- Packages that you can most easily test.
- Individually: If you need to analyze only one package, you can use Package Conversion Manager in Configuration Manager console. (For more information, see How to Analyze and Convert Packages in Package Conversion Manager).
- Small group: If you need to analyze a small group of packages, you can use Package Conversion Manager in Configuration Manager console.
- Large Group (Bulk Analysis): If you need to analyze a large group of packages, use the Scheduled Analysis features of Package Conversion Manager.( For more information, see How to Use Scheduled Analysis (Bulk Analysis) in Package Conversion Manager.