Skip to main content
Deploy Stable 0.3.46 (build 1144) as a configuration profile and a custom software package assigned to the same hosts.

​
Prepare the pilot

Have administrator access, an enrolled Mac running macOS 14 or later, and the vendor management agent where required. Download the Stable 0.3.46 (1144) Guardian Disabled PKG and complete the required configuration before upload. The completed Silmaril-Managed.mobileconfig has passed validation, and the package is the Stable PKG. Complete the shared profile preparation before adding the Fleet profile or package.

​
Install the profile

Stay in the Mac’s current fleet. Open Controls > OS settings > Configuration profiles, choose Add profile, and upload Silmaril-Managed.mobileconfig. Fleet signs uploaded profiles. Confirm supported targeting for the intended hosts before upload. Label-based profile targeting requires Fleet Premium. Keep existing baseline controls and assignments in place. If scoped targeting is unavailable, arrange a supported rollout with your administrator before uploading. For replacement, edit the existing profile row. Keep PayloadIdentifier dev.silmaril.mdm.managed, PayloadDisplayName Silmaril Managed, and every supplied UUID and permission payload. Confirm the profile is installed on the pilot hosts before distributing the package.

​
Install the package

With Fleet software management and scripts enabled, open Software in the current fleet, then Add software > Custom package. Upload the Stable PKG and match its targets to the profile. Use matching software labels where supported. Add software within the intended fleet. For a pilot, open Hosts > the Mac > Software > Library, find Silmaril under Available for install, and select Install. Check Status or device Activity. Use the linked automatic-install policy workflow for broader rollout. Use Fleet’s supported software/package status for deployment, then verify version 0.3.46, build 1144, and Guardian Disabled inside Silmaril.

​
Verify the pilot

Open Silmaril and verify its identity, managed connection, and fresh Protection activity. Check the intended Guardian Disabled build. Resolve Restart required by fully quitting and reopening the affected agent, then starting a new session.

​
Expand the rollout

For each later cohort, confirm profile installation before assigning or installing the package. Adding hosts to a label that already installs software can deliver both at once. Repeat the profile-first staging and endpoint verification for every cohort.

​
Update or replace policy

Deploy the intended Guardian Disabled version and update app/package metadata together. Replace the profile in its existing row with the same supplied identity and permissions. Removing managed keys restores saved local preferences. Verify a pilot before expanding the update.

​
Uninstall

Pause every Silmaril software install for the target Macs. Keep their fleet and baseline controls assigned. Run the shared MDM uninstall script as root with the affected user signed in. Retain its JSON receipt and exit code, then follow shared result handling. Upload the script under Controls > Scripts, select the Mac under Hosts, then Actions > Run script. Use a manual run and inspect the host activity feed before retrying. Complete reported permission follow-up and remove only the Silmaril profile when policy should stop applying.

​
Vendor references