Windows Installation Guide
Step-by-step guide to install TE Monitor Agent on Windows
Installation Steps
Get Your API Key
First, add a server in the Servers page and click the key icon to get your unique API Key.
Download PowerShell Script
Use PowerShell to download the monitoring script directly to your server.
Invoke-WebRequest -Uri "https://monitor.te.com.tr/downloads/te-monitor.ps1" -OutFile "te-monitor.ps1"
Set Execution Policy
Open PowerShell as Administrator and set the execution policy to allow script execution.
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Script indirilen dizinde calistirilacak
Script mevcut dizine indirildi. Eger farkli bir dizindeyseniz scriptin bulundugu dizine gidin.
cd C:\path\to\script
Run the Script
Run the PowerShell script with your API Key. The script will ask for your API key if you don't provide it.
.\te-monitor.ps1 -ApiKey "YOUR_API_KEY_HERE"
.\te-monitor.ps1 and the script will prompt you to enter your API key interactively.
Optional: Customize Settings
You can customize the monitoring interval and server URL.
.\te-monitor.ps1 -ApiKey "YOUR_API_KEY" -Interval 10 -ServerUrl "https://monitor.te.com.tr"
Verify Connection
Check your NetSentry dashboard to see if your server is online and sending data.
🚀 Run in Background (Optional)
For production servers, you can run the monitoring script silently in the background without any visible windows.
Start-Process -FilePath "powershell.exe" -ArgumentList '-NoProfile','-ExecutionPolicy','Bypass','-File','C:\path\to\te-monitor.ps1','-ApiKey','YOUR_API_KEY' -WindowStyle Hidden
System Requirements
- Windows 10/11 or Windows Server 2016+
- PowerShell 5.1 or later (built-in)
- Administrator privileges (for execution policy)
- Internet connection (HTTPS)
- Minimum 1MB free disk space
- No antivirus issues - PowerShell scripts are safe
Troubleshooting
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUserWindows Defender: PowerShell scripts are safer than executables and rarely trigger antivirus warnings.
• Verify your API key is correct
• Check your internet connection
• Ensure the server URL is accessible
• Look for error messages in the PowerShell window
• Check if your firewall allows outbound HTTPS connections
• Verify the server URL is correct
• Try running:
Test-NetConnection your-domain.com -Port 443