Hi ImmoGuy, You need to consider it's a virtual machine thats it . No specific fine tunning required and you can convert to template after building the virtual machine. If you are going to convert this to SQL DB then you need to follow best practices document. https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/solutions/sql-server-on-vmware-best-practices-guide.pdf
this post was submitted on 27 Nov 2023
1 points (100.0% liked)
Homelab
1045 readers
1 users here now
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
founded 2 years ago
MODERATORS
If it's critical for your business, spend the money and invest in getting resources for a cluster setup. If you lose your host or storage devices, how long can you tolerate being absolutely down?
Building something simple, yet robust. I have seen too many shops build on 1 host, then have a failure, take them offline for good.
If your plan is to setup AD DS, then i would STRONGLY advise against putting everything in one windows server VM. That is against all MS best practices and it will create many issues down the line.
Setup a Windows VM for AD DS, and another for SQL/application.
Ideally, you should run at least 2 domain controllers in an AD DS, but 1 can be enough for initial setup.
Windows AD controller doesn't need much in terms of resources (2-4 cores and 8GB RAM should be enough) for a few users. SQL, on the other hand is pretty resource intensive (especially memory) so grant those resources.
This is a homelab subreddit. You are asking for people to plan out a production environment, basically do your job for you which is inconsiderate.