Skip to main content
Ousmane Salifou Lankoandé

La Poste du Burkina Faso

Windows Server 2012 to 2019 migration and endpoint standardization

Migrating the server estate to Windows Server 2019, with a rebuilt Windows image strategy (DISM), consistent GPOs and SCCM deployments across a fleet spread over 119 branches.

Period
July 2015 – February 2022
My role
Regional IT Division Manager
Organization
La Poste du Burkina Faso

Technologies

  • Windows Server 2012 / 2019
  • Active Directory
  • GPO
  • Hyper-V
  • SCCM
  • DISM
  • WSUS
  • PowerShell
  • Windows 10/11
On this page
  1. Context
  2. My role
  3. Actions and tools
  4. Result
  5. Visuals and evidence

Context

The server estate ran on Windows Server 2012, approaching end of support, while endpoints across the network were moving to Windows 10 and then Windows 11. Without standardization, each branch accumulated configuration drift that made incidents hard to reproduce and deployments unpredictable.

My role

Regional IT division manager: leading the migration, defining the standard baseline, and carrying out the technical work on Active Directory, GPOs, images and deployments.

Actions and tools

  • Migration from Windows Server 2012 to Windows Server 2019, including the hosted roles and services.
  • Active Directory and GPO administration: user rights management and consistent policies applied to endpoints and servers.
  • Hyper-V server virtualization alongside the VMware platform.
  • Building and maintaining Windows 10/11 images with DISM, so every endpoint starts from an identical, documented baseline.
  • Application and update deployment with SCCM, backed by WSUS for patching.
  • PowerShell automation of application packaging, patch application and installed-version inventory across the fleet.
  • Laptop fleet and VPN access management, plus Microsoft 365 end-user support (Outlook, Teams, groups).

Result

  • The server baseline moved off an end-of-support release, restoring the flow of security updates.
  • Endpoints are deployed from controlled images and consistent GPOs, which makes incidents reproducible and deployments predictable.
  • Software version inventory is produced by script instead of being rebuilt manually branch by branch.
  • Migration: Windows servers covered by the modernization plan and validated in stages.
  • Outage windows: planned and communicated according to service criticality.
  • Endpoints: rebuilt and standardized as needed from the approved image.
  • Deployment efficiency: standardized, repeatable sequence, with no internal before/after measure published.

Visuals and evidence

Documentation describes migration and standardization steps without publishing SCCM screenshots or internal server configuration.