Install Vineforce Teams Lite via PowerShell | Silent Deployment (Windows)
Install Vineforce Teams Lite via PowerShell [Windows Only]
Windows 10 / 11 | Windows Server 2016+
This guide covers the fully automated PowerShell deployment of Vineforce Teams Lite — ideal for enterprise environments that need mass deployment across many machines.
One script handles everything automatically:
- Checks and installs .NET 9 (if not already present)
- Downloads the MSI installer from Vineforce CDN
- Installs silently using your authentication token
- Writes the token to
token.txtfor the application - Creates a Windows Scheduled Task so the app auto-starts on every user login
No user interaction is required after the script starts.
Prerequisites
| Requirement | Details |
|---|---|
| Operating System | Windows 10 / 11 or Windows Server 2016+ |
| PowerShell | Version 5.0+ (built-in on Windows 10/11) |
| Privileges | Must run as Administrator |
| Internet Access | Required to download .NET 9 and the MSI |
| .NET 9 | Installed automatically by the script if missing |
Step 1: Get Your Authentication Token
Contact your Vineforce Teams administrator to obtain your company-specific authentication token.
The token looks like this:
xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Why is this token needed?
The authentication token links the desktop application to your company's Vineforce Teams environment. Without it, the application cannot connect.
Step 2: Download the PowerShell Script
Download install-vineforce-lite-window.ps1
Save the script to your Windows machine — for example:
C:\Installers\install-vineforce-lite-window.ps1C:\Users\YourName\Downloads\install-vineforce-lite-window.ps1
Step 3: Update the Script with Your Token
-
Open
install-vineforce-lite-window.ps1in Notepad or VS Code -
Find this line near the top of the file:
$authToken = "YOUR_AUTH_TOKEN_HERE" -
Replace
YOUR_AUTH_TOKEN_HEREwith your actual token:$authToken = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -
Save the file
Step 4: Run the Script as Administrator
The script must run with Administrator privileges to install software and register a Scheduled Task.
-
Open File Explorer and locate
install-vineforce-lite-window.ps1 -
Right-click the file
-
Select Run with PowerShell
Windows may prompt: "Do you want to allow this app to make changes?" — click Yes.
Alternatively, from an elevated PowerShell window:
cd "C:\Installers"
.\install-vineforce-lite-window.ps1
Execution Policy If PowerShell blocks the script, run this first to allow local scripts:
Set-ExecutionPolicy RemoteSigned -Scope Process
What the Script Does (Automatic Steps 5–7)
Once the script starts, it runs fully automatically. Here is exactly what happens:
Step 5: .NET 9 Check and Installation (Automatic)
The script first checks whether .NET 9 is already installed on the machine.
- If .NET 9 is found → skips installation and moves on
- If .NET 9 is not found → downloads and installs
.NET SDK 9.0.310silently with no restart required
🔍 Checking if .NET 9 is installed...
📦 .NET 9 not found. Installing SDK 9.0.310...
✅ .NET 9 SDK installed successfully.
Step 6: Vineforce Teams Lite Installation (Automatic)
After .NET 9 is ready, the script:
-
Downloads the MSI from:
https://cdn01.vineforce.net/download-lite/vineforce/VineforceTeamsLiteInstaller.msiSaves it temporarily to:
C:\ProgramData\DesktopTracker\VineforceTeamsLiteInstaller.msi -
Installs silently using
msiexecwith your authentication token — no installer windows appear -
Writes a detailed log file to:
C:\ProgramData\DesktopTracker\VineforceTeams-Install-YYYYMMDD-HHMMSS.log -
Creates
token.txt(only if installation succeeded) at:C:\ProgramData\DesktopTracker\token.txtThis file stores your auth token for the running application.
-
Removes the downloaded MSI after installation to keep the system clean
📥 Downloading MSI from CDN...
📦 Installing silently...
✅ Exit Code: 0
📋 Log: C:\ProgramData\DesktopTracker\VineforceTeams-Install-20260327-143000.log
🔐 Token file created at C:\ProgramData\DesktopTracker\token.txt
Step 7: Windows Scheduled Task Registration (Automatic)
Finally, the script registers a Windows Scheduled Task named VineforceTeamsLite.
This task:
- Triggers on every user logon (with a 2-minute delay to allow system startup)
- Runs for all users on the machine
- Automatically restarts the app every 2 minutes if it is not running
- Uses least-privilege — no elevated rights required at runtime
🛠 Creating Scheduled Task using XML...
✅ Scheduled Task created successfully
After the Scheduled Task is created, Vineforce Teams Lite will automatically start the next time any user logs in. You do not need to launch it manually.
Step 8: Verify the Installation
After the script completes, verify that everything installed correctly.
Check the Installation Log
Open the log file to confirm a successful install:
Get-ChildItem "C:\ProgramData\DesktopTracker\" | Where-Object { $_.Name -like "*.log" }
A successful installation shows Exit Code 0 in the log.
Check the Token File
Confirm the token file was created:
Get-Content "C:\ProgramData\DesktopTracker\token.txt"
It should display your authentication token.
Check the Scheduled Task
Verify the Scheduled Task is registered:
Get-ScheduledTask -TaskName "VineforceTeamsLite"
Check the Running Process
After the next user login (or after the task triggers), verify the application is running:
- Open Task Manager (
Ctrl + Shift + Esc) - Go to the Details tab or Background processes
- Look for Vineforce Teams Lite
If the process appears, the application is running silently in the background.

