Advantages with MDM

Using an MDM to deploy and configure PowerMic Mobile provides the following solutions:

• Site administrators can centrally manage shared devices, including deploying and configuring PowerMic Mobile. This means that the site administrator or end user does not have to install PowerMic Mobile from the App Store or Google Play. New devices can be set up quickly.
• The configuration URLs are loaded via the MDM. The user does not need to access the configuration URLs and does not need to understand how to use them; this reduces the amount of time needed for training and administration tasks.
• Removes the risk that the web browser or email client renders the configuration URLs incorrectly.
• Site administrators can conform to security standards by controlling which apps are installed on managed devices and how the apps are configured.

Deploying PowerMic Mobile via MDM

AppConfig standard

PowerMic Mobile supports MDM configuration via the AppConfig standard (appconfig.org). Most major MDM vendors have adopted the AppConfig standard, including VMware AirWatch, MobileIron, Cisco Meraki and Sophos. If your MDM does not belong to AppConfig, it might still be possible to use the PowerMic Mobile MDM configuration file with your MDM or to extract the configuration elements from the XML file and load them into your MDM. For more information, see the documentation provided by your MDM vendor.

Software requirements

PowerMic Mobile

• Version 4.0 and higher.

• You will need access to the PowerMic Mobile apps available in the App Store and Google Play. Search for these apps from your MDM solution:

  iOS: https://apps.apple.com/us/app/powermic-mobile/id983002170?ls=1

   

  Android: https://play.google.com/store/apps/details?id=com.Nuance.Mobility.DMic.Live&hl=en

iOS

• iOS version 9.3.5 or higher.

• The device must be enrolled with Apple's MDM protocol.

• PowerMic Mobile must be provisioned and installed via Enterprise Mobile Management for the PowerMic Mobile configuration values to take effect.

  For more information, see: https://www.appconfig.org/ios/

Android

• Android version 6.0 or higher.

• Devices must be enrolled in Android for Work.

• The PMM app must be provisioned and installed via Enterprise Mobile Management for the PowerMic Mobile configuration values to be applied. Use an MDM solution to push Android for Work public applications to devices. This process includes adding and approving applications for integration between your MDM solution and Android for Work from the Google Play Store which can be accessed from your MDM solution.

  For more information, see: https://www.appconfig.org/android/

MDM configuration file

You will need an edited version of the MDM configuration file. Copy the sample XML at the end of this page to a text editor, modify the values for the PMMConfigurationName and PMMConfigurationURL parameters within the <dict> element and save the file with a .XML file extension.

• PMMConfigurationURL: The configuration URL provided in the Nuance welcome letter. This parameter is required in the MDM configuration file. If the parameter value is blank or invalid, PowerMic Mobile will ignore it.
• PMMConfigurationName: The profile name that will be associated with the configuration URL. Your users will select this profile name when they log on to PowerMic Mobile. Provide a name that will be intuitive for your users, such as the name of the site or department. For example, "Main hospital" or "Pain center."

This parameter is optional. If you do not specify a value for the parameter, PowerMic Mobile will generate a profile name; for example, "Profile 1."

Note: You can define a single profile in the MDM configuration file. If your users need multiple profiles because they work with multiple NMS organizations, use the MDM file to define the profile that will be used by the majority of your users. Users who need access to additional organizations will need to add additional profiles in PowerMic Mobile via the corresponding configuration URLs. Gather the required configuration URLs from the Nuance welcome letters and then distribute them to your users via the Nuance-hosted web page or via email.

Validating a configuration URL

It might be necessary to validate your configuration URL; for example, if the URL has been edited for an on-premise deployment. Proceed as follows:

1. Make the configuration URL accessible on a mobile device where PowerMic Mobile 4.0 or higher is installed. For example, send it in an email or access it from a web page. Be aware that the configuration URL is specific to Android or iOS.
2. On the mobile device where PowerMic Mobile is installed, copy the configuration URL to the clipboard.
3. Launch PowerMic Mobile.
4. On the logon screen, tap Settings.
5. Tap Add a Profile.
6. Paste the configuration URL into the Add Profile screen.

If the URL is valid, the Valid URL message is displayed.

Deployment procedure

We use VMware AirWatch as an example MDM solution. The procedure is similar for other MDM solutions that support the AppConfig standard.

Proceed as follows:

1. Log on to VMware AirWatch.
2. In the sidebar, click Apps and Books and select List View.
3. Open the Public tab and click Add Application.
4. On the Add Application tab, select iOS or Android from the Platform list.
5. Select Search App Store, enter PowerMic Mobile in the Name field and click Next.
6. Click the PowerMic Mobile app icon in the search results.
7. Click Approve to enable distribution of the app.
8. On the Add Application tab, click Import from App Store or Import from Play and click Next.
9. Make sure PowerMic Mobile is selected in the app list and click Import.
10. Click Add Assignment and then click Save and Publish.

11. Complete the following fields in the Add Assignment dialog box:

    Assignment Groups: Select the distribution groups to which you want to assign PowerMic Mobile.

    App Delivery Method: Select Auto.

    Deployment Begins On: Select a date to start installing PowerMic Mobile.

    Managed Access: Select Enabled.

    Application Configuration: Select Enabled.

12. Click Upload XML and browse to the location where you saved the MDM configuration file.
13. Click Add.
14. Click Publish.

PowerMic Mobile will be installed on managed devices, starting on the date you specified. When your users launch PowerMic Mobile, it will already be configured with the profile defined in your MDM configuration file. To begin using PowerMic Mobile, users enter their user name and tap Log In.

Sample MDM configuration file

<managedAppConfiguration>    
    <version>1.4</version>
    <bundleId>com.nuance.mobility.dMIC</bundleId>
    <dict>
        <string keyName="PMMConfigurationName">
            <defaultValue>
                <value>Enter the profile name here</value>
            </defaultValue>
        </string>
        <string keyName="PMMConfigurationURL">
            <defaultValue>
                <value>Enter your configuration URL here</value>
            </defaultValue>
        </string>
    </dict>
    <presentation defaultLocale="en-US">
        <field keyName="PMMConfigurationName" type="input">
            <label>
                <language value="en-US">Configuration Name</language>
            </label>
            <description>
                <language value="en-US">This is the default profile name for your organization in PowerMic Mobile.</language>
            </description>
        </field>
        <field keyName="PMMConfigurationURL" type="input">
            <label>
                <language value="en-US">Configuration URL</language>
            </label>
            <description>
                <language value="en-US">This is the configuration URL to set up the profile for your organization in PowerMic Mobile.</language>
            </description>
        </field>
    </presentation>
</managedAppConfiguration>

Benefits

The Nuance custom audio channel significantly reduces the bandwidth requirements for audio transmission from the client end point to the virtual application. Nuance provides custom audio channel implementations for Citrix, VMware and RDS.

These custom audio channels are automatically installed on the server when you deploy the main Dragon Medical One application. The client components of the extensions still need to be installed on the client PC using the installation packages below.

For more information on the available audio solutions for your configuration, see Dragon Medical One Audio Routing Solutions in Virtualized Environments.

Compatibility

The Nuance virtual extensions are designed to be backward compatible from Dragon Medical One to the client end point. This means you can run newer versions of Dragon Medical One in your virtual environment and they will be compatible with older versions of their corresponding client end point extension. The following recommendations and restrictions apply:

• Compatibility for up to one year: New versions of Dragon Medical One are backward compatible with the corresponding end point virtual extensions for up to a year.
• Best practice (end point): We recommend that you update your client end point extension as soon as possible to benefit from fixes and optimizations applied to the extensions.