Mark G38

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. 

With the 8.8.9 Linux Agent, you can now install Pulseway on ARM64-based devices (Raspberry Pi 3 and 4).

@BCons Maybe I'm not 100% following you on this.  Pulseway does have the ability to do exactly what you're asking.  Albeit, perhaps not in the most intuitive way, but it's there.  
If you go to any machine that has pending updates, you can see all critical, important, optional updates and then select which ones you want to install by checking or unchecking the box at the end of each one.
If there is a particular KB you know that is a cause for issues, you can go to Patch Management - Global Rules and very easily create a rule to not allow that patch.  
 

 

Also, exclusions and changes for a specific device are something I've requested.  If you wouldn't mind, here is the feature upvote link, give it a vote up.
https://pulseway.featureupvote.com/suggestions/217128/exclusions

Is that the full name of the software as it's installed on a machine? If not can you provide the full name.  Is it by Vivitek? 
I can probably help you out.  PM me some details like version your machines are on versus current version if you know it.   

@Greg Candido
You need to impersonate the actual user that you want the program to launch under.  Keep that in mind because if the script to update it requires administrator privileges, but the user does not, then the update script may fail once you turn on impersonation.  However, if that's not a concern, then run impersonation as the user you need the program to launch under.  
Alternatively, and I think this may work for you, it's a bit... emm janky lol, but it will serve the purpose.  Log onto the machine and create a scheduled task that is triggered on-demand only, and have that task start the program under the user account you need.  Now, in your update script, at the end, once the update has completed, have your script trigger the scheduled task.  If the scheduled task is correctly set up to run as the specific user, it should launch the program when you trigger the task from your script. 
I realized you said you are not well versed in scripting.  Let's make this a little easier.  Turn off impersonation so you don't have to worry about permission issues in the future with other scripts.  
Log into the machine as the user you need (this will make creating the scheduled task easier). Create the scheduled task.  I'll show you screenshots of an example one I did to show you steps. You can even test this yourself using Chrome and then triggering the task through PW and you will see it launches under the user account.  Make sure you have the correct user selected.  Should be the user you need if you're logged in as them already.  Change Configure for to suit your needs.  No trigger, no conditions. Set it up as below.
When you're done setting up the scheduled task, add this line to your update script:
Start-ScheduledTask -TaskName "THENAMEOFYOURSCHEDULEDTASK"
You can open PW, navigate to the machine, go down to PowerShell, and run the above command to test before even adding it to your script to confirm. 
 




 

Hey TeeJay,
I have a feature request in for this already if you wouldn't mind upvoting it. 
https://pulseway.featureupvote.com/suggestions/189283/more-robust-input-and-site-variables
 
 

As of right now, I do not believe there is any other way to move systems.  Permission enhancements across the board is something I'd like to see happen within Pulseway.  From script access (Scripts should have different access levels assigned to them so you can restrict certain scripts to a higher tier), to policies, to moving systems, etc.  As you build a team, permissions becomes extremely important.

Thanks @Mark G38 that's great. 
Re your  feature request, I have upvoted it. I've mentioned this request a few times and do find it frustrating that the Pulseway policies don't work in a similar way to AD Group Policy and require a completely new policy just for a single change. Also if I change a setting and don't use the same policy on all devices then that setting needs to be changed in multiple policies.

As of right now, I do not believe there is any other way to move systems.  Permission enhancements across the board is something I'd like to see happen within Pulseway.  From script access (Scripts should have different access levels assigned to them so you can restrict certain scripts to a higher tier), to policies, to moving systems, etc.  As you build a team, permissions becomes extremely important.

You can definitely do that inside the Bitdefender Gravity Zone portal.  You can also unselect it during install from Pulseway portal.
 

Hi Paul,
Yes Windows.  Interestingly enough, I'm not running that version, and I thought I might not have the updated version so I went to the Play Store and no update last night.  Literally checked it now, and update available.  So clearly, I should pay more attention to things lol.  Frustrating though because I have auto-updates on for my phone apps, so I shouldn't have to go manually update anything.  Anyway, thanks for the reply. 

Yea I noticed they are doing that too, which is very cool.  
And I don't know.  I still do not see the changes on the phone.  S21 Ultra on latest Android OS.  /shrug

It's under Automation - Workflows, you have to build the ones you want. 

