NetMotion company logo

NetMotion Mobility v11.4x Known and Resolved Issues

Last updated: October 16, 2018

The numbers in square brackets are internal issue numbers. Issues are grouped by product area and listed in descending order by issue number.

Known Issues

Resolved Issues

Release History


Mobility Client Compatibility with Windows 10 Upgrades

For the purposes of these client updates, there is no need to update the Mobility server.

Microsoft Windows 10 Fall 2018 release

Adopters of the Windows 10 Fall release (release 1809) must install the Mobility Windows client v11.43 to address issues with the Windows 10 network location awareness (NLA) feature. Failure to do so will result in elevated CPU utilization associated with NLA, and cause malfunctions in the Windows Edge browser and other applications that rely on NLA to function. [MOB-13108]

Microsoft Windows Updates Released January 2017

Versions of Mobility prior to v11.32 are fully compatible with Windows updates released January 3 and 9, 2017 that address the Spectre and Meltdown vulnerabilities. The Windows 10 Spring Creators update is incompatible with pre-v11.32 Mobility clients. You must upgrade to Mobility v11.32 or later before applying the Spring 2017 Windows updates, otherwise Mobility will not work.

  • For administrators who require a Mobility XE client, which uses an earlier client architecture, the release you must upgrade to is Mobility XE, v10.74.

  • If you are running security software from Trend Micro, read the description of MOB-12067 before upgrading.

Windows 8 and 7 Clients

We have seen no evidence indicating that there are imminent updates to Windows 8 and Windows 7 that would cause issues, but administrators should update their Windows 8 and 7 clients to the latest Mobility release as a precaution.

About Upgrading Mobility Server Components

Settings: When you upgrade Mobility, the settings that you have configured in the earlier release are used in the new installation. But sometimes NetMotion Software will change settings and you need to be aware of the consequences. See Things to Consider Before You Upgrade Mobility in the Mobility server help for details.

Mobility warehouse: Versions 10 and later of the Mobility server work only with version 7.0 and later of the Mobility warehouse.

  • If you are upgrading to the latest Mobility release, your starting point must be Mobility servers running v9.2x or later, and version 7.0 of the Mobility warehouse.

  • If you have version 7.0 of the warehouse from a previous release, upgrade the warehouse to v11.

See Upgrading the Mobility Warehouse in the Mobility server help for details.

FIPS 140-2 CNG Modules

When Mobility is configured to require FIPS 140-2 validated encryption, a Mobility server accepts connections from Mobility clients that use any of a list of cryptographic modules specified in the Mobility console. The default list of modules is as follows:

ModuleVersionOS
ccrypto7iOS
ccrypto8iOS
ccrypto9iOS
ccrypto10iOS
ccrypto10.11macOS
ccrypto10.12macOS
ccrypto10.13macOS
ccrypto11iOS
cng6.1.7600-
cng6.1.7601-
cng6.2.9200-
cng6.3.9600-
cng10.0-
mocana5.5.F-
openssl-fips2.0.12Android

Before you install or upgrade the Mobility server, refer to Preserving FIPS Customizations During an Upgrade in the help.

Customer Support and EOL Advisories

The Mobility server is supported only on Windows Server 2016 and Windows Server 2012 R2. For a list of advisories, with information about when support ends for operating systems or Mobility versions, see the Mobility server help.

Windows Server 2012 R2: Microsoft Support Advisory for NPS

On Tuesday August 8, 2017, Microsoft released a roll-up patch (KB4034681) for NPS running on Windows Server 2012 R2 that broke authentication based on RADIUS EAP-TLS and PEAP-TLS. You may no longer be able to authenticate after applying the roll-up.

Microsoft has published a work around that involves changing a registry setting on your NPS server. NPS administrators should evaluate whether to implement the work around, or to hold off installing the patch until Microsoft implements a fix.


Known Issues: Mobility Client

↑Top

Client issues are grouped by operating system and listed in descending order by issue number.

Cross-Platform Client Issues

