PowerShell Integration Overview

Powershell Integration Overview


The following article is intended to assist AirWatch Customers and Agents configure, validate and troubleshoot Powershell integration for email management.

CLICK HERE
for more information on an
assisted install. Reach out to
your Account Executive to
purchase.

PowerShell Integration Guide

The install guide is intended to walk users through the preparation, integration and configuration of Powershell for email management.

Pre-Install Requirements Worksheet

Provides a detailed explanation of all general, hardware, software and network requirements for a successful Powershell integration. Please only reference the tab for the ACC for this integration.

Install Validation

Provides tests and checks to perform in order to validate that the component has been successfully installed and configured. These should always be performed after a new install or upgrade to confirm functionality.

PowerShell Logs

How to guide for gathering logs related to Powershell integration. These logs will be needed if you run into any issues with the integration during or after an install or upgrade. It will also help our support team assist you more quickly if these are provided up front.

Install Troubleshooting

This forum provides resolutions to common issues and error messages that are encountered during Powershell integration. Please be sure to gather logs prior to beginning troubleshooting.


Install Validation


The following steps should be performed after Powershell integration or On Premise upgrade to confirm Powershell was integrated successfully. If you encounter issues at any point during validation, please proceed to the Powershell Logs and Install Troubleshooting sections.

Validation Step Actions Expected Results
Step 1 - PowerShell Test Connection Navigate to Console > Email > Email Settings > Test Connection Connection Succeeded
Powershell_Step_1.jpg

Feature Validation


The following steps should be performed after Powershell configuration or On Premise upgrade to confirm Powershell and email functionality.

Validation Step Actions Expected Results
Step 1 - Email Dashboard Updating Navigate to Console > Email > List View > Actions and click on "Sync Devices" New Records are generated after the integration
Powershell_Step_2.jpg
Step 2 - Test unmanaged device email access after Exchange Global Access Rule setup Manually configure an un-enrolled device to connect to Exchange Emails do not sync on the un-enrolled device
Step 3 - Test manged device email access Enroll a device with the corresponding email profile setup. Open configured mail client. Emails sync to device without issue

Powershell Logs


The following article provides information on how and when to collect and verbose logs related to PowerShell Integration.


I. MEG Queue Service Log


PowerShell Commands are sent through MEG Queue Service on either Console Server or Device Service server. For example, a whitelist operation from web console will generate a PowerShell command from the Console Server, while enrollment will generate a PowerShell command from the Device Service Server. The MEG Queue Service log not only shows what commands fail but also the errors that come with the failure.

1. To verbose the MEG Queue Service log, open the config file under the following path: \AirWatch\AirWatch8.2\Services\AW.Meg.Queue.Service.exe.config
2. Search for the keyword “level”, change its value to Verbose. Save.

Powershell_Log_1.1.jpg


3. Restart AirWatch MEG Queue Service under Windows Services.


II. ACC Logs


The setting on whether the PowerShell commands are going through ACC can be found on AirWatch web console. Navigate to Settings > All Settings > System > Enterprise Integration > Cloud Connector > Advanced > Enterprise Services > Exchange PowerShell to see how your environment is configured. In the cases that AirWatch Console or Device Service Servers don’t have connection to the internal Exchange PowerShell endpoint, the PowerShell commands are sent through ACC. The verbosed ACC log only shows what commands fail but also the errors that come with the failure.

Powershell_Log_2.1.jpg



1. To verbose the ACC log, go to \AirWatch\CloudConnector\Bank1\CloudConnector.exe.config.
2. Search for the keyword “level”, change its value to Verbose. Save.
3. Restart Windows Service AirWatch Cloud Connector.

Powershell_Log_2.2.jpg

III. Enable CAPI2 Logs


The CAPI2 log is useful to troubleshoot any issues concerned with certificate chain validation, certificate store operations, and signature verification.

1. Enable CAPI2 logging by opening the Event Viewer and navigating to the Event Viewer (Local)\Applications and Services Logs\Microsoft\Windows\CAPI2 directory and expanding it. You should see a view named Operational as shown below.

Powershell_Log_3.1.jpg

2. Right-click on the Operational view and click the Enable Log menu item as shown.

Powershell_Log_3.2.jpg

3. Once enabled, any warnings or errors are logged into the viewer. Reproduce the problem you are experiencing and check if the issue is logged.

Have more questions? Submit a request

0 Comments

Article is closed for comments.