Mariale_Pulseway

Hey @JoeS - Thanks for reaching out. Our support team will be better at assisting you with this. I just raised a ticket on your behalf and someone from our team will contact you shortly😊

Hey @mchristensen - Thanks for getting back to me on this. I think it would be best to involve our support team on this, so I just raised a ticket on your behalf and someone from the team will contact you shortly😊

We all come across those tickets that make us go, "This should definitely go in the knowledge base..." 😅 Whether it’s a browser not launching or an obscure config bug, documenting these moments can save your team a ton of time down the road. Here’s how you can do it using Pulseway: Let’s say a technician is resolving a ticket — for example, a browser application that suddenly stops working. During resolution, they realize the issue is unique and should be documented for future reference. Instead of writing a separate article later, they: Add their resolution note to the ticket Click “Publish to Knowledge Base” Select the appropriate category Save the ticket ✅ The ticket is now marked complete ✅ A brand new KB article is created — complete with the final resolution ✅ It links directly back to the original ticket for full context You can also build KBs from scratch: Just head to Knowledge Base → New, enter your title, keywords, and details. Choose when to publish — and done. It’s a super efficient way to turn real-world issues into lasting documentation, without doing double work. 🙌

Hey @mchristensen - We don't have a KB article for this as of now. However, the only difference in the installation process when compared to the Linux/Ubuntu article we have is the 1st command. In Ubuntu we use "wget <download link>" In PfSense we use "fetch <download link>" Here's the Linux article for clarity: https://intercom.help/pulseway/en/articles/2971801-how-to-install-and-configure-pulseway-linux-agent-on-ubuntu-os Fetch download URLPulseway.pkg Pkg install file_name.pkg Pulseway-registration Let me know if this works for you😊

@t_llc No worries! Let me know if you need assistance with anything else🙂

Hey @MrMattiPants - I understand. Let's try the workflow and let me know if you're still having the same issue after.

Hey @MrMattiPants - Thanks for reaching out. Can you run the script through a scheduled workflow? There you can choose the timezone (refer to image)

Hey @t_llc - Pulseway can approve the Windows upgrades; however, even end-users' prompt is also important during the upgrade. But before that, is the laptop compatible with Windows 11? Only then can the upgrade be approved from Pulseway. You can check the compatibility here from Microsoft website -> https://www.microsoft.com/en-in/windows/windows-11-specifications?r=1

Hey @Nexusphreez - Thanks for reaching out and giving your feedback. We appreciate it a lot. I'll pass this along to our product team😊

@Nac Critical Actually, for the SQL server enabling you'll have to do it through manually through the Pulseway manager.

Hey @compsmith - Thanks for reaching out. Can you check and see if the monitoring policy of the S.M.A.R.T. alert is assigned to the device? Navigate to devices > device list > policies > (refer to the image)

Hey @Nac Critical - Thanks for reaching out. To enable AD they can use this script: Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor\" -Name MonitorAD -Value 1 For SQL it isn't possible through this approach as the username and password is required. Let me know if you need more assistance😊

We’ve just rolled out Pulseway 9.15, and it’s a pretty major update. Here’s what’s new: 🔐 KaseyaOne Unified Login Single sign-on is now available. You can access Pulseway and your other Kaseya tools with one login, and navigate between them via a new app launcher (the waffle icon). 🧑‍💼 Access Groups (RBAC) User access can now be synced with KaseyaOne roles. Define permissions once and apply them across systems. Much easier to manage at scale. 🤖 Cooper Insights Cooper (Kaseya’s AI engine) is now integrated into Pulseway. It flags issues like missing patch policies, unassigned workflows, or unused features—so you can fix them before they become problems. 🧭 Centralized Experience Support tickets, billing, modules, navigation—all unified under one roof. This release is less about new buttons and more about making everything smoother, smarter, and more centralized for you. Read all about it here: Release Notes.

Hey @DahaS - You can find it next to the notifications icon on the dashboard above (refer to image). And if you want to know more about it, you can go to this KB: https://intercom.help/pulseway/en/articles/10095980-remote-control-on-demand 😊

Hey @ww3361 - Thanks for reaching out. Question: is there a monitoring policy from the webapp is assigned to this device? Navigate to devices > device list > go to the device > policies

Hey @Happybattles - Can you upload a screenshot of the configuration steps on which parameters they are selecting to run the advanced templates reports?

@Justin Wright Awesome! Let me know if you have any other questions :)

Hey @Justin Wright - Thanks for reaching out. You can use the tasks in the automation to run it on all the devices and post that run a task execution output report which will show the output of the script on the devices. Reporting > report templates > task execution output templates (refer to image) Let me know if this works for you😊

Hey @Martin Akamphuber - We don't have this feature available and there's no timeline for this to come back.

Hey @cts6288 @mchristensen - Thanks for reaching out. Our support would be able to assist you with this. I just raised a ticket on your behalf and they'll be in contact shortly😊

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. 👇

@Milton Polina No worries. I just raised a support ticket on your behalf and someone from our team will reach out shortly😊

Hey @Milton Polina - Thanks for reaching out. We have a KB with all the steps for this. Here's the link: https://intercom.help/pulseway/en/articles/6354183-pulseway-agent-installation-error-1001 Follow all of them, except for step 5. Let me know if you need more assistance😊

Hey @windracer - Totally understand, and thank you so much for using Pulseway! If your needs ever change or you decide to hop back in, you know where to find us😊

Tired of babysitting new machines just to get them patched right? We get it. You’ve got better things to do than click around chasing every new install like it’s a rogue Pokémon. Here’s the scenario: A new machine shows up. Instead of waiting on a manual trigger or even a regular notification schedule, Pulseway gives you the option to work ad hoc or notification-based. As soon as you install Pulseway for the first time, you’ll get a "system registered" alert. That alert is your magic trigger. From there, you can kick off a workflow like this one: Trigger Workflow: Use the "system registered" alert to start the automation engine. Assign Patch Policy: Automatically run the patching policy assigned to the group/org the machine belongs to. Reboot Prep: Before rebooting (because we all know it’s coming), send a message to the user “Heads up! Reboot in 10 minutes”. Schedule Reboot: Now that they’re warned, schedule the reboot time and close the loop. 🔁 It’s simple. It’s clean. And it saves you from 100 tiny headaches. No more micro-managing patch rollouts one device at a time.