Enterprise Deployment (Intune / GPO / SCCM)
For large-scale rollouts, edit the script with your auth token first, then deploy it using your management platform.
Microsoft Intune
- Update the
$authTokenvalue in the script - Create a PowerShell script deployment in Intune:
- Script: Upload the edited
install-vineforce-lite-window.ps1 - Run as: System (or Administrator)
- Script: Upload the edited
Group Policy (GPO)
- Update the
$authTokenvalue in the script - Add the script as a Computer Startup Script via Group Policy:
Computer Configuration → Windows Settings → Scripts → Startup
SCCM / Configuration Manager
- Update the
$authTokenvalue in the script - Create a Package or Application in SCCM with the detection rule checking:
Path: C:\ProgramData\DesktopTracker\token.txt
Troubleshooting
| Problem | Solution |
|---|---|
| Script won't run | Ensure PowerShell runs as Administrator. Run Set-ExecutionPolicy RemoteSigned -Scope Process if execution policy blocks the script. |
| Exit Code not 0 | Check the log file at C:\ProgramData\DesktopTracker\ for the specific error. |
| token.txt not created | Installation failed. Check the log file — fix the error and rerun the script. |
| .NET 9 install fails | Ensure internet access and that no firewall blocks builds.dotnet.microsoft.com. |
| MSI download fails | Ensure internet access and that no firewall or proxy blocks cdn01.vineforce.net. |
| Scheduled Task not running | Run Get-ScheduledTask -TaskName "VineforceTeamsLite" to confirm it exists. Check Task Scheduler for errors. |
| Antivirus blocks the app | Add C:\Program Files (x86)\Vineforce\Vineforce Teams Lite\ to your antivirus exclusions. |
Best Practices
- Always run the script as Administrator
- Update the auth token in the script before deploying — each company token is unique
- Review the log file after each deployment to confirm success
- Add the Vineforce Teams Lite folder to antivirus exclusions before deploying at scale
- Use the Scheduled Task verification step to confirm auto-start is configured correctly
What's Next?
Once installation is complete, Vineforce Teams Lite will:
- Start automatically on the next user login (via the Scheduled Task)
- Run silently in the background — no user interaction required
- Begin tracking activity and syncing with your Vineforce Teams server
View the recorded data in the Vineforce Teams Web Application.
For manual installation without PowerShell, see Install Vineforce Teams Lite (Manual).