Storage Provisioning For a Single Hyper-V Server Setup
-
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
@JaredBusch said in Storage Provisioning For a Single Hyper-V Server Setup:
I get that you are new to setting this up, and it is great that you reached out for advice. But you should not be learning, in production, on a client system FFS.
It's his boss that should be in trouble, or whoever decided to have him learn in that position.
I said that.
Might even be the client demanding it... same client that thinks that they themselves should be in charge of IT and makes some pretty basic day one mistakes like getting mismatched drives and buying gear before knowing the needed specs.
Unlikely, a client paying a MSP or consulting firm to implment should be getting the advice from that firm. I have seen it otherwise, yes. But I fire those clients or do not take the contracts. Not going to lose money ourselves by working with them.
-
@Dashrender said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@Dashrender said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
what way are you finding the RSAT tools cumbersome? I find them incredible easy. Where are you running into complications? Also, you need to be on Windows 10, obviously. Again, whoever chose Windows as your environment made most of these decisions for you.
I keep getting an access denied, even though, I use RSAT with proper credentials belonging to the remote server..
But you are using the wrong version, right? So that's not unexpected.
Seems more like an access issue, rather than a version issue
Possible. Are you using a VPN? Is there Active Directory?
- Make sure AD is not tied to Hyper-V, Hyper-V in this setup should not use AD at all. It needs to be totally independent.
- Use a local Windows 10 machine at the customer site and RDP to that, don't use a VPN to customer sites (for loads of reasons, but simplicity is the one here.)
No AD as yet... I RDP to the server, via VPN
What kind of VPN do you have?
SSL VPN
aww.. SSL VPN - that might be your problem. I know that RPD can work over SSL VPN, but RSAT might not.
SSL VPN does not support a lot of traffic types. There's a good chance the required ports aren't being routed correctly over your SSL VPN.
@scottalanmiller answered already, but in my own terms, WTF you smokin'?
A VPN is a VPN. Or it is some not VPN trying to fake it like a cheap hooker.
-
@JaredBusch said in Storage Provisioning For a Single Hyper-V Server Setup:
@Dashrender said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@Dashrender said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
what way are you finding the RSAT tools cumbersome? I find them incredible easy. Where are you running into complications? Also, you need to be on Windows 10, obviously. Again, whoever chose Windows as your environment made most of these decisions for you.
I keep getting an access denied, even though, I use RSAT with proper credentials belonging to the remote server..
But you are using the wrong version, right? So that's not unexpected.
Seems more like an access issue, rather than a version issue
Possible. Are you using a VPN? Is there Active Directory?
- Make sure AD is not tied to Hyper-V, Hyper-V in this setup should not use AD at all. It needs to be totally independent.
- Use a local Windows 10 machine at the customer site and RDP to that, don't use a VPN to customer sites (for loads of reasons, but simplicity is the one here.)
No AD as yet... I RDP to the server, via VPN
What kind of VPN do you have?
SSL VPN
aww.. SSL VPN - that might be your problem. I know that RPD can work over SSL VPN, but RSAT might not.
SSL VPN does not support a lot of traffic types. There's a good chance the required ports aren't being routed correctly over your SSL VPN.
@scottalanmiller answered already, but in my own terms, WTF you smokin'?
A VPN is a VPN. Or it is some not VPN trying to fake it like a cheap hooker.
You seem to be speaking from experience ..
-
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@JaredBusch said in Storage Provisioning For a Single Hyper-V Server Setup:
@Dashrender said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@Dashrender said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@scottalanmiller said in Storage Provisioning For a Single Hyper-V Server Setup:
what way are you finding the RSAT tools cumbersome? I find them incredible easy. Where are you running into complications? Also, you need to be on Windows 10, obviously. Again, whoever chose Windows as your environment made most of these decisions for you.
I keep getting an access denied, even though, I use RSAT with proper credentials belonging to the remote server..
But you are using the wrong version, right? So that's not unexpected.
Seems more like an access issue, rather than a version issue
Possible. Are you using a VPN? Is there Active Directory?
- Make sure AD is not tied to Hyper-V, Hyper-V in this setup should not use AD at all. It needs to be totally independent.
- Use a local Windows 10 machine at the customer site and RDP to that, don't use a VPN to customer sites (for loads of reasons, but simplicity is the one here.)
No AD as yet... I RDP to the server, via VPN
What kind of VPN do you have?
SSL VPN
aww.. SSL VPN - that might be your problem. I know that RPD can work over SSL VPN, but RSAT might not.
SSL VPN does not support a lot of traffic types. There's a good chance the required ports aren't being routed correctly over your SSL VPN.
@scottalanmiller answered already, but in my own terms, WTF you smokin'?
A VPN is a VPN. Or it is some not VPN trying to fake it like a cheap hooker.
You seem to be speaking from experience ..
He has VPN'd before
-
hello,
I managed to convince the seniors and client, and they've agreed upon the following : -
-
list item To switch to RAID10, at the cost of the losing 1TB from the 2x3TB HDDs.since RAID10 always creates an array size, based on the smallest HDD(s)
-
Use Windows 2016, through-out - for the HostOS as well as the guest VMs
However, they insisted that I start-off with the Desktop Experience(with just Hyper-V role enabled), setup everything, and then, once everything is working smoothly, down-grade to Server Core .... Their logic is that, it is better this way since I'm a newbie, and that Server Core is supported by MS, whereas Hyper-V server is not ..
Anyway, I carved-out a 64GB (C:)partition from the 3.6TB of usable space, and installed the Host OS, and enabled the Hyper-V role.
Now, does it make sense to further divy-up the HDD, for each VM, and the data ? Or should I just created another partition (D:), and allocate it the rest of the HDD space, then create all the VHDXs and VMs on this partition ?
-
-
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
whereas Hyper-V server is not ..
WHAT? what does who meant that it's not supported? Of course it is, if you pay for support, just like server core and normal server are. The biggest question might be is if the hardware is on the HCL, but even that is actually rarely a real worry.
-
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
Now, does it make sense to further divy-up the HDD, for each VM, and the data ? Or should I just created another partition (D:), and allocate it the rest of the HDD space, then create all the VHDXs and VMs on this partition ?
No, make the single largest partition you can. Put all VMs' in there.
It's even debatable if you needed to create the 64 separate partition for the OS, but I see both sides, so you like, fine go with it.
-
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
hello,
I managed to convince the seniors and client, and they've agreed upon the following : -
-
list item To switch to RAID10, at the cost of the losing 1TB from the 2x3TB HDDs.since RAID10 always creates an array size, based on the smallest HDD(s)
-
Use Windows 2016, through-out - for the HostOS as well as the guest VMs
However, they insisted that I start-off with the Desktop Experience(with just Hyper-V role enabled), setup everything, and then, once everything is working smoothly, down-grade to Server Core .... Their logic is that, it is better this way since I'm a newbie, and that Server Core is supported by MS, whereas Hyper-V server is not ..
Anyway, I carved-out a 64GB (C:)partition from the 3.6TB of usable space, and installed the Host OS, and enabled the Hyper-V role.
Uhm, installed the OS AND enabled Hyper-V role, or installed just Hyper-V roll during installation? Two very different things according to the licensing.
Now, does it make sense to further divy-up the HDD, for each VM, and the data ? Or should I just created another partition (D:), and allocate it the rest of the HDD space, then create all the VHDXs and VMs on this partition ?
I'd just use one partition to store all the VHDXs on.
-
-
@travisdh1 said in Storage Provisioning For a Single Hyper-V Server Setup:
Uhm, installed the OS AND enabled Hyper-V role, or installed just Hyper-V roll during installation? Two very different things according to the licensing.
No it is not. There is only one server OS. Server 2016. You add roles as needed.
There is only the OS and roles on the OS. The only licensing issue here would be to ensure that there are no roles other than Hyper-V enabled.
Enabling or disabling the GUI is not adding a role.
You always only install the OS and enable the roles you want.
This is how MS Server has worked forever.
-
In response to converting from Desktop Experience to Core. You will have to do a fresh install.
"Unlike some previous releases of Windows Server, you cannot convert between Server Core and Server with Desktop Experience after installation. If you install Server with Desktop Experience and later decide to use Server Core, you should do a fresh installation."
-
@JaredBusch said in Storage Provisioning For a Single Hyper-V Server Setup:
@travisdh1 said in Storage Provisioning For a Single Hyper-V Server Setup:
Uhm, installed the OS AND enabled Hyper-V role, or installed just Hyper-V roll during installation? Two very different things according to the licensing.
No it is not. There is only one server OS. Server 2016. You add roles as needed.
There is only the OS and roles on the OS. The only licensing issue here would be to ensure that there are no roles other than Hyper-V enabled.
Enabling or disabling the GUI is not adding a role.
You always only install the OS and enable the roles you want.
This is how MS Server has worked forever.
Yes, but installing any role other than Hyper-V is what causes the licensing issue. Sorry I wasn't clear enough.
-
@black3dynamite said in Storage Provisioning For a Single Hyper-V Server Setup:
In response to converting from Desktop Experience to Core. You will have to do a fresh install.
"Unlike some previous releases of Windows Server, you cannot convert between Server Core and Server with Desktop Experience after installation. If you install Server with Desktop Experience and later decide to use Server Core, you should do a fresh installation."
Major... major bummer !!
Plus, I hate the Windows 2016 desktop experience. Why couldn't they just let it be the same as 2012 R2
-
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
Plus, I hate the Windows 2016 desktop experience. Why couldn't they just let it be the same as 2012 R2
What's different about it from Win 10?
-
@Dashrender said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
Plus, I hate the Windows 2016 desktop experience. Why couldn't they just let it be the same as 2012 R2
What's different about it from Win 10?
The fact that it's not Windows 10 ... It is Windows SERVER 2016
-
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@Dashrender said in Storage Provisioning For a Single Hyper-V Server Setup:
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
Plus, I hate the Windows 2016 desktop experience. Why couldn't they just let it be the same as 2012 R2
What's different about it from Win 10?
The fact that is not Windows 10 ... It is Windows SERVER 2016
Win 2012 R2 is like Win 8.1, so what makes this so much worse? I guess I have to see how the tools are laid out. Though one thing all us Windows admins have to get used to is MS is moving more and more directly to the CLI instead of the GUI.
-
Yes, 2012 looks like 8.1, but it still did not provide a full-fledged desktop experience (Themes n all), out of the box... 2016 does that, on the other hand ... Why not have a minimal GUI just for servers, without the bells and whistles ..
I installed Hyper-V Core, and I'm facing a though time configuring... The server is at a remote location, and connect to the remote network via VPN, and am trying to use tools like Server Manager, Hyper-V manager, and even 5nine.. Server Manager itself works fine, but when I launch tools (such a Computer Management) from within Server Manager, I get random access denied messages .. Even after adding it as a Trusted host
-
@dr.funkenstein You were told to use a device on site. Most likely you are running into simple time out issues over the VPN link. I use various MMC tools (mostly Hyper-V manager) across a VPN all the time and have no issues.
-
This post is deleted! -
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
@black3dynamite said in Storage Provisioning For a Single Hyper-V Server Setup:
In response to converting from Desktop Experience to Core. You will have to do a fresh install.
"Unlike some previous releases of Windows Server, you cannot convert between Server Core and Server with Desktop Experience after installation. If you install Server with Desktop Experience and later decide to use Server Core, you should do a fresh installation."
Major... major bummer !!
So install Server Core only and then add the feature afterwards. Any feature added afterwards is supposed to be removable.
-
@dr.funkenstein said in Storage Provisioning For a Single Hyper-V Server Setup:
Yes, 2012 looks like 8.1, but it still did not provide a full-fledged desktop experience (Themes n all), out of the box... 2016 does that, on the other hand ... Why not have a minimal GUI just for servers, without the bells and whistles ..
Because you should not be running a GUI at all. Spending time and money to support people using the product in that way is not in MIcrosoft's interest and not really in yours, either.
