Forum Discussion

Marduk's avatar
Marduk
Level 4
13 years ago
Solved

TERMINAL SERVICES CLIENT IN BACKUP EXEC 2012

Hello, can someone explain to me what is this message that I get when I do the installation of Backup Exec 2012.

 

 

This application is being run ion a terminal services client in remote administration mode.

 

installing backup exec using a terminal services client is not supported. see the backup exec administrator guide for instructions on installing backup exec

2012
Backup and Recovery
Backup Exec
  • CraigV's avatar
    CraigV
    13 years ago

    Hi,

     

    You'd get this message if you were installing via an RDP connection. I've seen something similar with BE 2010.

    Launch the connection the the mstsc /admin switch and see if you still get it.

    THat said, it's just a warning and shouldn't stop the installation at all...ignore if so!

    Thanks!

  • CraigV's avatar
    CraigV
    Moderator
    13 years ago

    Hi,

     

    You'd get this message if you were installing via an RDP connection. I've seen something similar with BE 2010.

    Launch the connection the the mstsc /admin switch and see if you still get it.

    THat said, it's just a warning and shouldn't stop the installation at all...ignore if so!

    Thanks!

  • Marduk's avatar
    Marduk
    Level 4
    13 years ago

    oh grait!!!! i am installing BE 2012 to RPD. beacuse the server this in other side

  • John_Bonaccorso's avatar
    John_Bonaccorso
    Level 4
    13 years ago

    **** Please do not make any changes to the registry without backing it up first ****

    **** Always test registry changes on a non-production machine first ****

    Marduk, CraigV is correct.  As long as you are an administrator on the server and if UAC is enabled, you are "Running as Administrator" you'll be good to go.  Also, your DEP (Data Execution Protection) settings can interfere with the installation process.

    The reason more and more software vendors are putting this "warning" in their products is because some of the still supported operating systems came with some pretty cool lock-down features that vary from OS to OS such as the "Restricted" group in Windows 2003/R2 whose membership is hard-coded to include anyone logged on via RDP.  The default permissions in the registry lock such users down to READ on many of the hives.  This can be circumvented/mitagated by removing the "Restricted" ACE from every ACL that is affected, or simply grant "Restricted" Full control of those hives.

    Bottom line, they are basically saying, they will not help you with any trouble you have installing it that way.  Not saying they won't help you but they will likely insist that you do the install at the console or via a product that will remote control the console session on the server.