PowerSyncPro Migration Agent Deployment Guide

This guide outlines the recommended and supported methods for deploying the PowerSyncPro Migration Agent (PSPMigrationAgentInstaller.msi) across enterprise environments.

PowerSyncPro supports multiple deployment methods:

• Microsoft Intune (Line-of-Business MSI App) – Recommended
• Microsoft Configuration Manager (SCCM/MECM)
• Active Directory Group Policy (GPO) using MST transforms
• PDQ Deploy / RMM Platforms / PowerShell Automation
• Manual or Technician-Assisted Installation

The installer accepts configuration values via:

• MSI public properties – recommended for all platforms except GPO
• MST transform files – required for GPO deployments

Deployment Method Decision Guide

1. Recommended Method: Microsoft Intune (Line-of-Business MSI App)

Deploying the PowerSyncPro Migration Agent through Microsoft Intune as a Line-of-Business (LoB) App is the preferred and simplest method.

LoB apps support MSI command-line arguments, enabling PowerSyncPro-specific configuration during installation.

1.1 Required MSI Properties

PowerSyncPro requires two MSI properties:

• PSK — Pre-shared key generated by your PSP server
• URL — PowerSyncPro Agent registration endpoint

Verbose MSI logging is strongly recommended.

Recommended Intune Command-Line Arguments:

PSK="<your_psk>" URL="https://<your_psp_server>/Agent" /qn /L*V "C:\Temp\PSP-Agent-Install.log"

Notes:

• Do not include msiexec /i — Intune handles this automatically.
• Ensure C:\Temp exists on the target systems (or change the logging path, e.g. C:\Windows\Temp).

1.2 Intune Deployment Instructions

• In the Intune Admin Center, go to:
  Apps → Windows → Create→ Line-of-Business app
• Upload PSPMigrationAgentInstaller.msi.
• Enter application metadata (Name, Description, Publisher, etc.).
• In Command-line arguments, input:

PSK="<your_psk>" URL="https://<your_psp_server>/Agent" /qn /L*V "C:\Temp\PSP-Agent-Install.log"

• Assign the app to your desired device groups.
• Monitor installation status under Apps → Monitor → Device install status.

1.3 Intune Notes & Best Practices

• Always target devices, not users.
• Use pilot rings or test groups before broad rollout.
• Verify outbound network access to your PSP server.
• Use the MSI log (C:\Temp\PSP-Agent-Install.log) and Intune’s app reporting for troubleshooting.

2. Microsoft Configuration Manager (SCCM/MECM)

SCCM/MECM is suitable for traditional AD-managed or hybrid environments and supports MSI deployments with configuration properties.

Recommended SCCM Install Command:

msiexec /i "PSPMigrationAgentInstaller.msi" /qn PSK="<psk>" URL="https://<server>/Agent" /L*V "C:\Temp\PSP-Agent-Install.log"

SCCM Best Practices

• Use the Application model to leverage detection rules and rich reporting.
• Deploy first to a pilot collection before broad rollout.
• Ensure content is distributed to all required Distribution Points.
• Confirm that devices can reach the PowerSyncPro Agent endpoint (/Agent) during and after installation.

3. Group Policy (GPO) Deployment

Active Directory Group Policy (GPO) Software Installation is supported but has several limitations.  We highly recommend using this as the method of last resort.

GPO cannot pass MSI command-line parameters, so a custom MST transform is required to inject configuration values (PSK and URL). PowerSyncPro provides a script to automate MST creation.

3.1 GPO Deployment Limitations

GPO Software Installation is subject to several constraints:

GPO is best suited for traditional on-prem AD environments with consistent wired or pre-logon VPN connectivity.

3.2 MST Generation Script

The MST generation PowerShell script:

• Clones the MSI
• Injects PSK and URL values
• Generates a GPO-ready MST file
• Ensures proper encoding and version matching

Script Download:
Available on our GitHub: https://github.com/PowerSyncPro/MigrationAgent/blob/main/PSP-CreateMST.ps1

3.3 Using the MST Script

Example usage:

