One of the things that bothered me in the past was the fact that Task Manager showed all the required performance graphs, except the disk-related ones. Why is that, I don’t know. OK, you can see the disks through Resource Monitor console or PerfMon, but… I really like using Task Manager, with such nice colors and simple graphs, for a quick overall check.
So, when you’ve opened your Task Manager, you were shown something like this:
No disks. Too bad.
But… fear not, my friend! There is a solution for this “glitch”. Even a simple one.
All you need to do is run the following command in your administrative Command Prompt:
And now, when you reopen your Task Manager, you will see following:
I know, there is not much need for it (as everything usually works just fine), but still… there is a “Windows Server 2016 re-installation wave” coming and maybe you’ll find the the next pieces interesting and useful.
One of the “messy” tasks with Windows reinstallation is networking… and by “messy” I mean “you have more than one network cable in your Hyper-V hosts” and you need to know which networks are connected where.
What happens is that Windows somehow always forgets your network device order, all the pretty names you’ve applied and you get stuck with names like “Ethernet”, “Ethernet 2”, etc.
There is a way to fix this (there are many, actually) – we can ask our younger colleague to go to the server room and unplug the cables one by one and then plug them back in, following the rename on our (Windows) side. This way we are certain that all the corporate, DMZ, storage, live migration, etc. cables don’t get “confused” when added to their respective teams and if we labeled cables properly, everything will work with fresh Windows installation also.
But… there is another way. We can use what we already have – our documentation. Here I mean “our current setup” – we have our network adapters and teams already configured in our current Windows installation, why don’t we just export this info and use it after the reinstallation?
We can do this easily by using PowerShell!
The idea is to export network adapter names and MAC addresses of our physical network adapters (excluding the virtual and team adapters), in a CSV file, so that we can use it later, to rename our adapters after the reinstallation:
A couple of days ago, another achievement was unlocked – Microsoft rewarded me with another MVP award (7th in a row, actually ), again for my contributions to the Cloud and Datacenter Management community.
Thank you, Microsoft! (and also a big “thank you” to all of you who were with me during this wonderful 7 years… thank you for all your support!)
And for the year ahead, I wish myself many “challenging” situations in the cloud and datacenter area… where so many interesting things take place.
As mentioned before, I was at the MobilityDay 2016 conference on Thursday, where I’ve had an honor to deliver a session about Citrix XenMobile & NetScaler solutions (yup, I know… it’s not Hyper-V… go figure… but my demo environment was still runnning on top of Hyper-V, so…).
Session was actually a short introduction to what Citrix XenMobile solution offers and how to set it all up, combined with NetScaler, for a complete management of mobile devices and mobile applications.
Conference was great, as always – so much old (and new) faces, with lots of fun. This time it was actually a 10th birthday of MobilityDay!