E3 Application - MDM Deployment Guide for Microsoft Intune

This guide provides instructions for deploying the E3 Application via Microsoft Intune as a Line-of-Business (LoB) app.

Microsoft Intune: https://www.microsoft.com/en-us/security/business/microsoft-intune
E3 Application MSI: https://e3-apps.s3.us-west-2.amazonaws.com/Emergent3+4.0.0.msi

---

Deployment Steps

1. Navigate to Apps in Intune

In the Microsoft Intune admin center, go to:
Apps > Windows

2. Create a New App

• Click on Create

3. Select App Type

• From the Select app type dropdown, choose Line-of-business app
• Click Select

4. Upload App Package File

• Click on Select app package file
• Click the folder icon to browse for your application package
• Upload the E3Application.msi file
• Once uploaded, click OK

5. Configure App Information

In the App information section, enter the following:

• Name: Emergent3
• Description: Emergent3
• Publisher: Emergent3

In the Command-line arguments field, enter:
/quiet /norestart /l*v "C:\ProgramData\Logs\E3_install.log"

Click Next

6. Configure Assignments

In the Assignments tab, define how the app will be distributed:

• Required: The app will be automatically installed for assigned users/devices
• Available for enrolled devices: Users can install the app from the Company Portal
• Uninstall: The app will be removed from assigned users/devices if already installed

Configure assignments according to your organization’s needs.
Click Next

7. Review and Create

In the Review + Create tab:

• Review all settings
• Verify app information and command-line arguments
• If everything is correct, click Create

---

Installation Parameters

• /quiet – Silent installation (no user interaction)
• /norestart – Prevents automatic restart
• /l*v – Creates a detailed installation log

---

Common Installation Issues

Issue 1: Installation Fails with Error 1603

Symptoms: Generic installation failure
Solutions:

• Check installation log for specific error details
• Ensure the device has at least 500MB of free disk space
  
  

Verify Windows Installer service is running:
sc query msiserver  

sc start msiserver

• Run installation with elevated privileges
  
  

Clear Windows Installer cache:

%windir%\system32\msiexec.exe /unregister  

%windir%\system32\msiexec.exe /regserver

---

Issue 2: Error 1618 - Another Installation in Progress

Symptoms: Installation blocked by another installer
Solutions:

• Wait for other installations to complete

Restart Windows Installer service:

net stop msiserver  

net start msiserver

• Check for stuck installer processes in Task Manager
• Reboot the device if needed
  
  

---

Issue 3: Error 1639 - Invalid Command Line Argument

Symptoms: Incorrect msiexec parameters
Solutions:

• Verify command line syntax

Use the correct format:

msiexec /i "path\to\file.msi" /quiet

• Ensure file path has no special characters
• Enclose file paths with spaces in quotes
  
  

---

Issue 4: Application Not Starting After Installation

Symptoms: Installation succeeds, but the app does not launch
Solutions:

• Check Windows Event Viewer for app errors
• Verify all dependencies are installed:
  
  
  • .NET Framework (version X.X)
  • Visual C++ Redistributables
  • Windows Updates
  • Run the app once as administrator:
    
    runas /user:Administrator "C:\Program Files\E3Application\E3App.exe"
• Check antivirus exclusions

---

Issue 5: Add the Application to Windows Startup

Symptoms: Installation succeeds, but the app does not launch when Windows is started
Solutions: To launch the E3 Application automatically on user login, follow these steps:

Using Task Manager:

1. Right-click on the Start button and select Task Manager
2. Go to the Startup tab
3. If the E3 Application appears in the list:
   • Right-click it and click Enable
4. If it does not appear:
   • Click Run new task
   • Select the E3 Application
   • Click Ok

Note: The default path to E3 Application is “C:\Program Files\Emergent3\Emergent3.exe”.

This ensures the E3 Application will launch automatically every time the user logs in.

---

Pre-Installation Requirements

System Requirements

• Windows 10/11 (64-bit)
• Minimum 4GB RAM
• Minimum 500MB free disk space
• Administrator privileges
• Active internet connection (for license validation)

---

Deploying the Uninstall Script via Microsoft Intune

To deploy the above script using Microsoft Intune:

Step 1: Save the Script File

1. Open Notepad or any text editor.
2. Paste the script into the file:

Get-WmiObject -Class Win32_Product | Where-Object { $_.Name -eq "Emergent3" } | ForEach-Object {

    $_.Uninstall()

}

Save the file with the extension .ps1, for example: Uninstall-Emergent3.ps1

 Ensure the file is saved with a .ps1 extension, not .txt.

---

Step 2: Upload to Intune

1. Open the Microsoft Intune Admin Center.
2. Navigate to:
   Devices > Scripts and remediations > Add > Windows 10 and later > PowerShell
3. Upload the .ps1 script you created.
4. Configure the script settings:
   
   
   • Run this script using the logged on credentials: No
   • Enforce script signature check: No
   • Run script in 64-bit PowerShell Host: Yes
5. Assign the script to the target device group(s).
6. • Review and finish the deployment.

     The script will be executed on the assigned devices the next time they check in with Intune (usually within a few hours).

 

---

Need more help?

💬 Chat with us.

Click the blue icon on the bottom-right corner of this page to send us a chat.

✉️ Email us.

You can also send us an email at help@emergent3.com.