Video Screencast Help

Failed to make server a Managed Media Server

Created: 05 Apr 2012 • Updated: 01 May 2012 | 4 comments
This issue has been solved. See solution.

I have a Backup Exec 2010R3 server running CASO.  I wanted to add some Backup Exec 12 and 12.5 servers to be managed by it so I could report off the jobs in one central console.  Is it possible to add servers to CASO that are different verisons?

When I try to add them using BEUtility > Set Central Administration Server I get 

"Failed to access the registry keys of selected server SERVERNAME to get the Backup Exec version numbers."

Job ended with errors.

Comments 4 CommentsJump to latest comment

Backup_Exec's picture


On first place recommended and best way would be having backupexec on same version on CASO and MMS ,so I will recommend you to upgrade MMS on same level as CASO & then try to join them as MMS should work fine



Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

RahulG's picture

You may also refer and see if it helps.

However please see pg.1522 of the Admin Guide. - Backup Exec 2010 R2/R3 Administrator's Guide.

Symantec recommends that you do not keep a mix of versions in the CASO installation for an extended time. Key functionality for administering managed media servers is missing in a mixed-version environment, and decreases your ability to properly administer the CASO environment.

After you upgrade the central administration server to Backup Exec 2010, the following operations are supported on managed media servers that run Backup Exec 12.5:

■ Backup

■ Restore

■ Inventory

■ Catalog

CraigV's picture

Hi Jesse,

Much like an upgraded version of BE will work 1 version back, CASO does the same. Unfortunately those versions you have are too many revieions behind, and the system has changed between versions.


Alternative ways to access Backup Exec Technical Support:

JessePAIT's picture

It turns out that I could not add the 12.5 server to be managed by the new CASO installation because Backup Exec only supports upgrades on an existing installation of CASO, in my instance I had a brand new server with a brand new installation of Backup Exec and you can't point existing Backup Exec installations to point to a new CASO server