intunemdms.com

Intune Deployment Guide

Deploy TeamSpeak client (x64) with Intune

Overview

Deploy TeamSpeak client (x64) 3.6.2 from TeamSpeak Systems with a structured Intune workflow that covers packaging, assignment, and post-deploy checks.

App nameTeamSpeak client (x64)
PublisherTeamSpeak Systems
Version3.6.2
App typeWindows app (Win32)
Install behaviorSystem

Download Installer

Installer fileTeamSpeak3-Client-win64-3.6.2.exe
Download sourcehttps://files.teamspeak-services.com/releases/client/3.6.2/TeamSpeak3-Client-win64-3.6.2.exe

Build the IntuneWin Package

  1. Create a working folder on your local machine (for example: D:\Intune).
  2. Create two subfolders inside the working folder: Input and Output.
    • D:\Intune\Input: Folder for all setup files. All files in this folder are compressed into an .intunewin file.
    • D:\Intune\Output: Stores the generated .intunewin package.
  3. Place TeamSpeak3-Client-win64-3.6.2.exe in the Input folder.
  4. Download the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe) and place it in D:\Intune.

Start by organizing a dedicated packaging folder for TeamSpeak client (x64) to keep input binaries and generated .intunewin files traceable.

D:\Intune
├── Input
│   └── TeamSpeak3-Client-win64-3.6.2.exe
├── Output
└── IntuneWinAppUtil.exe
  1. Open Windows PowerShell or Command Prompt as Administrator.
  2. Navigate to the working folder: cd D:\Intune.
  3. Run the following packaging command to generate the TeamSpeak3-Client-win64-3.6.2.intunewin package. For packaging background, see .intunewin package preparation.
IntuneWinAppUtil.exe -c .\Input -s "TeamSpeak3-Client-win64-3.6.2.exe" -o .\Output
Command Prompt
  1. After the command finishes, the generated package should be available in the D:\Intune\Output folder.
D:\Intune
├── Input
│   └── TeamSpeak3-Client-win64-3.6.2.exe
├── Output
│   └── TeamSpeak3-Client-win64-3.6.2.intunewin
└── IntuneWinAppUtil.exe

Note: Windows application size is capped at 30 GB per app.

Create the Intune App Object

Create the Intune app record for TeamSpeak client (x64), then validate app information and execution settings prior to deployment.

  1. Go to Apps → Overview, then choose the Windows platform card (or expand Platforms and select Windows).

    intunemdms-generated-appsoverview
  2. Click Create to add a new app.

    intunemdms-generated-windowsapps-shot
  3. In the Select app type panel, choose Windows app (Win32).

    intunemdms-generated-selecttype-shot
  4. On the App information page, click Select app package file.

    intunemdms-generated-uploadpkg-shot
  5. Upload TeamSpeak3-Client-win64-3.6.2.intunewin, then confirm the App package file panel.

    intunemdms-generated-packagefile-modal

Configure App Settings

  1. Configure app settings for TeamSpeak client (x64) with a pilot-first mindset so install, uninstall, and detection behavior remain predictable at scale.

    NameTeamSpeak client (x64) 3.6.2
    DescriptionTeamSpeak client (x64) 3.6.2
    PublisherTeamSpeak Systems
    App version3.6.2
    intunemdms-generated-appinfo-shot
  2. Configure how Intune installs and uninstalls the app. Enter the values below in the Program tab and leave all other settings unchanged. See Intune install and uninstall commands for command guidance.

    Install/Uninstall typeCommand line
    Install command"TeamSpeak3-Client-win64-3.6.2.exe" /S /NCRC
    Uninstall command"%ProgramFiles%\TeamSpeak 3 Clientuninstall.exe" /S
    Install behaviorSystem
    Device restart behaviorApp install may force a device restart
    Allow available uninstallYes
    Installation time required60 minutes
    Return codesKeep the default Intune return codes.
    intunemdms-generated-program-shot
  3. Define which devices are eligible to install the app. Learn more in Intune requirements explained.

    Check operating system architectureNo. Allow this app to be installed on all systems.
    Minimum operating systemWindows 10 1607
    Additional requirement rulesNo requirements are specified.
    intunemdms-generated-req-shot
  4. On the Detection rules page, set Rules format to Manually configure detection rules. For the concept, see Intune detection rules explained.

    intunemdms-generated-detection-format-shot
  5. Click Add to create a detection rule.

    intunemdms-generated-detection-type-shot
  6. Select the appropriate Rule type (MSI, File, or Registry) based on the installer. Use the table below as a reference.

    #TypeTargetMethodValue
    1File%ProgramFiles%\TeamSpeak 3 Clientts3client_win64.exeString/version comparisonequals 3.6.2.0
    2RegistryHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallTeamSpeak 3 Client → DisplayVersionString comparisonequals 3.6.2

    Associated with a 32-bit app on 64-bit clients: No.

  7. On the Dependencies page, click Next unless this app must install after another app.

    intunemdms-generated-lite-wizard
  8. On the Supersedence page, click Next unless this app replaces an older app.

    intunemdms-generated-lite-wizard

