Fear not. Just grab mbr2gpt.exe from the \windows\system32 folder on a windows 10 machine and drop it anywhere you want on the new server, then run:
mbr2gpt /convert /disk:X /allowfullos
and you will be ready to restart and set your bios to UEFI support and finishing booting to your new uefi partition!
@JasGot said in Remote Hyper-V Manager Woes:
@JaredBusch said in Remote Hyper-V Manager Woes:
I don't use RDP anyway. I use ScreenConnect or MeshCentral for console access.
I don't either...... once I can get ScreenConnect installed. I haven't even tried to install SC on Hyper-V Server yet, does it install and work?
Sweet! Piece of cake! SC installed lickity split.
@JaredBusch said in Remote Hyper-V Manager Woes:
I don't use RDP anyway. I use ScreenConnect or MeshCentral for console access.
I don't either...... once I can get ScreenConnect installed. I haven't even tried to install SC on Hyper-V Server yet, does it install and work?
@Dashrender said in Remote Hyper-V Manager Woes:
Well - he didn't mention the whole host of other settings he had already done to make 2016 work, which still need to be done.
That's right. It was already addressed early on:
@JasGot said in Remote Hyper-V Manager Woes:
@DustinB3403 said in Remote Hyper-V Manager Woes:
There is a guide here by Timothy Gruber which appears to do what you want.
This is the guide that got me past all of the misinformation, and had all the important info left out by MS. This is by far the best write-up out there for a domain connected PC to manage a workgroup Hyper-V Server
Well, I'll be dipped. After installing KB4482887, and running these two commands on the server: "Enable-PSRemoting" and "Enable-WSManCredSSP -Role server"; I came back to Hyper-V Manager and BAM! connected right up!
@JasGot said in Remote Hyper-V Manager Woes:
http://www.catalog.update.microsoft.com/Search.aspx?q=KB4482887
This was released yesterday.
And it worked! Yippee. Now I can start trying to get Hyper-V Manager to work.
@scottalanmiller said in Remote Hyper-V Manager Woes:
@Dashrender said in Remote Hyper-V Manager Woes:
Well - apparently Hyper-V 2019 has had an issue where RDS doesn't work.
That's some serious fail right there.
Yes. So I am in worse shape now. But I did find an KB fix to allow RDP to Hyper-V Server 2019: http://www.catalog.update.microsoft.com/Search.aspx?q=KB4482887
This was released yesterday.
@scottalanmiller said in Remote Hyper-V Manager Woes:
Yeah, given that you are not in production yet. More stable, faster, more modern.
Invalid links. Can't download it.......
In Volume License Center? We have it in production, so it is definitely available.
Eval Center. I'll try VLC now.
@scottalanmiller said in Remote Hyper-V Manager Woes:
Yeah, given that you are not in production yet. More stable, faster, more modern.
Invalid links. Can't download it.......
@DustinB3403 said in Remote Hyper-V Manager Woes:
@Dashrender said in Remote Hyper-V Manager Woes:
I'm curious - why are you deploying/testing 2016 instead of Hyper-V 2019?
Good question.
But I don't have a good answer....
@DustinB3403 said in Remote Hyper-V Manager Woes:
There is a guide here by Timothy Gruber which appears to do what you want.
This is the guide that got me past all of the misinformation, and had all the important info left out by MS. This is by far the best write-up out there for a domain connected PC to manage a workgroup Hyper-V Server
@DustinB3403 said in Remote Hyper-V Manager Woes:
I assume you don't want the Hyper-V server connected to the domain for some reason.
There is a guide here by Timothy Gruber which appears to do what you want.
It's just a test box, and honestly, I like to get servers built as far as I can before we deliver them. So joining the domain is something I would prefer to do at a later time; once the server has been delivered on site.
I'm sure you'd like to stay within MS for this, but a year or so ago, I had a similar issue at a machine shop. After a few hours of getting no where, we threw an old copy of Lantastic on the CNC PC and the server. They were up and running in about 15 minutes.
Maybe this will get you thinking from another angle that may lead you to your solution.
Based on a comment in another thread I decided to take a look at MS Hyper-V Server 2016.
Simple to install. I LOVE the feel of it at the console and through RDP. It takes me back to my Dos and Unix days. 
Plus, It's almost identical to ScreenConnect Backstage, which is my new favorite place to work.
However........ After a whole week, I still cannot mange it from my workstation.
I have everything except one piece set properly, based on hours and hours of reading and trying.
Is it even possible to manage a workgroup Hyper-V Server from a Domain PC through Hyper-V Manager?
I am getting this error:
An error occurred while attempting to connect to server.
"R510-Hyperv". Check that the Virtual Machine Management service is running and that you are authorized to connect to the server.
The operation is not supported.
That's cool, look what a bunch of hyphens did!
Virtual Machine Management services is running.
I can successfully map a drive to it with Net Use, I can successfully RDP to it, I can ping it by name...... I just can't get Hyper-V Manager to connect to it.
Any ideas? Anyone been here before?
@dbeato said in Windows 10 Allowing a Regular User to Launch One Application as Admin:
This is what I use
We've been doing it this way for years.
@pmoncho said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2014 on same host:
@JasGot said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2014 on same host:
Winner Winner, Chicken Dinner. It was MDTC and Windows Firewall. (Which is frustrating, because the firewall is turned off for the domain!)
Good job at troubleshooting. I'm wondering what led you down this path versus something related to Networking, hard drives or software drivers?
Remembered it from several years ago with another SQL based application. Don't know what made me think of it at 1:30am. But I'm ok with it!
@Emad-R said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2014 on same host:
@JasGot said in Slow MS SQL Queries between Windows 10 VMs and MS SQL 2014 on same host:
Distributed Transaction Coordinator
I have never heard of
MS Distributed Transaction Coordinator
And i think im privileged, it seems like failed attempt to fix something that should be baked in already or something over complex and can be simply be reverse proxy
I don't follow..... MSDTC has been around a long time. You'll find it preconfigured in all Windows Firewall apps.
Winner Winner, Chicken Dinner. It was MDTC and Windows Firewall. (Which is frustrating, because the firewall is turned off for the domain!)
I won't know definitively until mid morning, but I think I sorted it out. It was the Distributed Transaction Coordinator in the Windows 10 VDI firewall. I allowed it for the domain profile and now the queries are running faster than I can witness.
From 15-16 seconds....to under one second. Holy crap!
I'll report back in a few hours.