Remote Shutdown Software

[Vanya Lamunyon]

Goto command prompt (start > run > cmd) on your workstation... and Typeshutdown -r -m \xxx.xxx.xxx.xxxReplace xxx.xxx.xxx.xxx with the IP address or computer name of the remote machine. -r option is for restart, don't use -r if want to just shut down the system.

shutdown -i gives you a nice simple little GUI for the shutdown command where you can target one or more machines, choose shutdown or restart, set the countdown timer etc.This is the command I always use when I want to restart a remote machine.

I do this at home. Start > Run cmd.exe and type in shutdown -s -t 60 (I always use -t 60 because I'll forget that I need to do something right when I press enter. shutdown -a will abort a shutdown if it isn't too late.)

And the 2nd part of my question is whether Labview RT supports a way to programatically shut down the controller? I'd like the controller to shut down when the startup application terminates. I've found the RT Restart Target VI, but not one for shutting down.

Power management on a PXI controller isn't well supported (or supported at all, really). WoL is only supported via Windows, LabVIEW Real-Time does not support the WoL feature. Shutting the controller down is only supported in LabVIEW 2012 and newer via the power button on an express chassis; LabVIEW Real-Time cannot programmatically kill the power on the controller, but it can put itself into a safe state (i.e. shut down) when the power button tells it that, "it has 13 seconds to shut down or else."

Other than saving power (which is a perfectly valid reason for a feature, by the way), why do you want a remote power capability for your PXI? It seems to me that something like "Wake on Lan" still requires power, as the remote system needs enough power to monitor and respond to the Lan inquiry and thereby switch on the power.

Which, of course, points to a way to solve your situation. Take a system that has WoL capabilities (say, a Windows PC). When it "wakes", all it needs to do is to power-on the PXI (surely there are ways of turning on and off Power Strips remotely or via a TTL signal). The PXI, if it is running a LabVIEW RT system, will auto-start the program -- this solves "getting the system started".

How about shutting the system off? Well, the PXI code can, on exit, reboot itself. Just before that, it could send a TTL signal to the Power Strip that says "Shut off the power in 5 seconds" (or however long it takes to finish the shutdown and restart the boot process).

As your note points out, turning a PC on and off is pretty simple -- you basically "short" Pin 6 to Pin 8 on the PC motherboard's Power Cable (I think it is called something like JFP1). However, doing this with a PXI is probably different -- my chassis has a mechanical on/off switch ...

The SignalFire RSDS can be implemented with a PLC monitoring inputs and generating control commands via the SignalFire Gateway and Counter Stick I/O node. Or, in environments where a PLC is not required for other needs, the SignalFire Gateway can monitor inputs and generate control commands autonomously as a stand-alone system.

The Remote Switch option allows for a standard RSD System to be configured for use as a stand alone system without a Gateway. Using a simple table based configuration the system can be setup to switch the relay outputs when one (or more) remote nodes reaches a limit. A typical application is to shut off a well when one or more remote tanks become full.

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Does anyone have experience of this, please?

We have Panorama in the environment, so alternatively, can this be achieved via ssh to the Panorama VM instance, which would then shutdown all managed firewall devices?

Many thanks,

Tim

Just a note on actually issueing the shutdown command however; are you sure that you actually want to do this? If the power is restored to the UPS before the battery runs out the firewall will actually need to be unplugged and plugged back in to power back on.

Thank you. I'd looked at the API but wasn't sure (this is not my area of any kind of expertise) how to use it.

e.g. so how would I invoke those commands post login?

The entire shutdown for the DC is being driven through PowerShell and PowerCLI, so the commands to login, authenticate and initiate shutdown have to be scripted for no manual intervention.

Tim

Thanks again.

@BPry Yes, I'm absolutely sure I want to do this. There's no issue with the manual/disconnect reconnect action post shutdown. That's been taken into consideration as part of the overall design.

Remote computer administration refers to any method of controlling a computer from a remote location anywhere in the world. Remote administration among other things includes the ability to shut down or restart a computer. If you have two or more computers connected to your home or office network, or even outside your network, you can use one of them to shut down the others remotely. Windows, Linux, and Mac computers all support this feature.

The net use command enables you to connect to, remove, and configure connections to shared resources such as mapped drives and network printers. You can also use it to shut down or reboot a remote computer. It does this using various parameters and switches. The command is available from the Command Prompt in Windows desktop (Windows 10/8/7) and server (server 2008/2016/2019) operating system.

To use the net use command to shut down or restart a computer over the network, you need to disable the User Account Control for remote executions in the registry by following the steps below:

PowerShell is a cross-platform task automation solution from Microsoft, consisting of a command-line shell, a scripting language, and a configuration management framework. PowerShell runs on Windows, Linux, and Mac. PowerShell can be used to perform the shut down of remote computers in bulk without enabling remote shut down capability.

Shut down using specified authentication: You may want to shut down a remote computer using specified authentication. This is where the WsmanAuthentication parameter comes into play. In the example below, the WsmanAuthentication parameter specifies using Kerberos to establish a remote connection.

Shut down on behalf of a specific account: If you need to perform a shut down on behalf of a particular account, then you can use the -Credential switch as shown below, which requires the domain name (domain01), the username (user001), and password when prompted:

Shut down multiple computers in a domain: A situation may arise where you are required to shut down multiple computers in a domain. The Stop-Computer command can easily cope with this task, but first, you need to create a text file containing a list of computers (in a single column) that need to be shut down, and then execute the command as shown below:

This method provides a GUI that makes sending the shutdown command to a remote computer across the network more accessible. This is where the shutdown\i command comes into play. This command brings up a graphical dialog that lets you select the remote computer or enter its name or IP address using the Add button. You can then specify whether you want to shut down or restart, including an option to add a comment.

Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft which provides a user with a graphical interface to connect to another computer over a network connection. To initiate an RDP connection, an RDP client and server software are required at the local and remote computers, respectively. Fortunately, all of these come pre-installed on Windows machines. RDP clients are also available for most versions of macOS, Linux, Android, and iOS. An open-source version is also available.

RDP saves you the headache of configuring and using the command line approach to shutting down and restarting remote computers. However, you may be required to configure port forwarding on your router if the remote computer is outside your network. Follow the steps below to shutdown a remote computer using RDP:

Apart from the built-in shut down commands and other embedded tools that can be used to shut down/restart a local or remote computer, there are lots of free and commercial third-party remote administration tools out there that can equally do the job, if not better. In addition, third-party tools are much simpler to configure and use than most built-in tools.

Other systems to try include TeamViewer, TightVNC, LogMeIn, PuTTY, Symantec pcAnywhere, ManageEngine Shutdown / Restart Tool, and a host of others including remote access VPN applications. The only downside is that some third-party tools require their software installed on both local and remote computers.

We have discussed various methods you can use to shut down or restart a remote computer. While remote computer administration, including the ability to initiate a shut down or restart, has many legal uses and offers many benefits, there are also security implications.

Cybercriminals may be able to take advantage of the configurations and settings that allow remote administration, as well as existing loopholes to gain remote access to your computer and carry out malicious activities. Therefore, you must adhere to secure remote access practices and ensure that appropriate security measures are in place to prevent security breaches.

3a8082e126