locked
SCOM 2016 - Management Server deployment failed RRS feed

  • Question

  • Hello All,

    I'm trying to install a brand new SCOM 2016 environment.

    Installation on Server 2019

    I am unable to install Management Server

    For ref:

    Management Server  - SCOM01

    db - SSQLSERVER on SQL01

    There is a log file that was generated.  The environment is brand new, no firewalls on same domain.

    Sunday, April 5, 2020 6:03 PM

Answers

  • The interesting part of the setup log is the following:

    [18:40:16]:	Error:	:GetCrackNameResult() DS_NAME_RESULT_ITEM crack failed with error = DS_NAME_ERROR_NO_MAPPING
    [18:40:16]:	Error:	:ValidateEssentialsAdministratorAccount() failed to crack NT4 format.
    [18:40:16]:	Info:	:ValidateEssentialsAdministratorAccount() Try to crack account with directory searcher.
    [18:40:19]:	Error:	:ValidateEssentialsAdministratorAccount() failed: Threw Exception.Type: System.Runtime.InteropServices.COMException, Exception Error Code: 0x8007054B, Exception.Message: The specified domain either does not exist or could not be contacted.


    The issue has to do when you have the RC4 protocol disabled, this can happen if the operating systems have been hardened, you'll find this issue described in the following blog posts:

    https://nathangau.wordpress.com/2018/06/22/scom-installer-failure-with-rc4-protocol-disabled

    https://www.bictt.com/blogs/system-center-2019-operations-manager-scom-installation-routine-and-the-unsecure-kerberos-encryption/

    -------------------------------------------------------------------------------------------------------

    Workaround:

    The registry key in question is: HLKM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\

    The DWORD value is “SupportedEncryptionTypes” which needs to be set to a decimal value of 2147483644.

    Or you can change this via GPO, this can be addressed by adding RC4 to the following GPO setting:

    Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > “Network security: Configure encryption types allowed for Kerberos

    If RC4 is missing here and this setting is enabled, you will want to change it.

    -------------------------------------------------------------------------------------------------------

    This appears to be only affecting the installation of SCOM, you can change back the values mentioned above  after the installations.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Sunday, April 5, 2020 7:45 PM
  • On a side note, since this is a brand new installation, you should deploy SCOM 2019 instead of 2016.

    Also SCOM2016 is not supported with Windows 2019, only windows 2012 R2 and 2016 are.

    Sunday, April 5, 2020 8:07 PM

All replies

  • Hi,

    What is the error you're receiving? Please provide the full error message and error ID.

    You can also have a look at the troubleshooting guide here:
    https://social.technet.microsoft.com/wiki/contents/articles/53430.scom-troubleshooting-management-server-installation.aspx

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:


    • Edited by Leon Laude Sunday, April 5, 2020 6:33 PM
    Sunday, April 5, 2020 6:30 PM
  • "Operational database configuration failed to install

    For more information view the setup log."

    What is the best way to upload the log file?

    Sunday, April 5, 2020 6:46 PM
  • Upload the log to a Microsoft OneDrive or Google Drive and share the link here.

    Blog: https://thesystemcenterblog.com LinkedIn:

    Sunday, April 5, 2020 7:12 PM
  • Here you go Leon

    Screenshot of error

    OpsMgrSetupWizard.log

    https://drive.google.com/open?id=18rARlIkKwHREYHD9Cm5OtuIOog6cNCJT

    Sunday, April 5, 2020 7:18 PM
  • The interesting part of the setup log is the following:

    [18:40:16]:	Error:	:GetCrackNameResult() DS_NAME_RESULT_ITEM crack failed with error = DS_NAME_ERROR_NO_MAPPING
    [18:40:16]:	Error:	:ValidateEssentialsAdministratorAccount() failed to crack NT4 format.
    [18:40:16]:	Info:	:ValidateEssentialsAdministratorAccount() Try to crack account with directory searcher.
    [18:40:19]:	Error:	:ValidateEssentialsAdministratorAccount() failed: Threw Exception.Type: System.Runtime.InteropServices.COMException, Exception Error Code: 0x8007054B, Exception.Message: The specified domain either does not exist or could not be contacted.


    The issue has to do when you have the RC4 protocol disabled, this can happen if the operating systems have been hardened, you'll find this issue described in the following blog posts:

    https://nathangau.wordpress.com/2018/06/22/scom-installer-failure-with-rc4-protocol-disabled

    https://www.bictt.com/blogs/system-center-2019-operations-manager-scom-installation-routine-and-the-unsecure-kerberos-encryption/

    -------------------------------------------------------------------------------------------------------

    Workaround:

    The registry key in question is: HLKM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\Kerberos\Parameters\

    The DWORD value is “SupportedEncryptionTypes” which needs to be set to a decimal value of 2147483644.

    Or you can change this via GPO, this can be addressed by adding RC4 to the following GPO setting:

    Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options > “Network security: Configure encryption types allowed for Kerberos

    If RC4 is missing here and this setting is enabled, you will want to change it.

    -------------------------------------------------------------------------------------------------------

    This appears to be only affecting the installation of SCOM, you can change back the values mentioned above  after the installations.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Sunday, April 5, 2020 7:45 PM
  • On a side note, since this is a brand new installation, you should deploy SCOM 2019 instead of 2016.

    Also SCOM2016 is not supported with Windows 2019, only windows 2012 R2 and 2016 are.

    Sunday, April 5, 2020 8:07 PM
  • Firstly thank you for the reponses.

    I have raised a change to the Local Policy via GPO and will also deploy 2019 tomorrow.

    Will update.

    Monday, April 6, 2020 4:58 PM
  • Did enabling RC4 fix the install issue? 

    I have it enabled but i am still receiving this error. 

    Any help is appreciated. 

    Thx

    Wednesday, June 24, 2020 4:05 PM