VMware Workspace One UEM (AirWatch) provides Mobile Device Management for your organization’s devices. VMware Workspace One UEM (AirWatch) supports several diverse devices from Apple, Android, and Blackberry to Symbian, windows and windows phone.
VMware Workspace One UEM (AirWatch) solution includes,
- Access Management
- Digital Workspace Intelligence
- Digital Workspace Security
- Bring Your Own Device (BYOD)
- Enterprise Mobility Management (EMM)
- Mobile Application Management (MAM)
- Mobile Content Management (MCM)
- Mobile Device Management (MDM)
- Secure Browser
- IoT Device Management
- Mobile Security
- Productivity Apps
- Unified Endpoint Management
In this blog series, I will be going through the installation and configuration of VMware Workspace One UEM (AirWatch) in my lab environment. The purpose of the blog series is to provide you with some basic information that helps you installing an on-premise Deployment of the VMware Workspace One UEM (AirWatch) solution.
Refer recommended Architecture Guide: Click Here
Refer Installation Guide: Click Here
Let’s begin with the installation.
The first component for VMware Workspace One UEM initial setup is to configure the SQL database.
SQL Server Software Requirements:
- SQL Server 2012, SQL Server 2014, or SQL Server 2016 with Client Tools (SQL Management Studio, Reporting Services, Integration Services, SQL Server Agent, latest service packs). Ensure the SQL Servers are 64-bit (OS and SQL Server).
AirWatch does not support Express, Workgroup, or Web editions of SQL Server. These editions do not support all the features used in the AirWatch application. Currently, only Standard and Enterprise Editions are supported.
- .NET 4.6.2 is required to run the database installer. If you do not want to install .NET on to your database server, then run the database installer from another AirWatch server or a jump server where .NET can be installed.
- Ensure the SQL Server Agent Windows service is set to Automatic or Automatic (Delayed) as the Start type for the service. If set to Manual, it has to be manually started before database installation.
- You must have the access and knowledge required to create, back up, and restore a database
TCP/IP is Enabled
Use TCP/IP to connect to the database and disable Named Pipes. In SQL Server Configuration Manager, navigate to SQL Server Network Configuration and select Protocols for MSSQLSERVER.
Ensure all the above prerequisites in place, once all done we can start the database configuration.
Creating the Database:
To create the database, please follow the below steps with an administrator account that has the correct read/write permissions.
On the SQL Server, open SQL Server Management Studio.
Log in using your username and password.
Right-click Databases and select New Database.
Enter AirWatch as the Database name
Scroll to the right side of Database files, select the ..next to Autogrowth for AirWatch, and change File Growth to “In Megabytes” and the size to 128, then select OK.
Select Options, and select SQL_Latin1_General_CP1_C1_AS and select Close.
Now we will Create AirWatch SQL Service Account and Assign DB Owner Roles
Log in to the Database server containing the AirWatch database.
Go to Security > Login, right-click, and select New Login.
Select whether to use your Windows account or local SQL Server account for authentication. In my lab I am using the SQL server authentication. Set the credentials.
Select the AirWatch database as the Default database.
Navigate to the Server Roles tab. Select the server role as Public.
Select User Mapping.
Select the AirWatch Database. Then, select the db_owner role.
Select the MSDB Database. Then, select the SQLAgentUserRole and db_datareader roles.
Now DB has been created.
AirWatch Database Setup
Once all prerequisites are met, Run the AirWatch database setup utility on the console server.
Click on Install
Select the installation path and Click Next
Enter the Database details and select the AirWatch DB to continue the installation
Click on Install
Click on Finish once you have done with the installation.
Now the DB installation has been completed.
Next setp is to proceed with the WorkspaceOne UEM (AirWatch) console installation.
Thanks for your time and stay tuned for more posts.