iOS and Android: Skype session does not persist during roam [MOB-8599]

If you are on a Skype video call and you roam between cellular and Wi-Fi, your call is disconnected.

Windows Client

Issue with connection default after Windows OS upgrade [MOB-12883]

The following situation results in an error that users can ignore:

  1. The Mobility client is not configured to run when Windows starts.

  2. The Windows operating system on the client is upgraded.

  3. The Mobility client is reconfigured to load on Windows startup.

Users will see the error once (Error writing Mobility configuration) and can ignore it: the configuration change has taken effect.

Upgrade fails unless Trend Micro has patch [MOB-12067]

If you are running security software from Trend Micro, and you plan to upgrade Mobility clients running on Windows, there are two options for ensuring a successful Mobility upgrade:

  • Install the latest client software patch from Trend Micro before upgrading Mobility. The client hotfix that addresses this issue is 4440; you may need to request it from Trend Micro.

  • Uninstall Trend Micro, upgrade the Mobility client, and then re-install your security software.

macOS Client

macOS: A quick disconnect/reconnect may cause Mobility to fail (Apple RADAR ID: 32073323) [MOB-11447]

If you disconnect your Mobility session, and then reconnect within 5 seconds, the operating system may spontaneously disconnect Mobility about 20 seconds later. In most cases Mobility will automatically reconnect when it detects this problem. This is an issue with the Apple operating system (Apple RADAR ID: 32073323).

macOS: AirWatch Per-App profile not displayed in Mobility client [MOB-8500]

If you create a VPN profile for Mobility in the AirWatch console, and you enable Per App VPN Rules in the connection info area, the profile does not appear in the list of configurations for the Mobility client for macOS.

iPhone/iPad Client

iOS: Upgrading the Apple OS [MOB-11563]

If the Mobility VPN is installed when you upgrade your Apple operating system to version 11, you may see problems connecting with Mobility after the upgrade. To resolve this issue, restart the device, open Mobility, and establish a connection to the Mobility server.

Android Client

Android client displays only numeric pad during native SecurID authentication [MOB-12490]

During Android native SecurID authentication, the user is prompted with a numeric keypad, not a standard keyboard; the user cannot enter an alphanumeric PIN. This is not an issue with SecurID RADIUS.

Android: Imported certificate does not immediately display [MOB-12413]

When you create a VPN configuration, and then specify a system certificate for it, the certificate you selected is not displayed in the user interface until you navigate away from that screen and then return to it.

Android: Conflict between Google-managed VPN and Mobility [MOB-11536]

Google Connectivity Services is available on some Android devices, and it includes a Wi-Fi assistant that automatically connects you to public Wi-Fi, securing the connection with a VPN managed by Google. If you are already connected using Mobility, the Mobility app will stop. This is Google issue 65645854.

Android: Application connections do not persist when roaming between networks [MOB-11233, MOB-3275]

Mobility supports two types of session persistence: application sessions and VPN tunnel sessions. Google made changes in Android 4.4, 7.x, and 8.x that may affect TCP application session persistence while roaming between networks. Session persistence when moving through coverage gaps are unaffected, as are all UDP traffic and VPN tunnel sessions, but when a network interface is reset (for example, roaming from cellular to Wi-Fi), TCP application sessions do not persist. Until Google fixes this issue, TCP session persistence on Android may be limited:

  • Most Android applications reconnect automatically and users are not disrupted.

  • Some Android applications may need to be restarted.

In all cases, Mobility automatically maintains the VPN tunnel session so that users do not need to re-authenticate. Even when there are interruptions, Mobility improves application behavior, performance, and stability.

Expected certificate is not listed as active [MOB-10703]

When you view or edit a VPN configuration for an Android device that includes a certificate in its credentials, the certificate is not always listed as expected. Here are situations in which that may occur:

  • Manually created profile: If a certificate is selected during authentication, it is not listed as the active certificate.

  • Android for Enterprise: The certificate in the profile is not listed as active.

  • nmcfg. file: You can create a configuration file and distribute it using email, as described here. If multiple certs are included with your .nmcfg profile, only the most recent certificate is selected and listed as active.

