AlteredAdmin Posted July 7, 2022 Posted July 7, 2022 Good morning We use VMware templates to create servers. We noticed that after installed windows server 2022 the recovery partition is after the C: drive.This can create issues when the C drive needs to be expanded. IS it safe just to delete and remove the recovery partition so C: can have room to expand?Would doing this cause ay future issues? Aside from needing the recovery partition. And could one just make a bootable DART disk if it was really needed?We never use the recovery drive, because we have snapshots backups and most of the time we would just rebuild the server. Thoughts?
mavhc Posted July 7, 2022 Posted July 7, 2022 Probably fine, but why do you have >1 partition on a virtual disk?
AlteredAdmin Posted July 7, 2022 Author Posted July 7, 2022 Probably fine, but why do you have >1 partition on a virtual disk? we will add another partition if its needed, some of servers are just small application servers and don't need a lot of space.
mavhc Posted July 8, 2022 Posted July 8, 2022 But you should just add another virtual disk, partitions are from a non virtual era
JackCPickup Posted July 8, 2022 Posted July 8, 2022 Ignoring the discussion as to the need for partitions, if you want to place the C: partition on the far right follow the below before installing the OS: Once you have booted into the ISO, Press “Repair” in the bottom left. Select to open a command prompt Issue the following Commands in order: Diskpart Select disk 0 Convert gpt Create partition primary size=250 Format quick fs=ntfs label=”Recovery” Set id=”de94bba4-06d1-4d40-a16a-bfd50179d6ac” flags partition as recovery gpt attributes=0x8000000000000001 flags partition not to assign drive letter create partition efi size=100 format quick fs=fat32 label=”System” create partition primary format quick fs=ntfs label=”Windows”
Davit2005 Posted July 8, 2022 Posted July 8, 2022 (edited) If you run MDT or SCCM you could easily deploy new server OS without all the mucking around. During the deployment you could change the name of the server and join to the domain. But I agree with @mavhc jus add a second virtual disk rather than adding a partition, depending on your need/setup you can then have flexibility and separate the OS from the Application data i.e. exchange/SQL to separate faster storage. Edited July 8, 2022 by Davit2005
JackCPickup Posted July 8, 2022 Posted July 8, 2022 Probably fine, but why do you have >1 partition on a virtual disk? They're referring to the recovery partition created as default by Windows. They moved this with Windows Server 2022 to the right of your OS partition.
mavhc Posted July 8, 2022 Posted July 8, 2022 Seems like you need a new template that creates 2 virtual disks, and makes the partitions that Windows will recognise https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions?view=windows-11 Or make just 1 disk, fill it with 1 partition, then it won't add another.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now