Skip to main content
Skip table of contents

How to deploy enterprise licenses on your managed Apple Vision Pro devices

Overview

Innoactive Spatial supports automatic enterprise configuration deployment through Mobile Device Management (MDM) systems. This guide explains how to deploy enterprise licenses to your organization's devices.

Configuration File Formats

Enterprise configurations are provided in one of two file formats:

  • .innoactiveconfiguration - Current format (recommended)

  • .innoactivelicense - Legacy format (still supported)

Both formats contain:

  • Encrypted license key

  • Organization details

  • Feature entitlements

  • Expiration date

  • Maximum concurrent users

Deployment Methods

Method 1: Documents Directory Deployment (Recommended for MDM)

This method allows MDM systems to deploy configuration files after app installation.

Location: App's Documents directory

Steps:

  1. Receive your enterprise configuration file from Innoactive (.innoactiveconfiguration or .innoactivelicense)

  2. Configure your MDM to deploy the file to the app's Documents directory

  3. The app will automatically detect and import the configuration on next launch

MDM Configuration Examples:

Jamf Pro

  1. Navigate to Computers > Configuration Profiles (or Mobile Devices for Vision Pro)

  2. Create a new profile or edit existing

  3. Add Custom Settings payload

  4. Upload your configuration file

  5. Set deployment path to app's Documents directory

  6. Assign to target devices

Microsoft Intune

  1. Go to Apps > App configuration policies

  2. Create new policy for managed apps

  3. Add custom configuration

  4. Upload .innoactiveconfiguration or .innoactivelicense file

  5. Target deployment to device groups

VMware Workspace ONE

  1. Navigate to Apps & Books > Applications

  2. Select Innoactive Portal

  3. Go to Files/Actions tab

  4. Upload configuration file

  5. Set deployment to Documents directory

  6. Save and push to devices

Method 2: Custom IPA Distribution

This method embeds the configuration file directly in the app bundle during distribution.

Use Case: Pre-configured app packages for enterprise distribution

Steps:

  1. Obtain your configuration file from Innoactive

  2. Add the file to your custom IPA build

  3. Distribute the custom IPA through your MDM

  4. Configuration activates automatically on first launch

Creating a Custom IPA:

CODE 
# 1. Extract existing IPA
unzip InnoactivePortal.ipa -d portal_app

# 2. Add configuration file
cp YourOrganization.innoactivelicense portal_app/Payload/InnoactiveSpatial.app/

# 3. Re-package IPA
cd portal_app
zip -r ../InnoactivePortal_Enterprise.ipa Payload/

Important: Custom IPAs must be code-signed with your enterprise certificate.

Method 3: Manual Import (For Testing)

Users can manually import configuration files through the app interface.

Steps:

  1. Email configuration file to user or share via AirDrop

  2. User opens Innoactive Portal

  3. Navigate to Settings > Enterprise Configuration

  4. Tap Choose Configuration File or Paste Configuration from Clipboard

  5. Select the configuration file

  6. Configuration activates immediately

Supported Import Methods:

  • Clipboard: Copy entire JSON configuration or just the license key

  • File Picker: Select .innoactiveconfiguration or .innoactivelicense file

  • AirDrop: Direct transfer from another device

  • Email Attachments: Open configuration files from Apple Mail

Automatic Detection Behavior

The app searches for configuration files in this priority order:

  1. Documents Directory (checked first)

    • Searched on every app launch if unlicensed

    • Allows dynamic MDM deployment

  2. App Bundle (fallback)

    • Checked if no file found in Documents

    • For pre-bundled configurations

File Detection:

  • Any file with .innoactiveconfiguration extension is detected (newer format preferred)

  • Falls back to .innoactivelicense if no .innoactiveconfiguration found

  • Filename doesn't matter - extension is the key identifier

Configuration Persistence

Once imported, configurations are stored securely in the device's Keychain:

  • Secure Storage: Encrypted in iOS/visionOS Keychain

  • Persists: Across app updates and device restarts

  • Removal: Only through app settings or device wipe

  • No Re-import: Once activated, won't re-import on subsequent launches

Verification & Troubleshooting

Verify Successful Deployment

After deployment, verify the configuration is active:

  1. Open Innoactive Portal

  2. Go to Settings > Enterprise Configuration

  3. Check status shows: "Enterprise configuration valid"

  4. Verify organization name and details match

Configuration States

State

Icon

Description

Unlicensed

⚠️

No configuration imported

Licensed

✅

Valid configuration active

Grace Period

⏰

Configuration expired, grace period active (30 days)

Expired

❌

Grace period ended, new configuration required

Over Limit

⚠️

More users than license allows

Common Issues

