...
The following are the best practices for migrating Workspace ONE SQL servers.
You can use SQL Server 2016, however, you will need to make sure it has the Client Tools. This primarily includes SQL Management Studio, Reporting Services, Integration Services, SQL Server Agent, latest service packs, and that it is 64-bit. It does not matter if the SQL Server is on the 2016 edition and the Application Servers are on a prior edition, as long as the minimum server software requirements are being met.Application Server Software Requirements Ensure that you meet the following software requirements for the application servers: Internet Explorer 9+ installed on all application servers Windows Server 2012 or Windows Server 2012 R2 64-bit Java (JRE 1.8) server needed for the server AWCM is installed on 64-bit Java (JRE 1.8) installed on all app servers Important: The Workspace ONE installer only includes the English version of Java. For installation of Workspace ONE components on non-English versions of the Windows Server, the appropriate non-English version of Java must be installed before running the Workspace ONE installer. .NET Framework 4.6.2 required. The installer is packaged with the .NET Framework 4.6.2 installer and will install it if it is not already present. PowerShell version 3.0+ is required if you are deploying the PowerShell MEM-direct model for email. To check your version, open PowerShell and run the command $PSVersionTable. More details on this and other email models can be found in the Workspace ONE Mobile Email Management Guide, available on docs.vmware.com. Database 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). Workspace ONE does not support Express, Workgroup, or Web editions of SQL Server. These editions do not support all the features used in the Workspace ONE 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 Wserver 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. For database migration, it is recommended you take a backup of the old database, restore the backup on the new server, recreate the SQL Server jobs there and make changes to the UpdateSQLServerInfo file on the Application Servers to point to the new SQL Server. Typically, you should be able to do a Telnet from the Application Server to the SQL hostname on port 1433.Steps to update the new SQL Server details on the Application Servers1. Navigate to AirWatch Root Folder on the application server.2. Navigate to AirWatch X.X\Supplemental Software\Tools\UpdateSQLServerInfo.3. Launch UpdateSQLServerInfo.exe.4. Update the Server Hostname, Database Name, Username and Password.5. Click on Update. Logic: The “sqlserver” update tool points to the each of the application server, such as console, DS server to the new database. These fields updates all config files for Workspace ONE services that are tied to the database.For additional information, please refer to the following guides:VMware AirWatch Database Migration GuideWorkspace ONE UEM Recommended Architecture GuideWorkspace ONE UEM Installation Guide