Upload a private installer
A private package is visible only to your organization, even if it shares an identifier with a community package. Devices download it from EndpointWorks through your source key.
Before you begin
Section titled “Before you begin”- Permission: Manage packages (
packages:write). - Plan: all plans.
- The installer:
.msi,.msix,.appx,.exeor.zip, up to 500 MiB by default.
Upload a new package
Section titled “Upload a new package”- Go to Packages and choose Upload installer.
- Choose the Installer file.
- Fill in:
- Package identifier, in WinGet form, for example
Contoso.Agent. - Name, Publisher, Version.
- Installer type and Architecture.
- Description (optional).
- Package identifier, in WinGet form, for example
- Choose Upload installer.
The file streams straight to storage. EndpointWorks computes its SHA-256 while it uploads.
Result
Section titled “Result”The Uploaded dialog offers Open package. The version is Pending review until its checks finish and you approve it.
Add a version to an existing private package
Section titled “Add a version to an existing private package”- Open the package from Packages › Catalog.
- Choose Upload new version and follow the steps above.
Portable apps
Section titled “Portable apps”A portable .exe gets a command named after the uploaded file. Name the file what users should type, for example contoso-cli.exe.
Troubleshooting
Section titled “Troubleshooting”| Problem | Fix |
|---|---|
| The upload is refused as too large | The default limit is 500 MiB. Contact support if you need more. |
| A version shows Scan failed | The malware scan couldn’t finish, so the version can’t be approved. Choose Analyze again in Security › Findings. |
A finding installer.storage_mismatch |
The stored file no longer matches the hash taken at upload. Upload the version again. |
| An older portable version has a UUID as its command | It was uploaded before command names were added. Upload it again. |