@tim_g 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:

Finally, after all that.. I still had trouble connecting from the Windows 10 computer through Hyper-V Manager. After another hour of pounding my head, I finally got connected.

I had to:

1. Run Hyper-V Manager as administrator and use the account that was a local admin on Hyper-V.
2. Connect to server: hv01 - and do nothing with the "connect as other user" option

Prior to this, I was just running Hyper-V Manager not as admin (my regular domain user account) and then I would choose "connect as other user" and put in the credentials of the domain account which was local admin on the Hyper-V server. That always lead to the permissions error.

I thought you were using a user that was a member of the "Domain Admins" group?

I would log into my main Windows 10 system as my regular domain user but then whenever I ran Hyper-V Manager, I would attempt to connect to the Hyper-V server as the domain admin account that was also local admin on the Hyper-V server. I had also tried running Hyper-V Manager as admin and used the same DA account but it didn't work -- this was before I realized I was using the wrong ISO.

Between all of the things I tried to get it to work, I lost track of the steps. So once I got the correct thing installed, I wasn't sure what way I should run Hyper-V Manager and connect.. So essentially, if I am logged into my Windows 10 system as a regular user, I need to run Hyper-V Manager as the user that has admin access to the Hyper-V server.

It's been a pain in the ass but at least I've learned a lot out of this.

Finally, after all that.. I still had trouble connecting from the Windows 10 computer through Hyper-V Manager. After another hour of pounding my head, I finally got connected.

I had to:

1. Run Hyper-V Manager as administrator and use the account that was a local admin on Hyper-V.
2. Connect to server: hv01 - and do nothing with the "connect as other user" option

Prior to this, I was just running Hyper-V Manager not as admin (my regular domain user account) and then I would choose "connect as other user" and put in the credentials of the domain account which was local admin on the Hyper-V server. That always lead to the permissions error.

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

@dave247 This post is what I had to set for firewall on the Hyper-V Server after joining the domain.

https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016/10

After that I posted some images of what I did to setup teaming and such.

Great, thanks. I will get on that once the install is finished. I've been working on this for about 3 days now. Unreal.

@jaredbusch 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:

@jaredbusch 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:

@jaredbusch 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:

@jaredbusch 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:

@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:

So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

See this is why I am so confused.

1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

I'm downloading it now. I have a crappy old desktop that may support it here that i can attempt the initial install on.

Also, this thread is what I did on a defualt AD domain.

https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016.

about halfway down I posted the firewall rules I enabled and such.

I'm downloading it now too. I do notice the file name is a bit different than the ISO I had downloaded before, about 3 months ago.

• Old file: 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO
• New file: 14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

Maybe, just maybe, I am a total fucking idiot and somehow mixed my ISOs up...

You are a total idiot based on THAT post.

The first is Server. The second is Hyper-V Server

pfffffhahahahahahahahah... WHAT THE FUCK.

Blame MS for making it confusing as fuck in the name of licensing dollars.

No one will hold it against you.

Yeah this time during installation it didn't give me any install options. Just installing straight Hyper-V... sigh

I never cease to amaze myself at my own ability to constantly screw up due to not paying attention.

Sorry guys and thanks for your help. Thanks for dealing with me.

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

There is Windows Server 2016, and HyperV Server 2016. One you do not use as a hypervisor (even though you can), the other you do.

Don't confuse the two.

Yes see but I already know this!!!!!!!!!!! I swear I thought I downloaded the correct ISO. I WAS CAREFUL TO DOWNLOAD THE RIGHT ISO!!

Ok I swear I thought I downloaded the correct ISO. It was directly after I had a conversation with Scott over the phone about my VoIP debacle, and we got into servers and he told me about Hyper-V being completely free and blew my little fucking mind. SO I rushed out to Microsoft and downloaded it, and I know I KNOW I went to the right spot because I was specifically careful to download the file under "Microsoft Hyper-V Server 2016" and not the one for regular Server 2016.

If this was my problem all along then I'm going to owe you all an apology and a beer.

