Deployment Editor
Developed by TUGI.CH
for Modern Endpoint Management Community
Welcome to the Deployment Editor. This application simplifies the packaging process for all Windows engineers. You can click your sequence for PSADT through the GUI and with just one simple click you get the fully automated coded PowerShell script for the deployment. The best part? It’s free and open source on GitHub!
OPEN
SOURCE
PACKAGING SOLUTION
_Visual Packaging Editor
Package Windows applications or create any task for enterprise deployment. No coding needed. 😊
Support
You like the idea of the Deployment Editor?
Every donation will go towards future development and infrastructure payments.
Thank you for your support! 😊
Video Tutorials
1. Download files
Download the archive (ZIP) containing all required files. System Requirements: Windows 10/11, 64-bit OS.
- Download the ZIP files using the [Download] button
- Unpack with Windows Explorer or 7-Zip
2. Prepare your test environment
Create a virtual machine to package
- Enable Hyper-V or use another hypervisor
- Enable Windows Sandbox
- Windows 10/11 (64-bit) is required
- Please use copy files of the production installers
3. Start the editor
Just simply run “DeploymentEditor.exe“.
- The Editor itself don’t need administrator privileges
- Generated deployment files are under PSADT license
- You can use the generated deployment files for commercial purpose
- The test project is located in the <Download>/Test folder
Latest Feature – Microsoft Intune Upload (v.2.1.0)
The latest version now finally supports direct upload to Microsoft Intune. Simply open the project in the Deployment Editor and run the upload script in the Plug-in Manager to upload any PSADT project directly to your Microsoft Intune tenant. PowerShell source code is included.
- Requirements:
- Enterprise App Registration in Azure – Permission:
DeviceManagementApps.ReadWrite.All (Type: Application) - Client Secret for Authentication (entered manually)
- Tenant & Client ID need to be updated in “.\Deployment Editor\Plugins\Enabled-Upload_MicrosoftIntune\Upload-MicrosoftIntune.ps1”
- PowerShell Module (IntuneWin32App):
https://github.com/MSEndpointMgr/IntuneWin32App - To ensure that the generation of the *.intunewin file does not fail, there must be no spaces in the project path
Improvements
on the way:
✅ Looking to the future, the following features will be available soon:
- Validation and Debugger
- General UI improvements
- Change history (reverting with CTRL+Z)
- Better keyboard support
- Duplicate functionality
- Parameters with special input fields by type
- Parameters with predefined options
- Folders and filters (if then) support
- Drag and drop support
- (…)
➡️ Updates for Preview 9:
- Updated PSADT and templates to v4.1.0
- Added ‘Open with VS Code’ to the project menu bar (#9)
- Fixed the demo project with 7-Zip
➡️ Updates for Preview 8:
- New Feature: WinGet Import
It is now possible to generate a PSADT project from most WinGet packages with an x64 or x86 installer.
The importer downloads the installer file and automatically generates the corresponding action with the silent switch.
The product name, vendor and app version will be automatically populated thanks to the information in the package manifest.
➡️ Updates for Preview 7:
FAQ
The file has been detected as a virus.
It’s a false alarm. You can find the VirusTotal report below the Download button.
DeploymentEditor.exe does not start / or is blocked by Microsoft Windows Defender for Endpoint and Business
If possible, add the Deployment Editor as an exclusion or simply use Microsoft 11 Dev Environment in Hyper-V. There are some environments that block Deployment Editor directly because the EXE is not signed. This will be fixed in the future with stable releases.
Is it possible to add more commands in the current preview version?
Yes, you can simply edit the “PSADT.sqlite” (under <Extracted Folder>\Databases) file with DB Browser for SQLite (sqlitebrowser.org).
Can I create directly an Intune package?
Yes! In combination with the Setup Packager Tool, you can easily create the Intune package (*.intunewin) for upload. In addition, the Setup Packager provides the necessary commands for Intune.
Can I create my own plugin?
Yes, you can write your own PowerShell plugins and call them directly from the UI. The script will be invoked with the path to the project folder as a parameter.
Your feedback is important to us.
Improvements come from feedback. We are happy to hear every opinion!
