Running different distributions of Linux or variants of BSD on Hyper-V has gotten a lot easier than it was even 2-3 years ago, but there are still considerations one should take when building VMs or VM templates for deployment in Hyper-V (or Azure), and my distribution of choice for a very long time has been Debian stable. While it might not have the feature set that Ubuntu has running on Hyper-V or Azure, I prefer it partly because it’s comfortable to me, and partly because I tend to agree with the Debian creedo. This will likely work for most distributions out there (Ubuntu included), but since Ubuntu gets all the love on Hyper-V and Azure, I figured I’d do a post around how to get the best performance out of your Debian installations on Hyper-V. At the time of this writing, the current stable release is 8.3 (Jesse), so that’s what you’re going to see here. Note that this is based on the “best practices” documentation currently found here.
Permanent link to this article: http://www.cluberti.com/blog/2016/03/21/debian-8-3-on-hyper-v-the-recommended-way/
I apologize for the horrible picture, but I couldn’t take a snapshot during the upgrade from my physical box. Guess the Windows folks don’t bother testing the upgrade process with the taskbar in a non-standard location, eh?
Nothing to worry about, as the upgrade went fine. Was a little odd to see, though.
Permanent link to this article: http://www.cluberti.com/blog/2015/11/17/windows-10-upgrades-and-the-taskbar/
Permanent link to this article: http://www.cluberti.com/blog/2015/10/16/windows-10-vdi-configuration-script-published/
Permanent link to this article: http://www.cluberti.com/blog/2015/09/26/powershell-profile/
I’ve run into this with increasing frequency in my Server 2012R2 clusters, and it ended up being WMI corruption. IPConfig would show correct IP addressing (and even the teamed NICs created with Windows teaming), and ping would work; however, the network connections dialog box (ncpa.cpl) was completely empty, Server Manager said teaming was disabled, launching the teaming administration page (lbfoadmin.exe) would show “Host Unmanageable” as the status, and attempting to make any connection to any other machine other than ping would result in failure (for example, \\server\share would fail immediately with the host being unavailable).
Here are the steps I needed to use to get the machines up and running again (and I’ve restored from failed backups on a few to test and retest these steps, and in this particular order which did seem to matter, to validate):
Permanent link to this article: http://www.cluberti.com/blog/2015/01/20/network-connections-dialog-empty-teaming-host-unmanageable-fix/
Ever had a machine where WMI stopped working properly and needed to be rebuilt? Was it running something that does high volumes of WMI calls (like System Center agents, or Tivoli, or HP OpenView (to name a few regular problem children – I’m sure you can think of more)?
Here’s a PS script I run to increase memory per WMI process (and globally across the machine) available to WMI, as well as modifying it in the boot order (if you rely on RSOP, WMI’s default configuration means it’s possible it won’t be completely loaded properly when Group Policy runs, and can cause RSOP issues, amongst other things).
$oWMI=get-wmiobject -Namespace root -Class __ProviderHostQuotaConfiguration $oWMI.MemoryPerHost=768*1024*1024 $oWMI.MemoryAllHosts=2048*1024*1024 $oWMI.put() Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\Winmgmt -Name 'Group' -Value 'COM Infrastructure' winmgmt /standalonehost
Permanent link to this article: http://www.cluberti.com/blog/2015/01/12/make-wmi-more-robust-to-large-volumes-of-queries/
I’ve gotten an elevated number of requests recently on “how do I disable IPv6” or “what’s the best way to configure IPv6 in my environment”. I’m not entirely certain of why I’ve gotten so many recently, and I’m not sure if it’s a coincidence or if there’s more to it. However, what I’ve found is that most IT departments I’ve come across over the years simply go and set IPv6 to completely disabled via setting the disabledcomponents registry value to 0xffffffff. While this does indeed disable IPv6 entirely, I have to warn everyone I come across with this set that Microsoft doesn’t test this setting at all, and support for resolving issues with this set have usually resorted to setting disabledcomponents back to 0x0 and retesting, where things magically work, and that’s the extent of what is done for obvious reasons. This can (and sometimes does) also break functionality in Windows, and the one that most customers eventually run across is DirectAccess (with Remote Assistance in second).
Permanent link to this article: http://www.cluberti.com/blog/2014/12/15/disabling-ipv6-breaking-down-the-disabledcomponents-registry-value/
NOTE – This has been fixed with the MS14-053 update.
Install KB2966828, and restart (that is the awesome PSWindowsUpdate in action):
I’ve also encountered it causing issues with starting ASP.NET app pools and causing failures while running iisreset. A quick workaround is to add the public key token that is failing (b03f5f7f11d50a3a, found while debugging the crash) to the registry in the strong name validation bypass list:
Adding that will allow things to work again, until the problem is fixed by Microsoft at some point.
Permanent link to this article: http://www.cluberti.com/blog/2014/09/10/kb2966828-breaks-net-pipe-listener-adapter-service-and-more/
Our SCOM monitoring environment monitors one of our provisioning environments, where machines come and go regularly. These hosts are potentially in many, many different groups depending on function, and they can come and go many times a day. Yes, a group can be put into maintenance mode easily, but doing so for a host, remotely, isn’t necessarily as easy. Here’s a PowerShell script (created after reading about something similar on the Coretech Blog, here) that takes machine names passed in as the first parameter, places all machine names in an array, and sets each machine into maintenance mode in a particular SCOM management group. There’s little error checking here, so if you wanted to make this more robust, you’d probably want to add some parameter validation, etc. Without ado, here it is:
Permanent link to this article: http://www.cluberti.com/blog/2014/09/05/put-agent-into-maintenance-mode-remotely-via-powershell-in-scom-2012-r2/
I had a set of Windows 2008R2 servers today that were having trouble backing up the system state via Windows Server Backup – they would fail with the error “System writer is not found in the backup”. I scoured the ‘net and talked to colleagues, and all of the resolutions I could find involved re-registering components, re-securing things in the Cryptography Service (prompted by CAPI or CryptSvc errors in the event log), setting ownership on WinSXS folders, etc. I did not have any such errors in my logs to indicate a permissions issue – in fact, I saw no errors at all (usually good – not so much when something is broken!). However, every time I ran “vssadmin list writers”, indeed the system writer was missing.
Permanent link to this article: http://www.cluberti.com/blog/2014/07/18/vss-system-writer-missing-no-cryptsvc-or-capi-errors-no-problem/