Mariale_Pulseway

Hey @ic-kfisc - Thanks for reaching out! I just raised a ticket for you and our support team will reach out shortly😊

Hey @Jason Beaver - Thanks for the feedback. I'll pass this to our product team😊

Pulseway 9.25 is live — and this release focuses on strengthening security, improving control, and giving you better operational visibility across your environment. This update sharpens compliance, streamlines automation governance, and enhances device management across macOS and iOS — all while keeping workflows smooth and scalable. Highlights in this release: Modern M365 OAuth authentication: outbound email now uses secure OAuth instead of basic auth, eliminating stored credentials and aligning with Microsoft’s deprecation timeline. Remote Control On-Demand for macOS: initiate remote sessions when needed, giving technicians flexibility while maintaining user transparency. Automation Hub folder permissions from Teams & Users: manage access directly from the RBAC layer, making governance cleaner and easier to scale. Patch Status reports: improved reporting visibility to track compliance and patch health across devices. Enhanced iOS MDM location tracking: access location history and richer device location details for better mobile oversight. 📄 Full release notes available here.

Hey @PK_GIT - Thanks for reaching out. I just raised a ticket for you and our support team will reach out shortly to assist you with this😊

Hey @Mike Shevenell - It’s certainly a hack that we had shared, but as I said there is no support on that. You can create/make changes. We have some library on that too on the forum.

Hey @Mike Shevenell - Thanks for reaching out. This is legacy and is no longer supported.

Hey @DJB - Thanks for reaching out. It hasn't been removed. Here's what to do: Click on Storage tab Choose your logical drive C: / D: / E : Then you will options to Upload / Download / Move To Refer to image.

Hey @John D - I just raised a ticket to support about this and they'll contact you shortly😊

Hey @MrMattiPants - Thanks for reaching out. I just submitted a ticket for you and our support team will contact you shortly🙂

Hey @IAndras - Thanks for reaching out. I just raised a ticket on your behalf and someone from our support team will get in touch shortly😊

Hey @aoarms - Thanks for reaching out. I just raised a ticket on your behalf and someone from our support team will get in touch shortly😊

Hey @jrmcanada - Thanks for reaching out. I just submitted a ticket on your behalf and our support team will reach out shortly😊

Hey @Joe Patrick Wertz - Thanks for reaching out. The maintenance mode can only be applied when the device is online and when it needs to be disabled once it's back online. You can use the Workflow adhoc/scheduled that gets queued if the device is offline.

Hey! @Hect0r - Thanks for reaching out! Just make that the policy is applied to the machines its needed for. Refer to images. If you have more questions, let me know😊

Hey @Alexx - I just raised a ticket on your behalf about this and someone from our team will assist you shortly😊

Starting the new year with the right foot: Pulseway 9.24 is live 🚀 Pulseway 9.24 is all about working faster with fewer obstacles. This release sharpens day-to-day workflows with improvements focused on technician efficiency, automation control, and clearer visibility across your environment. Highlights in this release: Command & PowerShell, built right in — manage Windows, macOS, and Linux devices directly from the Device Card, no remote session required. RBAC for Automation Hub folders — granular, team-based access so the right people can view, run, or edit automations (and nothing more). More flexible workflow scheduling — run workflows every 3–12 hours for tighter automation without overlap. Monitoring alerts with direct policy links — jump straight from an alert to the exact policy and profile that triggered it. Better mobile visibility — filter devices in the mobile app and track managed iOS device locations with ease. 📄 Full release notes available here.

Hey @NavNet_Aidyn - Thanks for reaching out. I just raised a ticket on your behalf about this and someone from our team will reach out shortly to assist you😊

Hey @GREGets - Thanks for reaching out, and happy new year! I just raised a ticket with our support team about this, and they'll reach out shortly😊

Hey @Mike Shevenell - Thanks for reaching out! I just raised a ticket for you, and they'll assist you shortly😊

Hey @Donald Jackson - Thanks for reaching out! I just raised a ticket for you and they'll reach out shortly😊

Hey @pavnk - Thanks for reaching out! I just raised a ticket for you and they'll assist you shortly😊

Hey @Daan - Thanks for reaching out! By default, Microsoft has set certain Microsoft Office apps to automatically close and re-open during update for a successful update. This is Microsoft's policy and we cannot change this. There are few other applications that follow this update policy. In this situation, you can have the PATCH set for a different time for patching where the users dont use the most of their Office applications/system. Or you can also setup many workflows for different ORGS/SITE/GROUPS so that, it sends a pop-up message at the start time of patching depending on the patch policy timing you have set. Refer to the images of the workflow. You can further customize the message.

Hey @Donald Jackson - Thanks for reaching out. There is no direct way to look at when it was run, but if you have diagnostic logging enabled (Configuration -> Settings -> Enable diagnostic agent logging) and also on this system after the previous. Then, whenever the group command is sent, you can pull up the diagnostic logging and then see when it was sent and if it worked or not. You can also check that specific system's Windows updates section, which reflects when the update was last checked. Refer to the image.

Hey @Labsy - Sorry to listen this has been happening. I just raised a ticket for you and they'll reach out shortly😊

Integrations refined. Automation streamlined. Visibility upgraded. Here’s the quick rundown: Improved ConnectWise integration — guided setup, smarter device matching, clearer org mapping, and expanded field syncing. Distribution Window — spread script/workflow execution over 1–12 hours to avoid bandwidth spikes. Linux OS patching from the Device Card — scan, review, and install updates without touching SSH iOS Remote View — real-time troubleshooting for enrolled iPhones/iPads If you're aiming for smoother workflows and better visibility, this release is absolutely worth a look. 📄 Read the full release notes here.