Setting Up a Virtual DC and File Storage Guidance Needed

[JATSO]

Hi All,

 

I have managed to create a new 2019 Virtual DC on our host which is also running Server 2019 and Hyper V.

I left SYSVOL as the default but have read and seen that I should create a separate VHDX for SYSVOL

 

Current Virtual Server Setup is:

 

Virtual DC called DC001

4Cores 8GB RAM

System Partition 200GB

SYSVOL C:\windows\sysvol etc - Should change this?

 

Have I allocated too much space for the server setup?

I have not setup any accounts or allocated any file storage yet in the new VDC and was wondering should I copy all data so that files and shares are in the virtual environment or put them storage space on the host?

The old server will be removed once I am happy that the new host and VDC are running ok and will be kept once fitted with new SSDs and used as a backup.

 

Thanks

[Jcx500]

I've always given less than 100gb vhd to a dc and keep everything on the c drive

[FishCustard]

I do the same - 100 GB VHDX, keep everything there. Not sure why you'd want a separate one for SYSVOL.

[rh91uk]

Agree - no reason to have a seperate drive for sysvol

[HPlum78]

For a few reasons as it happens, cache on the disk springs to mind in the fist instance. In fact instead of me highlighting the best practice I will let you read the following :-

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd363553(v=ws.10)

 

At the end of the day we could all have our own opinions on this but it's best to do as MS say, expecially if you ever need to seek help from them as they will ask about how you have followed the best practice documents.

[FishCustard]

Hmm, fair enough, that is what they recommend (note - you linked to the 2008 R2 version, but it's the same in the current guidance).

 

I'm skeptical as to how often not doing that causes actual problems though.

[HPlum78]

Yeah I did have both docs posted the older one sorry but like you have noted the disk bit is still essentially the same.

[HPlum78]

Oh on the how often it causes issues if you ever have to engage MS support for a product you best have followed best practice or at least be able to have a good technical reason for not doing so. I know this through many calls with prem and mis configured DCs/ Exchange / SQL and MIM installs to name but a few. Follow the best practice then at lest you have that to put in the back of your trousers if anything goes wrong.