Refresh the technology behind every working day
Server and device changes affect applications, data, access and staff productivity. Stratiis helps Scottish businesses coordinate both sides of a refresh, from estate assessment and migration planning to staged deployment, testing and support handover.
What is a server and workstation refresh project?
It is a planned replacement or improvement of server platforms and employee computers, coordinated around the applications and data people use. The project may include infrastructure assessment, device selection, migration, configuration, testing and handover. A joined-up plan helps avoid replacing one part of the environment without checking its dependencies on the other.
Connect infrastructure change to the user experience
Servers and workstations have different lifecycles, but they meet in the applications and services staff depend on.
Less uncertainty
Know which systems, users and devices are affected before work begins.
Clearer budget
Plan equipment, licences, migration and deployment as one programme.
Managed risk
Check compatibility, data protection and cutover before replacing systems.
Better handover
Give support teams updated records, ownership and open actions.
What should a combined server and workstation project include?
The scope should reflect the current estate, business needs and what staff must be able to do after the change.
| Workstream | What is checked | Practical output |
|---|---|---|
| Estate assessment | Server roles, workstation age, support status, applications, users and locations. | Inventory and priority view. |
| Dependencies | Which applications, data, peripherals and access methods rely on each platform. | Compatibility and migration requirements. |
| Target design | Capacity, device specifications, licensing, security and supplier constraints. | Agreed platform and device choices. |
| Migration and deployment | Data transfer, configuration, user profiles, application setup and deployment waves. | Schedule with owners and acceptance checks. |
| Security and recovery | Backup coverage, access controls, patching and safe handling of old data. | Risk actions and validation plan. |
| Testing and handover | Critical workflows, user sign-in, performance, documentation and support ownership. | Acceptance record and updated support information. |
Individual workstreams can link to specialist Servers and Core Systems or Workstations and Lifecycle services.
Should servers or workstations be changed first?
Start with support status, business risk and technical dependencies. A device rollout may depend on an application or identity upgrade; a server migration may need newer endpoint software to work well.
| Situation | Likely priority | Question to resolve |
|---|---|---|
| Unsupported core platform | Assess the server or application risk first. | Can current devices use the replacement service? |
| Failing or insecure endpoints | Plan a workstation wave while checking central dependencies. | Will existing applications and access work on new devices? |
| Both estates are ageing | Sequence the work by impact and dependencies. | Which change reduces the most risk without disrupting users? |
| Growth or a new location | Design capacity and user requirements together. | What must be ready before people or workloads move? |
Does every system need replacing at once?
No. A phased plan can spread investment and allow testing with a smaller group, provided the remaining systems stay supportable and compatible. The sequence should be based on business impact, security, vendor support and the dependencies between servers, applications and devices.
A technology roadmap can place the refresh within wider investment plans.
From estate review to supported rollout
Defined stages help teams make decisions before a change reaches all users.
Discover
Map assets, applications, users, risks and project constraints.
Plan
Agree specifications, migration order, rollout waves and acceptance criteria.
Deploy
Prepare systems, move data, configure devices and test with users.
Handover
Record outcomes, resolve open issues and assign ongoing support.
IT Project Management can coordinate milestones, suppliers, user communications and risks across the whole programme.
Choose the right path for each part of the estate
A combined programme should still give servers, devices and shared services the attention they need.
Servers and core systems
Assess hosting, storage, identity, application and recovery dependencies before platform change.
Workstations and lifecycle
Match device replacement to roles, support status, security needs and employee experience.
Infrastructure upgrades
Bring servers, networks, storage and core software into a broader modernisation plan.
Identity, applications and collaboration may also involve Microsoft 365 services.
Protect data and keep essential work moving
A refresh project should account for what happens if a migration or rollout step does not work as expected.
Before deployment
Check application support, backups and restore evidence, endpoint policies, user data locations, licences and supplier access. Agree a test group and a fallback for critical services.
During and after deployment
Track issues by wave, validate real workflows and keep affected teams informed. Retire old systems only when data, access and support responsibilities have been checked.
Review relevant Cybersecurity Services where the assessment identifies control gaps.
What should be handed over after the refresh?
The business should know what changed, what was tested and who will look after the environment.
| Handover item | Why it matters |
|---|---|
| Updated asset register | Shows which servers and devices are in use, where they are and who owns them. |
| Configuration records | Helps support teams maintain systems and investigate future issues. |
| Test and acceptance results | Records how key applications, access and user workflows were validated. |
| Licences and supplier details | Makes renewals, support agreements and vendor escalation visible. |
| Data and disposal actions | Confirms what happens to information and equipment being retired. |
| Ongoing support plan | Sets responsibility for monitoring, patching, incidents and change. |
Where ongoing help is needed, Stratiis can discuss managed IT support or co-managed IT.
Connect the refresh to planning and day-to-day support
These pages give more detail on each part of a joined-up project.
Servers and core systems
Review platform options, migration and support for critical services.
Workstations and lifecycle
Plan device specification, replacement and ongoing management.
IT project management
Coordinate scope, milestones, risks, suppliers and handover.
Technology roadmaps
Sequence the next wave of upgrades and investment.
Server and workstation upgrades explained
Why plan servers and workstations together?
Employees use applications and data delivered by core systems. Planning both estates together reveals compatibility, access, security and rollout dependencies before either side is replaced.
Do all devices need to be replaced at the same time?
No. Replacement can be phased by support status, condition, role and business risk. A pilot group helps validate applications and configuration before wider deployment.
Should server work happen before the device rollout?
It depends on application and identity dependencies. Some server changes must happen first; in other cases, new devices can be prepared while core systems remain in place. The sequence should follow assessment.
What happens to user data and settings?
The project should identify where data and settings live, how they will move or reconnect, and how the result will be checked with users. Backup and recovery arrangements should be confirmed before change.
Can older applications run on new workstations?
Compatibility depends on the application vendor, version, operating system, licensing and peripherals. Critical software should be tested before a full rollout.
How is downtime managed?
Plan change windows, pilot groups, communications and fallback steps around essential work. Some interruptions may be unavoidable, so expected impact should be agreed in advance.
How are old servers and computers retired?
Confirm data retention, licence transfer, secure data handling, asset records and disposal responsibilities before decommissioning. The exact process depends on the equipment and business requirements.
Who supports the new environment after the project?
The handover should assign monitoring, patching, incidents, user support and vendor escalation. This may sit with an internal team, managed IT support or a co-managed arrangement.
Discuss your servers and workstations
We can review what you have, what needs changing and the safest practical order for delivery.
