Windows 10: Pre-Provision a user’s OneDrive in Microsoft 365 using PowerShell

When a new account is created in Microsoft 365, its OneDrive is not provisioned, which the user must do. If you needed to pre-provision it for the user, you would need to log in with every user or use the below method to pre-provision it using PowerShell. Usually, this is done to pre-fill the OneDrive of a user with startup data and folder structure as well as it is needed to be provisioned for a migration process.

A requirement for this is to have the SharePoint Online Management Shell installed, which can be downloaded from the Microsoft site https://www.microsoft.com/en-US/dow...5588&msockid=3765afd8b0d06ff03ce2baf8b1a76eb2.

Once downloaded and installed, open a PowerShell window.

Type the following command

Connect-SPOService -Url <your admin sharepoint URL>

The admin SharePoint URL is usually the domain -admin.sharepoint.com for example https://mydomain-admin.sharepoint.com

Then you will need the following command to pre-provision the Onedrive.

Request-SPOPersonalSite -UserEmails <email address of user>

This will provision the OneDrive or the user.



read more...

 

Try out Windows Autopilot white glove pre-provisioning with Windows 10

Source: https://techcommunity.microsoft.com/...ng/ba-p/740502

 

Try out Windows Autopilot white glove pre-provisioning with Windows 10

Source: https://techcommunity.microsoft.com/...ng/ba-p/740502

 

Including Bitlocker Pre-Provisioning


Hi @Kari,

That was an awesome Tutorial, exactly what I've been looking for !

I have been doing a bit of experimenting and found that a slight modification to your procedure can be used to pre-provision Bitlocker encryption, as long as the machine has a TPM chip present and activated on the motherboard. This pre-provisioning, if successful, could save a few hours as compared to configuring it post-install.
Note: all of the following worked on Win 10 Enterprise x64 1709 on both an old Laptop (non-UEFI, non-Secure Boot e.g. a 10 year old Dell Latitude E4200 ) and a modern desktop (Dell Optiplex 5040 w UEFI and Secure Boot).
All that's needed is to insert a step between 2.6 and 2.7 which would check if the destination drive is encryptable, and, if it is then enable encryption of used space. Because the 'used space' at that point is almost zero it gets encrypted almost instantaneously. But, because the drive is now encrypted, anything that DISM adds to the drive gets encrypted on the fly ! End result is that when the installation is finished the drive is encrypted with Bitlocker and just needs a 'protector' (e.g. TPM and PIN) added ..

Here's what worked for me ....
- just after step 2.6, check that G: drive is actually encryptable (this also checks the BIOS, TPM activated etc.)
run command 'manage-bde -status' (if that lists the volume as encryptable, then we're good to go to next ..)
run command 'manage-bde -on G: -used' (that turns on bitlocker for the drive, and should finish after a few seconds ...... just wait a few seconds and verify that another 'manage-bde -status' now shows 100%)
- .. now proceed to step 2.7

At the end of the installation and after first bootup and logon you should see a little yellow triangle as well as an unlock icon on the drive, showing it's encrypted but with a 'clear protector' ...... then just need to add a protector, like TPM and PIN e.g. 'manage-bde -protectors -add c: -TPMAndPIN' where you will be prompted for PIN, and if all goes well, will be prompted to enter PIN in order for machine to boot up.