Download, activate and publish installers

Before you begin

• Users: know the edition and whether your access is public or a private beta invitation.
• Administrators: sign in to beta-admin and have the exact installer file, SHA-256 and recorded release-review evidence.
• Public availability, beta eligibility and activation licensing are separate. Uploading a draft does not complete any of the other steps.

1. Download an available public installer

1. Open Downloads and locate MSP Server, MSP Client, Professional or Free. Read the actual version beside the package rather than assuming every component has the same version.
2. Click its Download [version] button to open the public installer page. Check filename, platform, size, SHA-256 and notes.
3. Click Download installer on that page. Save the file, verify its SHA-256 and follow the installation guide.
4. If the card has no public installer, do not use a candidate filename as a direct download link. Contact Support or use an approved private invitation. Free does not require beta enrollment.

2. Activate an MSP Server license

1. On the server, open MSP Server Administration → Licensing. Click Copy Installation ID.
2. Provide that Installation ID through your established licensing request to Support. Identify the edition and organization. Do not substitute a different machine’s ID.
3. When the license is returned, enter it under License code and click Activate License, or use Import License File... for the supplied license file.
4. Click Refresh License Status. Read License status and the displayed limits before treating activation as complete. Workstation/Professional activation follows the edition’s own prompt; do not use the Server Administration form for a different installation.

3. Upload and review a package in beta-admin

1. Open Installer Library and find Upload a draft. Select Component, Platform and Architecture. Confirm the numeric Selected build shown for that component.
2. Choose the actual installer file. Its filename need not contain a candidate suffix or exactly match a release manifest. Verify that it is genuinely the selected component; renaming does not change its installed version.
3. Enter the 64-character SHA-256 from the build output for those exact bytes. Add useful Release notes, then click Upload draft. Wait for checking/encryption to finish.
4. Under Packages and publication, locate the uploaded draft. Expand Review and publish. Enter the observed installed numeric version and verified publisher/signer, and record the malware, signature and installation-test evidence.
5. Complete the review checkboxes only after performing those checks, then click the publication button. These are recorded owner checks; the website does not perform a malware scan or installation test for you.

4. Make the package public, or replace an old one

1. For a reviewed Published package, find Public access. Select the checkbox approving unrestricted public downloading, then click Make public and latest.
2. Open the provided public download page and confirm the expected package. Refresh Downloads; the card should show the filename, numeric version and button. Review download starts in the admin statistics after a real download.
3. If a wrong or outdated package must be removed, locate it under Packages and publication. Expand Delete package, read the confirmation and click Delete package and free upload slot when you intend to delete it.
4. Upload the replacement and repeat the release review and public-enable steps. It receives a new identity and does not inherit old private invitations or public approval. Withdraw package disables access but does not free the filename for reupload.

If something goes wrong