@jaredbusch 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:

@jaredbusch 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:

@jaredbusch 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:

@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:

So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

See this is why I am so confused.

1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

I'm downloading it now. I have a crappy old desktop that may support it here that i can attempt the initial install on.

Also, this thread is what I did on a defualt AD domain.

https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016.

about halfway down I posted the firewall rules I enabled and such.

I'm downloading it now too. I do notice the file name is a bit different than the ISO I had downloaded before, about 3 months ago.

• Old file: 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO
• New file: 14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

Maybe, just maybe, I am a total fucking idiot and somehow mixed my ISOs up...

You are a total idiot based on THAT post.

The first is Server. The second is Hyper-V Server

pfffffhahahahahahahahah... WHAT THE FUCK.

@jaredbusch 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:

@jaredbusch 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:

@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:

So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

See this is why I am so confused.

1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

I'm downloading it now. I have a crappy old desktop that may support it here that i can attempt the initial install on.

Also, this thread is what I did on a defualt AD domain.

https://mangolassi.it/topic/12296/my-experiences-with-hyper-v-server-2016.

about halfway down I posted the firewall rules I enabled and such.

I'm downloading it now too. I do notice the file name is a bit different than the ISO I had downloaded before, about 3 months ago.

• Old file: 14393.0.161119-1705.RS1_REFRESH_SERVER_EVAL_X64FRE_EN-US.ISO
• New file: 14393.0.161119-1705.RS1_REFRESH_SERVERHYPERCORE_OEM_X64FRE_EN-US.ISO

Maybe, just maybe, I am a total fucking idiot and somehow mixed my ISOs up...

@jaredbusch 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:

@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:

So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

See this is why I am so confused.

1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want money??

Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

Wait, when the fuck did they add a GUI to Hyper-V. I do not recall seeing that when I setup my last Hyper-V Server 2016 instance 8 months ago.

I don't know but I swear to God that I saw in three different attempts of installing hyper-v 2016 that there was the second option of having a desktop experience installed.

@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:

So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

Well... that's not a product option. To do that you have to buy and install a full Windows Server license, and then that license is tied to Hyper-V. If you od that, then you can admin it locally. But if you are even thinking about that, it's time to be on KVM.

See this is why I am so confused.

1. I can go to Microsoft and download Windows Server 2016, which when you install it, has options to install as core or GUI. Either way, I have to pay for a license because it's not free, core or GUI, RIGHT?? - https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2016
2. I can go to Microsoft and download the "evaluation" of Hyper-V Server 2016, which when I install, has the option to install standard evaluation, or desktop experience evaluation. I can just use the standard no GUI and it's 100% free, RIGHT?? So then what does it matter if I choose to install the free hypervisor with the desktop experience?? - https://www.microsoft.com/en-us/evalcenter/evaluate-hyper-v-server-2016

If both things are separate things, but installing the Desktop Experience means they are the same thing and I have to pay for a license to use Hyper-V, then I don't understand why they are selling them together... or wait is it because they want to rope you into having to pay them money??

Now I am not trying to make assumptions here or not thinking in a sensible GD way. I am just trying to navigate my way through options for installing Hyper-V, having it be free, and having it actually ****ing work.

So... if I just install Hyper-V Server 2016 WITH the Desktop Experience, I would be able to manage VM's by directly remoting into the server, right? Then I wouldn't have to mess with the Hyper-V Manager in Windows 10..

Would this somehow be different than a case where someone installs Windows Server 2016 and then adds the Hyper-V role?

And I know it would probably eat up some CPU power, but I really only want to run a few tiny VM's..

@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:

It's not like I just blindly downloaded XS and installed it without doing anything else. I've tried to get information. I've read the information on their website. I don't have endless amounts of time to dump into a full blown investigation to determine if their platform is actually dead or not.

I don't have any more hair to rip out.

