Mark G38

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

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

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

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

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

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 Greg, There are a number of ways to start a program, however, when you say you go to the remote computer, are you actually logging into the remote computer and opening PowerShell on the local machine and running those commands? If so, that's the difference. When running anything through Pulseway, it will default to running as the system account. So trying to run those commands through Pulseway, you're opening the program (if it even supports non-interactive) as the system account, and no user will see it. You could check processes to confirm that though. You would need to run it under user context and right now, Pulseway only has that ability to do this if you log onto the machine in question, open Pulseway Manager, go to Settings - Runtime and scroll to the bottom to Enable PowerShell User Impersonation. This will run scripts through Pulseway as the user you entered. This will do the trick. You can then call them different ways. Start-Process "Path\to\exe\" also will work.

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.

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

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

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.