2019 Datacenter - First Implementation Questions

Question

It’s always fun and interesting doing an implementation for the first time. While I fully expect to deal with errors and omissions, I’d like to minimize them so I’m looking for some guidance before I waste a lot of time. I’ve been unsuccessful in finding answers so far. If there’s a good cookbook that I haven’t found, just point me to it. If there are obvious (to you) things that I haven’t considered, please point them out. I’m starting to implement my first 2019 Server Datacenter Edition.

I have hardware that I believe is adequate for testing. I'm using an HPE Proliant Gen 10 server with 1 processor, 8 cores, 80 GB Memory and 2.7 TB Storage in a RAID5 Array.

I have installed a Server 2019 Datacenter Edition with Desktop Experience (Version 1809) . I’ll eventually switch to a Core only environment when I do my next implementation but I don’t want to take he time right now to learn all of the PowerShell and WAC management methodology. I’ll eventually blow this system away and re-do it with a Core implementation.

I have a test Domain available that doesn’t have AD implemented. The OS is up to date both from a Microsoft and HPE standpoint. All HPE Firmware updates are applied. The only Role I’ve installed on the Core is Hyper-V. I’m now ready to take the next steps and have questions:

1. I want to create an image with Sysprep so that I can create new VM’s quickly
   a. Have I screwed up by adding Hyper-V before doing this?
   b. Do I run Sysprep against my Core or do I create a VM that has no Roles installed to run it against?
   c. The documentation I’ve read indicates that I should run it with the /generalize /oobe and /shutdown options and then take a standalone image without booting the server back into Server 2019. i. Is there a recommended product to use to take the image?
   d. When I do reboot back into the Server and the mini Setup loads, what is the best way to kill it and boot back into my already installed and configured system?
2. I’m planning on adding a VM for AD. Am I correct in assuming that the Core can’t be a member of the AD unless there’s a separate physical server which is a DC. Would that mean adding the Core to the Domain before running Sysprep? If I need a separate machine, I’m planning on using a very low end non-virtualized 2019 Standard server.
3. I also intend to add a VM for AVMA which I’m again assuming has to be a Domain member.
4. I plan on adding another VM as an SDC. Should I promote it to PDC and keep the other DC server as an SDC?

I view this at the creation of the overall infrastructure and I can then move on to application servers. Is that correct. If you’ve gotten this far, thanks for taking the time, and for any guidance you can provide.

Answer 1

Hi，

This is Anne from Windows Hyper V team, according to your description, it seems you have a Windows Server 2019 datacenter and would like to install Hyper V and create VMs on the host. If there's any misunderstanding, please feel free to let me know.

1. It seems you would like to use sysprep to creata a VM template, it is OK, after installing Hyper V role on the Server 2019 host, create a VM with OS installed, then install latest windows update and necessary applications, then sysprep this VM to mark a template.
2. When create other VMs, we may use the template VM to do a quick install.
3. As for the AD domain, we can use VM as DC, after creating VMs, we may install related roles and features on dedicated VM.

If there's anything unclear about the Hyper V part, please feel free to let me know.

Best Regards,
Anne

Answer 2

Hi,

Thank you for coming Microsoft Q&A.

As your existing thread related with several issue with different direction. I will answer your issue about sysprep part. And my colleagues will reply on other sides.

For sysprep, we could refer to Microsoft official document Sysprep (System Preparation) Overview as cookbook. On the left navigation panel, we could choose different parts steps.

1-a I don't think enable hyper-v in sysprep will make any affection for your image. There is also no document about hyper-v affection on sysprep, so I think we could enable it.

1-b For Do I run Sysprep against my Core or do I create a VM that has no Roles installed to run it against? Would you clarify more detail about your purpose? I am not sure I could clear understanding about your meaning and want to confirm about it.

1-c For shutdown parameter, if we are ready to take the image of the computer and we use the generalize command, we are going to use it. But after all sysprep action done, we could power up to use this computer.

1-d If you want get out of audit mode, use the System Preparation Tool to prepare the system to boot back into OOBE. You can choose to reboot the system or shut it down, either way when the computer comes back on.

By the way, I don't recommend to add domain during sysprep, as it might bring risk to crash your image when loading GPO and local policy as I have heard other customers encounter such issue. After deployed image to VM, we could add domain.

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.