AudioDeviceCmdlets VS PrtgAPI

I worked with an issue close to this awhile ago when I needed to set a default audio device within a DSC (don't ask, it was dumb). Is the Get-AudioDevice cmdlet from the https://github.com/frgnca/AudioDeviceCmdlets repo? That was the one I ended up using, I found a bug in it with the way it was enumerating devices and had to dig into the C# underneath.

It uses a set of a cool set of PowerShell cmdlets named AudioDeviceCmdlets to query for the audio devices. Docs and installation instructions can be found in its GitHub repo. There are multiple ways of getting the list of audio devices on Windows, AudioDeviceCmdlets made it very easy to do.

Since my last update i have followed the links and advice that u/MasterChiefmas, u/PajamaDuelist, u/spyingwind, and u/ps1_missionary replied with. While none of their information directly helped, it helped me find the rabbit trails to get to this point. as of right now this script will control the remote audio devices but it will not allow you to play audio out of the remote pc speakers. if you run the contents of the invoke command in start-tone in a admin powershell window on your account it will work so i know the code is sound (pun intended). while doing researching this issue i came across AudioDeviceCmdlets from https://github.com/frgnca/AudioDeviceCmdlets and this helped solve many of the issues i had with controlling and unmuting audio remotely. However i still have issues getting audio to play remotely.

For Windows, aside from the other mention of NirCmd, there's also the AudioDeviceCmdlets PowerShell module (source here).

I just want to clarify that only one of the source files contains code that I wrote. https://github.com/frgnca/AudioDeviceCmdlets/blob/8a02ed8924d44e57338488e38927f35522d7853b/SOURCE/AudioDeviceCmdlets.cs

NIRcmd is great example, but I would add also AudioDeviceCmdlets https://github.com/frgnca/AudioDeviceCmdlets And if you want a physical switch, we should soon release the one which we developed last year https://youtu.be/2HNjlMSk42c

Managing multiple EQ profiles for different audio devices can be fuddly with EqualizerAPO, this PowerShell tool allows you to easily switch playback devices and audio device profiles among any number of devices using the AudioDeviceCmdlets module.

Alternatively you could check this is something that https://github.com/lordmilko/PrtgAPI can make a little bit easier since it abstracts a lot of the complexity of interacting with the API.

Not sure if there's a way to do this exactly within PRTG but I know you could write up some logic to report what you're looking for using the PrtgAPI PowerShell module, https://github.com/lordmilko/PrtgAPI

Or if you wanna script it with powershell: https://github.com/lordmilko/PrtgAPI

I don't use the built in reports from PRTG but I've written some custom reporting tools using the PowerShell module, prtgapi (https://github.com/lordmilko/PrtgAPI) which could get you what you're looking for.

If you are using a windows to manage it, you can also use the Powershell Module (https://github.com/lordmilko/PrtgAPI).

I ran across this https://github.com/lordmilko/PrtgAPI which I am trying to figure out how to leverage to create a script to run on hosts to schedule downtime for 2 hours. We use BigFix to patch Windows so I was going to try and get a script to run on each host, part of the patch deployment, to schedule 2 hours downtime which should be sufficient for patching. Our maintenance windows are constantly moving so setting up the maintenance schedules in PRTG seems to be more administration work.

I'm not sure if there is another way over the webinterface, but you can use LordMilko's PrtgAPI: https://github.com/lordmilko/PrtgAPI

You should hopefully be able to automate most (if not all) of what you're doing using PrtgAPI. While PrtgAPI's support for working with schedules is not as full featured as most other aspects, I believe you should be able to perform this migration by doing the following

You may want to look into the Powershell PrtgApi module, https://github.com/lordmilko/PrtgAPI . I have several scripts using this that allow me to update settings per sensor name/type. It's not quite officially supported by Paessler but it's well maintained and at least acknowledged by Paessler as a useful tool.