08-22-2013 07:47 AM
When I try to establish a trust or schedule a backup for a Windows 2012 Core Installation Domain Controller I get this error:
Failed to browse...
Failed to log on to Microsoft Windows.
Ensure that your logon credentials are entered and that they meet the following minimum requirements to log on to a Windows computer:
-The credentials used are a member of the Backup Operators group.
-For Windows Vista/2008 and later, the credentials hav ethe Log on as a batch job privilege.
Additional privileges may be required to access resources on the Windows computer.
I am running Backup Exec 2012 with Service Pack 2 on Windows Server 2008 R2 Std 64bit
My BE service account is
I am backing up Windows 2003, 2008, and 2012 platforms successfully with this service account.
I am also backing up Windows 2012 Core File Server installations successfully with this service account.
There are 4 DCs running Core Installations that have this issue:
All responses are greatly appreciated :)
Solved! Go to Solution.
12-16-2013 05:22 AM
After calling Symantec Tech Support & jumping through lots of Change Management hoops I modified the "Default Domain Controllers Policy" GPO -
Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies/User Rights Assignment
I added my BE Account to:
Doing all this locally on the problem servers did nothing, but applying the GPO worked.
08-22-2013 09:22 AM
Hello,
Please make sure these services are running as Domain\Administrator and verify the password is correct:
also see this link and verify these requirements are in place: Requirements for the Backup Exec Service Account (BESA)
08-22-2013 09:54 AM
Thank you for your response :)
The above services are running as Domain\Administrator and the rights assignments requirements have been met.
The error still occurs.
It is a 2003 domain level - if that makes a difference.
08-22-2013 03:37 PM
Check to make sure there aren't any policies that are restricting access to the servers.
Are the servers using IPV6 or IPV4? Try matching this in Backup Exec by editing the job then under Backup Options under Network make sure it is set to Use any available network interface and in Protocol: select the one that the server is using.
08-23-2013 05:43 AM
We have 11 domain controllers and the same policy is applied to all of them. It's only these 4 with Core installed on them that are having the issue.
We're using IPv4. IPv6 is not disabled however. Should it be?
I can't go to Backup Options - I get this error before backup options are available to select. The error comes up when it tries to list the drives available for backup or when it tries to establish a trust.
08-23-2013 07:00 PM
You should disable IPv6.
08-25-2013 06:38 PM
You might need to add the BESA account (Backup Exec services account) and Backup Operator account for the User Right assignment for some of them(listed below) found under local security policy.
NOTE: This should be done on the remote servers which you're unable to backup.
Check the article below on how to add it.
http://www.symantec.com/docs/TECH74365
Hope this resolves the issue!
11-18-2013 06:57 AM
12-09-2013 02:51 PM
Is there any movement on this? I am having the same issue.
Thanks,
Robert
12-16-2013 05:22 AM
After calling Symantec Tech Support & jumping through lots of Change Management hoops I modified the "Default Domain Controllers Policy" GPO -
Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies/User Rights Assignment
I added my BE Account to:
Doing all this locally on the problem servers did nothing, but applying the GPO worked.
11-07-2018 04:11 AM
This was the magic ticket. Thank you for sharing the solution!