_a9c1b4.png){kind=logo}
_49ee3f.png){kind=logo}
Search the Community
Showing results for tags 'Features'.
Found 6 results
-
You know that moment when you realize you’ve been doing something the hard way for years? Here’s how to upload and download files without opening a remote session: Open the device card for the machine you want to access Head to the Storage tab You’ll now see Upload and Download options (yep, both!) Upload any file or folder directly to the device Download files off the device—downloads as a ZIP, easy to extract This feature works on Windows, macOS, and Linux! Bonus: Use automation workflows to push files across multiple machines 💥 -
-
Your IT toolbox just got upgraded. Here are the top features to look out for: 🖥️ Peer-to-Peer Remote Control — now when you remote into Windows machines, Pulseway establishes a direct P2P connection, reducing latency and making your remote sessions much smoother. 🕰️ Ad-hoc Automation Scheduling — with Run Later you can now schedule ad-hoc scripts and workflows to execute at a specific date & time. Perfect for off-hours maintenance without disrupting end users. 🗂️ Hierarchical Automation Structure — a new folder hierarchy for Scripts, Tasks, Workflows & Managed Files. Default system content, pre-built packages, and your own creations are now neatly separated. 📊 Patch Status Page Enhancements — the updated Patch Status page shows live deployment progress per patch and allows you to drill down by device. Instantly see which devices are deployed, pending, failed or waiting for reboot. 📂 Background File Transfer — transfer files and folders across Windows, macOS & Linux — without starting a remote session or bothering the end user. Upload, download or delete files directly from the device card’s storage browser. 📋 Policy Extensions — you can build one master policy and fine-tune it per org, site or group as needed. Managing policies is simpler than ever, with streamlined cloning, importing, and exporting. Read more about these releases here: Release Notes
-
Sick of typing “browser not working” like it’s Groundhog Day? We feel you. Your techs have better things to do than copy-paste the same ticket info 47 times a week. Here’s the scenario: A user skips the portal and pings your technician directly (again). Now they have to create the ticket manually. But instead of starting from scratch every time, Pulseway lets you use ticket templates to fill in the usual stuff fast. ⚡ Let’s break it down: Template Time: Create templates for common issues like browser errors or password resets—with fields already filled in and a couple quick prompts for the user. 📝 Timer: Pulseway auto-tracks time spent on tickets so your team doesn’t have to guess later. ⏱️ Pull Reports: Use those tracked hours to show higher-ups how much time goes into common issues—and make the case for more hands on deck if needed. 📊 Got a ticketing pain point you want us to cover next? Drop it in the comments—we’re listening. 👇
-
Pulseway allows you to restrict access for Dashboard and Web Application by IP Address so only designated IPs will be able to connect. To add a restriction start Pulseway on a monitored PC and click "Change Account Details". On the account detail you can add IP addresses that are allowed to access either Dashboard or Web App or both. -
Pulseway supports Wake on LAN and Wake on WAN over Internet. The mobile application will send a magic packet in LAN while on WiFi. As well, our cloud servers will send the same magic packet to the public IP address on UDP 9 (you can change the port number and assign a different port number for each computer using the Pulseway app installed on your PC, go to System->Wake on WAN over Internet, default is 9). Please make sure that the router forwards those packets in the LAN and that the PC supports Wake on LAN (check BIOS and network interface settings). The only limitation at the moment using Wake on WAN over Internet occurs when our cloud servers have the last public IP used by your computer and your public IP changes. The magic packet will be sent to the last known public IP and will fail to wake the computer. We are planning to solve this problem in the future using a different method.