After you complete the upgrade procedure, verify that the Workspace ONE UEM services are started and that you successfully upgraded Workspace ONE UEM. Learn about how to verify the upgrade completed successfully and that all your services and components have been upgraded.
Verify Workspace ONE UEM Services Are Running
The first post-upgrade step is to verify that all Workspace ONE UEM services have started back up. Learn more about how to verify the post-upgrade status of your Workspace ONE UEM Services.
The Workspace ONE UEM installer properly configures the associated Windows services, the start type and recovery options for each service should not be modified. If services are not automatically restarted, use Windows Services Manager to reset Windows Services to Automatically Delayed Start.
After a typical upgrade, open the Windows Services Manager to verify that the installed component services are running.
-
Open the Server Manager.
-
From the left pane, select your local server and navigate to Tools > Services.
Workspace ONE UEM Services is at the top of the services list in alphabetical order. Each of these services start with Workspace ONE in the name.
-
Verify that each of these services show Started as the Status.
-
Verify the World Wide Web Publishing service is Started.
Verify the Upgrade
After you have validated that your Workspace ONE UEM Services are running, there are other verification steps to ensure that the updgrade completed successfully on the rest of your Workspace ONE UEM platform. Learn more about these verification steps and what to do next.
-
First, validate your Administrator Roles.
-
Log in to the Workspace ONE UEM console and navigate to Accounts > Administrators > Roles.
-
Verify that the update did not remove any of your custom administrator roles. If they are missing, recreate them manually.
-
-
Next, verify your Directory Service settings.
-
Navigate to Groups & Settings > All Settings > System > Enterprise Integration > Directory Services. Select the User tab.
-
Select Show Advanced. Verify that Auto Merge is selected. Select the Group tab.
-
Select Show Advanced. Verify Auto Sync and Auto Merge are checked.
-
Workspace ONE UEM recommends a minimum of 100 for the Maximum Allowable Changes. That way, the Console does not need to sync with your directory service as much.
-
-
Next, verify the Site URLs.
-
Navigate to Groups & Settings > All Settings > System > Advanced > Site URLs.
-
Verify the REST API URL and Sync Appcast URL are configured correctly:
-
| Parameter | Description |
|---|---|
| Console URL | "https://{CONSOLE_URL}/AirWatch", where {CONSOLE_URL} is the URL of your UEM console server |
| Device Services URL | "https://{AW_DS_URL}/DeviceServices", where {AW_DS_URL} is the URL of your Device Services server |
| REST API URL | "https://{AW_API_URL}/API", where {AW_API_URL} is the URL of your API server |
| SCL Sync Appcast URL | "https://{AW_DS_URL}/DeviceServices/AirWatchSyncAppcast.xml", where {AW_DS_URL} is the URL of your Device Services server |
| MdmAgentAppcast URL | "https://{AW_DS_URL}/DeviceServices/AirWatchAgentAppcast.xml", where {AW_DS_URL} is the URL of your Device Services server |
| Outlook Add-In SCL Appcast URL | "https://{AW_DS_URL}/DeviceServces/OutlookSCLAppcast.xml", where {AW_DS_URL} is the URL of the Device Services server |
| SCL Appcast URL | "https://{AW_DS_URL}/DeviceServices/SCLAppcast.xml", where {AW_DS_URL} is the URL of the Device Services server. Nothing should appear as "localhost" except for the Google Play Service URL |
-
Next, validate GEM Functionality.
-
In your Console server, navigate to AirWatch Root>\Logs\Services\. Delete the AirWatchGemAgent.txt file.
-
Open the Server Manager.
-
From the left pane, select Local Server and navigate to Tools > Services.
-
At the top of the services list, all Workspace ONE UEM Services are displayed in alphabetical order. Each service starts with Workspace ONE UEM in the name. For the GEM Inventory Service, right-click and select Restart.
-
Check your [Install Directory]\Logs\Services\ folder to see if a log regenerates. If a log regenerates with errors, contact Workspace ONE Support for further assistance. If you do not see a log file in this folder, then it is not necessary to contact Workspace ONE Support.
-
Post-Upgrade Checklist
Each component of Workspace ONE UEM has its own verification steps to ensure that they were upgraded sucesfully. Learn more about which components need upgrade verification, their functionality within Workspace ONE UEM, and how to verify.
| Status | Functionality | Verification |
|---|---|---|
| Workspace ONE UEM console Testing | ||
| Directory Services | Navigate to Groups & Settings > All Settings > System > Enterprise Integration > Directory Services and select Test Connection. | |
| Email (SMTP) | Navigate to Groups & Settings > All Settings > System > Enterprise Integration > Email (SMTP) and select Test Connection. | |
| AWCM | Attempt to access "https://<AWCM URL>:<port>/awcm/status", where <AWCM URL> is the URL of your AWCM and <port> is the port you configured it on. If functioning correctly, you see an "OK" status message. | |
| Devices are checking in | Verify on the Devices > List View page that devices are checking in by looking at the Last Seen column. | |
| Console Access using LDAP | Verify that AD or LDAP users work by logging into the Console with one (if applicable). | |
| Executing a Report | Try running an Admin User Roles report by navigating to Hub > Reporting & Analytics > Reports > List View. | |
| Content Management (if applicable) | Try downloading a piece of content from a device. | |
| iOS device testing | ||
| Enrollment | Try enrolling an iOS device. | |
| Sending Commands (for example, Device Lock) | Try sending a command to an enrolled iOS device. | |
| Create and Push Profile | Try creating and sending a profile from the Console to an iOS device. | |
| Create and Push Application | Try to create and send an application from the Console to an iOS device. | |
| Public Applications | Try to recommend a public application from the Console to an iOS device. | |
| Internal Applications | Try to push an internal application from the Console to an iOS device. | |
| Android device testing | ||
| Enrollment | Try enrolling an Android device. | |
| Sending Commands (for example, Device Lock) | Try sending a command to an enrolled Android device. | |
| Create and Push Profile | Try creating and sending a profile from the Console to an Android device. | |
| Create and Push Application | Try to create and send an application from the Console to an Android device. | |
| Public Applications | Try to recommend a public application from the Console to an Android device. | |
| Internal Applications | Try to push an internal application from the Console to an Android device. | |
| Windows Rugged device testing | ||
| Device Check-In | Verify that Windows Mobile devices are checking in after the upgrade process. | |
| Create and Push Provisioning Product | Try to create and push a provisioning product to a Windows Mobile device. | |
| AWCM Testing | Verify on the Device Details page for a Windows Mobile device that AWCM is Connected. | |
| Remote Control | Try to activate Remote Control for a Windows Mobile device on the Device Details page. Ensure that Privacy Settings are enabled. | |
| Screenshot/Send Message | Try to take a screenshot or send a message Windows Mobile on the Device Details page. |
If Problems Are Detected After the Upgrade
If during any of the verification steps listed above you are unsuccessful, verify the following:
- If all Workspace ONE UEM Services are up and running on the server with proper paths to the Workspace ONE UEM folder.
- If all Workspace ONE UEM Websites are listed in IIS.
- Windows Application Log shows any errors originated from the Workspace ONE UEM application.
- If any Workspace ONE UEM logs show any errors that have occurred.
- If you are still having problems and must contact Workspace ONE Support, have the earlier mentioned logs to expedite a resolution. Include the log from [Install Directory]\Database\AWDatabaseLog_MM-DD-YYYY_XX-XX-XX.txt.
Workspace ONE UEM Post-Upgrade Validation
After you complete the upgrade procedure, verify that the Workspace ONE UEM services are started and that you successfully upgraded Workspace ONE UEM. Learn about how to verify the upgrade completed succesfully and that all your services and components have been upgraded.
Verify Workspace ONE UEM Services Are Running
The first post-upgrade step is to verify that all Workspace ONE UEM services have started back up. Learn more about how to verify the post-upgrade status of your Workspace ONE UEM Services.
The Workspace ONE UEM installer properly configures the associated Windows services, the start type and recovery options for each service should not be modified. If services are not automatically restarted, use Windows Services Manager to reset Window Services to Automatically Delayed Start.
After a typical upgrade, open the Windows Services Manager to verify that the installed component services are running.
-
Open the Server Manager.
-
From the left pane, select your local server and navigate to Tools > Services.
Workspace ONE UEM Services is at the top of the services list in alphabetical order. Each of these services start with Airwatch in the name.
-
Verify that each of these services show Started as the Status.
-
Verify the World Wide Web Publishing service is Started.
Verify the Upgrade
After you have validated that your Workspace ONE UEM Services are running, there are other verification steps to ensure that the updgrade completed succesfully on the rest of your Workspace ONE UEM platform. Learn more about these verification steps and what to do next.
-
First, validate your Administrator Roles.
-
Log in to the Workspace ONE UEM console and navigate to Accounts > Administrators > Roles.
-
Verify that the update did not remove any of your custom administrator roles. If they are missing, recreate them manually.
-
-
Next, verify your Directory Service settings.
-
Navigate to Groups & Settings > All Settings > System > Enterprise Integration > Directory Services. Select the User tab.
-
Select Show Advanced. Verify that Auto Merge is selected. Select the Group tab.
-
Select Show Advanced. Verify Auto Sync and Auto Merge are checked.
-
Workspace ONE UEM recommends a minimum of 100 for the Maximum Allowable Changes. That way, the Console does not need to sync with your directory service as much.
-
-
Next, verify the Site URLs.
-
Navigate to Groups & Settings > All Settings > System > Advanced > Site URLs.
-
Verify the REST API URL and Sync Appcast URL are configured correctly:
|**Console URL**|"https://\{CONSOLE\_URL\}/AirWatch", where \{CONSOLE\_URL\} is the URL of your UEM console Server||Device Services URL|"https://{AW_DS_URL}/DeviceServices", where {AW_DS_URL} is the URL of your Device Services server| |REST API URL|"https://{AW_API_URL}/API", where {AW_API_URL} is the URL of your API server| |SCL Sync Appcast URL|“https://{AW_DS_URL}/DeviceServices/AirWatchSyncAppcast.xml", where {AW_DS_URL} is the URL of your Device Services server| |MdmAgentAppcast URL|"https://{AW_DS_URL}/DeviceServices/AirWatchAgentAppcast.xml", where {AW_DS_URL} is the URL of your Device Services server| |Outlook Add-In SCL Appcast URL|"https://{AW_DS_URL}/DeviceServces/OutlookSCLAppcast.xml", where {AW_DS_URL} is the URL of the Device Services server| |SCL Appcast URL|"https://{AW_DS_URL}/DeviceServices/SCLAppcast.xml", where {AW_DS_URL} is the URL of the Device Services server. Nothing should appear as "localhost" except for the Google Play Service URL|
-
-
Next, validate GEM Functionality.
-
In your Console server, navigate to AirWatch Root>\Logs\Services\. Delete the AirWatchGemAgent.txt file.
-
Open the Server Manager.
-
From the left pane, select Local Server and navigate to Tools > Services.
-
At the top of the services list, all Workspace ONE UEM Services are displayed in alphabetical order. Each service starts with Workspace ONE UEM in the name. For the GEM Inventory Service, right-click and select Restart.
-
Check your [Install Directory]\Logs\Services\ folder to see if a log regenerates. If a log regenerates with errors, contact Workspace ONE Support for further assistance. If you do not see a log file in this folder, then it is not necessary to contact Workspace ONE Support.
-
Post-Upgrade Checklist
Each component of Workspace ONE UEM has its own verification steps to ensure that they were upgraded sucesfully. Learn more about which components need upgrade verification, their functionality within Workspace ONE UEM, and how to verify.
| Status | Functionality | Verification |
|---|---|---|
| Workspace ONE UEM console Testing | ||
| Directory Services | Navigate to Groups & Settings > All Settings > System > Enterprise Integration > Directory Services and select Test Connection. | |
| Email (SMTP) | Navigate to Groups & Settings > All Settings > System > Enterprise Integration > Email (SMTP) and select Test Connection. | |
| AWCM | Attempt to access "https://<AWCM URL>:<port>/awcm/status", where <AWCM URL> is the URL of your AWCM and <port> is the port you configured it on. If functioning correctly, you see an "OK" status message. | |
| Devices are checking in | Verify on the Devices > List View page that devices are checking in by looking at the Last Seen column. | |
| Console Access using LDAP | Verify that AD or LDAP users work by logging into the Console with one (if applicable). | |
| Executing a Report | Try running an Admin User Roles report by navigating to Hub > Reporting & Analytics > Reports > List View. | |
| Content Management (if applicable) | Try downloading a piece of content from a device. | |
| iOS device testing | ||
| Enrollment | Try enrolling an iOS device. | |
| Sending Commands (for example, Device Lock) | Try sending a command to an enrolled iOS device. | |
| Create and Push Profile | Try creating and sending a profile from the Console to an iOS device. | |
| Create and Push Application | Try to create and send an application from the Console to an iOS device. | |
| Public Applications | Try to recommend a public application from the Console to an iOS device. | |
| Internal Applications | Try to push an internal application from the Console to an iOS device. | |
| Android device testing | ||
| Enrollment | Try enrolling an Android device. | |
| Sending Commands (for example, Device Lock) | Try sending a command to an enrolled Android device. | |
| Create and Push Profile | Try creating and sending a profile from the Console to an Android device. | |
| Create and Push Application | Try to create and send an application from the Console to an Android device. | |
| Public Applications | Try to recommend a public application from the Console to an Android device. | |
| Internal Applications | Try to push an internal application from the Console to an Android device. | |
| Windows Rugged device testing | ||
| Device Check-In | Verify that Windows Mobile devices are checking in after the upgrade process. | |
| Create and Push Provisioning Product | Try to create and push a provisioning product to a Windows Mobile device. | |
| AWCM Testing | Verify on the Device Details page for a Windows Mobile device that AWCM is Connected. | |
| Remote Control | Try to activate Remote Control for a Windows Mobile device on the Device Details page. Ensure that Privacy Settings are enabled. | |
| Screenshot/Send Message | Try to take a screenshot or send a message Windows Mobile on the Device Details page. |
If Problems Are Detected After the Upgrade
If during any of the verification steps listed above you are unsuccessful, verify the following:
- If all Workspace ONE UEM Services are up and running on the server with proper paths to the Workspace ONE UEM folder.
- If all Workspace ONE UEM Websites are listed in IIS.
- Windows Application Log shows any errors originated from the Workspace ONE UEM application.
- If any Workspace ONE UEM logs show any errors that have occurred.
- If you are still having problems and must contact Workspace ONE Support, have the earlier mentioned logs to expedite a resolution. Include the log from [Install Directory]\Database\AWDatabaseLog_MM-DD-YYYY_XX-XX-XX.txt.
¿Le resultó útil esta página?