SCCM deployment with detection rules
Deploy TwinPane through Microsoft Configuration Manager (SCCM/MECM) with silent install commands, robust detection rules, and phased collection rollout.
This guide shows how to deploy TwinPane with SCCM/MECM using silent commands and reliable detection rules.
Prerequisites
- Configuration Manager admin access.
- TwinPane installer files.
- License key for deployment.
- Device collection for pilot rollout.
If you need installer switches, see Silent install (Client and Server).
1. Create the application in SCCM
In Software Library:
- Create a new Application.
- Select manually specify application information (or your packaging standard).
- Add a deployment type using Script Installer.
Use separate apps for Client and Server where possible.
2. Client deployment type commands
Install command
"TwinPane - Client.exe" /LICENSE=YOUR-LICENSE-KEY /VERYSILENT
Uninstall command
"C:\Program Files\TwinPane\TwinPane - Client\unins000.exe" /VERYSILENT
Set installation behavior according to your endpoint standard (device/user context).
3. Recommended detection rules
Prefer registry detection because installer paths can vary.
Rule option A (recommended)
- Hive:
HKEY_LOCAL_MACHINE - Key:
SOFTWARE\FileSyncBridge\Client - Value:
InstallPath - Rule: value exists
Rule option B
- Detect executable file under your standard install path.
Registry references are documented in Registry keys (Client and Server).
4. Requirement rules
Typical requirement rules:
- OS version: supported Windows versions in your environment.
- Architecture: x64 if that is your standard.
- Optional: remote-session host collections for Server app.
5. Deployment strategy
Use staged collections:
- Pilot collection for validation.
- Early adopter collection.
- Production collection.
Start with Available for pilot, then move to Required for production once validated.
6. Monitoring and remediation
Monitor deployment success in SCCM reports and client status.
If failures occur:
- Validate the install command and license parameter.
- Confirm deployment content distribution to all DPs.
- Check detection logic is not too strict or too broad.
7. Server deployment notes
For server-side components:
- Create a dedicated Server deployment type with:
"TwinPane - Server.exe" /LICENSE=YOUR-LICENSE-KEY /VERYSILENT
- Scope server deployment to host collections only.