It was requested I post this so hopefully someone else in the community can benefit.  Until we are able to deploy Bitdefender from within Pulseway, this is the next best thing.  I wrote this again, for my clientele who generally are PS 3.0 + so some small adjustments may be needed if you are attempting to run this on PS 2.0.
This will download and silently install Bitdefender.  All you need to edit is the $BitdefenderURL and possibly the $BaseURL depending.  When you log into GravityZone and make a package and go to get install links, the base URL in your portal will always be the same followed by the remaining part of the URL which can change based on the package.  If you just make 1 generic one and then move the machines after install, you will only need to edit this once.  I've left my base URL in the script so you can see that part and the beginning of the unique part so you can easily know what to change. 
Function New-FileDownload {     param(         [Parameter(Mandatory = $true)]         [ValidateNotNullOrEmpty()]         [string]$Url,         [Parameter(Mandatory = $true)]         [ValidateNotNullOrEmpty()]         [string]$Destination     )     $webClient = New-Object System.Net.WebClient     $webClient.DownloadFile($Url, $Destination)     if (Test-Path -LiteralPath $Destination) {         Write-Verbose "File downloaded Successfully"         return $true     }     else {         Write-Verbose "File download Failed"         return $false     } }   $Installed = Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" |  Where-Object { $_.DisplayName -eq "Bitdefender Endpoint Security Tools" }   if ($Installed) {     Write-Output "Bitdefender already installed. Exiting."     Exit 1 }   $BitdefenderURL = "setupdownloader_thisistheuniquepart.exe" Write-Output "Beginning download of Bitdefender..." $BaseURL = "https://cloud.gravityzone.bitdefender.com/Packages/BSTWIN/0/" $URL = $BaseURL + $BitdefenderURL $Destination = "$($env:TEMP)\$($BitdefenderURL)"   $FileDownload = New-FileDownload -Url $URL -Destination $Destination if ($FileDownload) {     Write-Output "Download succeeded, beginning install..."     Start-Process $Destination -ArgumentList "/bdparams /silent silent" -Wait -NoNewWindow     Start-Sleep -Seconds 30 } else {     Write-Output "File failed to download. Exiting."     Exit 1 } $Installed = Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" |  Where-Object { $_.DisplayName -eq "Bitdefender Endpoint Security Tools" }   if ($Installed) {     Write-Output "Bitdefender successfully installed."     Exit 0 } else {     Write-Output "ERROR: Failed to install Bitdefender"     Exit 1 }

@Jamie Taylor This is great to finally have this.  Thanks.  One thing to note, I see it on my Web instance but when I check my mobile app, I do not see it available.  Any idea why?  Maybe I need to clear the app cache? 

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

Unfortunately, cannot help you here.  I demo'd the Cloud Backup and it has promise, but I found too many issues with it currently for me to be comfortable with using it in a production environment.  I hope your issue gets worked out. 

No worries about your English Dimitri. Doing my best to understand lol. 
Assuming the domain environment is the environment you are trying to deploy Pulseway to, then you can push Pulseway via a GPO, and you don't have to worry about enabling the admin share, because Active Directory will have the needed permissions to be able to deploy the software.  OR, even with GPO you can make registry changes. So you could hit every machine one way or another super easy with a GPO.  

@Powloj I'm not aware that there is a limitation on the trigger. I was pretty sure you could add more than 1 trigger of the same type, but I haven't run into that need myself, so I'd have to test it, but if you're saying it won't let you, then that is most unfortunate.  
In that cause, I'd suggest one of 2 things. 
 
1.  Just add the tagging to your existing system registered trigger. Since it's just adding a tag, I can't imagine it would hurt your existing workflow to just add a step of adding a tag.
2. The Rest API gives you the ability to pull system info complete with the name and group/organization it belongs to.  You could very easily pull this info, make PowerShell do a "count" and give you totals.  You could even have it export the results to csv for you.  
 

A workgroup setup is going to be a bit more tricky, but still mostly doable.  Pulseway has an agent deployment via a network probe option as well.  You can select 1 machine that has the agent installed already as a probe, and use that machine to scan the network for other machines.  At which point you can select the other machines to deploy Pulseway to, and enter necessary credentials, and then it will attempt to deploy to them.  
There are some caveats to this of course, because it needs access to the \admin$\ share on a machine, which most times, Windows has already defaulted to disabled.  So you'd need to psexec to the remote machines (or access the remote machines some other way) and enable it via registry changes.
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System”
Set a DWord called LocalAccountTokenFilterPolicy and set the value to 1.  Reboot.  
The last option I can think of is build yourself a Batch or PowerShell file that calls the installer using the CLI commands that Pulseway accepts and thus, making it silent after they run PS/Batch file. 

I now see it. Thanks.

You are right actually, it is sorting strange on mine too.
Also, the API, well, sorry to disappoint, I actually just connected and ran against mine, and filtered for the last_seen_online field, and hilariously enough, if the machine is currently offline, it doesn't display anything in that field, sooooo it's useless lol. 

It's disabled by default in Windows.  If you're not on a domain where you can use GPO, you have to do this to the registry on each machine. 
“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System”
Set a DWord called LocalAccountTokenFilterPolicy and set the value to 1.  Reboot.  Should do the trick.  

@Jamie Taylor Still don't see it.  When can we expect to actually see this feature?