Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare Remote Support User Guide > Remote system tasks and views > Remote Command view

Remote Command view

Table of contents
No headers
Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Jul 12, 2016

Views: 30 Votes: 0 Revisions: 2

DameWare Remote Support provides a Remote Command View and Remote Command Console that enables you to execute commands and kill processes on remote systems. When you select either of these options for a remote system, DameWare Remote Support determines whether Remote Support's service is installed or not. If it is not, Remote Support asks you whether it should install the DameWare Remote Support service on the remote system. With the DameWare Remote Support service installed, the Remote Command View/Console connects with the Remote Support service on the remote system and displays the Status, Remote Command Ready.

You can stop and restart the DameWare Remote Support service at any time from the Remote Command View by clicking the corresponding buttons on the mini-toolbar. For example, stop the service if you want to keep the service installed on the remote system, but would like to conserve memory while the service is not being used.

Remote Command from Remote Support is secure in two ways:

  • The logged on user must have interactive logon privileges on the target computer in order to connect to it.

  • Any programs executed on the target computer are executed impersonating the logged on user. Any access validation (such as opening files) is performed as if the user were logged on to the local computer.

Notes:

  • All Windows Workstation users have interactive logon privileges by default. Anyone who can locally log on to your system can transparently access it over the network unless you configure it otherwise. For Windows Server users, however, only system administrators have this privilege.

  • Executing START on the remote computer will result in spawning detached processes. These processes are not "connected" (that is, no input or output is possible) and will not be killed when you exit the remote command shell. This wastes resources on the remote computer.

  • The standard users environment is not set up in the remote command shell. Any environment must be set up explicitly during the command session.

Last modified
14:47, 12 Jul 2016

Tags

Classifications

Public