You need to manually set credentials for all machines that do not have the same username and password as the ones provided at the Acronis Group Server installation
Domain
If Primary Domain Controller of Windows 2000/2003 Active Directory goes down and Backup Domain controller automatically takes over, then Active Directory will be out of Sync after Primary Domain Controller is restored from a backup
How to collect Group Policies in a domain using Group Policy Management Console
This has been fixed
This has been fixed
The problem is in incorrect SSL certificate generation for intercomponent connections of Acronis products. As workaround, try disabling SSL encryption
How to save images to a network drive via smb or nfs
To migrate a domain controller, back up with VSS and use Acronis Universal Restore for recovery
An attempt to connect to an Acronis Agent fails with "Active Directory is not available for the specified user. Cannot create MAPI profile. Probably, the user does not have a mailbox or Microsoft Exchange MAPI and CDO are probably out of date."
This has already been fixed. The fix is available in the latest build of the product
How to solve the problem when a bootable version of Acronis product cannot log you into the network where the image archive is, and keeps asking for the user name and password again and again
When connecting to RHEV Manager, make sure you include domain in the user name
Symptoms
- You are installing Acronis Disk Director 11 Advanced on a read-only domain controller (RODC);
- The installation fails;
- In the installation log there is a message similar to the following one:
- If you selected to use an existing user for Acronis services:
AddUserToLocalGroup: add user 'DOMAIN\administrator' to the group ''Backup Operators' failed with error '' (1313720)
- If you selected to use an existing user for Acronis services:
During a remote installation, you specify target machine name and IP adress and account. You receive this SER Code. Please specify the account user in full form "domain\user" or ".\user" for local user
The user under which you are trying to install is part of the "Deny log on as a service" user rights assignment policy
Make sure you have ports 9876 and 25001 open
This article applies to:
- Acronis Backup Advanced 11.5 (Acronis Backup & Recovery 11.5)
- Acronis Backup & Recovery 11
Symptoms
- You start remote installation of Acronis components.
- Installation fails with the following error messages:
Failed to get information about remote machine
Failed to connect to the service
Failed to connect to Windows service
The "Log on as a service" right failed to be automatically added to the user under which you are trying to install
Back up Active Directory with Microsoft Ntbackup, then back up the server using Acronis True Image. Restore the server first with Acronis True Image, then restore Active Directory with Microsoft Ntbackup
The reason is that the backup was created with disabled VSS support
Create snapshots using Volume Shadow Copy
Symptoms
- You are installing Acronis Agent for Windows on a read-only domain controller (RODC);
- The installation fails;
- In the installation log there is a message similar to the following one:
- If you selected to use an existing user for Acronis services:
AddUserToLocalGroup: add user 'DOMAIN\administrator' to the group ''Backup Operators' failed with error '' (1313720)
- If you selected to use an existing user for Acronis services:
Summary:
In order to run Acronis Files Connect (formerly ExtremeZ-IP) or MassTransit or MassTransit Transporter Windows services under the credentials of a domain user, you must first allow the domain user the ability to "Act as part of the operating system."
Description:
Follow the steps below to do this (Note: That it usually takes a restart of the server before the changes will take effect):
This article describes, how to install Acronis Cyber Protect/Acronis Backup products successfully on a Microsoft Windows Read-Only Domain Controller.
Before installing the product on a read-only domain controller (RODC), log on to the primary (writeable) domain controller and perform one or more of the following steps, depending on which components you are installing on the read-only domain controller: