Paul

Hi, Yes, that setting is still recommended for resolving VSS problems. -Paul

Yeah, sorry about that. We've released an update that incorrectly incremented the version to 4.9. Today's release will have the build number 808. -Paul

That's why I've mentioned that it's only going to be available on the WebApp, reports (well mobile apps too (iOS and Android) but we won't change the app name or the icon/splash screen however we will display your logo on the settings page). We will consider extending this to the agents in the future too. -Paul

That's the plan. The agent should only have connection settings like Proxy, diagnostic logging and setting that are critical to making sure that the agent reaches our serves. Once they do, they'll get everything they need from there. Which allows you to centrally manage the settings from the webapp. -Paul

It is now . -Paul

A global search would be fantastic. This reminds me of the Mac OS X handy shortcut (CMD + SPACE) which allows you to search through everything on your computer. -Paul

Hi Jeremy, Initially we had a flash based web application and we were all reluctant to have configuration settings done there. Now that we've moved to a HTML5 web app it opened a world of possibilities. (I really mean a world of possibilities since we're still adding them and didn't manage to get to this one yet ). -Paul

Not really. Automation triggers like schedule or event based rules will not make the 4.9 (tomorrow) release but they will come in the ones that follow it. -Paul

WebApp and reports rebranding is coming up on the 4.9 release (tomorrow). Oh, did I mention it's awesome? -Paul

Yes. Even better, you just create a task with 3 scripts and have the task run on a system scope. If you add other systems in the future in a Group or Tag that is part of the system scope new systems will be automatically included in the task execution. We'll ship a couple of built-in scripts. Scripting has a very large community on the internet, I'll be impressed if there is something you're trying to do and there isn't a sample script somewhere on the internet already. -Paul

Hi Jeremy, Sorry for the delayed reply. We support Exchange 2016, we just don't advertise it on the Pulseway Manager. We'll make the changes in the agent so that we state that we support Microsoft Exchange Server 2016 too. Just select the 2010/2013 option on a Exchange Server 2016 and it will work flawlessly. -Paul

Yes, or you can go for yearly and we send an invoice every year. -Paul

Hi Jeremy, The Enterprise solution starts from 50 systems so that's: 2.01 (price per month per system) * 50 (minimum license count for the Enterprise edition) = 100.5€ (total cost per month - excluding VAT) -Paul

Hi Jeremy, You pay for each agent installation or API-created instance. During the trial period you have 100 system seats. When the trial ends you will have to decide the amount of systems you want to monitor and pay a fee for each system seat. More details on the pricing over here: https://www.pulseway.com/pricing. -Paul

Great, we don't have any license management capabilities but now that we have better reporting this opens a lot of possibilities including asset / license management. -Paul

The automation module will allow you to write scripts (Batch and PowerShell for Windows and Bash for Linux and Mac OS) and run them on demand. The schedule feature will come out in the following releases but yes, you will have to write the scripts yourself but this also comes with a greater management power. Did I mention that these scripts are centrally managed? -Paul

We're actually considering on how we can create a closed beta channel, I'll let you know when we have an update on this. -Paul

Thanks, I've added it on our todo list. -Paul

Web hooks are urls that are invoked when an even is triggered (like a notification is received). You can enter the API endpoint of LiveAgent, hook our parameters (system name, group name, notification title, notification message, etc) into the url based on their documentation and voila, you have LiveAgent integrated with Pulseway . -Paul

This could be done using the upcoming automation module. You can write a powershell script that can determine if it's a VM, create a snapshot using the vSphere PowerCLI and then schedule the windows update installation. PowerCLI link: https://my.vmware.com/web/vmware/details?downloadGroup=PCLI550&productId=352 Get available windows updates from powershell: $Searcher = New-Object -ComObject Microsoft.Update.Searcher $Results = $Searcher.Search("Type='Software' and IsInstalled=0") $Results.Updates -Paul

Hi Jeremy, CPU, Memory and disk usage trends are coming up in the next 4.9 release (Monday). Mail queue and SQL dead locks sound interesting, we'll see what we can do about those. -Paul

With the upcoming 4.9 release (Monday) you will be able to generate an installed software report per scope (collection of groups, tags and system types). What would you like to see in a license management feature? -Paul

Hi Jeremy, We use a proprietary protocol. -Paul

-Paul

Perfect, thank you. This helps us a lot.