Can I clone an M.2 SSD on an Azure-joined Windows 11 device with Intune and Secure Boot?

0
4
Asked By TechieGamer42 On

Hey everyone! I'm looking into whether I can clone the M.2 SSD from a Windows 11 device that's joined to Azure and managed with Intune, and has Secure Boot enabled. The main goal is to upgrade the SSD for better performance. I have a feeling this might be challenging, but I wanted to hear your thoughts before I dive in. I'm planning to use Clonezilla for the cloning process. Thanks in advance!

4 Answers

Answered By GadgetGuru88 On

Yeah, you can definitely clone that SSD! Just make sure to disable BitLocker first and wait for it to decrypt completely. Then, shrink the C: partition as much as you can in Disk Management, but leave a few gigabytes empty. If there's a WinRE partition, you can get rid of that via Command Prompt too. Once that's done, go ahead and clone your disk with Clonezilla. Restoring is easy—just expand the partition back and re-enable BitLocker if you want. And don't worry, being Azure AD-joined won't change this process much.

Answered By SecureBoot101 On

What's the deal with Secure Boot here? Are you talking about BitLocker instead? If so, you can simply suspend BitLocker before cloning and then resume afterward, which should work fine. Alternatively, you can decrypt the volume first, clone it, and then re-enable BitLocker, but that's a slower option. Also, running a cleanup on the system before cloning is a smart move to remove old data and temp files.

Answered By DiskWizard99 On

It should work if you're just swapping to a new drive in the same machine and not planning to use the old drive without formatting it first. Just a heads up—make sure it's not BitLocker-protected. Some cloning tools can be finicky about resizing partitions and extending filesystems, so keep an eye on that.

Answered By CloudTechie77 On

If you’re just upgrading the drive, you should have no issues cloning it and removing the old drive... but remember to format the old one because its partition IDs will match, causing confusion if you try to use it again in the same setup. If you're thinking about cloning the entire machine, that's a different story—machines need unique IDs, or you'll run into some serious AD conflicts like bad Kerberos tickets.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.