Infrastructure refresh
We design, source, migrate and manage server, storage and virtualisation environments. When hardware support, capacity or a platform renewal brings the next investment forward, we work through what to extend, replace or move, then deliver the changes.
- Hosts 1 and 2 Warranty ends 4 mo
- VMware subscription Renewal due 7 mo
- Storage array Support ends 14 mo
- Windows Server version Extended support ends 18 mo
- Host 3 Warranty ends 26 mo
Extend what you have, refresh it or change direction
Each path is costed over the same five years and against the same workloads, so the comparison is fair before anything is bought.
Keep the current environment for longer
Where the equipment remains suitable, we can extend warranty or support, make selective capacity upgrades and address maintenance or recovery gaps. We set out the remaining constraints and the next review point, so deferral has a plan behind it.
Replacement deferred to year 3
- Support extended on hosts 1 and 2
- Storage capacity added
- Review point set for year 3
Replace the platform where the direction still makes sense
Where workloads belong locally and the architecture still fits, we replace servers, storage or virtualisation components around measured demand. That can be a conventional server and storage design or hyperconverged infrastructure, with capacity for growth, maintenance and component failure.
New hosts and storage in year 1
- Three new hosts sized to measured demand
- Storage replaced with headroom for growth
- Recovery tested before cutover
Use the refresh point to reconsider the platform
A renewal or hardware replacement can be the point to change virtualisation platforms or move selected systems to Azure or Microsoft 365. We sequence those moves before sizing the remaining local environment, where the timing allows, to avoid buying capacity for workloads that are leaving.
Smaller local footprint, some workloads in Azure
- File and collaboration moved to Microsoft 365
- Two-node Azure Local for systems that stay
- VMware not renewed
Infrastructure decisions usually start because something is changing
01 Hardware support is ending Server replacement
Warranty expiry, parts availability or software support dates are bringing the replacement decision forward.
Go to Server replacement →02 VMware renewal and host replacement overlap VMware Renewal
The renewal quote and the hardware investment need to be considered together before either is committed.
Go to VMware Renewal →03 Performance or capacity is becoming a constraint Capacity and sizing
Application delays, storage growth or peak demand are affecting the way the business works.
Go to Capacity and sizing →04 Recovery has not been proven Backup and Disaster Recovery
Backups complete, but there is limited evidence of how quickly critical systems could be restored.
Go to Backup and Disaster Recovery →05 Some workloads may move to cloud Workload placement
An Azure or Microsoft 365 project could change how much local infrastructure the business needs.
Go to Workload placement →06 An acquisition or new site changes the requirements Design and delivery
Separate environments, new applications or additional locations need to be accommodated in the next design.
Go to Design and delivery →Windows server replacement, sized and costed before you buy
A server replacement plan needs to explain what the business is buying, why that capacity is required and what happens if part of the environment fails. We bring those decisions into the design and the cost comparison.
What can be retained
We check hardware condition, firmware, warranty, parts availability and the support position of Windows Server, the hypervisor and business applications. Equipment that can stay in service is separated from components that need replacing or a set transition date. Where eligible, Extended Security Updates can bridge the gap while an upgrade or migration is completed.
How much capacity the workloads need
We measure CPU, memory, storage utilisation, I/O and application response times, including busy periods. The design allows for data growth and for the capacity needed when a host is offline for maintenance or fails. Plant systems, large design files and latency-sensitive applications are checked before their location changes.
How services come back after a failure
We set recovery targets with you, then test the design against host, storage, network and power failures. Restore order, identity and DNS dependencies, backup separation and restore testing all shape the replacement environment.
What it costs to change and operate
We compare hardware, platform and guest licensing, backup, networking, migration, parallel running, training and ongoing management over a common planning period, typically three to five years. Support extensions and staged spending are costed alongside replacement, and the comparison is set out the way finance and leadership will review it: total cost over the period, what is deferred and what risk is retained.
Bring us the quote, renewal or capacity problem
Share the hardware quote, renewal notice or performance issue that has prompted the discussion. We can work from the records you have and fill in the missing technical detail before committing to a design.
Local infrastructure we design and run
We work across conventional infrastructure, Azure Local, Nutanix, VMware and Proxmox. Application support, storage design, licensing and the skills needed to operate the environment decide the shortlist. Hardware options include Lenovo ThinkSystem servers and ThinkAgile HCI configurations.
Modern server and storage
For workloads that suit a conventional local design, we specify servers and storage around capacity, resilience and lifecycle requirements.
Azure Local
A local platform with Azure-connected management through Azure Arc. We check validated hardware, connectivity, licensing and backup compatibility against the proposed configuration.
Compare VMware and Azure Local →Nutanix
AHV virtualisation, AOS storage and Prism management provide an integrated HCI option. The comparison includes application compatibility, lifecycle management, hardware and the commercial package.
Compare Azure Local and Nutanix →VMware
Retaining VMware can suit environments where compatibility, existing operations or migration risk justify renewal. We test the quote against the licensed capacity and the cost of changing platform.
Explore VMware Renewal →Where Proxmox VE fits
Proxmox VE runs Windows and Linux virtual machines through KVM and Linux containers through LXC. It can suit organisations that want flexibility over storage and virtualisation and have Linux expertise in their team or through us.
Storage and availability
We choose between local ZFS, shared NFS or iSCSI storage, and Ceph, against the required availability and recovery model. Ceph needs network capacity, disk design and failure domains planned together. Cluster quorum, failover and maintenance behaviour are defined and tested.
Backup and migration
Proxmox Backup Server and supported Veeam configurations are options for protection. We confirm version and workload coverage, offsite copies, retention and restore testing. VMware virtual machines can be brought across with Proxmox's ESXi import tooling, with guest driver checks, application validation and a cutover and rollback plan.
Running it after go-live
We configure and manage Proxmox environments with documented patching, upgrades, monitoring and escalation. The scope sets out our responsibilities, the client's responsibilities and the selected vendor coverage. Linux and storage expertise remain part of operating the platform.
Licensing
Subscriptions are priced per occupied CPU socket, with the same subscription level across cluster nodes. We compare that model with core-based licensing, including storage, backup, migration and ongoing engineering, and confirm the current support entitlement in the proposal.
We carry the work through to operation
Understand
We establish the workload inventory, application owners, lifecycle dates and the event driving the timing. Existing monitoring and backup evidence show where further measurement or testing is needed.
Decide
We document what will remain, change or move, with the cost, sequencing and constraints of the selected approach. Procurement lead times and renewal deadlines are built into the programme.
Design
We produce the target architecture and migration plan, covering network paths, firewall rules, identity, DNS, storage and backup. Acceptance tests, change windows and rollback limits are agreed before anything in production changes.
Source
We specify and source hardware, software, licensing and vendor support through our Technology Procurement service, checking commercial options, delivery dates and compatibility against the design.
Explore Technology Procurement →Implement
We build and validate the destination, then migrate in agreed stages, checking application behaviour, user and branch access, data integrity, performance and backup. Decommissioning follows acceptance and the agreed retention period.
Operate
We bring the changed environment into documented operation, with monitoring, firmware and software maintenance, capacity reviews, restore testing and vendor escalation assigned. Ongoing infrastructure management can stay with our team under the agreed scope.
Infrastructure decisions that connect through to delivery
01
Engineering across the environment
Our work spans local virtualisation, Azure, networking and backup, so we can deal with the network path or recovery dependency that affects an application alongside the server it runs on.
02
Technical and commercial scope together
We bring hardware specification, licensing, support terms and purchasing options into the same project. The investment reflects what will be installed and operated, including the transition costs.
03
Proven on real migrations
We moved PPK's 20+ workloads from VMware to Azure Local and migrated Kirby into a Sydney data centre, with backup and support aligned in both.
See what we’ve delivered for our clients
Questions that come up before an infrastructure refresh
Do ageing servers need to be replaced?
Age is one factor. We also consider hardware condition, support availability, workload performance and the ability to recover from failure. An extension can be appropriate where those requirements can still be met, with a review date and any limits documented.
How long can we keep our current servers running?
As long as parts, firmware and support remain available and the hardware still meets performance and recovery needs. We check warranty and support dates for each host, the condition of components and the support position of the operating system and hypervisor, then set a review date for the extension.
What if our VMware renewal falls due at the same time?
We align the renewal and refresh plans. Options include renewing, a staged migration or consolidation that reduces the physical capacity needing licences. Moving virtual machines alone doesn't necessarily reduce the licence bill, so the quote, licensing minimums and remaining hosts are checked together.
Does a refresh mean buying a hyperconverged platform?
Not necessarily. Azure Local or Nutanix may suit workloads that stay local, while conventional servers and storage can be the better fit for a simpler design. Moving selected applications first may also reduce the size of the replacement environment.
What happens when our Windows Server version reaches end of support?
Security updates stop unless the version is covered by Extended Security Updates, which Microsoft offers for some versions as a time-limited bridge, with the cost depending on where the server runs. We check eligibility for your version and use that time to complete the upgrade or migration, using Extended Security Updates as a bridge only.
Can Proxmox replace VMware?
Proxmox can run many Windows and Linux virtual machine workloads. We check application vendor support, guest requirements, backup tooling and the team's ability to operate the proposed design before recommending a transition.
Can the work be staged around business operations?
We agree the sequence, maintenance windows and validation with application owners. Some changes need an outage, while others can be prepared alongside the existing environment. The migration plan records the expected interruption and the point beyond which rollback changes or is no longer available.
Can you supply and manage the replacement environment?
Yes. We can take the work from design and procurement through installation, migration and ongoing management. Project responsibilities and the operating scope are agreed together, including what stays with your team or application providers.
Have an infrastructure decision coming up?
Talk to us before the next investment is locked in. We'll work through what can stay, what needs to change and how to deliver it around your operations.