70925: Acronis Cyber Protect: Agent installation on a Domain controller fails with the error: "Failed to get SID of group '....."

use Google Translate

Operating Systems: 

    Last update: 09-01-2023

    Scenario 1

    • You are trying to install Acronis cyber protect Agent on a Domain Controller
    • Installation fails with the error "Fatal error during installation. Failed to get SID of group '....'" 

     

     

    Cause

    Lack of user rights on the Domain Controller.

    Solution

    1. Create a new global admin user, e.g. "Acronis Domain Admin",
    2. Assign the user the necessary rights as per the following article
    3. Enable "unblock" for the installation file (right mouse click - properties)                                                      
    4. Run the installation file as an Administrator
    5. Choose the option "Customize installation settings" and specify the new Domain Admin user under "Logon account for the agent service" - "Use the following account".                                                                                                        

     

    Scenario 2

    • You are trying to install Acronis cyber protect Agent on a Domain Controller
    • Machine is a Secondary domain controller and a Primary domain controller exists in the environment
    • Installation fails with the error "Fatal error during installation. Failed to get SID of group '....'"

       

    Cause

    The security group 'Cyber Operators' was replicated from the Primary domain controller to the Secondary domain controller and it doesn't have the right IDs.

    Solution

    1. Remove the security group mentioned in the error message from the current machine where installation fails.
    2. Re-run the installation file as an Administrator
    3. A new group would be created with the installation.

    More information

    If the issue persists, follow these Microsoft articles to troubleshoot issues with setting up a secure session with a domain controller:

    Microsoft Article 1

    Microsoft Article 2

     

    Tags: