By Your PCMD
I am curious to know why 3rd party patch mgmt. is an additional paid feature. Before I would get notified for like Adobe Reader needed an update, know I have to pay additional to get this notification?
What else within the features we already get will be removed to a "module" that we have to pay additional for? I only oversee around 60 endpoints, so I am not a big player, but there are issues now that are making me look and trial other RMM solutions.
Today I logged into my dash-panel as I do everyday M-F only to be greeted with 53 notifications for critical updates for Windows. Going into to the systems one by one, I quickly realized that something is not right. When viewing the systems, it clearly stated there were updates for Windows needed, but going to the actual systems available updates, I see "No updates found". Is Windows itself considered a 3rd party now?
While writing this:
20 May 2019 08:45
1 critical update is available on computer 'REDACTED' in group 'REDACTED - Workstations'. Available Updates
No Updates Found
Last Checked: 20 May 2019 08:48
It would be great if we could make Asset Info available when devices are offline.
For example if a remote users PC fails to function and is still under warranty trying to explain to a user where to find the device Make, Model and serial number to log a warranty case is not always easy.
If the asset information was available when the device was off line then it would make this process mach easier as it contains all the information required
DAVID-O-MIIX Windows 10 Pro Offline Offline since 11 minutes ago Asset Info System DAVID-0-MIIX Name LENOVO Manufacturer 20M3 Model x64-based PC Type Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz CPU 1 Number of Processors 8 Number of Logical Processors DAVID-O-MIIX DNS Host Name TEST.local Domain Administrator Owner Name LM_Workstation, LM_Server, NT, Potential_Browser Roles OK Status BIOS YD05UDx7 Serial Number 6NCN33WW Name LENOVO Manufacturer 6NCN33WW SMBIOS Version 3 SMBIOS Major Version 0 SMBIOS Minor Version LENOVO - 1 Version Monday, 12 November 2018 1:00 PM Release Date OK Status 6NCN33WW Description Operating System Windows 10 Pro Name 10.0.17763.0 Version Multiprocessor Free Build Type systemadmin Registered User NF6EE-QH89W-F8WST-WWXZ4-WFG6P Product Key 00330-50000-00000-AAOEM Serial Number 0 Service Pack Major Version 0 Service Pack Minor Version \Device\HarddiskVolume3 System Device C:\WINDOWS\system32 System Directory C:\WINDOWS Windows Directory Monday, 11 March 2019 12:40 PM Install Date Monday, 20 May 2019 4:30 PM Local Date and Time Monday, 20 May 2019 8:10 AM Last Boot Up Time test\anton.rider Last Logged On User
Is there a way to MANUALLY open a ticket from within the RMM?
Since Pulseway doesn't offer "round trip ticketing" where a ticket can be automatically opened and closed by the RMM (if a ticket is opened automatically, then resolved from within the RMM the ticket is automatically closed) we are trying to reduce the "signal to noise ratio" by only having critical issues automatically open tickets in the PSA. However, since we do our billing from the PSA, I would like to have our techs be able to open a ticket by clicking a button on a device or alert in the RMM so a ticket is opened in the PSA with the pertinent information auto-filled and a timer started.
It seems that Pulseway has made a philosophical decision that doesnt quite make sense for MSPs. I cannot find a way to select a group of computers on which to perform an action. Specifically, I would like to add Tags to machines across clients, install Webroot on groups of machines, or activate the new 3rd Party Patch Management. In each case, I would have to click into each machine or click the agent then add a Tag, or click install on each agent. If I wanted to install the Patch Management on 100 Machines it would require at least 300 clicks AFTER we identified which machines we wanted to include in the new policy.
I know Pulseway is mobile forward, but there is nothing wrong with a checkbox here or there. It would be great to be able to identify a subset of machines and select them with a checkbox and then install, tag, or manually run a script on all those machine regardless of their client affiliation, location, or type of machine.