SCCM 2012 PCM (Package Conversion Manager) fails to install when console is in a non default location

By | February 12, 2013

While testing the SCCM 2012 PCM (Package Conversion Manager) tool, I came across a bug during the installation. 

The MSI installed fine, return code was good, but there were no extensions visible int he console. The Package Conversion Manager icons were not visible on the ribbon pane when selecting a package.

This is because the SCCM console was installed on the D:\ volume rather than the default C:\program files path (any location other than default is a problem)

Rather than reinstall the console to the default folder, copying the file Microsoft.ConfigurationManagement.exe  to the folder C:\Program Files(x86)Microsoft Configuration Manager\AdminConsole\bin  (obviously from the same folder wherever you installed the console) and then rerunning the PCM installation fixes the issue.

The ribbon icons are present, and the exe file can now be removed from the c:\ location.

One thought on “SCCM 2012 PCM (Package Conversion Manager) fails to install when console is in a non default location

  1. Rv

    Hi,

    I am new in powershell. I am trying to create a script.

    example i have 1 column and 3 rows. 1st and 2nd row contains application type and third package type .
    i am trying to move them in folder name delete.
    i am able to read the excel sheet and able to move the application to delete folder but not getting how to move package. What condition i can use. Could you please suggest.

    Reply

Leave a Reply to Rv Cancel reply

Your email address will not be published. Required fields are marked *