How to force a Wi-Fi USB adapter on a Synology DiskStation to use 5GHz ac from 2.4GHz

Useful if your SSIDs are identical for 5GHz and 2.4GHz. Having your SSIDs setup like this seems to confuse Synology DSM, and for me it would always connect to the 2.4GHz network.

I had this particular issue where my TP-Link T4U ac wifi adapter for my Synology kept dropping down to using the 2.4GHz network, which slows it down dramatically.

To fix this, here’s what I did. Your mileage may vary, and you may end up disconnecting your Synology from the network, so make sure you have another way of getting to it (such as Ethernet) before proceeding with any of this!

SSH to the DiskStation, login as admin.

sudo -s to root account (same password as admin account)

Make a copy of your existing wifi config file inside /usr/syno/etc/wifi/

For me, I did:

Edit the original file with vi. If you don’t know how to use vi, do a web searhc (it’s not hard, but not easy either).

What you need to do is remove reference to the 2.4ghz network, which you can identify from the bssid, which is the MAC address of your router’s 2.4ghz radio. Once you’re done, the file should just contain details for the bssid that’s your 5ghz network. On my router, the MAC address for the 5GHz network was one hex number higher than the 2.4GHz network.

Next, make a copy of the wpa_supplicant file in /usr/syno/etc. For me, this was called: wpa_supplicant.conf.wlan0

Now edit the file, and change the bssid (which will be the 2.4ghz bssid MAC address) to the bssid MAC address of the 5ghz network.

Reboot the Synology diskstation, and when it comes back, it should be on the 5GHz network.

Manage Hyper-V Server 2012 remotely from Windows 7 with PowerShell

I’ve been looking into Hyper-V Server 2012 recently, as it has some very nice Enterprise-grade capabilities for free; and the zero cost makes it very attractive for Labs that simply don’t have the budget for VMware. The only downsides I can see currently are that remote management is a pain from Windows 7.

Remote Management from Windows 7

Here’s the situation:

  • Much of the management of Hyper-V Server 2012 is via PowerShell 3.0 Hyper-V cmdlets, or the Hyper-V Manager GUI available in Windows 8/Server 2012.
  • PowerShell 3.0 can be installed on Windows 7, but it does not include the Hyper-V cmdlets that would enable you to manage Hyper-V remotely
  • The general consensus is to “Use Windows 8 or Server 2012” to manage Hyper-V Server 2012 remotely, as they include the Hyper-V cmdlets. Unfortunately, this doesn’t work in all scenarios and organisations.

Hello, PowerShell Remoting

A potential solution I found is to leverage PowerShell Remoting. You can use Enter-PSSession to “jump onto” the Hyper-V server from Windows 7, and then interact with PowerShell as though you were directly on the remote Hyper-V host.


Here’s an example:

Enter-PSSession -ComputerName hyperv-server-01

To get a list of available Hyper-V cmdlets:

Get-Command -Module Hyper-V


Admittedly, this might make scripting a bit more difficult, but I imagine it’s possible to do if you really can’t use Windows 8 or Server 2012.

Hope this is useful! 🙂

Tracking down SMB 2.1 support in NetApp ONTAP 8.1.x 7-Mode


This blog post covers how I tracked down when SMB 2.1 support was re-enabled in ONTAP 8.1.x 7-mode, having been disabled in the initial release of 8.1.2.

What’s new and shiny in Win 7 for IT Pros?

If, like me, you’re eagerly anticipating Win 7, you could do a lot worse than check out what’s new in Win 7 for IT Pros.

If you prefer video/speech to reading, there’s a very good video available for download as well 🙂

Automatically install Windows Updates / Hotfixes when installing Vista

If, like us, you run a BDD or MDT setup in order to install your Operating Systems, this might be useful 🙂

If you’d like to pre-install Vista updates and hotfixes while Vista is installing:

  1. Go to your Distribution Share (C:\Distribution)
  2. Go into Operating Systems, then find your Vista OS (C:\Distribution\Operating Systems\Windows Vista Business SP1 – 32bit\)
  3. Create a new folder in this directory called “update”
  4. Copy all of your Vista Update files (.msu) into this directory
  5. That’s it 🙂 The next time you run a Vista deployment, the updates will be pre-installed!
The same concept applies to installing from a Vista DVD.

Extra tip

If you’d like a list of updates released since Vista SP1, check out this site: