XOAP doesn’t replace Citrix or MCS/PVS; it automates everything around them.

Citrix then delivers the images to users.

This layered approach provides faster deployments, fewer errors, consistent environments and lower operational costs, which is far more scalable and future-proof than relying on MCS/PVS alone.

By using your own scripts or XOAP’s pre-built templates, you can automate AWS tasks directly, across any number of accounts:

• Connect your AWS environments easily (via access key or role).
• Create production-ready Landing Zones fast.
• Run Scripted Actions using PowerShell, CLI or your preferred language.
• Apply changes instantly or schedule them across time zones and regions.
• Automate configuration, security, updates and more.

No IaC or state files. Just automation that works at scale.

Instead of doing all that manually, XOAP lets you automate the entire process in just a few clicks. Here’s how it works:

XOAP allows you to build virtual machine images that work across different platforms, cloud or on-prem. You don’t have to rebuild your environment every time you switch providers; this saves time and keeps your infrastructure consistent.

Now, let’s edit the script quickly before uploading it:

• Remove the first and last lines of code: <powershell> and </powershell>.

• Replace the placeholder “USERNAME” in line 51 with a valid username.

• Remove the comments from lines 49 to 52 (optional, but considered a good practice).

To upload the script, open your XOAP Workspace and go to the Resources area in the left-side menu. Click + New Resource, then simply drag and drop the script. Click Next and Save.

Autopilot doesn’t install software, except in Autopilot Pre-Provisioning scenario, formerly known as ‘white glove’.  Usually that’s handled through Intune. But what if you need more?

With Application Management module, you get:

• A rich, reusable package library
• Centralized packaging support across multiple tenants
• A solution that works beyond Intune, including SCCM, hybrid setups, and disconnected environments

It’s a modern take on application delivery, with better flexibility and fewer limitations.

It’s tough to manage what you can’t see. In hybrid IT, teams often lack a complete view of what’s happening across all systems. This can lead to slower responses when something breaks or performs poorly.

However, this isn’t about a lack of skill – it’s about infrastructure complexity. It has a lot of moving parts, from on-prem servers and cloud platforms to APIs, containers, and third-party tools. These are often spread out across different environments, which makes it hard to see everything at once. Even strong IT teams can miss issues if they don’t have a clear, unified view.

In response, existing solutions have been around for a long time that still follow the core ideas of infrastructure as code, but with different priorities. Instead of being dependent on state files and extensive tooling, they are often enough to fulfill the needs of modern infrastructure deployments. We are discussing cloud-provider SDKs and command-line interfaces (CLIs).

These tools offer first-class feature access without the Terraform delay. And they give you finer control and custom logic through programmatic control and additional conditional logic, which is sometimes cumbersome or verbose in Terraform.

Often, the approach to implementing small-scale tasks leads to easier maintainability, faster execution, more predictable deployments, and less stress for the teams involved.

Last but not least, it reduces abstraction overhead; native tools do exactly what the API says, no translation or misalignment.

We could still say that with Terraform, you have one language that you have to learn to automate your entire infrastructure deployment on different platforms, but although you are using only one language, you still have to adjust all resource definitions to the cloud-specific parameters. So, why not use platform-specific tools directly from the start?

October is just around the corner, and 2029 not that far away. Large migrations and modernization efforts take months or even years.

System engineers and IT admins who act now—and who automate wherever possible—will avoid the stress of last-minute scrambles and future-proof their organizations.

With XOAP, you can automate inventory, migrations, deployments, patching and compliance, allowing you to focus on what matters most: delivering secure, modern infrastructure that’s ready for the next decade. 

Not all systems are the same. A web server in production might need one setup, while a test server or a server in a different country might need something slightly different.

Custom modules make that easier. You can build logic into the module to decide how it should behave based on things like location, server role, or environment. That way, you don’t have to create completely different configurations for every scenario.