Remote terminal

With Server Automation, you can log on to a managed server in a terminal window in two ways:

• Using the Remote Terminal, as described here.
• The rosh command entered in a Global Shell session.

The remote terminal opens a terminal window for UNIX servers or an RDP client window for Windows servers. Unlike a Global Shell session, a remote terminal session does not provide access to the OGFS.

You can specify your terminal and RDP client preferences for remote terminal and Global Shell sessions in the Set Preferences window. See Terminal and shell options for more information.

Prerequisite for a remote terminal

Logging into a remote server requires that you have SA login permissions on the managed server. See the SA 10.51 Administer section for more information. You cannot log into a remote terminal with a user name or password that contains multi-byte characters.

To open a remote terminal session on a Windows managed server running Windows Firewall, you must set an exception that is not enabled by default. On the managed server, run Windows Security Center, then select Windows Firewall > Exceptions > Remote Desktop.

This feature must be able to establish a loopback connection on the machine running the SA Client. Some firewall and VPN utilities have settings that prevent loopback connections.

Opening a remote terminal

In the Device Explorer of the SA Client:

1. Select a managed server.
2. Open the managed server.
3. From the Actions menu, select Remote Terminal.