White-label RDSH

Hosted Windows workspaces under your own brand.

infrahost operates RDSH environments for IT providers that want to offer central Windows workspaces to their customers — without building and maintaining the entire platform themselves.

Managed workplace

Offer RDSH without having to operate your own data centre.

Remote Desktop Services remain an efficient platform for central applications and location-independent work for many Swiss SMEs. For small IT providers, however, the real effort does not lie in the initial installation but in ongoing operations: updates, user profiles, storage, backup, gateway, monitoring and incident handling.

infrahost provides the technical foundation. Your IT company designs the solution, supports applications and users, and remains visible to the customer. Architecture, resources and responsibilities are defined for each environment.

Scope of service

The building blocks of an operable RDSH environment.

The exact scope depends on user count, applications, data volume and the required service level.

Virtual server platform

Resources on Proxmox-based infrastructure with NVMe storage and sizing tailored to the workload.

RDSH components

Session hosts, gateway services and core components are built to match the customer environment.

Profile management

User profiles and data are integrated in a structured way, for example using FSLogix-based concepts.

Backup & Recovery

Protection of relevant systems and data according to agreed retention and recovery priorities.

Monitoring

Monitoring of key services, resources and availability with defined alert paths.

Partner support

Your first-level support stays close to the customer; infrahost assists with platform and infrastructure topics.

White-label delivery

Your RDSH service remains your solution in the customer’s eyes.

Access addresses, portals and user information can be aligned with your IT company’s domain and brand. You define the service offering, communication and customer support.

infrahost appears where technically or contractually required — not as a competing provider in day-to-day customer interactions.

  • Access address under your domain
  • Branded user information and documentation
  • Coordinated support and escalation paths
  • Flexible roles between application support and platform operations
  • Extend with monitoring, backup or additional managed services

Operations

Operations with clear boundaries and realistic commitments.

An RDSH platform is only as reliable as its architecture, maintenance and recovery processes. We define these points transparently instead of making blanket availability promises.

01

Capacity planning

CPU, RAM, storage and user behaviour are assessed realistically before the environment is built.

02

Maintenance

Updates and changes are carried out in agreed maintenance windows with clear communication.

03

Data protection

Backup scope, retention and recovery priority are defined for each customer.

04

Incident handling

Alerting and response follow the agreed service level and the criticality of the service.

Transparency

No hidden 99.99% promise.

Standard environments are designed to be robust and economical, but they are not automatically built as interruption-free clusters. If a customer requires higher availability or particularly short recovery times, we explicitly design the additional architecture and corresponding service level.

Frequently asked questions

Questions about white-label RDSH.

For binding details on architecture, scope and service levels, we discuss your specific environment.

Ask a technical question
Is RDSH suitable for every customer?

No. Applications, user count, peripherals, latency and licensing need to be assessed first. We support the IT provider with the technical evaluation.

Who supports line-of-business applications in the RDSH environment?

Typically, the IT provider supports line-of-business applications and users. infrahost is responsible for the agreed platform and infrastructure components.

Are backups automatically included?

Basic protection may be part of the service. Retention, scope, external copies and recovery priority are nevertheless defined explicitly for each environment.

Can an existing RDS environment be migrated?

In many cases, yes. Before migration, we assess operating systems, Active Directory, profiles, applications, data and dependencies. This forms the basis for a concrete migration plan.

Next step

Planning an RDSH solution for a customer?

Together we assess applications, users, data, operations and responsibilities.