Skip to main content
Deploy Swif silently on Windows machines
Updated over a week ago

Swif supports Windows silent installation to replace MDM on the target Windows machines. The silent installer can be requested via Swif's support channels. It will be available on the web app soon. The installer file is an MSI file.

To installer it, there are 2 methods

1) Install via command line like

msiexec /i "{{FILE_FULL_PATH}}.msi" /quiet


2) Install via an existing MDM or software patching tool. Let's use Intune as an example.

  1. Make sure your managed devices show up on the Intune Dashboard on the Microsoft Intune admin center.

    *To enroll a device into Intune is outside of this article's topic. Here is how you can do it. Make sure you have an admin user password when connecting to Intune from the device.


  2. Click the menu item Apps. Then click Add → Select Line of business app.

  3. Upload the MSI app you downloaded from Swif. (Please ask the Swif support team for the MSI app.)

  4. Type Name, Description, and Publisher and click "Next".

  5. Based on your deployment needs, choose the devices or users you want to deploy the Swif app with. Then click "Next".

  6. Review and click "Create"

  7. By default, the Intune agent will install the app within 5 minutes.

  8. If you can access the device, you can speed up the sync process by going to Company Portal from Microsoft Store Apps > Open the Company Portal app. Click on the left bar menu: Settings → Sync. Wait while the system syncs to the Intune server. After the sync is completed, it’ll show a message “Last sync on {DATE} was successful.”

  9. The silent installation will take place within 5 minutes. If it doesn't happen, you can sync it from the Intune portal, it will force the device to sync.

  10. Then you can verify Swif Agent Installed by right-clicking from the Windows icon and clicking Settings → Accounts → Access work or school.

  11. You can check logs in C:\Program Files\Swifteam\log.txt. Or open the PowerShell terminal and then check the scheduler running sc.exe query STService.

Did this answer your question?