Android: Interface proxy settings are ignored when connected with Mobility [MOB-4190]

In the Android operating system you can modify the proxy settings for WiFi connectivity, but these settings are ignored when the device is connected over the Mobility VPN tunnel (without a VPN installed the proxy works as expected). This is due to Google issue 33935.

Known Issues: Mobility Server

↑Top

Mobility v11 browser settings for Internet Explorer 10

The Mobility console cannot be accessed using TLS 1.0; if you have only TLS 1.0 enabled, you will see the error This page can't be displayed. To change your Internet Explorer browser settings, go to Tools > Internet options > Advanced tab > Security and then select Use TLS 1.1.

This is a workaround for Internet Explorer 10; it is not an issue with Internet Explorer 11, Firefox, or Chrome.

Mobility is incompatible with RSA version 7.4 [MOB-13078]

The Mobility server supports v7.3.3 build 99 of the RSA authentication agent. If you upgrade the agent to version 7.4, the Mobility server cannot function properly (the nmservic service fails).

Domain controller mapping offers AD distribution groups [MOB-13054]

You can have Active Directory group members automatically moved into Mobility user groups when they connect to the Mobility server. When a domain controller mapping is configured for use with RADIUS authentication, it currently offers both AD security and distribution groups; only security groups should be available for mapping.

Warehouse upgrade: user limitation [MOB-12522]

There is a limitation in Mobility v11.40 as to who can perform warehouse upgrades (this will be fixed in a later release). When upgrading the Mobility warehouse to v11.40 or using the v11.40 Warehouse Management Tool, the user performing the upgrade must be one of the following:

  • The same user who installed the current warehouse (in other words, Username in the error message below). Domain users are not permitted to upgrade the warehouse, unless this is the same user who performed the current warehouse install.

  • A local user who is a member of the local Administrators group.

If you are not logged on as the original installer or as a local Administrator, the installation will not complete, and this message is logged in the install log:

Only Username and root can run this command

If you have already attempted a warehouse upgrade and encountered this problem, log on as Username or a local Administrator, run the warehouse upgrade again, and select the Repair option.

ActiveMQ event log error message [MOB-11443]

In the Mobility server event log you may see a Reporting error, right after you enable a publisher target, that looks like this: TaskRunnerFactory - Error in thread 'ActiveMQ VMTransport: vm://Log4MobilityCollector#1-2'. This should be rare and the error can be ignored.

Primary warehouse name cannot include Japanese characters [MOB-7821]

If you are running Mobility software that has been localized for the Japanese market, do not assign the primary warehouse a name that includes Japanese characters: a standby warehouse will not be able to create a replication agreement with the primary warehouse.

Known Issues: Analytics Module

↑Top

Analytics alerts using syslog do not send Japanese characters correctly [MOB-10135]

If your analytics server is hosted on a computer running a Japanese operating system, and you configure analytics to send alerts to a syslog server (Analytics > Settings > Send Alerts - Syslog), the characters are not sent correctly. To work around this issue, specify a syslog server using server settings instead (Configure > Server Settings > Syslog).

Known Issues: Policy and Network Access Control (NAC)

↑Top

AVG Business Edition not detected

When the antivirus software AVG Internet Security - Business Edition is installed and NAC policy is enabled, the Mobility client reports that no antivirus software was detected.

McAfee VirusScan Enterprise not detected on Windows 7/32-bit

When the antivirus software McAfee VirusScan Enterprise is installed on a Windows 7/32-bit computer and NAC policy is enabled, the Mobility client reports that no antivirus software was detected.


Resolved Issues: Mobility Client

↑Top

