The question "can you manage devices that aren't on our network?" used to be an edge case. Now it's the primary use case for many organisations.
Branch offices without local IT. Kiosks deployed at remote locations. Laptops that travel with users. Devices at partner sites. Machines that were shipped directly to remote workers and have never touched your corporate network. These aren't exceptions anymore - they're how organisations operate.
Faronics Cloud was designed for exactly this reality. This guide explains why off-network management matters, how policies reach remote devices, what visibility you have into off-site endpoints, and how to troubleshoot machines you can't physically access.
Why Off-Network Management Matters
Traditional endpoint management assumed devices lived on your network. Management servers sat in your datacentre. Devices connected to the corporate network, received policies, reported status. The model worked when devices stayed in buildings you controlled.
That assumption has collapsed. Consider how devices actually exist today:
• Branch offices connect over the internet, not dedicated WAN links
• Kiosks and terminals deploy to locations with no IT presence
• Laptops move between home, office, coffee shops, and airports
• Multi-site organisations have devices scattered across dozens of locations
• Remote workers may never visit a physical office
The problem with network-dependent management: If your management tools require devices to be on your network (or VPN-connected), you have gaps. Devices that can't reach your management infrastructure can't be configured, monitored, or controlled. They become invisible until they reconnect - which might be days, weeks, or never.
What cloud-based management solves: Faronics Cloud doesn't require devices to be on your network. Devices connect to the cloud service over the internet - any internet connection, anywhere. Your management capability follows the device, not your network perimeter.
This isn't a feature added to a network-based tool. It's the foundational architecture. Remote management isn't an afterthought; it's the design principle.
How Policies Apply to Remote Devices
Understanding the mechanics helps you trust the system. Here's how policy management actually works for off-site devices:
The agent check-in process. Each managed device runs a Faronics Cloud agent. This agent periodically checks into the Faronics Cloud service over HTTPS. During check-in, it:
• Reports current device status
• Receives any pending configuration changes
• Downloads updated policies if changes have been made
• Executes any queued commands
When you make policy changes. You update a policy in the Faronics Cloud console. The change is stored in the cloud immediately. On their next check-in, devices in that policy group receive the updated configuration and apply it. No manual push required - changes propagate automatically.
Timing and propagation. Devices check in every few minutes under normal conditions. Policy changes typically reach devices within minutes of being made. For urgent changes, you can trigger an immediate check-in from the console, forcing the device to fetch updates now rather than waiting for the next scheduled check-in.
What happens when devices are offline. If a device can't reach Faronics Cloud (no internet, powered off, network issues), it continues operating with its last-received configuration. Protection remains active - Deep Freeze still protects the system, Anti-Executable still blocks unauthorised software, WINSelect restrictions still apply.
When connectivity resumes, the device checks in, receives any accumulated changes, and updates its configuration. There's no timeout that disables protection. A device offline for a week still works correctly; it just hasn't received updates during that period.
No VPN required. The agent uses standard outbound HTTPS connections. If the device can browse the web, it can reach Faronics Cloud. No VPN client needed, no split tunnelling to configure, no connectivity dependencies beyond basic internet access.
Visibility for Off-Site Devices
Managing devices you can't see is anxiety-inducing. Faronics Cloud provides visibility into remote endpoints so you're not flying blind:
Device status at a glance. The console shows each device's current state:
• Is the device checking in? (Online/offline indicator)
• When did it last check in?
• Is Deep Freeze frozen or thawed?
• Is protection active?
• What policy is applied?
Fleet-wide overview. Dashboard views show your entire device fleet. See how many devices are online, how many are frozen, how many haven't checked in recently. Identify devices that may need attention without checking each one individually.
Grouping and filtering. Organise devices by location, function, or any criteria you choose. View just "Branch Office A" devices, or just "Kiosks," or just "Devices offline more than 24 hours." Filter and sort to find what you're looking for.
Historical information. See when devices last rebooted, when policies were last applied, when protection state changed. This history helps you understand device behaviour over time, not just current state.
Proactive awareness. Devices that haven't checked in recently stand out. Rather than discovering problems when users complain, you can identify devices that may need attention before issues escalate.
Location doesn't affect visibility. A device in another country looks the same in your console as one in the next room. You have identical visibility regardless of where devices physically sit.
Troubleshooting Remote Endpoints
When something goes wrong with a remote device, you need options beyond "have someone look at it." Here's how to troubleshoot off-site endpoints:
Start with status. Before anything else, check the device in Faronics Cloud. Is it online? When did it last check in? Is it frozen or thawed? What policy is applied? Often, status information reveals the issue - or at least narrows the possibilities.
Remote commands. Faronics Cloud lets you send commands to remote devices:
• Restart the device
• Thaw or freeze Deep Freeze
• Refresh configuration
• Force an immediate check-in
Commands queue and execute when the device checks in. For urgent issues, trigger an immediate check-in first.
Reboot as first response. For Deep Freeze-protected devices, rebooting solves most problems. User complains something isn't working? Schedule a remote reboot. Deep Freeze restores the machine to its baseline state. This works regardless of whether you understand the specific problem - a significant advantage for remote troubleshooting.
Configuration adjustments. If the problem is configuration-related (restriction too tight, needed software blocked), adjust the policy from the console. The change propagates to the device on next check-in. You can fix configuration issues without physical access.
Scheduled maintenance. For issues requiring changes to the frozen baseline, schedule a thaw window. The device thaws at the scheduled time, allowing changes to persist. Combine with Remote Pro, part of Faronics Cloud, if you need to make manual changes during the thaw window.
Combining with remote access tools. Faronics Cloud manages Faronics protection; it's not a general remote access tool. For hands-on troubleshooting, combine it with remote desktop or remote access software. Use Faronics Cloud to thaw the device, then connect via remote access to investigate and fix, then refreeze via Faronics Cloud.
When remote troubleshooting isn't enough. Some issues require physical access - hardware failures, severe OS corruption, problems preventing the agent from functioning. For permanently-deployed devices (kiosks, branch equipment), have a process for dispatching service when remote options are exhausted. The goal is to resolve 90% of issues remotely; the remaining 10% still need physical intervention occasionally.
Common Remote Management Scenarios
Here's how remote management plays out in practice:
Scenario: User at branch office reports software not working.
1. Check device status in Faronics Cloud - device is online, frozen
2. Send remote reboot command
3. Device reboots, Deep Freeze restores baseline
4. User confirms issue resolved
Scenario: Kiosk at remote location showing wrong configuration.
1. Check device status - last check-in was days ago
2. Contact location to verify kiosk is powered on and connected
3. Location confirms network cable was unplugged - reconnects it
4. Device checks in, receives pending policy updates
5. Configuration corrects automatically
Scenario: Need to add software to all remote training room PCs.
1. Schedule thaw window for overnight
2. Devices thaw at scheduled time
3. Use Software Updater, part of Faronics Cloud, to install software during thaw
4. Devices refreeze with new software in baseline
5. Confirm in Faronics Cloud that devices returned to frozen state
Frequently Asked Questions
How quickly can I respond to remote device issues?
Immediately, if the device is online. Check status, send commands, adjust configuration - all from your browser, anywhere you have internet access. For Deep Freeze devices, a remote reboot often resolves issues within minutes.
What if a remote device can't reach Faronics Cloud?
Protection continues locally with the last-applied configuration. You can't send new commands until connectivity is restored, but the device isn't unprotected - it's just not receiving updates. Most connectivity issues are local (unplugged cable, Wi-Fi problem) and resolve when connectivity returns.
Can I manage devices in different time zones?
Yes. Maintenance windows and scheduled actions can use local device time. A thaw scheduled for "2:00 AM" happens at 2:00 AM wherever the device is located. You can also create separate policy groups for different regions with region-appropriate schedules.
Do I need line-of-sight or any special network path to remote devices?
No. Devices connect outbound to Faronics Cloud over standard HTTPS. You don't need direct network access to devices, no VPN tunnel, no port forwarding. If the device can reach the internet, you can manage it.
Is remote management secure?
Yes. All communication is encrypted via TLS. Agent-to-cloud authentication ensures only your devices connect to your account. Console access requires authentication. The cloud architecture is often more secure than exposing on-premises management ports to the internet.
The Bottom Line: Manage Anywhere, From Anywhere
Yes, Faronics Cloud can manage remote and off-site devices. More than that, it's designed around the assumption that devices won't be on your network. The cloud architecture makes location irrelevant to management capability.
Policies propagate automatically. Visibility is consistent regardless of device location. Troubleshooting happens remotely for most issues. You manage devices from wherever you are, regardless of where they are.
For organisations with distributed devices - branch offices, remote locations, travelling users, deployed kiosks - this changes what's possible. No local infrastructure required. No VPN dependencies. Just internet connectivity and a browser.
Ready to Manage Your Remote Devices?
Try Faronics Cloud free for 30 days. Experience off-network endpoint management for yourself.
