Updated 02/10/2025
Overview
This guide provides step-by-step instructions on:
- Wrapping the Liquidware ProfileUnity Client into an Intune Win32 package.
- Editing and Wrapping the Configuration PowerShell Script.
- Deploying ProfileUnity, the Runtime Package, and the Configuration Script in Intune while ensuring proper dependencies.
Step 1: Wrapping ProfileUnity Client into an Intune Win32 Package
Before proceeding, ensure you have the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe).
1.1 Prepare Installation Files
- Download the ProfileUnity Client installer from Liquidware.
- Create a folder, e.g., C:\Intune\ProfileUnity.
- Extract the ProfileUnity client installer into the new folder.
1.2 Create the IntuneWin Package
- Download IntuneWinAppUtil.exe from Microsoft.
- Open Command Prompt as Administrator and run:
cd C:\IntuneWinAppUtil
IntuneWinAppUtil.exe -c C:\Intune\ProfileUnity -s LwL.ProfileUnity.Client.Startup.exe -o C:\IntuneWinPackages
This creates a ProfileUnity.intunewin file.
Step 2: Editing and Wrapping the Configuration PowerShell Script
To ensure ProfileUnity is properly configured, we deploy a PowerShell script.
2.1 Create the Configuration Script
- Inside the ConfigureOnly_ProU_v4.ps1 make sure you fill in (at least these 3 fields):
$UserINIPath = "\\some.server\somewhere\ProfileUnity or AZ://blob/folder"
$LicenseServerConnectionString = ""
*Available in Administration, Client Settings section, Manage Connection Strings button, Copy to clipboard button
$AzureStorageCredentials = ""
See for reference: https://docs.liquidware.com/profileunity/en-us/687/using-cloud-storage/azure-blob.htm
2.2 Convert Script into IntuneWin
- Create a folder, e.g., C:\Intune\ProfileUnityConfig.
- Place ConfigureOnly_ProU_v4.ps1 inside the folder.
- Run:
IntuneWinAppUtil.exe -c C:\Intune\ProfileUnityConfig -s ConfigureOnly_ProU_v4.ps1 -o C:\IntuneWinPackages
This creates ProfileUnityConfig.intunewin.
2.3.1 Prepare the Runtime Installer
- Download the Runtime Installer from Liquidware.
- Create a new folder, e.g., C:\Intune\RuntimeInstaller.
- Place RuntimeInstaller-<version>.exe inside the folder.
2.3.2 Convert Runtime Installer to an IntuneWin Package
- Open Command Prompt as Administrator and run:
cd C:\IntuneWinAppUtil
IntuneWinAppUtil.exe -c C:\Intune\FlexAppRuntime -s RuntimeInstaller-<version>.exe -o C:\IntuneWinPackages
This generates RuntimeInstaller.intunewin.
Step 3: Deploying in Intune
Now, we deploy:
- FlexApp Runtime (FlexAppRuntime.intunewin).
- ProfileUnity Client (ProfileUnity.intunewin).
- Configuration Script (ProfileUnityConfig.intunewin).
3.1 Deploy FlexApp Runtime
- Open Microsoft Intune Admin Center.
- Navigate to Apps > Windows > Add.
- Select App Type: Windows app (Win32) and upload FlexAppRuntime.intunewin.
- Set Install Command:
RuntimeInstaller-1.7.0.exe -d -l c:\ProgramData\Liquidware\Customization\runtime.log -q
- Set Detection Rules:
- Rule Type: File Exists
- Path: c:\ProgramData\Liquidware\Customization\
- File: runtime.log
- Click Next and Assign the app to devices.
3.2 Deploy ProfileUnity Client
- Repeat steps from 3.1, but upload ProfileUnity.intunewin.
- Set Install Command:
LwL.ProfileUnity.Client.Startup.exe --install
- Set Detection Rules:
- Rule Type: File Exists
- Path: C:\Program Files\ProfileUnity
- File: LwL.ProfileUnity.Client.Startup.exe
- Click Next and Assign the app to devices.
3.3 Deploy ProfileUnity Configuration
- Repeat steps from 3.1, but upload ProfileUnityConfig.intunewin.
- Use install command:
powershell.exe -ExecutionPolicy Bypass -File ProfileUnityConfig.ps1
- Set Detection Rules:
- Path: C:\Program Files\ProfileUnity
- File: ProfileUnityConfig.xml
Step 4: Setting Dependencies
-
ProfileUnity Client depends on FlexApp Runtime
- Go to "Dependencies" when deploying ProfileUnity.intunewin
- Select FlexApp Runtime as a dependency.
-
ProfileUnity Config depends on ProfileUnity Client.
- Go to "Dependencies" when deploying ProfileUnityConfig.intunewin.
- Select ProfileUnity Client as a dependency.
Final Dependency Order
- FlexApp Runtime → Install first.
- ProfileUnity Client → Dependent on FlexApp Runtime.
- Configuration Script → Dependent on ProfileUnity Client.
Conclusion
By following these steps, you ensure that:
- ProfileUnity installs correctly in Intune.
- FlexApp Runtime functions properly.
- Configuration is automatically applied.