Configuration Not Detected

Symptoms: App shows as unlicensed after deployment

Solutions:

  1. Verify file extension is .innoactiveconfiguration or .innoactivelicense

  2. Check file was deployed to Documents directory, not a subdirectory

  3. Ensure app has been restarted after MDM deployment

  4. Check MDM deployment logs for errors

  5. Verify file is valid JSON (open in text editor)

Check File Location (via device):

  • Open Files app

  • Navigate to On My Vision Pro > Innoactive Portal

  • Configuration file should be visible

Invalid Configuration Error

Symptoms: Import fails with "Invalid configuration format"

Causes:

  • Corrupted file during transfer

  • Wrong file type (.license files not supported)

  • Modified or tampered configuration

  • Public key mismatch

Solutions:

  1. Re-download configuration file from Innoactive

  2. Ensure file is .innoactiveconfiguration or .innoactivelicense, not .license

  3. Don't edit the file contents

  4. Verify file size matches original (should be ~1-2 KB)

Signature Verification Failed

Symptoms: "Configuration signature verification failed"

Cause: File contents were modified or corrupted

Solution: Obtain a fresh configuration file from Innoactive Support

Enable Debug Logging

To troubleshoot deployment issues:

  1. Open Innoactive Portal

  2. Go to Settings > Advanced

  3. Enable Debug Mode

  4. Restart app

  5. Check logs in Settings > Logs

Key Log Entries:

CODE 
🔑 Checking Documents directory for configuration files...
🔑 Found .innoactiveconfiguration in Documents: YourFile.innoactiveconfiguration
🔑 Successfully decoded as UTF-8
🔑 Public keys match: true
🔑 ✅ Successfully auto-imported enterprise configuration
🔑 License ID: LIC-XXXXXXXX, Organization: YourOrg

Best Practices

For IT Administrators

  1. Test First: Deploy to test device before organization-wide rollout

  2. Name Consistently: Use descriptive filenames (e.g., CompanyName_Dept_LIC-ID.innoactiveconfiguration)

  3. Track Expiration: Monitor configuration expiry dates

  4. Plan Renewal: Request new configurations 30 days before expiry

  5. Document Process: Keep internal documentation of your deployment method

  6. Backup Files: Store configuration files securely for future deployments

Security Considerations

  • Configuration files contain signed licenses but no secrets

  • Files can be safely stored on MDM servers

  • Public sharing of configuration files should be avoided (enables unauthorized use)

  • Revoke compromised configurations immediately through Innoactive Support

Capacity Planning

  • Each configuration specifies maximum concurrent users

  • Monitor usage in app analytics

  • Request increased capacity before limits are reached

  • Over-limit warnings appear 10% before maximum

Configuration File Structure

For reference, configuration files are JSON with this structure:

CODE 
{
  "fileType": "PORTAL_CONFIGURATION",
  "version": "1.0",
  "licenseKey": "[signed-license-data]",
  "metadata": {
    "description": "Portal Configuration for [Organization]",
    "generatedAt": "2026-02-13T16:36:34Z",
    "generatorVersion": "1.0"
  },
  "payload": {
    "licenseId": "LIC-XXXXXXXX-XXXXXXXX",
    "licensee": {
      "org": "Your Organization",
      "department": "Department Name"
    },
    "maxConcurrent": 50,
    "issuedAt": "2026-02-13T16:36:34Z",
    "expiresAt": "2027-02-13T16:36:34Z",
    "features": ["vred", "collaboration", "object-tracking"]
  },
  "publicKey": "[public-key-for-verification]"
}

Do not modify any fields in the configuration file - changes will cause signature verification to fail.

Support & Renewals

Request New Configuration

To obtain an enterprise configuration:

  1. Visit: Enterprise Configuration Request Form

  2. Fill out organization details

  3. Specify required features and concurrent users

  4. Submit request

Processing time: Typically 1-2 business days

Renew Existing Configuration

Configurations have expiration dates. To renew:

  1. Contact Innoactive Support 30 days before expiration

  2. Provide current license ID (found in app settings)

  3. Confirm user count requirements

  4. Receive renewed configuration file

  5. Deploy using same method as original

Grace Period: 30-day grace period after expiration allows continued use while renewing

Technical Support

For deployment assistance:

Appendix: Supported MDM Systems

Innoactive Portal enterprise configuration deployment is compatible with:

  • Jamf Pro

  • Microsoft Intune

  • VMware Workspace ONE

  • Cisco Meraki Systems Manager

  • IBM MaaS360

  • Citrix Endpoint Management

  • MobileIron (Ivanti)

  • Any MDM supporting custom file deployment

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.

Contact Support Close