@black3dynamite said in Spin VMs quickly with KVM + virt-sysprep:

@stacksofplates said in Spin VMs quickly with KVM + virt-sysprep:

I usually use virt-builder to build the image, and then I can clone from that. Then you have nice really small images to build from.

Have you ever created your own repo using virt-builder-repository?

No I've always pulled from upstream. I've honestly never looked into that before.

@coliver said in Sysprep won't run if a drive has Bitlocker enabled:

@Dashrender said in Sysprep won't run if a drive has Bitlocker enabled:

@coliver said in Sysprep won't run if a drive has Bitlocker enabled:

@dbeato said in Sysprep won't run if a drive has Bitlocker enabled:

@coliver Did you setup a Microsoft account on them?

No domain joined machines.

Are you sure Bitlocker isn't on, just not activated?

I'm not sure what you mean? Bitlocker is a part of the operating system... you need to turn it on to enable encryption. So if you're asking if it is installed the answer is yes. If you're asking if it is enabled the answer is no.

Bitlocker has three states, as far as I can tell

Bitlocker Off Bitlocker On, but not activated - not encrypting drive Bitlocker activated

In my experience, a BIOS based machine puts Windows 10 into option 1 above.
My recent experience has shown that machines with UEFI and Secure Boot enabled that Windows 10 puts the system in option 2 or 3 depending on setup.
If you add a Microsoft Account while going through OOBE, the Windows will create a recovery key for Bitlocker, save it to your OneDrive account, and use option 3.
If you add a local account during OOBE, Windows will put the system into option 2.

It s good advices to Sysprep for windows 7

I solved this by removing all but one profile on the machine, then running
sysprep /oobe /generalize /reboot

Then during the mini setup I joined to Azure AD.

@Dashrender said in Fresh Win 10 install - doesn't include crapware:

Now that's really weird.

is that 1703? What is the last cumulative update you have installed?

That one is current. Image was put on last week and then updates ran.