Once you have your repackaged file, how do you get it to the unmanaged users?
Select a destination folder. SEPM will generate a standalone setup.exe or an .msi file pre-configured to run as an unmanaged endpoint. Method 2: Creating a Silent MSI Wrapper (Command Line)
Choose a target folder where the exported files will be saved.
SetupStateManagementTool.exe /configure /outputstate:"C:\Repack\setup.state"
Step 3: Repackaging the Unmanaged Client for Silent Deployment Once you have your repackaged file, how do
Method 1: Exporting an Unmanaged Package via SEPM (Recommended)
Uncheck the box that says “Pick a policy mode” or explicitly select Unmanaged if prompted by your specific SEPM version. This ensures the installer does not look for a parent management server.
Click to build your custom repackaged file (e.g., SEP_Unmanaged_Repack.exe ). Distributing and Downloading the Repack
: Under Installation Features and Settings , choose which security modules to include (e.g., Core Protection, Network Threat Protection). You can also choose to include virus definitions directly in the package to save bandwidth on the first run. Method 2: Creating a Silent MSI Wrapper (Command
Place this custom policy XML file into the installation folder of your repackaged source files, renaming it to match the default policy import name specified in the deployment manual for your specific SEP version. Compressing into a Self-Extracting Executable
If you have a legitimate license, do not search for a shady download. Create your own repack in 20 minutes.
Older networks that have decommissioned their SEP Management Server but still have valid licenses for the clients. To keep desktops protected without spinning up a full Windows Server VM for SEPM, administrators repack the client into an unmanaged configuration.
When creating your repack, ensure the sylink.xml or license file is placed in the root of the installation directory, or script the install to inject the license key via the command line: Click to build your custom repackaged file (e
You can use standard compression tools like WinRAR or built-in Windows deployment tools like IExpress to create a Self-Extracting Archive (SFX). Open your preferred SFX creation tool (e.g., WinRAR).
: Use a utility like 7-Zip or WinRAR to extract the downloaded master .zip file to a temporary folder on your local drive.
Locate the raw Windows installation files (usually containing Sep64.msi , setup.exe , and a series of .cab data files).
The full software package contains configurations for both infrastructure servers and client endpoints. You must isolate the raw unmanaged client installer.
Generate an MD5 or SHA-256 checksum of the final repackaged executable. Provide this hash alongside the download link so deployment teams can verify the package integrity before execution.