- OS: Windows 10 (64-bit) or Windows Server 2016
- RAM: 4 GB
- Disk Space: 150 MB
- PowerShell: Version 5.1 or later
- Network: TCP/IP connectivity to target machines
- OS: Windows 11 or Windows Server 2022
- RAM: 8 GB or more
- PowerShell: Version 7.x
- Permissions: Domain Administrator account
Depending on your chosen execution method:
PSRemoting (Recommended)
- WinRM enabled on target machines
- Port 5985 (HTTP) or 5986 (HTTPS) open
- Target machines in same domain or trusted
Copy-First
- Admin shares enabled (
C$,ADMIN$) - SMB ports 445 open
- File and Printer Sharing enabled
PsExec
- PsExec.exe installed and in PATH
- Port 445 (SMB) open
- Administrative credentials
Navigate to the dist folder in your Scriptographer directory:
C:\Dev\Scriptographer\dist\Scriptographer Setup 1.0.0.exe
Or download from the releases page.
- Right-click
Scriptographer Setup 1.0.0.exe - Select "Run as administrator"
- If Windows SmartScreen appears, click "More info" → "Run anyway"
- Welcome Screen - Click "Next"
- License Agreement - Accept and click "Next"
- Installation Location - Choose directory (default:
C:\Users\<username>\AppData\Local\Programs\scriptographer) - Start Menu Folder - Choose folder name (default: "Scriptographer")
- Additional Tasks - Select:
- ☑ Create desktop shortcut
- ☑ Create Start Menu entry
- Install - Click to begin installation
- Finish - Click to complete
- Launch Scriptographer from desktop or Start Menu
- You should see the main window with:
- Script library on the left (5 sample scripts)
- Script editor in the center
- Execution panel on the right
- Output log at the bottom
On first launch, Scriptographer will:
-
Create Database - Initialize SQLite database in:
C:\Users\<username>\AppData\Roaming\scriptographer\ -
Load Sample Scripts - Pre-populate with 5 example scripts:
- Get System Info
- Check Disk Space
- Get Installed Software
- Test Network Connectivity
- Clear Temp Files
-
Initialize Settings - Create default configuration
- Select a Script - Click "Get System Info" in the left panel
- Review Code - Examine the PowerShell script in the editor
- Test Locally - Enter
localhostin the Targets field - Deploy - Click "Deploy (Ctrl+D)" or press Ctrl+D
- Check Output - View real-time logs in the bottom panel
If you see output with system information, the installation is successful!
Ensure PowerShell can execute scripts:
# Check current policy
Get-ExecutionPolicy
# Set to RemoteSigned (recommended)
Set-ExecutionPolicy RemoteSigned -Scope CurrentUserOn target machines, run as Administrator:
# Enable WinRM
Enable-PSRemoting -Force
# Configure trusted hosts (if not in domain)
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "*" -Force
# Verify WinRM is running
Test-WSManOn target machines, allow WinRM:
# Allow WinRM through firewall
Enable-NetFirewallRule -DisplayGroup "Windows Remote Management"For domain environments:
-
Group Policy - Enable WinRM via GPO:
Computer Configuration → Policies → Administrative Templates → Windows Components → Windows Remote Management (WinRM) → WinRM Service → Allow remote server management through WinRM -
Firewall Rules - Deploy firewall rules via GPO to allow WinRM
- Open Settings → Apps → Installed apps
- Find Scriptographer
- Click ⋮ (three dots) → Uninstall
- Confirm uninstallation
- Open Control Panel → Programs → Uninstall a program
- Find Scriptographer
- Click Uninstall
- Follow the wizard
To completely remove all data:
# Remove application data
Remove-Item -Path "$env:APPDATA\scriptographer" -Recurse -Force
# Remove local data
Remove-Item -Path "$env:LOCALAPPDATA\scriptographer" -Recurse -ForceWarning: This will delete all your scripts and execution history!
Problem: "Windows protected your PC" message
Solution:
- Click "More info"
- Click "Run anyway"
- Or disable SmartScreen temporarily
Problem: Error during installation
Solution:
- Ensure you have administrator rights
- Close any running instances of Scriptographer
- Temporarily disable antivirus
- Check disk space (need 150 MB free)
Problem: Application doesn't start after installation
Solution:
- Check Windows Event Viewer for errors
- Verify .NET Framework is installed
- Try running as administrator
- Reinstall the application
Problem: Error creating database on first launch
Solution:
- Check permissions on
%APPDATA%folder - Ensure antivirus isn't blocking file creation
- Manually create folder:
%APPDATA%\scriptographer - Restart application
- Read the Quick Start Guide to learn basic operations
- Review User Manual for detailed feature documentation
- Check Execution Methods to choose the right deployment method
- See Troubleshooting for common issues
Need Help? See the Troubleshooting Guide or open an issue on GitHub.