Fileserver Offline, Part Two

I woke up extra early today, my mind racing about this hard drive. If you remember from yesterday my operating system drive for HV-01 failed yesterday. I was able to replace it with a nice brand new SSD and reinstall the operating system. However one of the eight data drives in the machine, used for fileserver, is not accessible.

The drive in question is actually number six. I locate six in the case, hoping I may just have a failed SATA cable. Even better, the cable wasn't fully inserted last night. This is why I hate late night jobs, you're tired and rushing, and very prone to small, simple, and silly mistakes. I firmly plug the cable in and power HV-01 back on. Poof! Drive six is available along with the other seven drives. We're in business now!

I let HV-01 begin to download the available Windows Updates while I take the little one to school.

When I get back I begin to connect HV-01 to my administrative tools. In Windows Admin Center I remove the old instance of HV-01 and add the new instance of HV-01. Next I remove the old instance from Hyper-V Manager on my desktop but I'm unable to add the new instance.

Steps performed on HV-01 via PowerShell

• Enable-PSRemoting
• Enable-WSManCredSSP -Role server

Steps performed on desktop via Windows Terminal

• Set-Item WSMan:\localhost\Client\TrustedHosts -Value "hv-01.domain.local"
• Enable-WSManCredSSP -Role -client -DelegateComputer "hv-01.domain.local"

Steps performed on desktop via Local Group Policy

• I navigate to Computer Configuration --> Administative Templates --> System --> Credential Delegation
• I select Allow delegating fresh credentials with MTLM-only server authentication and then click Enable
• I add wsman/hv-01.domain.local and hv-01.domain.local

This resolves my issue and I can not connect to HV-01 via Hyper-V Manager. Adding the new instance of HV-01 to good old Server Manager is quick and painless.