Fixed In Summary Issue Number Description
11.43 Compatibility with the Windows 10 Fall release MOB-13108 Adopters of the Windows 10 Fall 2018 release must upgrade to v11.43. See the note above for more information.
11.42 With Aegis Mobile software, UDP heartbeats were dropped MOB-12969 Aegis Mobile (developed by New World Systems) sends a heartbeat at a regular, 10-second interval. Mobility v11.40 was dropping some of these heartbeats.
11.42 iOS: Prompt for credentials during certificate-based authentication MOB-12902 When the Mobility iOS client is configured for certificate-based authentication and an MDM profile pushed down to it includes valid certificates, the user should not first be prompted to enter a user name and password.
11.42 Mobility upgrades after installing Windows 10 1810 fail unless Mobility v11.42 is installed MOB-12853 On a Windows 10 device that is upgraded to the Microsoft fall release (Windows 10 1810), you must install Mobility v11.42. Though an earlier Mobility client is compatible with the operating system upgrade, subsequent Mobility client updates will fail unless the client is running v11.42 or later.
11.41 macOS clients and certificates MOB-12806 Fix for a problem with displaying certificate properties.
11.41 Occasional iOS crash MOB-12783 Occasional iOS crash.
11.41 Android: access to internal hosts interrupted MOB-12740 On some devices, connection attempts to internal hosts failed.
11.41 DNS issue MOB-12676 Fix for a DNS resolution issue on the Mobility client for iOS.
11.41 Threats mistakenly indicated MOB-12528, MOB-12519 On Mobility clients using Network Access Control (NAC) and running third-party antivirus software (for example, Cisco AMP), multiple threats were indicated on the client where none existed.
11.41 Captive portal detection sometimes failed MOB-12503 Mobility client automatically detects a hotspot (also known as a captive portal) when a new interface is encountered; this detection sometimes failed.
11.41 Policy: allow rule for DNS has no effect if local networking is enabled MOB-12421 If the local DNS was on the same subnet as the local IP network, and you also had local networking enabled, an allow rule for DNS would send DNS requests out the point-of-presence adapter.
11.41 Cannot save files to OneDrive MOB-9477 When Mobility was connected, files could not be saved to Microsoft OneDrive (users would see the error UPLOAD FAILED).
11.40 build 19423 Operating system crash when installing on Windows 7 with security software running MOB-12485 Installing or upgrading to Mobility v11.40 (build 18434) on a Windows 7 (32-bit or 64-bit) computer running security software resulted in an operating system crash.
11.40 Add ability to always display the Mobility icon MOB-12221 On Windows devices, the Mobility client system tray icon can be configured to always display on provisioned systems (and not be hidden). For more information, see this help topic.
11.40 Skype for Business unable to accept calls MOB-12335 Skype for Business (lync.exe) is sometimes unable to accept a call, failing with the error message Call was not completed.
11.40 DDNS sometimes disabled MOB-12209 If you have a pre-v11.40 Mobility client running on Windows 10, it may fail to register dynamic DNS when connected.
11.40 Windows: ping target cannot be edited MOB-12190 When you gather support data in the Mobility Logs dialog, ping sends a request to the IP address of the server for which for you are configured. This text field can no longer be edited.
11.40 Misleading disconnect reason MOB-12186 A temporary loss of connectivity was incorrectly identified as disconnect reason 11 (Connection was terminated by the Mobility administrator); in Mobility v11.40 this is disconnect reason 10 (Server network interface changed), where clients attempt to reconnect without user intervention.
11.40 Windows 10: Mobility logon appeared before the Windows prompt MOB-12181 Users with a non-domain user account (with password) were not automatically signed on to Windows again after rebooting from the Start menu.
11.40 Skype for Business voicemail MOB-12160, MOB-12318 Skype for Business (lync.exe) voicemail failed after upgrade to Mobility v11.32.
11.40 Android: Mobility VPN indicator sometimes disappeared MOB-12081 On Android 4.4.4 devices, the key icon periodically disappeared from the notifications bar, even though Mobility was connected and functioning properly.
11.40 Send DHCP requests over the internal interface MOB-11950 If a DHCP relay is defined, force the DHCP proxy to send DHCP requests on the internal interface.
11.40 Android: Device authentication incorrectly prompted users to specify a certificate MOB-11920 When MDM software pushes configuration settings and certificates down to Mobility Android clients, no user interaction should be necessary for authentication.
11.40 Android 8: name resolution MOB-11680 The client sometimes had issues with names that require a DNS server to be accessible via the local network (for example, a local printer).
11.40 Android 8: Mobility notifications not displayed MOB-11679 Some Mobility client notifications were not working in Android 8; Mobility works as expected, but the user is not notified of connection issues.
11.40 Client logon with UPN fails when authentication is NTLM MOB-8578 If you use a UPN to log on to a Mobility server (for example, user.name@your.company.com), and if the authentication protocol is NTLM, the logon was failing.
11.31 Skype for Business sometimes fails with an 0xC0000142 error MOB-11657 Skype for Business (versions 17.01 and 17.05) did not always work properly with Mobility.
11.05 Windows clients: Disconnect reason 107 MOB-10459 Mobility clients sometimes disconnected at logon (reason 107).
11.05 Windows clients: 32-bit Chrome v56 and Windows 64-bit MOB-10420 Running version 56 of the 32-bit Chrome browser on a 64-bit computer caused the Mobility client to fail.
11.04 macOS: Settings not preserved during Mobility upgrade (Apple RADAR ID: 25911312) MOB-8671 Configuration profiles created in Mobility disappeared when you upgraded Mobility (this was an issue with the Apple operating system). If you are running macOS version 10.12 or later, this is not an issue.
11.04 iOS: Per-App VPN manual connect fails (Apple RADAR ID: 27704986) MOB-9348 This was an issue with the Apple operating system that has now been resolved.
11.03 Reauthentication using certificates failed on iOS devices when the device was locked MOB-9836 If reauthentication occurred while a device was locked, Mobility did not have access to the certificate and the process failed. This is fixed in v11.03.
11.03 Windows Defender update incompatible with Mobility client MOB-9771 On the Mobility client running Windows 10 or Windows 8.1, the latest Windows Defender virus definition update failed. This is fixed in Mobility client v11.03.
11.03 When policy changes, re-evaluate the traffic flows MOB-9666 When a policy change occurs on the Mobility client, immediately re-evaluate the UDP and TCP traffic flows (do not use the cached flow).
11.02 Mobility now supports TLS1.1/1.2 for RADIUS authentication MOB-8613 Pre-v11.02 Mobility clients accept only TLS1.0 for RADIUS authentication.
11 Passthru DNS traffic is routed to the virtual adapter MOB-7084 Passthru DNS traffic is routed to the virtual adapter.
11 TCP active sessions aborted MOB-6925 Outbound RDP failed.

 

