Deploy Tinkle Using Windows Silent and Bulk Installation

For silent, bulk and managed deployments, the MSI installer is the recommended installation method.

1. MSI Installation Options

The following examples use the installer filename Tinkle.msi.

Run commands from the directory containing the installer, or provide the full file path.

Basic Installation (Default UI)

Installs Tinkle using the standard Windows Installer interface.

msiexec /i Tinkle.msi

The user will see the installation interface and any applicable prompts.

Silent Installation (No UI)

Installs Tinkle silently, without displaying installation windows or requiring user interaction.

msiexec /i Tinkle.msi /quiet

This option is recommended for automated deployments.

Passive Installation (Minimal UI)

Installs Tinkle without requiring user interaction but displays an installation progress indicator.

msiexec /i Tinkle.msi /passive

Install for All Users (Per-Machine)

To install Tinkle for all users of a Windows computer, open Command Prompt with administrator privileges and run:

msiexec /i Tinkle.msi ALLUSERS=1

For a silent installation available to all users:

msiexec /i Tinkle.msi ALLUSERS=1 /quiet

Important: Administrative privileges may be required for per-machine installations. The installation scope is also dependent on the configuration of the MSI package.

Administrative Installation (Network Extraction)

An administrative installation extracts the Tinkle installation files into a designated folder for distribution.

msiexec /a Tinkle.msi

This allows administrators to prepare installation files for deployment across multiple devices.

Note: Administrative installation does not install Tinkle on the local computer.

2. MSI Uninstallation Options

Tinkle can be uninstalled using either the original MSI installer or the application's Windows Installer Product Code.

Uninstall Using the MSI File

msiexec /x Tinkle.msi

For silent uninstallation:

msiexec /x Tinkle.msi /quiet

Uninstall Using the Product Code

Each MSI installation has a unique Product Code GUID which can be used to uninstall the application without requiring the original MSI file.

msiexec /x "{PRODUCT-CODE-GUID}"

For silent uninstallation:

msiexec /x "{PRODUCT-CODE-GUID}" /quiet

Replace {PRODUCT-CODE-GUID} with the Product Code associated with the installed version of Tinkle.

Finding the MSI Product Code

The Product Code can be identified using PowerShell.

Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*", "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*", "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" -ErrorAction SilentlyContinue | Where-Object { $_.DisplayName -like "*Tinkle*" } | Select-Object DisplayName, DisplayVersion, PSChildName

For MSI-based entries, the PSChildName may contain the Product Code GUID.

Product Codes can change between application versions, so administrators should confirm the correct identifier before performing bulk uninstallation.

3. Additional MSI Installation Arguments

Standard Windows Installer arguments can be combined with Tinkle installation and uninstallation commands.

Restart Behaviour

Argument	Description
`/norestart`	Prevents an automatic system restart
`/forcerestart`	Forces a restart after installation
`/promptrestart`	Prompts the user to restart when required, where supported by the UI mode

Installation Logging

Windows Installer supports detailed logging to assist administrators with troubleshooting failed installations.

msiexec /i Tinkle.msi /quiet /l*v "C:\Windows\Temp\Tinkle-Install.log"

The resulting log records detailed information about the installation process.

Example: Silent Installation for All Users

msiexec /i Tinkle.msi ALLUSERS=1 /quiet /norestart

Example: Silent Installation with Logging

msiexec /i Tinkle.msi ALLUSERS=1 /quiet /norestart /l*v "C:\Windows\Temp\Tinkle-Install.log"

Example: Silent Uninstallation with Logging

msiexec /x Tinkle.msi /quiet /norestart /l*v "C:\Windows\Temp\Tinkle-Uninstall.log"

4. Bulk Deployment

Tinkle can be deployed across multiple Windows devices using endpoint management and software deployment platforms that support MSI packages.

Examples include:

Microsoft Intune
Microsoft Group Policy (GPO)
Microsoft Configuration Manager
Remote Monitoring and Management (RMM) platforms
Third-party software deployment solutions

For centrally managed deployments, the following command is recommended as a starting point:

msiexec /i "Tinkle.msi" ALLUSERS=1 /quiet /norestart

Administrators should ensure that the deployment process has the required privileges and that the installer is accessible to the target device.

Per-machine deployment should be tested before wider distribution to confirm compatibility with the supplied MSI package.

5. Troubleshooting

If Tinkle fails to install or uninstall, administrators should enable Windows Installer logging to identify the cause.

Generate a Detailed Installation Log

msiexec /i Tinkle.msi /quiet /norestart /l*v "%TEMP%\Tinkle-Install.log"

Review the log file for Windows Installer errors and failed installation actions.

Common Windows Installer Exit Codes

Exit Code	Meaning
`0`	Installation completed successfully
`1603`	Fatal error during installation
`1618`	Another Windows Installer operation is in progress
`1619`	Installer package could not be opened
`1638`	Another version of the product is already installed
`3010`	Installation successful; restart required

Note: Exit codes are returned by Windows Installer and should be interpreted alongside the installation log.

6. Recommended Deployment Command

For most managed Windows environments, the recommended starting command is:

msiexec /i "Tinkle.msi" ALLUSERS=1 /quiet /norestart /l*v "C:\Windows\Temp\Tinkle-Install.log"

This command requests a per-machine installation, suppresses the installation interface, prevents automatic restarts and produces a detailed installation log.

Important: The examples use standard Microsoft Windows Installer functionality. Individual installation features, upgrade behaviour and supported deployment scope depend on the specific Tinkle MSI package and should be validated before production deployment.

Important: When using this method, automatic updates will be disabled and the admin is responsible for handling these with a new version of the MSI.

MSI can be found here: https://www.tinkle.co/download/Tinkle.msi