Posts made by dave247

Guys, does anyone here have a 2016 Hyper-V and Windows 10 setup, both joined to the domain? Otherwise, is anyone willing to set it up as a test to see if you get it working? I really want to figure out what my problem is. I think I've literally tried everything at this point and I just can't connect. I even tried adding the Hyper-V Management tools from another Windows 10 system and got the same errors..

@matteo-nunziati said in Trying to set up Hyper-V Server 2016, ripping my hair out:

Yes. I did that a while back. Running winrm quickconfig, it tells me this on both Windows 10 pc and Hyper-V server:
"WinRM service is already running on this machine.
WinRM is already set up for remote management on this computer."

@coliver said in Trying to set up Hyper-V Server 2016, ripping my hair out:

What version of Windows 10? Did you mention that already?

Already mentioned it above, but here it is:

• Windows 10 Pro
• Version: 1703
• OS Build: 15063.726

And FWIW: My Windows 10 isn't activated yet. I really don't think that matters since everything else works, I just haven't had a chance to purchase another license yet.

@tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:

Get-VM -ComputerName HV01

That yields the following:

So it looks like it doesn't like something about my installation of Hyper-V Management tools or something? I don't know.. really strange.

@scottalanmiller said in Trying to set up Hyper-V Server 2016, ripping my hair out:

@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

At this point, I'm considering trying out XenServer..

Don't, it's a dead project. Try KVM.

I don't doubt for a second that you know what you're talking about, but if it's a dead project, then why the heck is their site still up and allowing people to download and use their products?

@tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:

I don't think the problem is HV01.

If you have just done a fresh install, joined it to the domain, and enabled remote management... you're good on that end.

Now on your Win10 computer, if you are logged in as a Domain Admin, you shouldn't have any trouble accessing it via Hyper-V Managaer.

You can try running Enable-PSRemoting on your Win10 computer, I think #4 on the Hyper-V host does the same thing, which looks like it's already done.

I have not logged in as a domain admin on my Windows 10 workstation however I have tried running the hyper-v manager as an administrator and use the domain admin credentials for that. I thought it didn't matter if I was logged into my workstation as a domain admin, and I wouldn't want to be doing that anyways in a normal environment, and running hyper-v as admin seem like the reasonable alternative. I can still give it a try though. EDIT: I tried it and it still doesn't work.

I have already run Enable-PSRemoting on both systems.

@tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:

That's just so weird, these problems you are having.

If I list a group policy setting, would you be able to apply it to HV01 and your desktop?

Yes, I know, very very frustrating. I actually just got done completely re-installing Hyper-V server 2016 just to go through all the steps again to see if I missed anything. It's now set up and joined to the domain again and I am able to RDP in as the domain user, but still I can not connect to it via the Hyper-V Manager in Windows 10. I get this error when I specify the proper user to connect with:

And I have applied this GPO to my system:

@dbeato said in Trying to set up Hyper-V Server 2016, ripping my hair out:

@black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:

I just don’t recall having any issue with connecting to Hyper-V 2016 when both server and workstation is on the same domain.

The issue you are having makes sense if the server is not on a domain.

That is something to look for, @dave247 if you go to \servername\c$ and enter the server credentials and open the administrative share. Then now attempt to connect to the server, are you able to.

Also what problems are you having installing RSAT and what Windows 10 version do you have?

Yes, I am able to get right into the C$ no problem. I still can't connect via Hyper-V Manager in Windows 10.

My Windows 10 info:

• Windows 10 Pro
• Version: 1703
• OS Build: 15063.726

@black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:

I just don’t recall having any issue with connecting to Hyper-V 2016 when both server and workstation is on the same domain.

The issue you are having makes sense if the server is not on a domain.

Well they are in fact on the same domain and yes I have looked at all the links and taken all the steps that apply. I have joined HV01 to the domain and I see it listed in AD as a computer and I have dropped it in the "Servers" OU.

At this point, I'm considering trying out XenServer..

@tim_g said in Trying to set up Hyper-V Server 2016, ripping my hair out:

What error are you getting?

This is the main error I'm getting now: "<< Failed to connect to server "<Computerame>". Make sure the administrative service is running on virtual machines and you are authorized to connect to the server.
The Hyper-V administration tools did not allow access to an expected WMI class on computer "<Computerame>".
This may indicate that the Hyper-V platform is not installed on the computer or that is the version of the Hyper-V platform
Hyper-V platform is not compatible with these management tools"