.\PSP-CreateMST.ps1 `
    -MSIPath "C:\Temp\PSPMigrationAgentInstaller.msi" `
    -PSKValue "<your_psk>" `
    -URLValue "https://<server>/Agent"

Script output (In the same directory as the MSI):

PSPMigrationAgentInstaller-AutoInject.mst

This MST file is used in the GPO Software Installation package.

3.4 Creating & Assigning the GPO

Step 1 — Prepare the Deployment Share

Use a UNC path reachable by computer accounts, for example:

\\corp.local\software\PowerSyncPro\

Place the following files in this directory:

• PSPMigrationAgentInstaller.msi
• PSPMigrationAgentInstaller-AutoInject.mst

Ensure Domain Computers have at least Read permissions.

Step 2 — Create the GPO

• Open Group Policy Management Console (GPMC).
• Right-click the target OU.
• Select Create a GPO in this domain, and Link it here….
• Name it, for example: "PowerSyncPro Migration Agent Deployment"

Step 3 — Edit the GPO

In the GPO Editor, navigate to:

Computer Configuration
   → Policies
      → Software Settings
         → Software Installation

• Right-click Software Installation → New → Package.

• Select the MSI via UNC path (do not use a mapped drive).
• Choose Advanced when prompted.

• Go to the Modifications tab.
• Click Add… and select:

PSPMigrationAgentInstaller-AutoInject.mst

• Confirm that the MST appears in the Modifications list.

Step 4 — Apply the GPO

• Ensure the GPO is linked to the correct OU.
• Confirm Security Filtering includes the target computers (or a suitable security group containing them).

Step 5 — Force Group Policy Update (Optional)

On a test machine, you can refresh policies with:

gpupdate /force

Note: This does not trigger the MSI installation immediately; installation occurs only at next reboot.

Step 6 — Reboot Devices

At startup:

• The device processes the GPO.
• The MSI installs with the MST transform applied.
• PowerSyncPro agent configuration is injected.
• Once the installation completes, the machine should appear in your PSP console under Agents.

4. PDQ / RMM / PowerShell Deployment

This method is ideal for:

• Mixed AD + Intune environments
• MSPs managing distributed fleets
• Remote or roaming endpoints

These platforms ultimately run msiexec with PowerSyncPro configuration parameters.

4.1 Recommended MSI Command

msiexec /i "PSPMigrationAgentInstaller.msi" /qn PSK="<psk>" URL="https://<server>/Agent" /L*V "C:\Temp\PSP-Agent-Install.log"

4.2 PowerShell Installation Script Template

Use the following PowerShell script as a standard template for PDQ, RMM platforms, scheduled tasks, or manual execution.

# ===============================================================
# PowerSyncPro Migration Agent Installation Script
# ===============================================================

# Ensure log directory exists
if (-not (Test-Path "C:\Temp")) { New-Item -Path "C:\Temp" -ItemType Directory | Out-Null }

# Transcript Logging
$LogName = "PSP-Install.log"
$LogPath = "C:\Temp\$LogName"
Start-Transcript -Append -Path $LogPath

# -------------------------
# Configuration Placeholders
# -------------------------

# Path to the MSI (local or UNC)
$MsiPath  = 'PSPMigrationAgentInstaller.msi'   # <-- Update if needed

# PowerSyncPro Pre-Shared Key
$PSK      = '<INSERT_PSK_HERE>'               # <-- Replace with actual PSK

# PowerSyncPro Agent URL
$AgentURL = 'https://<YOUR_PSP_SERVER>/Agent' # <-- Replace with actual Agent URL

# -------------------------
# Build MSI Argument List
# -------------------------

$Arguments = @(
    '/i'
    "`"$MsiPath`""
    "PSK=`"$PSK`""
    "URL=`"$AgentURL`""
    '/quiet'
    '/L*V'
    '"C:\Temp\PSP-Agent-Install.log"'
)

Write-Host "Starting PowerSyncPro Migration Agent installation..."
Write-Host "Arguments: $Arguments"

# -------------------------
# Execute Installer
# -------------------------

$Process = Start-Process -FilePath 'msiexec.exe' -ArgumentList $Arguments -Wait -PassThru

Write-Host "PSP Migration Agent installer exited with code: $($Process.ExitCode)"

Stop-Transcript

4.3 Usage Scenarios

PDQ Deploy

• Create a new PDQ package.
• Add a PowerShell step and paste the script.
• Place the MSI in the same package directory or reference a UNC path.
• Run as Local System.
• Review PDQ output and the logs in C:\Temp.

RMM Tools (NinjaOne, Automate, Atera, Kaseya, N-Central, etc.)

• Upload or paste the script into the RMM script module.
• Upload the MSI to the RMM file repository or download it via the script.
• Ensure <INSERT_PSK_HERE> and <YOUR_PSP_SERVER> are updated or pulled from secure variables.
• Run the script as SYSTEM for reliable installation.

Manual / War-Room Deployment

• Copy the script and MSI to the device or a shared location.
• Open PowerShell as Administrator.
• Update PSK and URL values.
• Run the script to install the agent and log output to C:\Temp.

5. Best Practices

Logging

Enable MSI verbose logging on all installations:

/L*V "C:\Temp\PSP-Agent-Install.log"

Use transcript logging in scripts (as shown in the PowerShell template) for full command and error visibility.

Network Requirements

All devices must be able to reach:

https://<psp-server>/Agent

In order to register against the PowerSyncPro Server.

Ensure firewalls, proxies, and SSL inspection tools allow this traffic.

If using SSL for Migration Agent to Server communication, the certificate used on the server must be trusted by the endpoint.  If the certificate is not trusted you will see errors in the Application Event Viewer when the agent installs.

Security

• Rotate PSKs regularly based on your organization’s security policies.
• Avoid embedding long-lived credentials or sensitive information in scripts or MST files.
• Use dedicated or segmented networks for large-scale “war room” migration events when possible.

Upgrades

• Intune LoB → Upload the new MSI and configure supercedence/assignments as required.
• SCCM → Update the Application’s Deployment Type to use the new MSI.
• GPO → Regenerate the MST with the new MSI version using the same MST script. Replace the existing MSI / MST in the GPO with the new versions per instructions above.
• PDQ / RMM / PowerShell Deployment -→ Update the MSI included with the script and run.  The MSI will handle updating the agent present on the system.