Running Windows Workloads in the Cloud: What Changes and What Doesn't

Windows workloads move to the cloud later than everything else, and usually for good reasons. The application is business-critical, the licensing is unfamiliar, someone once heard that remote desktop over the internet is dangerous, and the server in the office has been running for four years without complaint.

Then the hardware warranty expires, or a client asks for evidence of a proper environment, and the question becomes concrete. It is worth answering precisely, because the move changes fewer things than teams expect and a couple of important things that they often overlook.

Key Takeaways

• The application layer usually does not change at all the same Windows Server, the same software, the same configuration.
• Licensing, access model and sizing are the three areas that genuinely change and need decisions.
• Remote Desktop exposed directly to the internet is the single most common mistake in a Windows migration.
• Snapshots are not backups; both belong in the plan.
• Responsibility for patching, hardening and access control stays with you unless you explicitly buy a managed service.

What does not change

Start with the reassuring half, because it is the larger one.

Windows Server behaves identically on virtualised infrastructure. The same editions, the same roles, the same management tools. A line-of-business application that runs on Windows Server 2019 in your office runs on Windows Server 2019 in a data centre without modification, and in most migrations the application is never touched the disk contents arrive, the services start, and the users notice nothing except that the system is faster.

Active Directory still works the way it always has. Domain controllers can run on virtual machines; this has been standard practice for well over a decade. File shares, print services, IIS sites, scheduled tasks and Windows services all behave the same.

Your administrative skills transfer directly. Group Policy, Event Viewer, Task Scheduler, PowerShell, the Server Manager console nothing here is replaced by a cloud-specific equivalent you would have to learn.

And crucially, your responsibilities transfer directly too. Patching, antivirus, account hygiene, backup verification and access control remain yours. Moving a machine into a professional data centre improves the power, cooling, connectivity and physical security around it. It does not administer the operating system for you.

What genuinely changes, part one: licensing

This is where most planning time is spent, and it is worth being precise.

There are two legitimate routes to a licensed Windows Server in a hosted environment.

Licence included by the provider. The provider supplies the Windows Server licence as part of the service. You choose the edition and the version, and licensing compliance for the operating system is handled within the subscription. This is the simplest option and the right default for most businesses.

Bring your own licence. If you already hold appropriate licences, they can often be transferred to hosted infrastructure without additional cost, provided the licence terms permit it. This is worth checking before you buy anything twice.

Two additional licence types come up constantly and are separate from the operating system itself:

Remote Desktop Services. Windows Server permits two simultaneous administrative remote sessions out of the box. If several people need to work on the server at once the classic scenario of an accounting or ERP application accessed by a team you need RDS licences. This is the single most frequently forgotten item in a Windows migration budget.

Microsoft SQL Server. SQL Server is licensed independently of the operating system. If your application depends on it, plan the edition and licence count deliberately rather than discovering the requirement during cutover.

On our platform both can be purchased alongside the server, or transferred in if you already own them. What matters is that the decision is made in advance; retrofitting licences after go-live is possible but rarely comfortable.

What genuinely changes, part two: how you reach the machine

In an office, the server sits on the local network and Remote Desktop is reachable from inside the building. In a data centre it is reachable from the internet and that difference deserves attention, because automated scanning finds an exposed RDP port within hours of it opening.

A Delta Windows VPS gives full administrative GUI access with RDP included, which is both the convenience and the exposure. How you use it is the decision that matters.

Three approaches, in ascending order of sensibility:

RDP open to the world. Convenient, and the reason a large proportion of ransomware incidents involving small businesses begin. Not acceptable for a production system.

RDP restricted by firewall rule. Access permitted only from known office IP addresses. Simple, effective, and adequate for teams that work from fixed locations.

RDP behind a VPN. The server exposes no remote desktop port publicly at all; administrators connect to a private network first. This is the correct answer for most businesses, and the one worth the extra configuration.

Alongside this, the usual measures apply and cost nothing: rename or disable the default administrator account, enforce strong credentials with account lockout, enable Network Level Authentication, and keep the machine patched on a schedule rather than when someone remembers.

Our platform also offers VPN as a service for teams that want the private-network approach without building it themselves. The tooling is straightforward; the discipline is what matters.

What genuinely changes, part three: sizing and storage

Physical servers are bought with headroom, because adding memory means buying memory, scheduling downtime and opening a chassis. Cloud instances are not bought that way resources can be increased later, so the correct starting point is what the workload actually uses rather than what it might use in three years.

Two practical notes.

Measure before you size. Performance Monitor over a normal fortnight, capturing peak CPU, peak committed memory and disk queue length, tells you more than any estimate. Most on-premise Windows servers are substantially over-provisioned on CPU and closer to the line on memory than their owners expect.

Storage changes character. Local RAID protects against a drive failing inside one machine. Our platform stores every block on all-NVMe hardware with triple replication across separate nodes, so a drive failure or a whole node failure is a background event rather than a restore. That is a stronger guarantee than a single chassis can offer, and it changes what your disaster recovery plan needs to cover.

It does not change what it needs to cover entirely, though. Replication faithfully copies a mistaken deletion, a bad update or a ransomware encryption three times over. Snapshots ours are free with 48-hour retention are excellent for rollback around a change window, and are not a backup either, because they live on the same platform as the machine. A genuine backup is a separate copy, held separately, that you have actually restored from at least once.

A practical migration sequence

1. Inventory. Applications, services, scheduled tasks, dependencies, hardcoded IP addresses, and every licence currently in use.
2. Choose the Windows Server version deliberately. We offer 2012 R2, 2016, 2019 and 2022 Standard. Where the application supports it, take the newest support lifecycles are finite and migrating twice is worse than migrating once.
3. Provision and rebuild, or lift and shift. A clean install with a documented configuration is preferable where the application allows it; an image-based move is faster where it does not.
4. Test with real users, not just a login. Print, scan, reports, integrations, backups, the month-end routine the things that break are always the peripheral ones.
5. Plan the cutover with DNS TTL reduced in advance and an explicit rollback path.
6. Verify backups from the new environment before decommissioning the old machine. Keep the old server powered off but intact for a few weeks.

Conclusion

Running Windows in the cloud is mostly not a technical change. The operating system, the application and the administrative model come across unchanged, and the environment around them improves considerably redundant power, proper cooling, multi-carrier connectivity and hardware you no longer have to replace.

What does require decisions is the paperwork and the perimeter: which licences you need including RDS and SQL, how administrators reach the machine, how large it actually needs to be, and what your backup means when the storage layer already keeps three copies. Settle those four before you migrate and the migration itself tends to be uneventful.

Planning a Windows migration? Delta.BG offers Windows Cloud VPS on all-NVMe infrastructure with triple replication, Windows Server 2012 R2 through 2022, optional RDS and MS SQL licences or transfer of your own, free snapshots and deployment in under a minute from an Equinix Tier 3+ data centre in Sofia. Call our team on +359 2 4 288 288 or write to [email protected].