03-25-2010 04:47 AM
Solved! Go to Solution.
04-09-2010 07:38 AM
Hi Guys,
Sorry for the delay in responding, but we have been busy here plus had the Easter Bank Holiday.
I have followed Dev T's procedure but after talking with a senior colleague he advised:
1. We did not need the account to be a member of Local Admin Group even though Exchange was a member server. He says that if the account has Domain Admin rights it will have Local Admin rights.
2. The account did not need to be an Exchange Server Administrator. Again, the Domain Admin membership is sufficient.
So this is what I did:
Create a new account in AD with following settings:
1 : Member of the Domain Admin group
2 : Created a Mailbox for the account and opened it to activate the mailbox (did not send a test email)
3 : Make sure that the Mailbox is not hidden from the Global Address List.
4 : Open Backup Exec, go to NETWORK--Logon Accounts and Change the Logon Account to the new account.
This worked OK whether the account was the default or simply selected at the time the job was run.
The new account will definitely not work if it's mailbox has not been created and activated.
I still do not know why the original Logon Account started to fail, but it is now redundant and I am using the new account for backups and restores.
Thanks a million for all you help
Best regards,
Michael
03-25-2010 05:38 AM
03-25-2010 08:02 AM
03-25-2010 10:57 PM
Maybe look at removing, and then readding the user account in BEWS...?
And is the backup service account a delegated admin in Exchange?
03-29-2010 02:36 AM
03-29-2010 02:43 AM
03-29-2010 02:56 AM
Hello,
Create a new account in AD named : symantec with following settings:
1 : Member of the Domain Admin group and Local Admin Group if Exchange is a member server
2 : Create a Mailbox for Symantec, send a test email and oprn it in OWA to activate the Mailbox.
3 : Make sure that the Mailbox is not hidden from the Global Address List.
4 : Add the account "symantec" as Exchange Server Administrator in Exchange Management Console.
Open Backup Exec, go to TOOLS--Logon Accounts and Change the Logon Account to "symantec", make sure that "system Logon Account" and "Default Logon Account" is symantec.
Now restore any individual item from exchange backups.
Hope this helps...
04-04-2010 10:36 AM
04-09-2010 07:38 AM
Hi Guys,
Sorry for the delay in responding, but we have been busy here plus had the Easter Bank Holiday.
I have followed Dev T's procedure but after talking with a senior colleague he advised:
1. We did not need the account to be a member of Local Admin Group even though Exchange was a member server. He says that if the account has Domain Admin rights it will have Local Admin rights.
2. The account did not need to be an Exchange Server Administrator. Again, the Domain Admin membership is sufficient.
So this is what I did:
Create a new account in AD with following settings:
1 : Member of the Domain Admin group
2 : Created a Mailbox for the account and opened it to activate the mailbox (did not send a test email)
3 : Make sure that the Mailbox is not hidden from the Global Address List.
4 : Open Backup Exec, go to NETWORK--Logon Accounts and Change the Logon Account to the new account.
This worked OK whether the account was the default or simply selected at the time the job was run.
The new account will definitely not work if it's mailbox has not been created and activated.
I still do not know why the original Logon Account started to fail, but it is now redundant and I am using the new account for backups and restores.
Thanks a million for all you help
Best regards,
Michael