Resolved Issues: Mobility Server

↑Top

Fixed In Summary Issue Number Description
11.40 For automated warehouse backup, non-default warehouse port could not be specified MOB-12139 By default, Mobility servers communicate with the warehouse over port 389. If you specified a different port in a pre-v11.40 release, automated backups of the warehouse would not work.
11.40 The report Network Usage by User did not show unattended devices MOB-12082 With Mobility server v11.31, the analytics report Network Usage by User failed to include devices running in unattended mode.
11.40 Inaccurate device/user counts MOB-10243 The device and user counts on the Mobility console status page did not always match the total number of Mobility clients. In addition, on the Devices and Users pages, the counts were sometimes affected by changing the sort order.
11.31 Policies compatible with v10.70 were disconnecting v10.70 clients MOB-11770 When a policy rule was configured to disconnect clients that were incompatible, and the rule action or condition required v10.70 or later, v10.70 clients were incorrectly disconnected.
11.31 Error when moving a user from one group to another MOB-11750 When a user was moved from one group to another, the following error appeared in the event log: Web Server Cannot communicate with Mobility server.
11.31 Analytics failed to start after upgrade from v10.71 to v11.30 MOB-11728, MOB-11853 After upgrading from Mobility v10.71 to v11.30, the analytics module did not start (AmqInfo-Reporting-Server.log reported Detected missing journal files).
11.31 Could not restrict web server access to a particular IP address range MOB-11676 In the Mobility Management Tool, on the Web Server tab, the Network access options are designed to let you restrict access to the Mobility console. The Only from the IPv4 network defined below option did not work in v11.30.
11.30 Setup issue—Windows Server 2016 configured for Secure Boot MOB-11643 Mobility server installation failed on Windows Server 2016 configured for Secure Boot. Mobility v11.30.7299 addresses this issue.
11.30 Policy rule or rule set names required ASCII characters MOB-9892 With Mobility server v11.03 only ASCII characters were valid for the names of policy rules or rules sets. If extended characters were used, such as an "a" with a diaresis (ä) or a Japanese character, the policy could not be pushed down to any clients.
11.30 A user was temporarily prevented from being re-added to a group MOB-6755 If a user belonged to a group and the entry was somehow corrupted, the Mobility warehouse put a "lock" on the data that lasted about 30 minutes. A server reboot after the 30-minute waiting period was over was required.
11.03 Warehouse errors displayed in Mobility console MOB-9755 The Mobility warehouse stores configuration settings and client policies. A change to the warehouse sometimes failed until it was attempted a second time.
11.03 Mobility server upgrades to v11.02 sometimes failed MOB-9687 During Mobility Setup there was an incompatibility with Windows Server 2012 R2 certificates.
11.02 Automatic warehouse backup failed with older base DN MOB-9480 In earlier Mobility releases, Setup prompted users to enter a base DN for the Mobility warehouse. Users with a non-default base DN who upgraded to Mobility v11 were unable to use the automatic warehouse backup feature.
11.02 Make log messages sent to syslog easier for Splunk to parse MOB-9406 Make session numbers consistent across logs (regardless of source).
11.02 New clients cannot connect after incomplete upgrade to v11 MOB-9388 If you were prompted to reboot the Mobility server during an upgrade to v11, it is possible that the Configuration Wizard failed to run following the reboot. In this case, the upgrade is incomplete and clients are not able to connect. In Mobility v11.02 the Configuration Wizard starts automatically after a reboot.
11.02 Testing DC mapping only found groups that belonged to the user's logon domain MOB-9102 The Domain Controller Mapping Test button only mapped AD groups that belonged to the user's logon domain. As of v11.02 there is an option for also searching trusted domains.
11 Firewall failover failed with Mobility XG clients MOB-7263 During a failover to another firewall node Mobility failed to send packets to the new firewall MAC address.
11 A custom Logon Notice was not shown on initial connection MOB-6647 If you configured Mobility to add devices to a group based on operating system, and you also configured a logon notice, the notice was not displayed when the device connected for the first time.
11 Could not establish a remote session on the Mobility server over WAN MOB-5145 With the Mobility client running on iPhone or iPad, a remote session on the Mobility server over WAN timed out with an error.
11 TcpTransport event log errors when adding an Analytics Module MOB-782 If you added an Analytics Module to a pool of Mobility servers, you might see (ignorable) errors in the event log that look like this: Error <time stamp> Reporting TcpTransport - Reason: java.lang.InterruptedException

 

