This quick walkthrough shows you how to access your Workspace ONE UEM SaaS sandbox tenant.
The Workspace ONE UEM sandbox tenant is provisioned by TestDrive in a localized VMware Shared SaaS environment, not in a TestDrive environment. Other than the basic administrator account also provisioned for your initial access, the tenant has no other configuration. It's a blank slate.
- Per VMware Shared SaaS security policy, basic admin account passwords expire after 30 days. Use the tenant environment's password reset feature to reset your password.
- Support for partners and customers is facilitated through My Workspace ONE.
- Turn on access to your Workspace ONE UEM Sandbox
- Log in to the Workspace ONE UEM Admin console
Before you Begin
In order to access your sandbox please make sure you have the following:
- A valid account in the VMware TestDrive environment. If you don't yet have an account reference our Getting Started Guide.
Your sandbox is your personal Workspace ONE UEM playground where you can create accounts, profiles, build out organization groups, configure apps, and access advanced admin settings. You will be able to make custom admin configurations in the Workspace ONE UEM console and then enroll devices to see the corresponding features on the device.
Your personal tenant will get deleted when your TestDrive account expires. These tenants are non-convertible to production.
Warning: Turning the toggle switch in the TestDrive portal back to OFF after enabling the product will deprovision your tenant and all your data within your test tenant will be lost.
First, you'll need to turn on your sandbox within the TestDrive portal. To do so navigate to the TestDrive portal at portal.vmtestdrive.com. Next, click Log In in the top right.
Enter your TestDrive username and password and click log in.
If you're having issues with your password you can always reset it on this page or send us an email at email@example.com.
Now, you'll be logged into the TestDrive portal. Next, you'll need to locate the Workspace ONE UEM card within the Sandbox Experiences section. Toggle the switch to the right to turn this on. Note there is another Workspace ONE UEM card under the "Ready to Use Experiences" section. Ensure you're choosing the product under the "Sandbox Experience" section.
You'll get a notification at the bottom of your screen notifying you that the service is turning on. Once it finishes you'll get another message stating the service is ready to be used and the Launch button will light up.
Now you can click "Launch" to go into the service. This will bring you to the log in page of the SaaS environment where your sandbox is located. Here you will enter the username and password listed under your Workspace ONE UEM Sandbox card and click "log in"
Due to VMware security policies, the password used to log in to your sandbox will expire every 30 days. This means after the first 30 days, when you return to your sandbox and attempt to log in you will be required to create a new password. This process will repeat every 30 days. If you ever forget your password ensure you have kept note of the security questions you answered when first logging in. You can use these security questions to reset your password at any time.
Now you'll be logged into your own blank Workspace ONE UEM environment. You have full admin rights and can made any configurations you please.
Device Root Certificate
Before you begin to enroll devices in your Workspace ONE UEM sandbox, verify the Device Root Certificate is enabled.
Log in to your sandbox's Workspace ONE UEM console and go to Settings > System > Advanced > Device Root Certificate. It should already be enabled.
Since TestDrive sandboxes are fully configurable, users must be created. The account provided by TestDrive provisioning is a basic administrator account.
Let's go ahead and add a user account. Click on the Accounts button in the left sidebar to open the User menu.
From the List View page, hover the cursor over the Add dropdown, then click the 'Add User' option.
Fill in the required fields and click Save when finished.
The list view will refresh to show the new user has been added successfully.
By selecting the check box next to the user's name you can add a device and manage various group options directly, without having to navigate to the other sections.
In order to enroll your device at your sandbox, please replace the 'cn' portion of your console URL with 'ds' (e.g. Enrollment URL for https://cn1206.awmdm.com is https://ds1206.awmdm.com; Exception: AW400.awmdm.com)
Note: To enroll a device, make sure you've first added a user account which is detailed in the section above.
First, you'll need to identify the Group ID for your sandbox. This information is found under Enrollment Details in the expanded Workspace ONE UEM tile in the TestDrive portal.
Now that you have your unique URL and Group ID, power up your device and download the AirWatch Agent from the app store.
Open the Agent and choose the Server Details option.
Enter your URL in the Server field, and then enter the Group ID. Click Next when finished.
Next, you'll be brought to the User Credentials page. Enter the Username and Password for the user account you set up earlier. Click Next.
At the bottom of the screen select Redirect and Enable, which will open up a browser to begin installing the management profiles to your device.
Now, you'll be prompted to install the Device Manager profile. Click Install and continue through the prompts.
Next, you'll be redirected to the AirWatch Agent. Click Done to proceed.
Click Done to continue.
You will be asked to create a more secure passcode for the Agent. Click Create when finished.
The data and privacy policies are displayed. Click I Understand to proceed.
Here you are given an opportunity to help us improve and develop new app features and functionality through anonymous data sharing.
Your device now reports as enrolled.
If you go back to the Workspace ONE UEM Sandbox Admin Console, you'll see the device now appears in the list view.
For product documentation on how to use Workspace ONE UEM please refer to the VMware Product Knowledge base page found here.