none
Unknown Conponent failed to install

    Question

  • I have upgraded a Configuration Manager 2012 R2 site to 1511 and a component has failed to install.  The component is named "SMS_DMAPPSVC_CONTROL_MANAGER".  I do not know what that component is, does someone know about this component and what is does?  A search of the internet did not return any hits on that name.  The SiteComp.log files states "Component file list item in the install map for component SMS_DMAPPSVC_CONTROL_MANAGER does not contain srvboot.exe".  Any ideas will be appreciated.
    Wednesday, December 16, 2015 7:21 PM

Answers

  • This is a known, but completely benign issue. It is annoying but ignorable in 1511. The product group are aware though and *may* issue a fix.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by pnnl Wednesday, December 16, 2015 9:58 PM
    Wednesday, December 16, 2015 9:19 PM

All replies

  • This is a known, but completely benign issue. It is annoying but ignorable in 1511. The product group are aware though and *may* issue a fix.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    • Marked as answer by pnnl Wednesday, December 16, 2015 9:58 PM
    Wednesday, December 16, 2015 9:19 PM
  • Thank you Jason, I appreciate your response.  I was able to eliminate the error messages by following the information provided for a similar issue that occurred in SMS 2 (MS KB article: http://support.microsoft.com/kb/227010).  I copied the line "FILE <srvboot.exe><0><3667640>" from a different component in the install.map file, and placed it into the SMS_DMAPPSVC_CONTROL_MANAGER component of the file.  After a restart of the server the component installed without an error.  Hopefully this will not bring me any grief down the road.
    Wednesday, December 16, 2015 9:58 PM
  • Yup, this worked for me also. (Lab environment so not so concerned about potential implications)
    Friday, February 12, 2016 12:54 AM
  • Thanks, we were having the same issue uninstalling this too (though it did install), adding srvboot to install.map in X:\Program Files\Microsoft Configuration Manager fixed this issue:

    BEGIN_COMPONENT_FILELIST
        <SMS_DMAPPSVC_CONTROL_MANAGER>
        <536871017>
        BEGIN_DIRECTORY
            <bin\x64>
            <5><AMD64><>
            FILE <NDP452-KB2901907-x86-x64-AllOS-ENU.exe><8388608><0>
            FILE <TEMHostWrapper.dll><1><23736>
            FILE <Microsoft.ConfigurationManager.TaskExecutionManager.dll><0><33464>
            FILE <Microsoft.ConfigurationManager.TaskExecutionManager.tlb><0><2616>
            FILE <SMS_DMAPPSVC_CONTROL_MANAGER.xml><0><312>
            FILE <Microsoft.ConfigurationManager.DeviceManagement.CMServiceWorker.dll><0><36024>
            FILE <Microsoft.ConfigurationManager.DeviceManagement.InformationService.xml><0><1191>
            FILE <Microsoft.ConfigurationManager.ManagedBase.dll><1><145592>
            FILE <srvboot.exe><0><3667640>
        END_DIRECTORY

    Monday, February 15, 2016 4:42 PM
  • What is the use of SMS_DMAPPSVC_CONTROL_MANAGER?
    Tuesday, March 01, 2016 9:47 AM
  • It's a new component being developed that is not enabled/active in 1511. I don't know off-hand if it is in 1602 or not though.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, March 01, 2016 2:45 PM
  • OK, just checked a 1602 site. It does exist and looks to be part of the on-premises MDM functionality.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, March 01, 2016 4:38 PM