travis' brain dump

Author Archive

when a vacation yields you finally fixing your blog

by on Oct.27, 2019, under General, Personal

Ok, so… anyone who has visited my site in the last year has probably tapped their fingers on the desk for more than a few moments waiting for content to load. Well, you weren’t the only one and I’m pretty sure that was one of the reasons why I didn’t update more content out here. It’s been just as much a pain for me, but I’ve lacked the time to actually dig into it and figure out what’s going on.

With my vacation ending today, I figured I’d do one more me thing before I return to work tomorrow… So with that, I’m pleased to say, the sites is working much cleaner now that I’ve slimmed down some of the plugins; removed outside sources from loading content to the blog; upgraded and tweaked php significantly and did some pretty neat stuff with the sql backend. In short, I believe became a victim of bloating my own blog and essentially shot myself in the foot because of it.

So… will I get to posting useful items anytime soon? I honestly don’t know. I’d like to think I will but given the last year and my work schedule working through a large merger, I really got burned out and didn’t want to do anything “personal” in the technology world. The sad part? I usually dump stuff here that I know I’ll forgot and I’ve forgotten quite a bit of the cool stuff I figured out over the last year because I didn’t dump it off here for reference later. It may work out, I’ll probably end up repeating some of this work as we prepare to do some similar activities in moving objects around our domain, in the cloud and into a dumpster, so we’ll see. 🙂

For now, one less thing to haunt me, lol.

Leave a Comment more...

Skype For Business: Invalid incoming HTTPS certificate

by on Dec.15, 2018, under Tech Stuff

Skype for Business Front End Server
Event ID 32042 – LS User Services – Invalid incoming HTTPS Certificate

I ran into this issue recently when someone thought it’d be cute to have the intermediate and root certs for a domain sitting in the same container (Trusted Root Certification Authorities). There’s a reason we have different containers folks. 🙂

Needless to say I was not amused after wasting an hour or so trying to figure out just why this error kept popping up in my event logs and the FE services wouldn’t come up. The worst part? I’d looked at the certificate objects and because these two certs looked almost identical in name, I missed them entirely during my search. 

So after doing a little digging around, I was pointed back towards a problem with a chain. There were a few examples of some Powershell to accomplish what I needed, but I liked this one the best. It allowed for me to see the list of my offenders easily. 

Get-ChildItem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} |fl FriendlyName,Subject,Issuer

Once run, any certificate listed is going to be a cert you need to take a look at. You’ll most likely either move these certificates to the Intermediate or Personal containers. Just be careful where you move stuff so you don’t create new problems for yourself. 

Hopefully you can save yourself some time by having this handy. 

Leave a Comment more...

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...

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!