Of course not, that's why no IT department should be less than ... well a lot of people. No one has the time to investigate this stuff. IT should always be a team. And IT should not investigate all options, there isn't time for that. Quickly determining projects that aren't currently viable (too early, too late, bad idea, bad vendor, etc.) is an important piece of that. Rule things out and move on. ESXi is easy to rule out of rthe average SMB due to cost and licensing overhead, as an example. Rule out, move on.

lmao. And we have vSphere 6.5 in my SMB environment...

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

Sadly, for Xen, XS was its only really nice full features distro and XS was not cared for by its steward. Suse continues to support "pure" Xen but it is a lot more complex than using a distro like XS. For shops with that special Xen need, it's out there. But it's mostly for large enterprises that are going to build an in house Xen team and provide their own support.

ok. Well thanks for the info. I really want Hyper-V to work but if I can't get it working, I will try KVM.

@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:

You talk to people like they already know everything but are choosing to ignore certain facts and then ask them why in the world they would make such an assumption, in what I assume is a subconscious attempt to set yourself up to sound like the smart guy. It's very frustrating.

Or, maybe I'm trying to help you figure out why you are making assumptions. How would I help you most - by just telling you you are wrong and acting like I know everything? by berating you with "facts" based on how I assume you were wrong? Or by asking you to provide the foundation for your assumptions

Assumptions are one of the biggest stumbling blocks in IT. Our field is full of them and they make good decision making almost impossible. Learning to look at out assumptions, question them, and dig in to figure out if they are valid or not is very, very important.

