Deploying configuration files

If MAC is not feasible, companies may deploy the configuration files by emailing them to the users. These files contain the same information as MAC, but are text files with the .immconfig file extension. If a device receives configurations through both MAC and an .immconfig file, an order of precedence is applied. MAC always takes precedence over immconfig files. This is a security feature to prevent users from manually crafting their own immconfig file to bypass company app enforcement from MAC. If a firm switched from immconfig files to MAC, the managed app configuration file overwrites the previous immconfig settings.

The immconfig file is a way of configuring users’ applications outside the MDM. All the users must use this file before they start using iManage Work Mobility for iOS. The immconfig file contains all the necessary configuration files. The file is emailed to users, who then open this file (named 'iMan Work') on their iOS devices. When the application receives this file, it applies the configuration. The same immconfig file can be used for all users, or different configurations can be sent to different users.
If deploying through MDM, the same information in the immconfig file is fed into MAC. One of the limitations of MAC is that all the users will have the same configuration.

IMPORTANT:

The immconfig must be replaced with your entries and all the sample entries must be removed. For additional details on each of the fields, see iManage Work Mobility for iOS.

Following is a sample file for iManage Work Mobility.immconfig:

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
         <key>version</key>
         <integer>1</integer>
         <key>server0_uuid</key>
         <string>11caf952-9111-45c5-8914-145fb19e4ce1</string>
         <key>server0_name</key>
         <string>Server 0 Name</string>
         <key>server0_auth</key>
         <integer>0</integer>
         <key>server0_url</key>
         <string>server0.yourcompany.com</string>
         <key>server1_uuid</key>
         <string>ec740280-dc8b-4e67-a094-a25dba5918a2</string>
         <key>server1_name</key>
         <string>Server 1 Name</string>
         <key>server1_auth</key>
         <integer>0</integer>
         <key>server1_url</key>
         <string>server1.acme.com</string>
         <key>server2_uuid</key>
         <string>22caf952-9111-45c5-8914-145fb19e4ce1</string>
         <key>server2_name</key>
         <string>Server 2 Name</string>
         <key>server2_auth</key>
         <integer>0</integer>
         <key>server2_url</key>
         <string>server2.whitehouse.gov</string>
         <key>open_in_receive</key>
         <true/>
         <key>open_in_send</key>
         <true/>
         <key>enable_native_email</key>
         <true/>
         <key>enable_app_extensions</key>
         <true/>
         <key>enable_airdrop</key>
         <true/>
         <key>enable_printing</key>
         <true/>
         <key>enable_downloading</key>
         <true/>
         <key>enable_privacy_curtain</key>
         <true/>
         <key>relax_ssl_certificate_verification</key>
         <false/>
         <key>login_user_account_auth0_only</key>
         <string>exampleDomain/{{UserID}}</string>
         <key>show_demo_connection</key>
         <true/>
         <key>enable_touch_id_for_passcode</key>
         <true/>
         <key>number_of_passcode_retries_min_3_max_20_default_10</key>
         <integer>10</integer>
         <key>passcode_grace_period_seconds_min_10_max_999999999_default_60</key>
         <integer>10</integer>
</dict>
</plist>

NOTE:

The login_user_account_auth0_only setting is optional.