System Center Configuration Manager и как с ним бороться

В процессе эксплуатации возникли ошибки работы точки управления.

MPSetup.log:

mp.msi exited with return code: 1603
Backing up C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log to C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log.LastError
Fatal MSI Error — mp.msi could not be installed.

mp.MSI.log:

ERROR: Method ‘DeleteExtensionFileRecord’ failed with error code 80020009
ERROR: Automation Exception invoking method «DeleteExtensionFileRecord»
ERROR: Automation Exception Source is «<null>»
ERROR: Automation Exception Description is «<null>»
ERROR: Automation Exception wCode is 0
ERROR: Automation Exception sCode is 0x800CC801
IGNORE: Failed to delete extension ‘c:\program files (x86)\sms_ccm\x64\getsdmpackage.dll’. Error Code = 0x80020009 (The extension might not registered)

SMS_MP_CONTROL_MANAGER

ID 4963:

MP Control Manager detected MPsetup has failed to create the CCM_Incoming Virtual Directory.

SMS_MP_CONTROL_MANAGER

ID 1020:

SMS Site Component Manager failed to reinstall this component on this site system.

SMS_MP_CONTROL_MANAGER

ID 4951:

SMS Site Component Manager failed to install this component, because the Microsoft Installer File for this component (MP.msi) could not install.

Сам компонент SMS_MP_CONTROL_MANAGER находится в состоянии Offline. При попытке вручную запустить компонент получаем ошибку:

Решение простое — удалить BITS и MP, заново установить BITS и MP. Также проверьте содержимое файла WebDAV_schema.xml:

<attribute name=»allowHiddenFiles» type=»bool» defaultValue=»false» />
<attribute name=»useTransactionalIo» type=»bool» defaultValue=»false» />
<attribute name=»hideChildVirtualDirectories» type=»bool» defaultValue=»false» />