travis' brain dump

Author Archive

Migrating Windows DNS Server

by on Dec.09, 2018, under Tech Stuff

Ever needed to migrate a non-AD integrated Windows DNS Server to another instance of Windows? I found myself in the situation to do so this weekend so I figured I’d share the process for reference. 

From the source server: 

  1. Create a folder for storing the migration files. (ex. c:\temp\dnsgmig)
  2. From an elevated command prompt, execute the following commands:
    1. ‘reg export “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Parameters” c:\temp\dnsmig\dns-params.reg
    2. ‘reg export “HKEY_LOCAL_MACHINE\System\CurrentVersion\DNS Server” c:\temp\dnsmig\dns-version.reg
  3. Modify dns-params.reg and change “PreviousLocalHostname” to the fqdn of your new DNS server. If you using the same name, skip this step. 
  4. Copy the folder c:\windows\system32\dns to c:\temp\dnsmig\

Copy the source folder (c:\temp\dnsmig) to the destination server. (example will use the same folder name)

  1. From an elevated command prompt, execute the following command: 
    1. Stop-Service DNS
  2. Click to import your two registry files, dns-params.reg and dns-version.reg. You’ll be prompted each time to confirm you want to import the information. Click ‘Yes’. 
  3. Copy all of the files from c:\temp\dnsmig\dns to c:\windows\system32\dns
  4. From an elevated command prompt, execute the following command:
    1. Start-Service DNS

You should now be up and running. 

Leave a Comment more...

SCVMM Error 12711

by on May.19, 2017, under General

So while working on some virtual machines in the clusters we’ve been upgrading I’ve run across this error a couple of times and I figured it merited a post as one of the errors thrown in the mix wasn’t easily found in any solution online. 

Primary Error Description: 

Error (12711)
VMM cannot complete the WMI operation on the server (CLUSTERNAME) because of an error: [MSCluster_ResourceGroup.Name=”12df9151-eb2a-46e7-8a3e-58ae746b8783″] Not found
Unknown error (0x1002)

-or-

Error (12711)
VMM cannot complete the WMI operation on the server (CLUSTERNAME) because of an error: [MSCluster_ResourceGroup.Name=”12df9151-eb2a-46e7-8a3e-58ae746b8783″] The cluster resource could not be found  
The cluster resource could not be found (0x138F)

0x138F can be resolved by running the following in the VMM powershell: 

Get-ClusterResource -c CLUSTER.FQDN |Where {$_.ResourceType.Name -eq ‘Virtual Machine Configuration’} | Update-ClusterVirtualMachineConfiguration

0x1002 may require a little more involved work. However, before we dig into that one, make sure it’s not just some WMI problem on the host holding the cluster resources. Go into Failover Cluster Manager, right-click the cluster, hit more-actions and move core cluster resources to any other host. If this clears it up, great. If not, continue forward. 

I’ve had some success with pulling the resource and re-registering it. To accomplish this, you’ll need to remove the cluster resource and bring it back in as an update won’t cut it.

From the Failover Cluster Manager, find the virtual machine in the Failover Cluster Manager. Right click the resource and remove the item. It won’t delete it, but will remove the resource from the cluster and return it to the host it’s running on as a regular VM.

Once removed, expand the cluster name, right-click ‘Roles’ and select ‘Configure Roles’. In the list presented, select ‘Virtual Machine’ and click ‘Next’. You should see the machine you just removed in the list. Select it and complete the process to bring the resource back into the cluster. From VMM you should now be able to right-click the machine and select ‘Repair’ and ‘Ignore’ to resolve the issue. 

This issue is provided as-is with no warranty and if you end up deleting your VM, you’re on you own. 🙂 

Leave a Comment more...

MPIO on Nano Server

by on May.10, 2017, under Tech Stuff

After hunting around a little bit I found some great information on enabling and configuring MPIO on Nano Server. I figured, as always, I record down my thoughts here so I can reference them again later if needed and post it out publicly where it can be of some use to anyone wandering by. 

Useful Links: 

General information on MPIO from TechNet: Multpath I/O Overview

To enable MPIO on Nano Server, execute the following over your remote powershell session: 

Enable-WindowsOptionalFeature -Online -FeatureName MultiPathIO

Once enabled your SAN disks will be presented as duplicates (just as they are with MPIO under Windows Server), so you’ll need to execute additional powershell in order to claim or manage disks. 

Thankfully, Microsoft has published a script for this which can be downloaded from here: MPIO on NanoServer

It’s straight forward and works as designed, which feels odd sometimes when talking about Microsoft. 🙂 

Leave a Comment more...

Get BlockSize of Disks Using WMI & Powershell

by on Apr.12, 2017, under Tech Stuff

Ok, so I couldn’t find this earlier on the web easy enough, so I figured I’d stick it here for later if I ever need it again. I was trying to verify that my scripts had correctly formatted the volumes for SQL data with the correct block size. This should come in handy for anything else you need to verify block size with as well. 

$WMIQuery = “SELECT Label, Blocksize, Name FROM Win32_Volume WHERE FileSystem=’NTFS'”
Get-WmiObject -Query $WMIQuery -ComputerName ‘.’ | Select-Object Label, Blocksize, Name

Leave a Comment more...

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!