Release Notes
Microsoft System Center Configuration Manager Package Conversion Manager
How to install Microsoft System Center Configuration Manager Package Conversion Manager
Package Conversion Manager is an add-on to the SystemCenter2012 ConfigurationManager console. Before installing Package Conversion Manager, you must have a SystemCenter2012 ConfigurationManager primary site or central administration site installed and configured.
Before installing Package Conversion Manager, you must download the Package Conversion Manager installation program, PCMSetup.exe.
To install the Package Conversion Manager
1. On the computer where a SystemCenter2012 ConfigurationManager console is installed, run PCMSetup.exe.Package Conversion Manager is installed.
Online Help
Online help is located here.
Other
Packages associated with collections, with sub-query in the WHERE clause, won’t be converted.
Known Issues
Collection conversion with valid WQL: SMS_G_System_Class.InstallDate value will need to be updated on the Deployment Type.
CAUSE: A valid WQL: SMS_G_System_Class.InstallDate will not convert the correct date value during conversion.
WORKAROUND: After the Application is converted, change the WQL value on the Deployment Type.
Package with program dependent upon another program in the SAME package will not have that dependency converted.
WORKAROUND: This is not best practice, but after the Package is converted to an Application you can manually add that dependency to that Deployment Type in that same package.
Fix and Convert System.FormatException: The string was not recognized as a valid Date Time
CAUSE: Asian DBCS characters (such as Chinese or Japanese characters) in the collection membership rule WQL query (such as SMS_G_System_<Class>.InstallDate= '2011/4/3 11:00:00 下午') would cause the error.
WORKAROUND: Change the DBCS characters to English string. For example, change InstallDate = '2011/4/3 11:00:00 下午' to '2011/4/3 11:00:00 PM'
On Windows XP an error occurs when running PCM stating there is a problem configuring PCM log file and that the path could not be found.
CAUSE: This problem occurs when the temp directory’s path, used for storing the PCMTrace.log, contains a “~” and is different than the temp directory which PCM is looking for.
WORKAROUND: After installing Package Conversion Manager open %ProgramFiles(x86)%\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe.config
Change initializeData="%UserProfile%\AppData\Local\Temp\PcmTrace.log"
To
initializeData="%temp%\PcmTrace.log or to another location that is suitable to store the PCMTrace.log
Save the file and restart the console.
Support
For additional information, see Information and Support for Configuration Manager.