Read summarized version with
About project
Working time:
Since 2025
Industry:
Distribution
The service:
Managed Services
Overview
The customer is a Canadian building products distributor with branches in several provinces. Its ERP, warehouse and file services run on Windows Server and SQL Server instances that were lifted and shifted to Amazon EC2.
The Challenge
The servers moved to AWS, but the old operating habits came with them, and the small IT team had little time for Windows administration.
1. Manual Patching
Patches were applied by hand, irregularly and outside any maintenance window.
2. Directory Issues
Group policy and replication problems surfaced as login failures at branches.
3. Untested Backups
Backups ran nightly but had never been restored.
4. End of Support Approaching
Windows Server and SQL Server versions were nearing end of support with no plan.
Technology & Approach
We brought the Windows estate onto a managed monthly cycle, with Windows engineers on call.
Implementation
Onboarding
Inventoried servers, roles, applications, licenses and backups, set patch baselines and maintenance windows with AWS Systems Manager Patch Manager, and set alarms on health and capacity.
Monthly Operations
Our engineers patch Windows Server and SQL Server in agreed windows, respond to incidents, maintain the Active Directory domain controllers on AWS and verify backups with monthly test restores.
Licenses and Upgrades
License use is tracked with AWS License Manager, and the Windows Server and SQL Server upgrades were planned ahead of end of support.
Reporting
A monthly report covers patch compliance, incidents, backup verification, license use and upgrade timelines.
Customization & Client Adaptation
Branch operations set the constraints for every change.
Windows Skills on Call
Engineers who know Active Directory, group policy and SQL Server handle incidents directly.
Branch-Friendly Windows
Patching runs overnight and on weekends, outside branch opening hours.
Restore Tests That Count
Each month a different system is restored into an isolated environment and checked by its application owner.
Right-Sized Instances
AWS Compute Optimizer findings are reviewed monthly and applied with approval.
If you find this case interesting, we recommend taking a closer look at
The Results
Patching moved from irregular to a fixed monthly cycle, every critical system has passed a test restore, and the SQL Server upgrade was completed ahead of end of support.
Long-Term Value
- A patch and backup routine that does not depend on one person.
- Upgrade plans tied to support dates.
- License use visible every month.
Business Impact
- Fewer branch login incidents.
- Confidence that recovery works.
- IT team time back for business projects.