Assign and Deploy

  1. Scope assignments for TeamSpeak client (x64) by rollout intent and ring maturity instead of moving directly to full production.

    Assignment options

    Required

    Installs the app automatically on targeted users or devices. Use this after install, uninstall, and detection are verified.

    Available for enrolled devices

    Shows the app in Company Portal so users can install it manually. Use this for pilot users, IT validation, or optional apps.

    Uninstall

    Automatically removes the app from targeted devices. Use this when you need to retire or remove the app.

    Note: Start with a dedicated test group before broad deployment. For example, use the Required assignment option to automatically install the app on targeted devices.

    intunemdms-generated-lite-wizard
  2. Review all configuration details, then click Create to deploy the app.

    intunemdms-generated-review-create
  3. Verify the app in Intune. Confirm that the upload is finished, the application is saved, and the app overview shows the expected package details.

    Note: If Intune says the app is not ready yet, wait a few minutes and refresh the page.

    intunemdms-generated-postcreate

Trigger Intune Policy Sync

Trigger and confirm policy sync for TeamSpeak client (x64) before troubleshooting deeper packaging assumptions.

01

Manual device sync

  1. On the Windows device, open Settings.
  2. Go to Accounts → Access work or school.
  3. Select the connected work account, then click Info.
  4. Click Sync.
02

Remote Intune sync

  1. Open Devices → Windows devices.
  2. Select the pilot device.
  3. Click Sync from the device action bar.
03

Company Portal sync

  1. Open Company Portal on the device.
  2. Go to Settings.
  3. Click Sync.
04

Restart device

  1. Restart the Windows device.
  2. The device will automatically check in and apply policies during startup.

End User Experience

Confirm expected end-user experience for TeamSpeak client (x64) on pilot endpoints before broad rollout communications.

intunemdms-generated-enduser

Required apps install automatically. During installation, Windows may show notifications from Microsoft Intune Management Extension. Users can see the app move from installing to installed.

Note: Notification visibility depends on Windows notification settings and Intune app deployment behavior.

Track Install Progress and Results

Review deployment status for TeamSpeak client (x64) with return-code context so escalation is evidence-driven.

intunemdms-generated-tracking-overview

Click Device install status or User install status to see the list of devices or users with their installation status.

intunemdms-generated-tracking-device

Uninstall the App from Intune

When the app is no longer needed, remove it by changing the Intune assignment to Uninstall for the target group.

  1. Go to Apps → All apps, then select the app you want to remove.

    intunemdms-generated-uninstall-select
  2. Open Properties and click Edit next to Assignments.

    intunemdms-generated-uninstall-properties
  3. Move the target group to the Uninstall section.

    intunemdms-generated-uninstall-edit
  4. Review the assignment, then click Save. Devices will remove the app after the policy is applied.

    intunemdms-generated-uninstall-review

After saving, the uninstall policy is applied. The device removes the app automatically.

Note: The uninstall process may take a few minutes depending on device check-in and policy sync timing.

Troubleshoot Installation and Detection

Start with these troubleshooting checks to identify whether the issue is assignment, execution context, detection configuration, or policy sync timing.

IssueWhat to check
App does not installConfirm the app is assigned to the correct user or device group.
App shows as failedReview the install command, silent switch, and Intune Management Extension logs.
Detection rule failsCheck the file path, MSI product code, registry key, or detection value.
App is not visible in Company PortalConfirm the assignment type is Available and the user is in the target group.
Install works manually but fails in IntuneVerify the install command runs silently under system context and does not require user input.
Uninstall does not runValidate the uninstall command and confirm the app is assigned with uninstall intent.
Device has not received policyTrigger a manual sync or wait for the next Intune device check-in.
App stuck on installingCheck if a restart is pending and verify no other installation is blocking the process.
Install fails due to contextVerify the app runs correctly under System or User context based on the install behavior.
Need detailed logsCheck Intune Management Extension logs in C:\ProgramData\Microsoft\IntuneManagementExtension\Logs for installation details and errors.
Tip: When behavior is intermittent, validate the same build on two pilot devices to separate package issues from endpoint state drift.

Deployment Fit and Risks

Before production rollout, verify that TeamSpeak client (x64) matches your target context, change policy, and monitoring posture.

  • Install behavior is currently set to system; confirm it matches the expected execution context.
  • Restart behavior resolves to basedOnReturnCode; align this with maintenance windows and user-impact constraints.
  • Validate requirements and detection against real endpoint state before widening assignment scope.
  • Escalate only after reproducing failures in pilot scope with logs and consistent return-code evidence.

Validation Checklist

  • Use a phased rollout for TeamSpeak client (x64), beginning with a small validation cohort.
  • Confirm the install command executes silently in the target context: "TeamSpeak3-Client-win64-3.6.2.exe" /S /NCRC.
  • Validate detection outputs (types observed: manual/unspecified) using post-install file and registry checks.
  • Capture deployment status, error codes, and retry behavior in Intune reports before expanding assignment.
  • Ensure rollback notes align with tested uninstall behavior before broad deployment.

Change Control and Rollback Notes

  • Record pilot baseline details for TeamSpeak client (x64) (version 3.6.2) prior to wider deployment.
  • Rollback path available via uninstall command: "%ProgramFiles%\TeamSpeak 3 Clientuninstall.exe" /S.
  • Treat rollback as a tested path, not a plan-only artifact, before moving beyond pilot cohorts.
  • If this package supersedes another app, complete coexistence checks before removing legacy assignments.

Deeper Internal References

Use the focused guides below for deeper implementation details tied to this deployment.

Leave a feedback

Include versions, steps, and any error text if you have them.