Also, I am getting,

"Enable delegation of user credentials? This computer is not configured to allow delegation of user credentials. Do you want to allow delegation of user credentials to HV01.domain.com?"

I have enabled remote management and added a domain admin as a local administrator to see if I could connect from my Windows 10 management computer. I just can't get in.

Screenshot of my console:

I also tried running these Powershell commands as admin and I still can't connect. I don't really understand the error messages:

Also, I have also attempted to install RSAT on my Windows 10 computer but still no luck.

@black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:

@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

Additional info:

On my Windows 10 system, I've enabled ONLY the Hyper-V Management Tools, and not the Hyper-V Platform.

My domain user account I use on this Windows 10 system is not a local admin, just a regular low priveleged user. However, I have tried running the Hyper-V Manager as admin and put in the credentials of the domain user that I also assigned as my Hyper-V server admin. When I go that route, I get the error:

"<< Failed to connect to server "<Computerame>". Make sure the administrative service
Is running on virtual machines and you are authorized to connect to the server.
The Hyper-V administration tools did not allow access to an expected WMI class on computer "<Computerame>".
This may indicate that the Hyper-V platform is not installed on the computer or that is the version of the Hyper-V platform
Hyper-V platform is not compatible with these management tools"

Have you confirmed that you can connect with a domain admin account? At least with that you can confirm its an permission issue?

Yes I've tried with a DA account but no dice.

@black3dynamite said in Trying to set up Hyper-V Server 2016, ripping my hair out:

@dave247 said in Trying to set up Hyper-V Server 2016, ripping my hair out:

Additional info:

On my Windows 10 system, I've enabled ONLY the Hyper-V Management Tools, and not the Hyper-V Platform.

My domain user account I use on this Windows 10 system is not a local admin, just a regular low priveleged user. However, I have tried running the Hyper-V Manager as admin and put in the credentials of the domain user that I also assigned as my Hyper-V server admin. When I go that route, I get the error:

"<< Failed to connect to server "<Computerame>". Make sure the administrative service
Is running on virtual machines and you are authorized to connect to the server.
The Hyper-V administration tools did not allow access to an expected WMI class on computer "<Computerame>".
This may indicate that the Hyper-V platform is not installed on the computer or that is the version of the Hyper-V platform
Hyper-V platform is not compatible with these management tools"

Have you confirmed that you can connect with a domain admin account? At least with that you can confirm its an permission issue?

Yes I've tried with a DA account but no dice. I can log in directly to the hyper-v server with the da account but not through the hyper-v manager on my Windows 10 system.

Additional info:

On my Windows 10 system, I've enabled ONLY the Hyper-V Management Tools, and not the Hyper-V Platform.

My domain user account I use on this Windows 10 system is not a local admin, just a regular low priveleged user. However, I have tried running the Hyper-V Manager as admin and put in the credentials of the domain user that I also assigned as my Hyper-V server admin. When I go that route, I get the error:

"<< Failed to connect to server "<Computerame>". Make sure the administrative service
Is running on virtual machines and you are authorized to connect to the server.
The Hyper-V administration tools did not allow access to an expected WMI class on computer "<Computerame>".
This may indicate that the Hyper-V platform is not installed on the computer or that is the version of the Hyper-V platform
Hyper-V platform is not compatible with these management tools"

@mike-davis said in Trying to set up Hyper-V Server 2016, ripping my hair out:

Is your Windows 10 workstation joined to the same domain your hyper-V host is? It sounds a lot like it's not. If that's the case, it's a real pain to get them to connect.

Yes, my Windows 10 workstation is joined to the domain, same one that the Hyper-V server is joined to. I haven't gotten back to this yet since it's the holidays but I plan to do a little more in the next day, then I'll report back.

Thanks for the help

I'm trying out Microsoft's Hyper-V 2016 server -- not the OS role, I'm talking about the actual Hypervisor without the "Desktop Experience" GUI. I got that installed and joined to our domain and then added an administrator and then I installed the Hyper-V management tools on my Windows 10 workstation and then I tried to connect to the server as that user. However I can't seem to get connected. It's constant errors.

Right now I'm stuck on "Enable delegation" as I get an error that says "Delegation of credentials to the server could not be enabled. CredSSP authentication is currently disabled.

I keep trying to google things but 90% of the stuff I find seems to be about setting up the Hyper-V role, not the straight Hypervisor. Then anything more explicit than that, such as with the CredSSP stuff, I just find about of stuff regarding PowerShell scripts.

