OS Deployment: Preserve data partitions (don’t wipe the whole disk) + duplicate boot entries after deployment

OS Deployment: Preserve data partitions (don’t wipe the whole disk) + duplicate boot entries after deployment

Product/Module: ManageEngine Endpoint Central (Desktop Central) – OS Deployment

Problem description:

I’m trying to deploy Windows OS to client machines using OS Deployment, but I need a scenario where the entire disk is NOT formatted.

My goal is:

  • Do not touch data partitions (e.g., D: / other volumes where users store documents).
  • Only remove/format the OS partition (usually C: where the old Windows is installed), then deploy the new OS to that space.

However, I could not find an option in OS Deployment that allows selecting/controlling which partitions to delete/format during deployment.

Current workaround (manual):

  1. Boot the client with a Windows Live/WinPE environment.
  2. Manually delete the old OS partition (C:) so it becomes Unallocated.
  3. Reboot the client and start the Endpoint Central OS Deployment (PXE boot / boot media).
  4. Proceed until the wizard detects the Unallocated space and deploy the OS there.

Issue after deployment:

After deploying the new OS, the machine shows:

  • Two BSD entries, and
  • Two Windows boot options (one for the old OS and one for the new OS)

So it looks like the old boot records/entries are still present even though I deployed a new OS.

Questions:

  1. Does Endpoint Central OS Deployment provide a built-in option to preserve specific partitions (keep data volumes intact) while allowing me to delete/format only the OS partition during deployment?
  2. Is there a supported way to define a partitioning scheme during deployment (e.g., delete/format partition X, keep partitions Y/Z)?
  3. How can I prevent or automatically clean up the duplicate boot entries (BSD/Windows boot options) after deployment, so only the new OS boot entry remains?

Expected result:

  • Ability to deploy Windows to a machine without wiping the entire disk, keeping user data partitions unchanged.
  • After deployment, only one correct Windows boot entry should exist.

                      New to ADSelfService Plus?