How to Install Sync on Windows with Intune

Contents

Prerequisites

A list of firewall rules and exclusions can be found here.

Gather Software

  1. Log onto https://sync.logitech.com then go to System-->Bulk provisioning.

  2. Download the Windows Sync Provisioning Bundle.

  3. Extract the bundle into a single folder, e.g. LogiSyncProvisionBundle. You can delete the readme file to reduce the size of the file. 

  4. Download the Microsoft Content Prep Tool (IntuneWinAppUtil.exe). This will bundle the files required for Sync into a single folder that Intune can use: 
    https://github.com/Microsoft/Microsoft-Win32-Content-Prep-Tool

  5. In the extracted folder create the file installsync.cmd with the following lines:

    start /wait LogiSyncProvisionStub.exe
    Set ErrorState=%errorlevel%
    echo %ErrorState% > %WinDir%\Temp\LogiSync\%ErrorState%.txt 
    echo %ErrorState%
    exit /B %ErrorState%


    Build the Package

  6. From an elevated command line, run the command below. Here, the IntuneWinAppUtil and the LogiSyncProvisionBundle folder are in the same location. If not, you need to give the full path of the Bundle Folder. The -s is the filename that the installer will run, no path is required, just the name of the installer. The -o is the folder to put the Intune file. 

    IntuneWinAppUtil.exe -c LogiSyncProvisionBundle -s installsync.cmd -o SyncIntune
    
  7. This will create a file called: SyncIntune\LogiSyncProvisionStub.intunewin

  8. Log into your Intune portal.

  9. Go to Client Apps

  10. Go to Apps.

  11. Add a new App.

  12. Under other, choose Windows-app (Win32), then click Select.

  13. Add the App Package file, this is the LogiSyncProvisionStub.intunewin file that you created above.

  14. Add the App Information, you can customize this as needed. 

  15. In Program, make the following changes:

    • Install command: installsync.cmd

    • Uninstall command: "C:\Program Files (x86)\Logitech\LogiSync\uninst-main.exe"

    • Install behavior: System

    • Restart behavior: No specific Action
      Add the following return codes:

      Return Code

      Code Type

      8

      Retry

      9 

      Retry

      122-125

      Failed

  16. Windows Requirements

    • x64 architecture

    • Windows 10 1607

  17. Create a manually configured detection rule

    • Rule Type: File

    • Path: %windir%\Temp\LogiSync

    • File: 0.txt

    • Detection: File or Folder exists

  1. There are no Dependencies.

  2. Scope Tags are not required. 

  3. Add it to the required group.

    • Make sure to hide all Toast Notifications.

  4. Add your room systems under the required group.

Verify Install

  1. Go to the Apps List

  2. Drill Down into the Application you just created

  3. Click on Device Install Status

  4. Check for any failed systems.

  5. Any failed system in the Status list will also be missing from the Sync Portal.

Troubleshooting

  1. Drill down into the Managed Apps for the failed system

  2. Go To Devices -> All Devices -> Select the computer the failed and then select Managed Apps

  3. The installer failed to find the 0.txt file required for successful install.

  4. Click on collect Logs and enter the path %windir%\Temp\LogiSync\LogiSyncProvisionStub_Result.txt

  5. In a few minutes the log file will be ready to download.

  6. You can also go to the system directly and open the Result file. Here is a description of the results and possibilities of why what may have caused it.

    Code

    Definition

    Cause

    122

    Provisioning Token not found

    The logisyncprovisiontoken.json file is either corrupted or was not part of the intunewin file

    123

    Syncagent Download failed

    Usually firewall, make sure all firewall rules required are available

    124

    Syncagent Installation failed

    After all the downloads completed, something prevented the install from completing.

    125

    Room provisioning failed

    The system could not communicate with the Sync portal, either an expired token or firewall issue

  7. Once you have resolved the issue you can re-deploy to the system by removing it from the deployment group, restarting the Intune services or rebooting the system and adding it back to the deployment group.

AI assisted translation
Menu