Change Default Windows Audio Device via Command Line

I just had to share this!

I use 3 different audio devices (Speakers, Stereo Headset and a 7.1 Headset) for various different applications. While Windows is now relatively smart about how it sets the default device when detected, it still requires removing / adding the device.

I thought to myself, wouldn’t it be great if I could just create a script that I could execute before running certain applications that would allow me to set the audio device automatically. Most search results provided links to third party macro / hotkey applications which was not what I was looking for. Looking deeper I came across a gem of an application, AudioEndPointController by Dan Stevens.

This application lets you list the audio output devices attached to the computer and can also set the default output. Using shortcuts to call the executable, I can parse the audio device number of my choosing, and the default device flips, simple as that. Chrome plays well and any audio playing (Youtube etc) will immediately switch over. Firefox (for me) requires a restart.

I Googled for images of my headphones / speakers and converted them to .ico files so I could have graphical shortcuts on the start bar. I used http://www.convertico.com/ to convert them online. Works great!

Compulsory – yet tiny image:


Hyper-V Getting MAC Address using VM Name

As part of my automated provisioning (yes – System Center and Sysprep will probably be a better option, but hey whatever) script, I need to be able to automatically assign an IP address to a VM. At this point, the only way I can see this being a possibility is to mount the VHD before booting then copying a script that will set the correct IP address to an autostart location.

The ‘script’ is broken down into two parts. The first needs to run on the node, and create the second script inside the VHD. The second script then needs to identify what network adapter/s are present and assign the correct IP address to each.

The first challenge is finding out how to have the second script identify the correct adapter. I initially though about testing connectivity after the IP address was set, and upon a failure, revert the changes and try the next adapter present. Rather than doing this, I found you can get the MAC address for a VM from the Hyper-V node, and filter based on which Virtual Switch the interface is attached to:

The following example will get the MAC address for a VM based on the VM name, and the network it is attached to:

This returns a MAC address.

I believe I can then use this MAC address in the second part of the script to pull the network adapter name.

Something along the lines of this:

Once I have the correct adapter name, I can use this in an IP address setting script to set the correct IP / gateway etc essentially automating the networking side of provisioning.

At this point there are a few things I have yet to confirm that might make the above attempt futile. First, I do not know if I can run a powershell script on startup – I know there are issues with signed code etc, and this might mean a freshly provisioned system will not allow unsigned code to run – especially if it needs administrator permissions. Second – I don’t know how this will work with a sysprepped image. It is possible (probable?) that with a sysprep image, the network configuration information could be copied to the sysprep config eliminating the need for an autorun script.

You can see an example of a powershell script to assign IP addresses here: https://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/040b8993-d737-4436-8fb1-29187583e7d1/

© 2017 Chris's Blog

Theme by Anders NorénUp ↑