Summary
The Synergetic Deployment Tool (SDT) transforms Synergetic upgrades into a fast, simple, and safe self-service operation. Once configured, upgrades that previously required complex coordination and hours of manual intervention can now be completed autonomously in as little as 15 to 20 minutes with robust safety and straightforward recovery options.
The Synergetic Deployment Tool (SDT) transforms Synergetic upgrades into a fast, simple, and safe self-service operation. Once configured, upgrades that previously required complex coordination and hours of manual intervention can now be completed autonomously in as little as 15 to 20 minutes with robust safety and straightforward recovery options.
1. Why Upgrade with SDT? (Speed, Simplicity & Safety)
The Synergetic Deployment Tool replaces manual file copying, manual SQL script execution, and service restarts with a single, resilient deployment orchestrator designed specifically for school IT environments. By making upgrades quick and low-friction, SDT ensures your school can regularly apply releases that deliver security updates, bug fixes, and new functionality.
✓ Fast & Simple Execution
- 15–20 Minute Maintenance Window: Most routine upgrades complete in 15 to 20 minutes from start to finish.
- Guided 3-Click Workflow: Sign in > Check Health > Apply Release. SDT handles downloads, decompressions, migrations, and service restarts automatically.
- Complete Autonomy: Schedule deployments outside school hours or over weekends without needing to wait for a support appointment.
✓ Built-In Safety & Resilience
- Automated Pre-Flight Health Checks: Validates share paths, write permissions, and SQL connectivity before any software is altered.
- Pre-Upgrade Application Backups (Optional): Can take a timestamped snapshot of live application folders prior to deployment if configured.
- Simpler Rollback & Recovery: While there is no automated rollback, because the database is updated and verified first, rolling back is significantly easier in the unlikely event an issue arises that cannot be resolved in real time.
✓ Security, Bug Fixes & New Features
- Security & Protection: Releases may include security updates and vulnerability enhancements that are not explicitly detailed in public notes to protect schools on earlier versions. Keeping up to date helps shield your school systems against newly identified vulnerabilities.
- Prompt Bug Fixes & Stability: Rapidly resolve known issues, calculation adjustments, and edge cases as soon as maintenance builds are released, keeping daily operations stable.
- Immediate Access to New Features: Unlock product enhancements, user interface updates, and statutory compliance reporting changes the moment they become available.
- Safer Incremental Updates: Frequent, small upgrades via SDT avoid high-risk multi-version "jump upgrades", making each update a routine, low-risk non-event.
2. Host Server & System Requirements
The SDT desktop client is typically installed on the primary Synergetic SQL Server or an internal Administrative Jump Host that has direct network connectivity to all Synergetic server tiers.
| Component | Requirement | Details |
|---|---|---|
| Operating System | Windows Server 2016, 2019, or 2022 | 64-bit architecture. |
| .NET Framework | Microsoft .NET Framework 4.8 or later | Required for the SDT desktop client and updater executables. |
| Database Patcher Runtimes | SQL 2016 DB Patcher Runtimes | V68_20170505DBPatcherRuntimesInstaller-SQL2016.exe. Required if running SDT from a Jump Server that has not previously run database patches. (Available upon request from Tes Support). |
| SDT Client Installer | System MSI Installer | Download: SDTSetup.zip |
Notice Regarding Legacy Portable Installations:
Any standalone or extracted versions running from legacy paths (such as
Any standalone or extracted versions running from legacy paths (such as
C:\SDT\Synergetic.Application.SDT.exe) are deprecated and will no longer connect to the deployment services. Please ensure any legacy directory is removed and the modern MSI version (C:\Program Files\SDT\) is installed.
3. Network Architecture & Cross-DMZ Traffic
To execute deployments, the host server running SDT requires bidirectional access across your network infrastructure and outbound access to Tes cloud services:
A. Outbound Internet Access
- HTTPS (TCP Port 443): Outbound communication to the Tes SDT API service (
https://sdt.educationhorizons.com/) and package repository distribution endpoints (AWS S3).
B. Internal Subnets & Cross-DMZ Firewall Clearances
In many school networks, components reside in segmented zones (e.g. SynWeb hosted in a perimeter DMZ, application servers in an internal subnet, and databases in a dedicated database tier). SDT traffic must be explicitly permitted through internal firewalls:
- SynWeb Server (DMZ / Perimeter): Internal firewalls must allow SMB (TCP 445), RPC, and administrative file sharing from the SDT host to the DMZ web server to enable automated web application backups and file deployments.
- Synergetic Application Server (SynMain): SMB (TCP 445) network access to update client files.
- Synergetic SQL Server: Direct SQL connectivity over TCP Port 1433 (or your designated SQL named instance port).
- Custom Network File Shares: Unrestricted SMB file share access to working and backup locations.
Important DMZ Traffic Notice:
If internal firewalls block SMB or RPC traffic between the SDT host and the perimeter DMZ, pre-flight health checks and file synchronization for SynWeb will fail. Ensure rules permitting traffic from the SDT host are active prior to commencing an upgrade.
If internal firewalls block SMB or RPC traffic between the SDT host and the perimeter DMZ, pre-flight health checks and file synchronization for SynWeb will fail. Ensure rules permitting traffic from the SDT host are active prior to commencing an upgrade.
4. Application Directory & Shared Paths
All Synergetic application components must reside on custom network shares (UNC paths) rather than local drive roots:
- Synergetic Application Share: Custom network share hosting production binaries (e.g.
\\fileserver\Synergetic\). - Working Directory Share: Staging file share used by SDT for package download, validation, and decompression.
- Backup Directory Share: Dedicated file share receiving pre-upgrade component snapshots before new binaries are applied.
5. Access Control & Permissions
To ensure SDT can perform atomic upgrades without permission conflicts, configure the following credentials and group memberships:
Active Directory Group
- Create an Active Directory security group named:
Synergetic Upgrades - Add the Synergetic service account (commonly
synadmin,synergetic, orcda). - Add any systems administrators or IT staff who will execute or oversee upgrades.
Share & NTFS Permissions
- The
Synergetic Upgradesgroup must have Full Control (Share and NTFS permissions) across the Synergetic application network share, the working directory share, and the backup share.
SQL Server Role
- The Windows user or service account launching SDT must possess the fixed server role
sysadminon the target Synergetic SQL Server instance to execute database schema migrations.
6. Storage Capacity & Snapshot Optimisation
Expedite Your Upgrade Window with VM Snapshots:
Prior to initiating an upgrade, Tes strongly recommends taking a complete hypervisor VM / SAN storage snapshot of your Synergetic SQL and application servers.
Advantage: Taking a VM snapshot allows you to safely bypass the lengthy manual native SQL database backup stage during the maintenance window, significantly accelerating the upgrade duration. If a VM snapshot is not taken, a full manual database backup must be performed prior to patching, which adds substantial time for larger databases.
Prior to initiating an upgrade, Tes strongly recommends taking a complete hypervisor VM / SAN storage snapshot of your Synergetic SQL and application servers.
Advantage: Taking a VM snapshot allows you to safely bypass the lengthy manual native SQL database backup stage during the maintenance window, significantly accelerating the upgrade duration. If a VM snapshot is not taken, a full manual database backup must be performed prior to patching, which adds substantial time for larger databases.
Storage Capacity Allocation
- Working Share: Allocate at least 10 GB of free space for package downloads and staging extraction.
- Backup Share: Allocate at least 2.5× the size of your current application file share to accommodate optional timestamped application snapshots (
{BackupPath}\{Environment}\{Timestamp}\{Product}).
7. Handover Sessions & Assisted Upgrades
Tes is dedicated to ensuring your team feels confident managing your environments:
- Operator Credentials: If you do not yet have login credentials for the SDT client, raise a ticket via the Tes Help Portal under Synergetic > Upgrades and migrations.
- Complimentary Handover Session: We encourage all clients to complete a guided handover session on their Test environment before performing an autonomous upgrade in Production. You can book a convenient handover session here.
- Assisted Upgrades: If you would prefer Tes engineers to conduct or supervise your upgrade, you can book an upgrade appointment here (subject to operating hours).
Next: Review the step-by-step upgrade procedure in How to Update Synergetic Using the Synergetic Self Deployment Tool (SDT).
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article