Sometimes the fix is simple: turn it off and on again. The problem is getting to the machine to do it. When you're managing devices across multiple buildings, multiple sites, or from home, walking to each computer isn't practical.
Remote device control solves this. From the Faronics Cloud console, you can restart computers, shut them down, wake sleeping machines, and trigger other power-related actions - all without leaving your desk. A computer acting up in Building C? Restart it from your office in Building A. Need to wake a lab for maintenance at 2 AM? Do it from home.
This guide explains what remote actions are available, when they're most useful, and how remote control reduces the need for on-site visits.
Remote actions explained
Here are the remote control capabilities available through Faronics Cloud.
Remote restart
The most commonly used remote action. A remote restart does exactly what it sounds like - reboots the computer remotely.
- How it works: Select the device (or multiple devices) in the Faronics Cloud console and issue a restart command. The command is sent to the device's agent, which initiates a system restart.
- What happens on the device: The computer restarts. If Deep Freeze is active, the machine returns to its frozen baseline - this is why remote restart is so powerful. It's not just a reboot; it's a restoration to a known-good state.
- Requirements: The device must be online and connected to Faronics Cloud. You can't restart a machine that's already powered off or disconnected from the network.
Remote shutdown
Shut down computers remotely when they should be off:
- How it works: Issue a shutdown command from the console. The device receives the command and initiates a proper Windows shutdown.
- Use cases: End-of-day shutdown across a lab. Powering off devices before a holiday closure. Energy saving by ensuring computers aren't left running overnight.
- Considerations: Once shut down, the device can't receive further commands until it's powered back on (unless Wake-on-LAN is configured). Use shutdown when you genuinely want machines off, not when you might need them again soon.
Wake-on-LAN
Wake sleeping or powered-off computers over the network:
- How it works: Wake-on-LAN (WoL) sends a special network packet - a "magic packet" - to the device's network adapter, which triggers the computer to power on.
- Requirements: The device's BIOS/UEFI must have Wake-on-LAN enabled. The network adapter must support WoL. The device must be connected to power (obviously) and connected to the network (usually via Ethernet - Wi-Fi WoL support is inconsistent).
- Limitations: Wake-on-LAN works best on local networks. Waking devices across different subnets or over the internet requires additional network configuration (directed broadcasts or WoL relays). Devices that are completely powered off (rather than in sleep/hibernate) may or may not respond, depending on hardware and BIOS settings.
- Best practice: For reliable WoL, configure devices to sleep rather than shut down. Sleep mode keeps the network adapter powered and listening for wake packets.
Remote freeze and thaw
Control Deep Freeze state remotely:
- Remote thaw: Unfreeze a device to allow changes. Useful for one-off updates, software installations, or troubleshooting that requires persistent changes. The device becomes modifiable until you refreeze it.
- Remote freeze: Lock down a thawed device. After making changes, freeze the device to protect the new baseline. Useful when you've finished maintenance and want protection restored.
- Thaw with reboot options: You can thaw for a specific number of reboots or until a certain time. The device automatically refreezes after the specified condition is met - no need to remember to manually refreeze.
Force check-in
Request an immediate status update:
- How it works: Devices normally check in every few minutes. A force check-in command requests immediate communication, updating status and applying any pending policy changes.
- Use cases: Verifying a device is online and responsive. Pushing policy changes immediately rather than waiting for the next scheduled check-in. Confirming a remote action completed successfully.
Bulk actions
Apply remote actions to multiple devices at once:
- Select multiple devices in the console
- Apply the same action to all selected devices
- Restart an entire lab with one command
- Shut down all devices in a building at end of day
This scales remote management. Restarting 30 computers takes the same effort as restarting one.
When Remote Control helps most
Remote device control is useful in many situations, but some scenarios show its value most clearly:
Remote troubleshooting
When a user reports a problem, remote restart is often the first step:
- User reports: "Computer in Room 204 isn't working right"
- You check the device status in Faronics Cloud - it's online, frozen
- You issue a remote restart command
- The computer reboots and restores to its baseline
- You verify it's back online and frozen
- Problem resolved - no physical visit needed
For Deep Freeze-protected machines, a remote restart often is the fix, not just a diagnostic step. Whatever was wrong is cleared by the reboot.
Preparing devices for use
Ensure devices are ready before users arrive:
- Before exams: Restart all exam room computers to guarantee clean, consistent state. Every machine starts fresh with identical configuration.
- Before training sessions: Restart training room PCs to clear any residue from previous sessions.
- Before opening: Libraries or public computing centres can restart all public PCs before doors open, ensuring every machine is in known-good state.
After-hours management
Handle issues without being on-site:
- Evening maintenance: Wake devices, trigger maintenance actions, verify completion - all from home.
- Emergency response: Issue reported after hours? Restart the device remotely. If that resolves it, no need to go in.
- End-of-day shutdown: Ensure all devices are properly shut down even if you've left the building.
Multi-site management
When you're responsible for devices across multiple locations:
- Manage all sites from one console
- Issue commands to any device, any location
- No driving between sites for routine tasks
- Handle urgent issues at remote sites immediately
A multi-academy trust IT team can manage computers across all schools from a central location. A library system can manage branches across a county. Geography stops being a barrier.
Energy and cost management
Remote power control supports energy efficiency:
- Scheduled shutdown: Ensure devices aren't running overnight or during holidays when they shouldn't be.
- Wake when needed: Keep devices asleep until actually needed, then wake them for use or maintenance.
- Verify power state: Check which devices are running and shut down any that shouldn't be.
Avoiding on-site visits
Every on-site visit has a cost: travel time, interruption to other work, wear on vehicles if driving between sites. Remote control reduces these visits significantly:
- "Computer isn't working": Remote restart - if it fixes it, you're done
- "Computer is frozen/stuck": Remote restart
- "Something's wrong after the last user": Remote restart restores baseline
- "Computers were left on overnight": Remote shutdown
- "Lab needs preparing for tomorrow": Remote restart all devices
- "Verify everything's working before an event": Check status, restart any that show issues
- "Apply urgent configuration change": Update policy, force check-in, restart if needed
What still requires a physical visit
Remote control doesn't eliminate all visits - some things need hands-on attention:
- Hardware failures: Dead drives, broken screens, failed power supplies
- Network connectivity issues: If a device can't reach Faronics Cloud, you can't control it remotely
- Power problems: Devices that won't power on (and WoL isn't working)
- Physical setup: New device installation, cable management, peripheral setup
- Persistent software issues: Problems that survive reboot (rare with Deep Freeze, but possible if the baseline itself has issues)
The goal isn't zero visits - it's eliminating unnecessary visits. Many "computer problem" calls become remote restarts rather than physical trips.
Decision framework: remote first
When an issue is reported, start with remote options:
- Check status: Is the device online? What state is it in?
- Try remote restart: For most issues, this is the first response
- Verify result: Did the device come back online? Is it in the expected state?
- Check with user: Did the problem resolve?
- Visit only if needed: If remote actions don't resolve it, then go on-site
This approach resolves many issues in minutes rather than requiring a trip that might take an hour including travel time.
Frequently asked questions
What if someone is using the computer when I restart it?
The restart happens regardless - there's no "are you sure?" prompt to the user. Best practice is to verify no one is using the machine before restarting, or communicate with on-site staff. For scheduled restarts (like before exams), ensure the timing is clearly communicated so devices are clear of users.
How quickly do remote commands execute?
Commands typically execute within seconds to minutes. The device needs to receive the command during its next check-in. Force a check-in first if you need immediate action. Network conditions and device state can affect timing.
Can I schedule remote actions?
Yes. Maintenance windows schedule thaw/freeze cycles automatically. You can also schedule restarts and other actions for specific times - useful for "restart all library computers at 6 AM before opening."
What happens if a remote restart fails?
The console shows command status. If a restart doesn't complete successfully, you'll see the device isn't responding or hasn't come back online. This usually indicates a deeper issue - hardware problem, network issue, or a device that's already powered off - that may require a physical visit.
Can remote actions work over the internet, or only on the local network?
Restart, shutdown, freeze/thaw, and check-in commands work over the internet - they go through Faronics Cloud. Wake-on-LAN is more complex; it works best on local networks and requires additional configuration for remote wake across the internet.
The bottom line: control without walking
Faronics Cloud puts essential device controls at your fingertips. Restart computers to resolve issues and restore baselines. Shut down devices that should be off. Wake machines for maintenance. Control Deep Freeze state. Do all of this from wherever you are, for devices wherever they are.
The practical impact: fewer trips to physically touch machines, faster resolution of reported problems, and the ability to manage devices after hours without being on-site. For IT teams managing distributed devices - across buildings, campuses, or regions - this transforms what's possible.
Start with remote control. Visit only when you must. That's efficient device management.
Ready to manage devices remotely?
Try Faronics Cloud at no obligation for 30 days. Experience remote control for yourself.
