Network Actions

You can execute different network actions on clients managed by ERA Server. If you right-click a client in the Clients tab of ERA Console and select Network Actions, you are presented with several options: Ping, Wake On LAN, Share, Shutdown/Restart, Message, RDP or Custom... . These network actions correspond to Windows network actions and have the same functionality.
Every network action you run (except the Ping) will inform you about the state of the action via a progress bar in the dialog window. The table below lists the available network actions, the generic windows command they execute (unless implemented another way in ERA Server) and some of the prerequisites. In many cases, not all Prerequisites have to be satisfied or additional prerequisites are not mentioned here. This table is contains the recommended course of action to resolve most issues.

Network Action

Command

Prerequisites

ping

-

ICMP enabled on firewall

Wake on Lan

-

Network card of the selected computers must support the standard Magic Packet format

Wake On Lan must be configured in BIOS of the selected computers and configured in their network card

more information in the dialog window itself

Share

explorer.exe \\<computer>

sharing enabled on the target computer

firewall exception for sharing

Shutdown/Restart

shutdown /s /t <timeout> /c "<reason_comment>" /f /m <computer>

when restart is selected, there is /r instead of /s

if „Reason comment“ is empty, there is no /c "<reason_comment>"

if „Force applications to close“ is unchecked, there is no /f

if „abort shutdown action“ is checked, it is always only shutdown /a /m <computer>

Remote Registry service enabled

Windows Management Instrumentation service enabled

Windows Management Instrumentation (WMI) firewall exception

current Windows user on the console computer must have administrator permissions on the target computer (this assumes a domain environment)

running it under administrator account on the local computer

Add credential:

a.Look up the Credential Manager of Windows

b.Click the Add a Windows Credential

c.Enter the name of the target computer (or IP address), username and password on that target computer

Message

msg.exe /SERVER:<computer> * "a"

But, on Windows 2000 it is:
net send <computer>

registry change:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server
 
Name: AllowRemoteRPC
Type: REG_DWORD
Value: 1

run ERA under the administrator account on the local computer

Add credential:

a.Look up the Credential Manager of Windows

b.Click the Add a Windows Credential

c.Enter the name of the target computer (or IP address), username and password on that target computer

RDP

mstsc.exe /v <computer>

 

custom - you can execute any custom command valid for cmd.exe

The Command is executed on the computer where the ERA console is running (so executing the Command using cmd.exe on the console computer should behave exactly the same and can be used to determine what is wrong). The <computer> is replaced by the target computer host name or IP address based on "Use hostname instead of IP address when executing a Network Action" setting in Tools > Console Options > Other Settings in ERA Console.

Some commands work better in a domain environment – when logged in as a domain user (which has administrator privileges on the target computer) there is no need to Add credential.