Release Dates and Build Numbers

↑Top

Version Component Release Date Build Number Description
11 Server July 5, 2016 14681 See What's New in NetMotion Mobility
11 Windows client July 5, 2016 14681 See What's New in NetMotion Mobility
11 macOS client July 5, 2016 14548 See What's New in NetMotion Mobility
 
11.01 Server July 27, 2016 15791 Japanese language support
11.01 Windows client July 27, 2016 15791 Japanese language support
 
11.02 Server August 31, 2016 17625 Maintenance release (English, Japanese)
11.02 Windows client August 31, 2016 17625 Multilingual (Japanese, French, Italian, German, and Spanish) support
11.02 Windows client October 10, 2016 19757 slipstream Maintenance release (MOB-9771)
11.02 Android client September 15, 2016 18145 Multilingual (Japanese, French, Italian, German, and Spanish) support
11.02 iOS client October 10, 2016 19666 Multilingual (Japanese, French, Italian, German, and Spanish) support; iOS 10 is required
 
11.03 Windows client October 17, 2016 19822 Maintenance release (MOB-9771, MOB-9666)
11.03 Server October 17, 2016 19822 Maintenance release (MOB-9687, MOB-9755)
11.03 iOS client October 28, 2016 20378 Diagnostics compatibility.
 
