Virtualize Windows Server 2022 in Proxmox - VLANs, Sysprep, and Template!

preview_player
Показать описание
Learn how to install, configure, sysprep, and clone to template a Windows Server 2022 virtual machine and see how to install the drivers needed for the Windows Server 2022 installation on Proxmox.

My blog:

_____________________________________________________

Social Media:

LinkedIn:

Github:


Introduction to Proxmox Windows Server 2022 installation - 0:00
Describing the ISO images needed including Windows Server 2022 and VirtIO drivers - 1:10
How to download the VirtIO drivers for Windows - 1:53
Uploading the ISO images to your Proxmox ISO images storage - 2:18
Creating the Windows Server 2022 - 3:05
Adding the additional virtual CD-ROM drive for the VirtIO drivers - 4:26
Starting the Windows Server 2022 installation - 5:25
Windows has not detected hard disks - 6:00
Laoding the VirtIO drivers for Windows Server 2022 - 6:10
Setting the initial administrator password - 6:46
Installing the VirtIO package in Windows Server 2022 - 7:07
Windows drivers are being installed including network drivers - 7:46
Reboot Windows Server 2022 virtual machine - 8:00
Looking at the network IP address pulled - 8:15
Adding VLANs to virtual machines in Proxmox - 8:35
Making the default Linux Bridge VLAN aware - 8:50
Configuring our Proxmox Windows Server 2022 VM with a different VLAN - 9:20
Windows Server 2022 rebooted and checking the IP address for the different VLAN - 10:00
Discussing creating a Windows Server 2022 virtual machine template - 10:30
Avoiding potential problems using Sysprep - 11:15
The Sysprep command and parameters - 11:28
The Windows Server 2022 VM shuts down and we can convert to template - 12:24
Concluding thoughts - 12:42

Promox and ESXi comparison:

Proxmox iSCSI storage using Synology NAS:

Рекомендации по теме
Комментарии
Автор

Just the video I needed! Clear and concise. Super helpful, thank you!

tylergastelua
Автор

Awesome job explaining the steps. Subscribed!

WilliamMcNeill
Автор

A great video. It's just what I needed to know. It has the basic information, few steps, and very well explained. Another similar video would be ideal giving a configuration recommendation (best practices) to adjust Windows Server in detail and thus get the most out of Proxmox. Your videos have been a great help to me, thank you very much! 👏👏

juanpablopalmag.
Автор

nice video, but you skip the last part:
- deploy that template & test that SysPrep worked!!!!

fbifido
Автор

Thank you Brandon, Great job my friend. I appreciate you very much.

michaelcooper
Автор

You left mounted the isos on the template configuration, that means any new virtual machine will deployed from this template will point and have mounted those isos

VK-qfqi
Автор

What is the difference between qcow2 & raw, i notice your disk was raw and greyed out.

Popcorncandy
Автор

I thought the template was going to create one of my current server not turn it into Lost my server and when I try to use the clone it keeps erroring out. Thanks.

jazz
Автор

You forgot to say "twenny-twenny-too" after "windows server" at 09:58.

audunaa
Автор

Great video however however I noticed the cpu type of the vm was x86-64-v2-aes. I change mine to host in order to reflect the same cpu type on the physical server.

alphabanks
Автор

in to you homelab!!
me setting everything up at the actual office ._.

Thehoneybadger
Автор

I have an issue with VLANS on Proxmox. I have turned on VLAN aware on the bridge interface and added the VLAN ID's to the VM NIC's, but it doesn't work. PfSense is unable to provide DHCP to either interface. As soon I remove the VLAN tag, the NIC's work and get a DHCP address, on the same subnet / vlan as the proxmox host.

Grand_Alchemist
Автор

On admin command prompt: " sysprep /generalize /oobe /shutdown " is the command!

TomiWebPro
Автор

Nice video. If you were going to make this Widows server a nice file server. How would you add about 50TB and keep it scalable ?

alainterriault
Автор

You made a single connection. What about passthrough for Linux and Windows?

jeffharwood
Автор

I would like to run a Windows domain using the trial server licensing provided by MS that lets you run for 180 days... My thought is that every 6 months, I'll spin up a new server and join/promote it to be a DC, then shut down the previous one before the 6 months expires. If I create a template as you describe, including sysprep, will the license clock start fresh with each cloned VM, or will they all start from the point in time at which the initial VM was installed from which the template was created?
Alternatively... does anyone know of a _reasonable_ way to purchase a server license for home lab use? I would happily spend a few dollars to be able to do it, but I haven't seen anything from MS that would help make it more affordable for such applications.
Thanks

martyewise
Автор

has anyone done vs passthrough for a x710?

johnwuethrich
Автор

I watched a lot of your videos on Proxmox but I had a question for you. I have Proxmox 7.3 installed and now I see 7.4 is out. Is there an easy way to upgrade to 7.4 through the GUI? I have watched all your Proxmox videos but I did not see anything about upgrading from one version to another (I do not have a subscription to Proxmox), I did not want to just installed the new version on my boot drive, because I would have to do a lot of things to get it back to what I have now, just a few VM's but.

I am sure there must be a way to upgrade?

Also I had another request, sometimes when you talk about things in Proxmox (talking about network items), if you can could you say something like creating a linux bridge is like creating a virtual switch in Netware or HyperV. I have a very good understanding of MS Server and HyperV, and I am sure some things in Proxmox would be similar to Hyperv(I know not exact), but explanations like that would help me and I am sure others too.

jimholloway
Автор

but do you virtualize inside of that VM?

Thehoneybadger
Автор

Why do you leave the Graphics card in default, and not virtio as well?

Bogomil