Mark G38

No it can't.  You are better off with some other tool to look at network traffic.

Put back the registry entry or use PowerShell to grab the uninstall string and script the uninstall. 

No, 21H2 is a shared version number between Win 10 and Win 11.  See here:

https://docs.microsoft.com/en-us/lifecycle/products/windows-11-home-and-pro-version-21h2
 
That is why you have to take the above steps to prevent Windows 10 from going past 21H1

I see you found the thread where this is discussed.  This still will not stop users from clicking upgrade.  I've not had a single machine from any of my clients update to Win 11 yet, and I took the same steps I outlined in the below thread. 
 
 

@merritt.bishop There shouldn't be anything special you need to do.  Without seeing your code, I can't tell you for sure, but my guess is unfortunately you're missing something in your code. 
For instance, I have no trouble doing a computer reboot from Pulseway using PowerShell, however, you have to add -force at the end to get it to do so.
Restart-Computer -ComputerName "$env:ComputerName" -Force Works like a charm.   Happy to help with other items if you need it. 

Windows Service Monitoring can now be configured directly in the Web Application, within Endpoint Policies, accessible using the NEW Monitored Service category. In addition, a new Monitored Services section has been added to the Services feature page when working with an online System, providing a distinction of general Service information and those Services being actively monitored.

@Michael Woffenden Are you asking for this to just be added via a Pulseway feature or how to actually do it via PowerShell through Pulseway? 

@merritt.bishop There shouldn't be anything special you need to do.  Without seeing your code, I can't tell you for sure, but my guess is unfortunately you're missing something in your code. 
For instance, I have no trouble doing a computer reboot from Pulseway using PowerShell, however, you have to add -force at the end to get it to do so.
Restart-Computer -ComputerName "$env:ComputerName" -Force Works like a charm.   Happy to help with other items if you need it. 

Going to bring this thread back to the top.  If anyone else feels that having the ability to input at run time a variable they declared as a custom field in their scripts, please upvote.  This is probably one of the single biggest improvements I want to see with Pulseway.  Custom variables should be able to be set to prompt at run for input.  We should also be able to set Customer level variables that are static and can be called in a given script.  
Here is the link to the feature request.  I did search and didn't find someone else asking about this, but I may have missed it. Either way, doesn't seem high on the list of votes so getting more attention to it would be great. 
https://pulseway.featureupvote.com/suggestions/189283/more-robust-input-and-site-variables

Agreed!
I'm sure Pulseway does some great development behind the scenes, but the current ways to let us know simply aren't working.
You should consider regular updates along a predefined schedule, like publishing updates on day X once a month or on day X once every quarter, and then map a forum thread or webpage to it so we can get a better idea of what is coming and when.

Curious if we can be provided a bit more detailed road map.  It would be nice if when ideas from the Feature Requests page get approved, that we can an idea of the timeline until we see that feature.  For example, all the ones in my below screenshot marked "In Development" have been in that status for months.  When you look at the Roadmap thread, it doesn't show any of these specific items in there.  It would be nice to see an estimate on when we can expect some of these features to be released.

 
 
 

@spinto Yes there is.  Was released by Datto RMM in collaboration with others. 
Modify it to suit your needs.  It works well to identify vulnerable files as it scans inside jar files as well.  
 
With some small modifications you can run it through Pulseway of course.   
https://github.com/datto/log4shell-tool

You can do both of these things already in regards to triggering workflow off specific event log item as well as sending an email on new system registered.  The only thing it doesn't do is the total in the group.  

@Mark G38Thanks very much for this. I was able to configure monitoring as you said. 

@Randula All you need to do is log onto 1 machine that has the Veeam and create the needed event log monitor through the Pulseway Manager on the local machine, than export that.  
Go into Policies on the PWA and it allows you to import there.  It will the apply to all machines under that policy.  I have several custom alerts set up using a custom event log that I created and write to, and this is how I had to do it.  I have a "dev" machine that I use to create and test alerts and export from there into my policies for my clients. 

