<

Changing the Backup Exec Service Account and Password

Posted on
7,900 Points
1,700 Views
2 Endorsements
Last Modified:
Published
Experience Level: Beginner
4:18
Rodney Barnhardt
I have over 30 years in the IT industry. During this time I have worked with a variety of products in a variety of industries.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently changed.

Video Steps

1. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stopped, then more than likely there is a login or account authorization problem.

2. Locate the BEUtility.exe application. This should be located in the installation path, which is generally in the <Drive Letter>:\Program Files\Symantec\Backup Exec folder. The quickest way to locate it in the folder is to type “BEU” in the quick search bar.

3. Once the BEUtility.exe file has been located, double-click it to launch the application

4. Read the warning message about utilizing this utility with technical support. If you still desire to proceed, click Yes.

5. Select All Backup Exec Servers in the middle of the screen, and then select the server where the database is located. The question mark indicates the services are down

6. Right click the selected server and select Change Service Account from the list of options (generally the third option down from the top)

7. Enter the name of the user or system account and the password twice. Then click OK and then Close.

8. Right-click on the server and select Start Services

9. Once all of the services have successfully started, launch Backup Exec and ensure that the application launches successfully

2
0 Comments
Regardless of the size of your organization, there are some common technology mistakes every business must avoid to not impede their ongoing success. These mistakes can lead to data loss or compromise, a lack of consumer trust, and may mean that you…
Tips and tricks to avoid some problems when migrating local user profiles from an old Windows Terminal Server 2008r2 to Windows Terminal Server 2016/2019.