UPDATE (January 16, 2013): Workarounds available – Confirmed: ConfigMgr 2012 PCM install is hard-coded to the C: drive
We announced the release of the SP1 version of Package Conversion Manager 2.0 for ConfigMgr 2012 here: The SP1 version of ConfigMgr 2012 Package Conversion Manager is released
However, there are now a multitude of reports that the new PCM installs successfully but the application’s icon cannot be located in the ConfigMgr console afterward.
Here’s an example, posted to the SCCM email discussion list:
From Andrew Macdermott…
I see the same behaviour in two freshly build SCCM 2012 SP1 deployments. PCM does not appear in “Programs and Features” after installation, despite Event Viewer logging a successful MSI install – and no PCM elements are present in the SCCM console after installation. I even uninstalled and reinstalled the console on one server and it did not help (although I reinstalled it to the \Microsoft Configuration Manager\AdminConsole folder not the default path it wanted to use (C:\Program Files etc).
However, on an SCCM 2012 SP1 console that is installed on a Windows 7 workstation, the PCM 2 package does work as expected. I wonder if PCM 2 does not like the console being installed anywhere other than the default stand-alone location?
Are you seeing the same? Let us know.
BTW: There’s other gotchas with PCM 2.0. Grab the release notes here: Package_Conversion_Manager_ReleaseNotes.docx