Today I had a strange problem when instaling a Management Point (MP) on a Primary ConfigMgr 2012 site server that is a child of a ConfigMgr 2012 Central Administration Site.
The installation of the MP failed with the well-known 1603 error that is a generic error that can be caused by several things.
A closer look at the mpmsi.log file showed the following cause of the problem:
Action start 11:40:26: CcmMigratePolicySettingsInit.
MSI (s) (80:94) [11:40:26:152]: Note: 1: 2235 2:3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'CcmMigratePolicySettingsInit'
MSI (s) (80:40) [11:40:26:167]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI23B.tmp, Entrypoint: CcmMigratePolicySettingsInit
[11:40:26] Getting settings from WMI and storing in D:\Prog\SMS_CCM\polmig.mof
CustomAction CcmMigratePolicySettingsInit returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 11:40:26: CcmMigratePolicySettingsInit. Return value 3.
MSI (s) (80:94) [11:40:26:167]: Machine policy value 'DisableRollback' is 0
MSI (s) (80:94) [11:40:26:167]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (80:94) [11:40:26:183]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (80:94) [11:40:26:183]: No System Restore sequence number for this installation.
MSI (s) (80:94) [11:40:26:183]: Unlocking Server
Action ended 11:40:26: INSTALL. Return value 3.
I had chosen a non-standard location for installation of ConfigMgr. "D:\Prog\Microsoft Configuration Manager". Therefore the MP installation would try to install in the "D:\prog\SMS_CCM" folder.
The problem was that at the time the MP installation tried to generate the polmig.mof file it had not yet created the SMS_CCM folder.
I therefore created the SMS_CCM folder manually before I reinstalled the MP. Now the MP installed as it should.
Some people might think of this as a feature… I think it is a bug :-D