I'm now trying to run Enable-WSManCredSSP commands according to this guide but it's not working...

I've been slowly doing this for hours now and I'm just ripping my hair out at this point. Is there a more straight-forward way to set up and manage Hyper-V without having to do a bunch of obscure steps? I just want to get to where I can install some VMs. See I've gotten used to the user friendliness of WMware where I can just connect to the hosts or vCenter via web browser and go from there.

Now I'm not crying about this because it's hard -- I enjoy learning challenges.. but right now I'm just drained and need some guidance. Otherwise I was considering installing some other free Hypervisor in hopes that it's easier to setup.

@rojoloco said in Where/who should I be buying Microsoft Server licensing from?:

@dave247 said in Where/who should I be buying Microsoft Server licensing from?:

One thing that's always fun is when I get a quote from my VAR and a quote form CDW and the price is different.. then it's like pitting against each other to fight for the sale..

Throw them all into the ring and let them fight it out for your business by lowballing each other. Then you'll see how much margin they have on these licenses (which is plenty). Since it is MS licenses, take the lowest price and run.

Thanks for all your input guys. This has really helped me.

@jaredbusch said in Need some guidance - replacing physical 2008 R2 DC with a virtual 2016 DC - keeping same name and IP:

And you do not have to use a CNAME. An A record is just fine too. For excample, notmydc can be an A record pointing to the same IP as DC1. Or it can be a CNAME pointing to the DNS name of DC1.

Got it.

Either way, when DC1 goes to shit

hahaha

@scottalanmiller said in Need some guidance - replacing physical 2008 R2 DC with a virtual 2016 DC - keeping same name and IP:

@dave247 said in Need some guidance - replacing physical 2008 R2 DC with a virtual 2016 DC - keeping same name and IP:

@jaredbusch said in Need some guidance - replacing physical 2008 R2 DC with a virtual 2016 DC - keeping same name and IP:

@dave247 said in Need some guidance - replacing physical 2008 R2 DC with a virtual 2016 DC - keeping same name and IP:

@scottalanmiller said in Need some guidance - replacing physical 2008 R2 DC with a virtual 2016 DC - keeping same name and IP:

@dave247 said in Need some guidance - replacing physical 2008 R2 DC with a virtual 2016 DC - keeping same name and IP:

@scottalanmiller said in Need some guidance - replacing physical 2008 R2 DC with a virtual 2016 DC - keeping same name and IP:

How I'd handle it....

Well, I'd not do it if possible and fix things pointing to something that they shouldn't here. That's the root level fix.

To go after a proximate fix...

1. Set up the new DC. Do NOT use the old IP or hostname.
2. Get it all working with the old machines in place.
3. Create a CNAME to point the old name to the new server's A record. Remove the old machine.
4. If you must, change the new IP to the old IP.

Ok, let's scratch everything I mentioned. If I were to do this the best practice way, would I simply:

1. Set up the new 3rd domain controller new name (DC3) and IP address
2. Pass the roles from DC1 to DC3
3. Finally, go through and point all "primary DNS" entries on Exchange and EVERYTHING else to the new DC3

If I perform the above steps, I am assuming no systems will have issues authenticating since they will all be reaching out to one of the three DCs, right? Therefore, I can gradually point systems to the new DC as needed.

Otherwise, please help me understand what I should do. I am going to spend my day tomorrow researching this stuff so I'm better educated on what I'm doing and can come up with an action plan.

Thank you

Systems should never be pointed to a DC. They shoudl be pointed to an alias for their service.

I don't quite understand this. In the TCP/IPv4 DNS settings, it only accepts an IP address, which are the DNS servers/domain controllers.

What @scottalanmiller is talking about is inside your applications and programs, they should always use a name value instead of an IP address.

Unless it is really crappy software, it should be able to do that.

You are correct in your devices, you use IP/DNS manually if DHCP is not an option, but that should be extremely rare.

Edit: And Scott replied while I was. (teach me to be on the phone while responding).

oooh ok yes, I got that. I do use a name (not ip) for those. I'll still have to update them to say DC3 instead of DC1.. unless if I can just start using CNAMEs..

You can always use a CNAME. The app can't tell what is an A record or a CNAME record.

And I've just re-learned about this... so essentially I could have a CNAME called "DCGOUP" which would point to DC1, DC2, DC3, etc, and the app would just work?