OBR10 - Server Setup
-
@emad-r said in OBR10 - Server Setup:
How about ordering 5 drives and keep one as cold spare.
make sure to note down the Serial ID and numbering on them so you know which is drive 1 and drive 2,3,4 without command line. So when one fails you can easily identify which one, you can do this via file on your desktop.
The physical drive bays (at least on Dell) are numbered 0 - x. Also, the status light will most likely amber color. Easy to identify the bad drive... hot-swap it out and you're good to go.
-
@emad-r said in OBR10 - Server Setup:
How about ordering 5 drives and keep one as cold spare.
Why pay for something you never need until you actually need it?
Also as it is new, the warranty will cover failure for X years. -
@obsolesce said in OBR10 - Server Setup:
You'll have a folder in
D:\Hyper-V\<vmName>idealy for your VMs.You set this location in Hyper-V manager when you first set things up. I always recommend to change it from the default to something simple like
D:\Hyper-Vas noted above. -
Thanks guy so to confirm, when I boot the Hyper Visor for first time, I should go into Intelligent provisioning and configure the Raid in R10. Then I should create two partitions C:\ for the Hyper-V's OS, then a D:\ for my VM's data store?
Then using Hyper-V Management tools, I can connect to HV01 server, and install 2x VMs (storing the data on the D:\ drive partition).
Then, when it comes to creating the VMs (DC and FS), do I just partition more of that inital D:\ drive to be the C:\OS and D:\Storage for myVMs?
-
@joel said in OBR10 - Server Setup:
Then, when it comes to creating the VMs (DC and FS), do I just partition more of that inital D:\ drive to be the C:\OS and D:\Storage for myVMs?
No.
-
@joel said in OBR10 - Server Setup:
Thanks guy so to confirm, when I boot the Hyper Visor for first time, I should go into Intelligent provisioning and configure the Raid in R10.
You should configure the RAID10 in the bios or the server remote management before an OS is installed.
-
@joel said in OBR10 - Server Setup:
Then, when it comes to creating the VMs (DC and FS), do I just partition more of that inital D:\ drive to be the C:\OS and D:\Storage for myVMs?
You don't partition anything else in the Hyper-V server. It handles everything for you after the initial configuration.
If you're interested, it actually creates a file for each virtual drive on the system. You shouldn't every have to deal with these files yourself.
-
@joel said in OBR10 - Server Setup:
Then, when it comes to creating the VMs (DC and FS), do I just partition more of that inital D:\ drive to be the C:\OS and D:\Storage for myVMs?
No, you don't partition anything else at all.
-
Ok, so if I want my VM's to have a
drive for OS and then a 
drive (Data) - Would it just be a case of adding an additional Virtual Hard Drive and storing it in the initial D partition? eg.My HyperV server will be in Raid10 with 2 partitions - C:\OS (100GB) - D:\Data (1.9TB)
(on D drive, create folder called VM\DomainController)
(on D drive, create another folder called VM\FileServer)Then, I can provision DomainController
Add Virtual Hard Drive - C:\OS (130GB) - (Location: D:\VM\DomainController)
Add Virtual Hard Drive - D:\Logs (20GB) - (Location: D:\VM\DomainController)Provision FileServer
Add Virtual Hard Drive - C:\OS (130GB) - (Location: D:\VM\FS)
Add Virtual Hard Drive - D:\Data (1.6TB) - (Location: D:\VM\FS)Make Sense?
-
@joel said in OBR10 - Server Setup:
Ok, so if I want my VM's to have a
drive for OS and then a drive (Data) - Would it just be a case of adding an additional Virtual Hard Drive and storing it in the initial D partition? eg.My HyperV server will be in Raid10 with 2 partitions - C:\OS (100GB) - D:\Data (1.9TB)
(on D drive, create folder called VM\DomainController)
(on D drive, create another folder called VM\FileServer)No
Then, I can provision DomainController
Add Virtual Hard Drive - C:\OS (130GB) - (Location: D:\VM\DomainController)
Add Virtual Hard Drive - D:\Logs (20GB) - (Location: D:\VM\DomainController)No, all VM files are in D:\Hyper-V. Hyper-V Manager does that automatically. Don't customize things.
Provision FileServer
Add Virtual Hard Drive - C:\OS (130GB) - (Location: D:\VM\FS)
Add Virtual Hard Drive - D:\Data (1.6TB) - (Location: D:\VM\FS)Make Sense?
No, all VM files are in D:\Hyper-V. Hyper-V Manager does that automatically. Don't customize things.
-
Prior to any VM creation.
Open Hyper-V Manager and choose settings.
Go through all of these settings. Specifically to this part of the conversation, setup the top two settings to be
D:\Hyper-V\Virtual Hard DisksandD:\Hyper-V
-
@joel said in OBR10 - Server Setup:
Ok, so if I want my VM's to have a
drive for OS and then a drive (Data) -Stop here. Before you ask this question, WHY are you asking this question? You don't normally want this. What is making you think you should do this? This is non-standard and should only be done when it makes sense, not by default.
-
@joel said in OBR10 - Server Setup:
My HyperV server will be in Raid10 with 2 partitions - C:\OS (100GB) - D:\Data (1.9TB)
(on D drive, create folder called VM\DomainController)
(on D drive, create another folder called VM\FileServer)Don't make folders. This is all much simpler than you are making it out to be. All of this is stuff you can ignore.
-
@joel said in OBR10 - Server Setup:
Then, I can provision DomainController
Add Virtual Hard Drive - C:\OS (130GB) - (Location: D:\VM\DomainController)
Add Virtual Hard Drive - D:\Logs (20GB) - (Location: D:\VM\DomainController)Why would you make a domain controller like this? Of all workloads, should not be this way.
-
@jaredbusch Thanks, yes this is what I was meaning, I'd be placing the VM on that Initial D drive.
-
@scottalanmiller said in OBR10 - Server Setup:
@joel said in OBR10 - Server Setup:
Ok, so if I want my VM's to have a
drive for OS and then a drive (Data) -Stop here. Before you ask this question, WHY are you asking this question? You don't normally want this. What is making you think you should do this? This is non-standard and should only be done when it makes sense, not by default.
*In the past I used to have a C drive for the OS and a second disk (D) for data.
So what is standard now? Just one Drive with everything on there? -
@scottalanmiller said in OBR10 - Server Setup:
@joel said in OBR10 - Server Setup:
My HyperV server will be in Raid10 with 2 partitions - C:\OS (100GB) - D:\Data (1.9TB)
(on D drive, create folder called VM\DomainController)
(on D drive, create another folder called VM\FileServer)Don't make folders. This is all much simpler than you are making it out to be. All of this is stuff you can ignore.
Cool cool - thanks SAM
-
@scottalanmiller said in OBR10 - Server Setup:
@joel said in OBR10 - Server Setup:
Then, I can provision DomainController
Add Virtual Hard Drive - C:\OS (130GB) - (Location: D:\VM\DomainController)
Add Virtual Hard Drive - D:\Logs (20GB) - (Location: D:\VM\DomainController)Why would you make a domain controller like this? Of all workloads, should not be this way.
- I recall reading a MS article stating should have the OS installed but then a second drive should be used as SysVOL/Logs
- I recall reading a MS article stating
-
@joel said in OBR10 - Server Setup:
@scottalanmiller said in OBR10 - Server Setup:
@joel said in OBR10 - Server Setup:
Then, I can provision DomainController
Add Virtual Hard Drive - C:\OS (130GB) - (Location: D:\VM\DomainController)
Add Virtual Hard Drive - D:\Logs (20GB) - (Location: D:\VM\DomainController)Why would you make a domain controller like this? Of all workloads, should not be this way.
- I recall reading a MS article stating should have the OS installed but then a second drive should be used as SysVOL/Logs
- I recall reading a MS article stating
-
@joel said in OBR10 - Server Setup:
@scottalanmiller said in OBR10 - Server Setup:
@joel said in OBR10 - Server Setup:
Then, I can provision DomainController
Add Virtual Hard Drive - C:\OS (130GB) - (Location: D:\VM\DomainController)
Add Virtual Hard Drive - D:\Logs (20GB) - (Location: D:\VM\DomainController)Why would you make a domain controller like this? Of all workloads, should not be this way.
- I recall reading a MS article stating should have the OS installed but then a second drive should be used as SysVOL/Logs
No, that's not a normal or recommended setup. Maybe for some very specific scenario, but absolutely is not a good default. Default is one
for everything. For DCs, always a single drive, never do this extra stuff. This is what we call "getting weird." - I recall reading a MS article stating
