Administrators can administer from remote hosts in several ways that are described in this guide, as summarized below:
After logging in to the local host and assuming a role, administrators can log in to a remote host from a terminal in their role workspace and use the commands rlogin(1), telnet(1), or ftp(1). See "To Log In Remotely From the Command Line" for how roles can log in remotely and work on the command line.
From a local host's CDE login screen, anyone can log directly into the CDE window system on a remote host (as described in "To Log In and Assume a Role"). . This works just as it does on a Solaris system.
After CDE remote login is complete, the CDE window environment from the remote host displays on the screen of the local host. An administrator can then assume a role from the Trusted Path menu and work as if logged in directly to the remote host.
Administrators can launch a Solaris Management Console (SMC), server that is running on a remote host. Accessing the SMC is described in "To Launch the Solaris Management Console".
The Application Manager can be started remotely by double-clicking the Application Manager icon from the Legacy Application list in the SMC. The Application Manager contains the System_Admin folder, a collection of programs to modify local system files that are not managed directly by the Solaris Management Console.
While working in a role workspace on a local host, the role can use the dtappsession(1) command to launch an Application Manager that runs and makes changes on the remote host. The dtappsession script starts an independent instance of the CDE Application Manager that runs on the remote host and displays on the local host. Unlike CDE remote login, dtappsession enables the administrator to work remotely within a local login session.
dtappsession is useful when a remote host does not have a monitor. For example, dtappsession is often used instead of CDE remote login when administering domains on large servers, such as a Sun EnterpriseTM 10000.