Server installation
Physical and virtual servers, operating system builds, Active Directory, file and print services — including migration off whatever you are replacing.
Technology foundation →GigaDeploy — IT Deployment Services
GigaDeploy
You've chosen the technology. We put it in.
Deployment and implementation for the platforms your business actually runs — scoped, built, cut over and handed to you by the same engineers, with documentation you keep.
The engineers who scope it are the ones who build it
Written handover, not a verbal one
Buy the hardware where you like — we will still deploy it
What we deploy
Across the platforms our clients actually run.
Some of this is physical and goes in a rack. Some of it is a tenant, a cluster or a policy. The common part is that it is designed before it is built, tested before it is trusted, and written down before we leave.
Network installation
Switching, routing, firewalls and wireless. Segmentation, VLANs and remote access configured to a design you have seen and approved — not left on defaults.
Enterprise networking →Virtual desktops and apps
Full desktops where people need a whole workspace, or just the applications that need publishing — delivered from the same platform, sized for real concurrency rather than headcount.
CitrixOmnissa Horizon
Digital workplace →
Hyper-converged infrastructure
Cluster build, networking, storage policy and workload migration — with the sizing argued out on paper before any hardware is ordered.
NutanixVMwareSangfor
Private cloud and HCI →
Microsoft 365 and SharePoint
Tenant build, mail and file migration, SharePoint structure that people can navigate, Teams, and device enrolment — with the cutover planned around your working week.
Microsoft 365SharePointIntune
Modern digital workplace →
Backup software
Policy design, the first full backup, retention and offsite copies — finishing with a restore you have watched work, because an untested backup is only a hope.
VeeamAcronisExaGrid
Backup and continuity →
Not listed? Ask. This page grows as our clients' estates do — if it runs in yours, we can scope it. Installing locally? Server installation in Oman and Gurugram, network installation in Oman and Gurugram.
How a deployment runs
Designed on paper before anything is racked.
The same shape whether it is one firewall or a cluster and four hundred desktops. What changes is the size of each stage, not whether it happens.
01
Scope
We look at what you already have before quoting anything: what is running, what it depends on, and what has to keep working while we work. If a change is big enough to need planning rather than installing, we will say so — that is TeraConsult, and it comes first.
02
Design
A written design: sizing, IP and VLAN plan, licensing, the cutover method, and the rollback if it goes wrong. You approve this before hardware is ordered or a tenant is touched.
03
Build and stage
Built and tested away from production wherever the platform allows it, so the change window is a cutover rather than a first attempt.
04
Cut over
A planned window with agreed communications, a named person on our side, and the rollback ready rather than theoretical.
05
Handover
Documentation, a walkthrough with your team, and a clear route for support — whether that route is us or you.
What you hold at the end
A deployment you could hand to someone else.
The test of a finished project is whether a competent engineer who has never met us could pick it up from the documentation alone. That is the standard we write to — including for the day you take it in-house, or hand it to someone else.
- As-built documentationWhat was actually deployed, not what was proposed
- Configuration and IP schedulesAddresses, VLANs, licences and where each thing lives
- Test and acceptance resultsWhat was tested, and what the result was
- The rollback planKept on file afterwards, not discarded at go-live
- Knowledge transferA working session with your team, not a PDF dropped in an inbox
- Licence and warranty registerWhat you own, and the dates that matter later
While it is happening
You should not have to ask how it is going.
Every deployment we run is visible in your client portal from the day it starts. Milestones, delivery notes and sign-off live in the same place as your tickets and documents — so progress is something you check, not something you chase.
- Project milestones with their real status, updated as they move
- Hardware delivery notes confirmed digitally — signed and dated
- Project sign-off recorded against the project, not lost in email
- Documentation and the asset register in the same portal afterwards
Buy the kit where you like
Procurement is your call. The engineering is ours.
You do not have to buy the hardware or licences through us to have us deploy them. Plenty of clients procure through an existing supplier, a distributor or an open tender, and bring us in only for the parts that need engineering. Take one of the three below, or all of them.
Consultancy, before you commit
Have the design and the specification checked while the quote is still a quote — sizing, licensing and what it will actually need to run. Cheaper to change on paper than on a delivery note.
Deployment, whoever supplied it
We install what you bought, from wherever you bought it. If we think the kit is wrong for the job we will say so before we start rather than after — but the decision, and the supplier, stay yours.
After-sales support, if you want it
Once it is live you can keep senior engineering behind just the platform we built — that is GigaExtend, cover for the technologies you nominate rather than your whole estate — or hand it to your own team with the documentation to run it. Either way it is a separate decision, made after go-live rather than bundled into the project.
Questions, answered plainly
The things people ask before signing.
How do we see progress without chasing someone?
In your client portal. Milestones move as the work moves, hardware delivery notes are confirmed there digitally, and sign-off is recorded against the project. It is the same portal your tickets, documents and invoices already live in — one login, not a project tracker bolted on for the duration.
What happens if the cutover does not go to plan?
We roll back to the state agreed in the design, because that plan was written before the window opened rather than improvised during it. Then we work out what we missed, tell you, and re-book. The rollback plan stays on file afterwards.
Do we have to take a support contract afterwards?
No. Deployment stands on its own, and nothing here is priced on the assumption that support follows. The handover pack is written so your own team, your existing IT company, or another provider can run what we built.
Do we have to buy the hardware and licences through you?
No. Buy through your existing supplier, a distributor, or whoever wins your tender — we will still deploy it. Where we can help before that point is checking the specification while it is still a quote, which is the cheapest moment to find out something has been sized wrong.
Can you install equipment we have already bought?
Yes. We will look at it against what you are trying to achieve first, and if we think it is wrong for the job we will tell you before we start rather than after.
Start with the scope
Tell us what needs to go in.
We will look at what you have, tell you what the work actually involves, and put it in writing — before anyone talks about a price.