03-09-2016 05:41 AM
I'm testing Backup Exec 15 Trial Version (well, just trying because I've been not able to install a managed server).
My "intended" installation is as follows:
My steps so far:
My "settings":
My "research":
Any ideas to point me in the right direction?
Thanks in advance,
Emilio
Solved! Go to Solution.
04-06-2016 06:51 AM
Unbelievable!
I got it working!
I was almost giving up and I tried one last thing (out of hope because it has no sense at all): I've checked dozens of times that I met all the criteria to have it working, but it refused to. What have I done? I've explicitly included BESA into the local administrators group of the CASO server. Yes, I know that's a basic requirement, but I thought that having domain admins group (of which BESA is member) into this group should suffice. It turns out that my assumptions were wrong. Not that I find any sense but at least I have it ready for testing.
Thanks to everybody who tried to help.
03-09-2016 06:19 AM
Have you checked:
1. DNS to make sure you can resolve IP-name and vice versa from the CASO and MMS servers?
2. On any firewalls running, make sure port 10000 is open for the RAWS agent to work correctly.
Thanks!
03-09-2016 06:47 AM
03-10-2016 12:58 AM
First of all, thank you for your time.
@CraigV:
@pkh:
Like I said BESA is a domain admin. I've added it to Backup Operator group. I've checked all the user rights assignments and the only one missing was "Create a token object". I've added it and restarted both servers. Result: no changes. Same error.
Any other idea?
Thanks again.
03-10-2016 06:47 AM
03-10-2016 07:20 AM
I've checked the 5 causes:
[A] Password is ok. Verified 100%.
[B] & [C] User has this right (Logon as batch job) because Domain Admins have it and Deny Logon as Batch is granted to nobody nor Deny Logon as a service. Same as before: Create a token object was not granted int the Default Domain Controllers Policy and now is.
[D] It's a member od Domain Admins that are members of Local Admins.
I've to create another account, but I did it yesterday (without granting the only right missing, create a token object) and the outcome was the same.
[E] RAWS is running on the CASO Server (the only one installed at the moment).
Just for clarification, the user being used is the same that I'm using in our actual setup that's been running for years with backup exec 2010 r3. So, I don't think it's a permission issue... But may be...
Thanks
03-16-2016 04:07 AM
Any more ideas?
03-29-2016 09:43 AM
Nobody?
I'm still stuck at this point. No changes...
Any help would be appreciated.
03-30-2016 12:18 AM
If you do a local install instead of a push does thae local installation also block you making it into a Managed Server?
03-30-2016 04:28 AM
Yes. Same behaviour...
.
03-31-2016 10:02 AM
I've also installed it locally as an independent server and then tried to change it to a managed server as per https://www.veritas.com/support/en_US/article.000075693. Same result. No way of getting a managed server.
04-06-2016 06:51 AM
Unbelievable!
I got it working!
I was almost giving up and I tried one last thing (out of hope because it has no sense at all): I've checked dozens of times that I met all the criteria to have it working, but it refused to. What have I done? I've explicitly included BESA into the local administrators group of the CASO server. Yes, I know that's a basic requirement, but I thought that having domain admins group (of which BESA is member) into this group should suffice. It turns out that my assumptions were wrong. Not that I find any sense but at least I have it ready for testing.
Thanks to everybody who tried to help.