Due to differences between ConfigMgr 2012 RTW and SP1 the same PCM code base needed to be compiled differently for these versions. This means that the installer needed to determine which set of binaries to install on a machine based on the Configuration Manager console version. To determine this the installer looks at the version of Microsoft.ConfigurationManagement.exe and then installs the appropriate set of binaries. The installer is looking in the default location, %programfiles(x86)%\Microsoft Configuration Manager\AdminConsole\bin, for this binary and if it doesn't find it the installer still appears to install successfully. However, PCM wasn't actually installed at all.
Before I get into the actual workaround let me just say there have been a few people who I talked to about the problem and they all asked, "Do I really need to uninstall my console and reinstall it to the default location?" No, you do not need to reinstall your console to the default location. Yes, that will work, but we should be able to get it to work without reinstalling the console at all. Currently the best workaround to get the appropriate set of PCM binaries installed is to copy the Microsoft.ConfigurationManagement.exe from wherever the console is currently installed into %programfiles(x86)%\Microsoft Configuration Manager\AdminConsole\bin (creating the directories if you have to) then run the installer.
We are still checking into our options, but in the meantime I hope this helps those of you that are running into this issue.
System Center 2012 Service Pack 1 has been released. This release of Package Conversion Manager (PCM) supports that release. PCM was originally released to support RTM of ConfigMgr 2012 and due to changes made in service pack 1 we had to update PCM.
Download Package Conversion Manager 2.0 from the Microsoft Download Center today.
Although there have been a few bug fixes, the main difference between PCM 1.0 and 2.0 are small changes required to support ConfigMgr SP1. However, some of these changes are not compatible with the RTM version of ConfigMgr 2012. Despite this we have been able to get PCM into a single installer which supports both ConfigMgr 2012 RTM and SP1. Therefore, you can use a single download of PCM for either RTM or SP1 for any of the languages which are supported.
Please visit the PCM Home page to get started or follow the links below to download PCM for any of the appropriate languages:
PCM 2.0 will be fully supported through CSS just as 1.0 was. This support will be valid for 1 year from 2.0's release date.