@BurseyC It's 100% the system uptime. 
#1 rule, Never trust an end user.  They don't enough to be able to accurately say one way or the other in most cases. To an end user, turning their computer off every night could mean sleep mode, hibernation, logging out, or turning off the monitor. 
#2. In Windows 10, a shutdown doesn't actually clear the system up time if Fast Startup is enabled (which is the default setting).  Only restarts clear the uptime in this scenario.  You can disable this or force reboots. 
 

@Circumflex Are you strictly looking for a script to be able to do this? Because you can set storage limits in Windows for restores, and it will simply store as many as it can up to given limit, and then start deleting older ones to make room for the latest ones. 

@Randula All you need to do is log onto 1 machine that has the Veeam and create the needed event log monitor through the Pulseway Manager on the local machine, than export that.  
Go into Policies on the PWA and it allows you to import there.  It will the apply to all machines under that policy.  I have several custom alerts set up using a custom event log that I created and write to, and this is how I had to do it.  I have a "dev" machine that I use to create and test alerts and export from there into my policies for my clients. 

@Greg Candido I'm going to guess by now that you've probably have resolved this perhaps with one of the given methods.  But I wanted to bump this thread because of another way to accomplish this, which is actually probably easier than the other methods suggested, and it will work well for others needing to run scripts as users. 
There is a PS module on PSGallery called RunAsUser which allows you do just that.  You can very easily implement this and run through Pulseway.  As an example, using the same scenario I did above where I wanted to launch Chrome as the user, look how much less work this is lol.
###Check if module is installed and if not, install it### if (!(Get-InstalledModule | Where-Object { $_.Name -eq "RunAsUser" })) {     Install-Module RunAsUser -Force }   ###Whatever code you want to run as the user### $ScriptBlock = {     Start-Process "C:\Program Files\Google\Chrome\Application\chrome.exe" }   Invoke-ASCurrentUser -ScriptBlock $ScriptBlock  
Adding link to the module for reference: https://github.com/KelvinTegelaar/RunAsUser

Happy to help and yes, sorry about that should be reg_sz as you mentioned. 

@Gregory Candido That's correct. It will apply to ALL patch policies you have in place.  You can create rules for new ones as well yes.
However, you can also do the registry entries as mentioned previously.  They will prevent auto updates to anything past what you set.  Obviously, this may need to change as Windows 10 continues to release updates, but we will have to wait and see if they alter version numbers so that Windows 11 is different from Windows 10 in that regards.  
For now, you can script these reg entries or deploy via GPO if you have an AD environment. 
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.
Create or update the Dword TargetReleaseVersion to 1.
Create or update the Dword TargetReleaseVersionInfo to 21H1.
 

@Continu IT Solutions That's odd as all Bitdefender issues have been resolved for my instance.  You might want to hit up Support in that case. 

@Gregory Candido That's correct. It will apply to ALL patch policies you have in place.  You can create rules for new ones as well yes.
However, you can also do the registry entries as mentioned previously.  They will prevent auto updates to anything past what you set.  Obviously, this may need to change as Windows 10 continues to release updates, but we will have to wait and see if they alter version numbers so that Windows 11 is different from Windows 10 in that regards.  
For now, you can script these reg entries or deploy via GPO if you have an AD environment. 
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.
Create or update the Dword TargetReleaseVersion to 1.
Create or update the Dword TargetReleaseVersionInfo to 21H1.
 

I've taken 2 steps to this.
1.  Create a Global Rule in Pulseway that says if Name or Description contains 21H2, don't install.  21H2 is used by Windows 11.  
2. Set registry entries to tell Windows 10 to not update Feature version past 21H1 for now.  This can also be done via GPO in a domain environment. 
 
 
BUT - I don't think this stops end users from clicking upgrade if they get a prompt or choose to be curious themselves.  I've also sent out communications to my customers explaining that they should not be pressing update to any Windows 11 prompts if they happen to see any lol. 

@JoeS In light of what Paul mentioned, you could set up a custom event log alert to monitor the backups through Pulseway in the meantime.