In this case, you approached with a number of assumptions - like that XS was active (maybe it is, but it doesn't appear to be and the terrible 7.2 release is one of the reasons that we feel this way) or that XS was a hypervisor, or that XS was one of the big three, that you didn't present until quite far along. Now, I think it is worth looking at why you felt these were good assumptions. What was their source? Maybe you have a bad source of info. Maybe you are processing good info in a bad way. Maybe I'm wrong and they are all good assumptions.

It's impossible to know what assumptions you are basing decisions on until they are stated. Once stated, often they are worth testing to see if they are valid. You'd be amazed how many IT issues we resolve simply by removing a bad assumption that was never mentioned.

I don't know man... you could have just given me some specific examples or sources that show how the latest releases of XS are terrible. Although, to be fair, I didn't even realize how it was different that Xen. I'm sure that's common...

I can't question every single assumption and meticulously double check every single thing I look at as that would be endless rabbit holes. Plain and simple: I assumed XenServer was still a thing because I've seen it talked about in numerous threads, there has been a recent release and their website makes no mention that they are no longer supporting their project.

Now what you are suggesting is almost that they are being deceptive in maintaining their website and software in an attempt to continue to take in money, but not really provide acceptable support for their product. ANY other company could be doing that. You could say Microsoft is doing that on a larger scale. They release updates that break things sometimes. Does that mean that I should stop and say, wait a minute, I think this project is dead and I will no longer use Microsoft products? Yes? No? I don't know.

It's not like I just blindly downloaded XS and installed it without doing anything else. I've tried to get information. I've read the information on their website. I don't have endless amounts of time to dump into a full blown investigation to determine if their platform is actually dead or not.

I don't have any more hair to rip out.

@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:

Now I am only looking at XenServer for the first time and since it's one of the three main free hypervisors, I wanted to consider using it unless there's a really clear reason not to. You say it's a ghost ship with major issues that haven't been fixed, so that's at least something. But I have other people suggesting I use it. You can see why I'm questioning what you say about it being dead right??

XS is not a hypervisor. XS is a specific distribution of Xen. Xen is the hypervisor. Xen is the oldest, but by far the fourth place, of the four main hypervisors.

It's fine to question why we feel it is dead. It's how you present things like the website as if a commercial vendor trying to make a quick buck is an indicator as to the engineering of a project. That requires me to either ignore the point, or explain why companies put up websites to make money and how software gets abandoned.

If you want to know why we feel it is dead, I would suggest asking more like "Oh, I had the impression it was still active, what are the indicators that make you feel it is dead." Instead of challenging with marketing and sales resources from a vendor.

Does that make sense?

blinks

Let me ask this then: Is Xen dead? Is Xen free? Should I use Xen as an alternative to KVM or Hyper-V?

@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:

@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:

@dbeato 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:

@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:

@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?

I'm not even sure what you mean to imply by this question. Why would the status of a project affect vendors trying to make money from people buying it or things around it?

Oh come on, you know what I meant. I suppose yes the obvious answer is in case someone wants to send them money.. but I can just download XenServer and use it for free can't I? No money there..

You certainly can use it and it is free but the issue is the development moving forward with security and feature updates.

hmm.. I'm talking about xenserver.org and it appears to still be active.. are we talking about the same thing??

You are using active to mean "the company is still making money", we are using "dead" to mean "there is no real further development and no future to the platform."

Can you provide me with a source that shows that the development of the platform is no longer happening? I mean, right on the front page it says that 7.2 was released May of 2017.

Or are you suggesting that they are continuing to develop their dead platform in an attempt to get people to continue giving them money?

Release numbers tell us nothing. What in 7.2 was so big that you feel its release constitutes a viable future for the product? Especially when we are talking about a system built on outdated tech like EXT3.

I don't know! I haven't even used it yet! I only brought it up earlier in the thread because I was asking about Hyper-V alternatives and then you said not to use it because it's a dead platform. I didn't think you were wrong but I was trying to understand why you would say that when their website makes it seem like it's alive.

You talk to people like they already know everything but are choosing to ignore certain facts and then ask them why in the world they would make such an assumption, in what I assume is a subconscious attempt to set yourself up to sound like the smart guy. It's very frustrating.

Now I am only looking at XenServer for the first time and since it's one of the three main free hypervisors, I wanted to consider using it unless there's a really clear reason not to. You say it's a ghost ship with major issues that haven't been fixed, so that's at least something. But I have other people suggesting I use it. You can see why I'm questioning what you say about it being dead right??

rips hair out

@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:

@dbeato 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:

@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:

@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?

I'm not even sure what you mean to imply by this question. Why would the status of a project affect vendors trying to make money from people buying it or things around it?

Oh come on, you know what I meant. I suppose yes the obvious answer is in case someone wants to send them money.. but I can just download XenServer and use it for free can't I? No money there..

You certainly can use it and it is free but the issue is the development moving forward with security and feature updates.

hmm.. I'm talking about xenserver.org and it appears to still be active.. are we talking about the same thing??

You are using active to mean "the company is still making money", we are using "dead" to mean "there is no real further development and no future to the platform."

Can you provide me with a source that shows that the development of the platform is no longer happening? I mean, right on the front page it says that 7.2 was released May of 2017.

Or are you suggesting that they are continuing to develop their dead platform in an attempt to get people to continue giving them money?

@dbeato 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:

@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:

@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?

I'm not even sure what you mean to imply by this question. Why would the status of a project affect vendors trying to make money from people buying it or things around it?

Oh come on, you know what I meant. I suppose yes the obvious answer is in case someone wants to send them money.. but I can just download XenServer and use it for free can't I? No money there..

You certainly can use it and it is free but the issue is the development moving forward with security and feature updates.

hmm.. I'm talking about xenserver.org and it appears to still be active.. are we talking about the same thing??

@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:

@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?

I'm not even sure what you mean to imply by this question. Why would the status of a project affect vendors trying to make money from people buying it or things around it?

Oh come on, you know what I meant. I suppose yes the obvious answer is in case someone wants to send them money.. but I can just download XenServer and use it for free can't I? No money there..

@tim_g 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:

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

I've been using it that way since forever.

Hyper-V 2016 and Win10 1703 to manage it.

Any Win10 computer that is joined to the domain can manage the Hyper-V server simply by logging in with the correct credentials, or like you are doing, providing the correct credentials when adding the server to Hyper-V Manager.

Geeze.. would it be possible for you to list out the exact steps you took from installing Hyper-V all the way to connecting to the server via the Hyper-V Manager in Windows 10?

I''ve gone through everything twice now and I just can't get it working...