11.04 Server November 22, 2016 21384 Support for Windows Server 2016, policy issue fix (MOB-9892)
11.04 Windows client November 22, 2016 21384 Maintenance release (MOB-9894, MOB-9805)
11.04 macOS client November 22, 2016 21579 Maintenance release (MOB-9894, MOB-9805)
11.04 iOS client November 23, 2016 21379 Maintenance release (MOB-9894, MOB-9805)
11.04 Android client November 22, 2016 21376 Maintenance release (MOB-9894, MOB-9805)
11.04 Windows client December 8, 2016 22344 Maintenance release (MOB-10020)
11.04.01 iOS client January 24, 2017 23750 Maintenance release (MOB-9969)
11.04 Windows client February 13, 2017 25554 Bug fixes (MOB-10290).
 
11.05 Windows client April 3, 2017 27233 Bug fixes (MOB-10420, MOB-10459).
11.05 iOS client June 7, 2017 31089 Improved integration with NetMotion Diagnostics; minor bug fixes.
11.06 iOS client June 16, 2017 31657 Minor bug fixes (MOB-11003).
11.06 Windows client August 18, 2017 04461 Bug fixes:
MOB-11376—Failure to load drivers on some Windows 10 systems
MOB-11337—Timeout of video uploads using Coban application (client fix)
 
11.30 Android client August 10, 2017 04151 The user interface and functionality of the Android client has improved dramatically in this release; for a list of changes, see What's New in NetMotion Mobility.
11.30 Server
Windows client
September 29, 2017 7087
7299 (Windows Server 2016 only)
Includes support for publishing Mobility client and server data to a log management server, such as Splunk or NetMotion Mobile IQ (see What's New in NetMotion Mobility), and the fix for MOB-11337 on the Mobility server.
11.31 Server and Windows client November 15, 2017 9670 Bug fixes (MOB-11657, MOB-11676, MOB-11728, MOB-11750, MOB-11770). In addition, we now use consistent identification of users and devices when both Mobility and Diagnostics are publishing data to a common system.
11.31 iOS client November 14, 2017 9670 We now use consistent identification of users and devices when both Mobility and Diagnostics are publishing data to a common system.
11.31 Android client November 17, 2017 9670 We now use consistent identification of users and devices when both Mobility and Diagnostics are publishing data to a common system.
11.32 Android client December 12, 2017 11185 Minor bug fixes.
11.32 Windows client January 17, 2018 12223 Fix Windows 10 forward compatibility issue (MOB-11980)
11.40 Server and Windows client April 18, 2018 18434 Support for DSCP-tagged network traffic, FIPS change management during a server upgrade, iOS client for supervised (DEP) devices, and bug fixes. See What's New in NetMotion Mobility for details.
11.40 Windows client May 10, 2018 19423 Fix for MOB-12485. Installing or upgrading to Mobility v11.40 (build 18434) on a Windows 7 (32-bit or 64-bit) computer running security software resulted in an operating system crash.
11.41 Windows client June 29, 2018 21761 Fixes for MOB-12519, MOB-12503, MOB-12421, and MOB-9477.
11.41 iOS and macOS clients August 6, 2018 23686 Fixes for MOB-12806, MOB-12783, and MOB-12676.
11.41 Android client August 27, 2018 25571 Fix for MOB-12740.
11.42 Windows client September 14, 2018 26303 Fixes for MOB-12853 and MOB-12969.
11.43 Windows client October 15, 2018 28150 Fix for MOB-13108.