BETA-Windows 10 Bulk Provisioning Tool

Steps

From 10.68 release, MaaS360 supports customers to on-board bulk deploy Windows 10 Laptops without having to create any enrollment requests in the system. 

Customers using legacy Windows devices such as Windows 7 or 8 and do not have an Azure Active Directory can still do bulk provisioning into MaaS360 during their regular deployment of Windows 10 images.  

This function is available as BETA. Inorder to opt in for this feature, contact IBM MaaS360 Customer Support team.

How to configure Windows 10 Bulk Provisioning Tool from MaaS360 portal and on Windows 10 laptops?

1. Log into MaaS360 application portal, Click Configure for Windows 10 Bulk Provisioning Tool in portal. You will see an option under Setup > Settings > Device Enrollment Settings > Enrollment Programs > Windows > Windows 10 Bulk Provisioning Tool.
   This function is available as BETA. Inorder to see this feature, contact IBM MaaS360 Customer Support team.

2. Prepare any Windows laptop as base image running the Windows 10 OS version of your choice and with all the software, applications and configurations for your user base.
3. Download Windows 10 Bulk Provisioning Tool from MaaS360 application portal on the base image machine and save this file.

4. Open the downloaded installer from the file location and run the saved file.

• Follow the on-screen wizard instructions and click Install to continue installing the Deployment Agent.
• Enable Launch Deployment Agent and click Finish.

The deployment agent will launch Windows 10 Bulk Provisioning Tool on the base image. Follow the steps about how to use Windows 10 Bulk Provisioning Tool and click Continue.

Enter Administrator Username and Password to complete IBM MaaS360 Authentication and click Next. Only on successful authentication, you will be able to continue with the next steps. 

7. Enter the following details ad click Next.

•  Email Address for Enrollment: A temporary email address against which against which all managed devices will be enrolled to start with when image gets deployed.  
• Select account to Enroll that represents the user account type that managed devices should be enrolled with such as,

1.  New Local User: Use this option if you are deploying the image in new local machine. The device gets enrolled when a new local user is created and the user logs in for the first time. User must be administrator user for the enrollment to be completed. If user is a non-admin user then enrollment will not complete.
2. New Domain User: Use this option if you are deploying the image on a domain connected machine - Azure Cloud or OnPrem Active Directory domain. The device gets enrolled when a new domain user is created and the user logs in for the first time. User must be administrator user for the enrollment to be completed. If user is a non-admin user then enrollment will not complete.
3. Existing User: Enrollment for any existing user available on the base image. Enrollment happens when the existing user logs in to the account. For example, if you are setting up kiosk devices, you may want to setup a "kiosk" user on the base image and have enrollment carried out on the "kiosk" user always. 

8. Accept the End User License Agreement on behalf of all users who will be enrolling automatically when image gets deployed and click Next.

9. Click Finish. This completes the Bulk Provisioning Tool setup.

What Next?

Close the Windows 10 Bulk Provisioning Tool and create a base image from the current machine. Once you complete the deployment of the image on the end user machines, managed devices will be automatically enrolled when Os boots up and right user logs in based on configurations pre-saved in this tool.

Note: Windows 10 Bulk Provisioning Tool is not limited by the the maximum number of devices that are allowed to be enrolled by any user  that is specified in Advanced Device Enrollment Settings for Limit devices per user.