This error occurs when RecoveryManager Plus cannot access the ADMIN$ share of the configured DC.
To fix this issue, reboot RecoveryManager Plus.
This error occurs when the account used to configure RecoveryManager Plus does not have sufficient privileges.
To fix this issue, perform the following steps in the configured DC.
Check if the machine in which RecoveryManager Plus is installed and the configured DC are in the same domain network. If not, add the DC to the trusted hosts list of the machine. Perform the following steps in the machine in which RecoveryManager Plus is installed.
winrm s winrm/config/client '@{TrustedHosts="<dc1-name>,<dc2-name>"}'
This issue occurs when the group policy module is not present in the DC.
Note: If you are using a Window Server 2008 DC, contact RecoveryManager Plus support to resolve your issue. For all other versions of DCs, follow the steps listed below.
Check if group policy module is installed in the DC. If not, install it by following the steps listed below.
This issue occurs when the GPO that is to be backed up is not found in the environment. This might be due to orphaned GPOs being present in the environment.
This behavior occurs if a user or a group name that is referenced in a Group Policy Object corresponds to an abbreviation that is defined for a built-in group that is used by the Security Descriptor Definition Language (SDDL) format. For example, this behavior occurs if you name a user or a group "SA." The "SA" abbreviation corresponds to the SDDL security identifier (SID) string that represents the built-in Schema Admins group.
If a user name or a group name matches an SDDL abbreviation that is defined for a built-in group, a function that is called by the Group Policy Management Console treats the user name or the group name as a SID. Therefore, the backup fails.
To fix this issue,
This error occurs when the account used to configure RecoveryManager Plus does not have privileges to access the GPO containers.
This error occurs when the specific GPO is corrupted or when it cannot be copied or imported to GPMC.
Contact Microsoft support or delete and recreate the GPO.
This error occurs when a Folder Redirection Policy is set for a GPO. This issue occurs due to an SID change in machines running Windows Server 2003 or higher.
These issues occur because the Folder_Redirection section of the .ini files is larger than 32,767 characters. However, the limit for the combined SID list for all folders is 32,767 characters. For more information on this issue, click here.
To solve this issue,
This error occurs when the account used to configure RecoveryManager Plus does not have enough privilege to read the specific Group policy container.
This issue occurs when the GPO container is not present in the SYSVOL folder.
To fix this issue, try either of the following steps.
%ALLUSERSPROFILE%\Application Data\Microsoft\Group Policy\History contains a copy of the preferences contained in GPOs. If the copy process failed, an invalid XML file may be left in one of the subdirectories, thus creating the error.
To fix this issue, create a clean copy of the GPO by following the steps listed below.
Contact support@recoverymanagerplus.com to resolve this issue.
Copyright © 2023, ZOHO Corp. All Rights Reserved. |