Table of Contents
Banner for the article "What Is End-User Computing (EUC)? Components, Models and Examples", with the TSplus Remote Access logo and an illustration of a central laptop connected to devices, a server, and cloud resources.

What does end-user computing mean?

End-user computing includes the technologies, services, processes and policies used to give people access to the applications, desktops and data they need across suitable devices and locations.

A practical definition:

EUC (End-user computing) is the complete environment which both connects a user to the digital resources required for work and supports its management, usability and security. A laptop running locally installed software is part of EUC, just as a published Windows application, virtual desktop or Cloud PC is.

An EUC environment can be entirely local, remotely delivered, cloud-based or hybrid and is neither inherently remote nor inherently virtual. Indeed, desktop virtualization is one part of the broader category, therefore application virtualization should not be used as an imprecise synonym for application publishing or for End-user Computing as a whole.

Examples:

TechTarget includes physical, virtual and mobile computing within EUC, while Forrester treats it as a broad technology category rather than a single product type. Both perspectives reinforce the same boundary: EUC starts with what the user needs to accomplish, not with a specific desktop architecture.

Core components of an EUC environment

  • Endpoints: Desktop computers, laptops, thin clients, tablets, mobile devices.
  • Applications and desktops: Locally installed software, software as a service (SaaS) applications, published Windows applications, shared desktops, virtual desktops, Cloud PCs.
  • Identity and access: Authentication, authorization, access policies and controls based on the user, device or location.
  • User state and data: Files, profiles, settings and approved storage locations.
  • Management and security: Endpoint configuration, patching, monitoring, access control, backup, user support.
  • User experience: Login time, application responsiveness, availability and the behaviour of peripherals (printers, etc.).

Five EUC delivery models compared

Organizations can combine EUC models instead of assigning one architecture to every user. The right choice depends on whether a group needs individual applications, a shared desktop, a personal desktop or local access which continues regardless of reliable connectivity .

Model What the user receives Where it runs and who operates it Practical fit Main constraint
VDI A complete virtual desktop, often using centralized images and profiles Organization-controlled data center or cloud infrastructure Standardized desktops at scale, regulated environments and managed user personas Infrastructure, storage, profile management and specialist administration
Desktop as a Service (DaaS) Cloud-delivered virtual desktops or applications Provider cloud, with responsibilities divided between provider and customer Organizations seeking cloud space but less infrastructure ownership Subscription costs, provider dependence, connectivity and cloud skills
Remote Desktop Services (RDS) or application publishing Shared Windows applications or a session-based desktop A Windows server or Windows machine on premises, in a private cloud or on chosen cloud infrastructure Users who need the same business applications without a personal virtual desktop Session compatibility, capacity, peripherals and Microsoft licensing
Cloud PC A persistent personal cloud-hosted PC for each assigned user Cloud provider environment Users who need a consistent personal desktop across devices Full per-user desktops can be excessive when users only need shared applications
Local computing Applications and data on a physical endpoint Primarily on the user’s device, managed by internal IT or a managed service provider (MSP) Offline work, device-dependent software and direct local hardware access Device-by-device management and possible local data exposure

Licensing:

Whereas requirements depend on the operating system, configuration, users and applications, Microsoft licensing remains the customer’s responsibility, especially for RDS or application publishing. Validate your Windows Server, RDS CALs and other licensing requirements directly with a qualified Microsoft contact.

Deployment location:

Deployment location and delivery model are separate decisions. Application publishing can run on premises or in Cloud machines controlled by the customer, while virtual desktops can be self-managed or consumed as a Cloud service. On-premises, private-cloud, public-cloud and hybrid deployments are all legitimate choices so long as they match the workload, control requirements and operating capacity.

Delivery model:

Where delivery models are concerned, Microsoft Learn documents full desktops and individual RemoteApp delivery as distinct options in Azure Virtual Desktop. Its Windows 365 documentation also illustrates the difference between shared resources and a persistent personal Cloud PC assigned to a user.

These distinctions come into play for instance because delivering one application does not automatically imply giving every user a complete desktop.

EUC tools, services and engineering encompass more than desktops

End-user computing (EUC) tools are not one single product class. The label combines:

  • endpoint management,
  • identity and access,
  • application delivery,
  • desktop delivery,
  • profile and data management,
  • security, monitoring,
  • remote support and
  • digital employee experience tools.

EUC services are thus the operational activities around those tools. They can include:

  • device provisioning,
  • application packaging,
  • access administration,
  • patching,
  • helpdesk support,
  • monitoring,
  • lifecycle management and
  • improvements to application performance or user experience...

EUC engineering is the design and technical work required to keep these services usable. Thus, depending on the organization, an EUC engineer may:

  • package applications,
  • automate endpoint configuration,
  • integrate identity systems,
  • design desktop delivery,
  • apply security controls and
  • troubleshoot user experience problems.

The role description varies by organization.

Therefore, the End-user computing market encompasses a broad span of technology and services categories, across local endpoints, endpoint management, application delivery , virtual desktops, Cloud PCs, security and employee-experience tooling. What's more, Gartner’s digital workplace research describes traditional end-user services as evolving toward operations which also emphasize experience, visibility, predictability and resilience, consequently expands EUC beyond device provisioning or virtual desktops.

What happened to VMware EUC?

VMware EUC commonly referred to VMware’s former End-User Computing business, including products such as Horizon and Workspace ONE. That business officially became Omnissa in 2024. VMware EUC was a vendor portfolio within the wider end-user computing market and, following the brand change, its current product name is Omnissa Horizon.

How to choose an EUC model?

Use the least complex model to meet the requirement. If users need a few shared Windows applications or a session-based desktop, start with application publishing. Evaluate VDI or Desktop as a Service when you must manage personal, standardized desktops, images and profiles at scale. Consider a Cloud PC when each user needs a persistent personal desktop, and keep workloads local when offline access, hardware dependencies or latency make remote delivery unsuitable.

  1. Define what users need to open. Separate individual applications, shared desktops and persistent personal desktops. Do not assume every remote user needs an entire virtual machine.
  2. Locate the applications and data. Identify where they run today, whether they can move and which dependencies must remain on existing Windows infrastructure.
  3. Segment the users. Employees, contractors, customers, developers and shift workers can have different access patterns. One EUC model rarely fits every group equally well.
  4. Check workload behaviour. Review connectivity, latency, graphics, printing and peripheral requirements. Test label printers, scanners, USB devices, computer-aided design (CAD), video and other demanding workloads in the intended environment.
  5. Decide who operates the service. Compare your internal skills, available time, security ownership and willingness to manage infrastructure with the responsibilities offered by a cloud provider or MSP.
  6. Validate licensing. Include Microsoft, application and Office or Microsoft 365 licensing before selecting an architecture, not after deployment has begun.

Made simple: the TSplus suite!

TSplus Remote Access fits the shared-desktop part of EUC and supports Windows application publishing when Windows applications run on a Windows server. Application delivery and remote desktop access are as simple as we could make them for admins and users. Additionally, browser access requires the Web Mobile or Enterprise edition, while gateway, farm and load-balancing features require the Enterprise edition. Note: many deployments do not need a farm.

TSplus Remote Access is not VDI, full DaaS or a persistent Cloud PC service, so an enterprise platform may be the better fit when you need large-scale image, profile and personal desktop management yet need the management of it outsourced. As ever, Microsoft licensing remains the customer’s responsibility. Compare the TSplus Remote Access editions to see which delivery options fit your environment .

Short examples

These illustrative scenarios show how the models differ:

  • A small accounting team which needs one Windows accounting application from home may need versatility of application publishing rather than one virtual desktop per person.
  • A regulated enterprise standardizing a large population of managed desktops and profiles may chose likewise or see its needs justify enterprise VDI or DaaS.
  • A developer who needs a persistent personal Windows environment across devices may deploy TSplus software as part of their cloud offer or prefer a Cloud PC.
  • A field worker who must continue working without reliable connectivity may need a locally installed application with synchronized data.

EUC risk management covers access and business-built applications

End-user computing risk management has two established meanings.

1. Risk management

This first meaning covers risks across the user environment, including unmanaged endpoints, excessive privileges, unpatched systems, exposed remote access, data leakage, failed access revocation, weak monitoring and service outages.

Centralized delivery can make policy enforcement and data control easier, but it does not make an EUC environment inherently secure. NIST SP 800-46 Rev. 2 recommends protecting all components of remote access and bring your own device (BYOD) systems against expected threats. Multi-factor authentication (MFA) should be a baseline for remote and administrative access, alongside patching, account lockout, brute-force protection, network segmentation, least privilege, monitoring, backup and tested recovery.

2. Business-managed apps

The second meaning appears frequently in financial services and governance. In this context, an EUC can be a spreadsheet, database, script or other application developed or managed by business users outside normal software-development controls.

Critical business-managed applications need a named owner, an inventory, access controls, change control, testing, backup and periodic review. European Banking Authority guidance calls for financial institutions to maintain a risk-based register of applications supporting critical functions or processes. Its guidance applies to financial institutions and is a useful governance example, not a universal legal requirement for every organization.

In Conclusion: Choosing End-user Computing Models

EUC is a broad environment through which users reach applications, desktops and data. Choose the model according to what your users need, where your applications run and what your IT team can manage, and avoid building full VDI when publishing a handful of Windows applications solves the actual requirement.

You can test TSplus Remote Access for 15 days on your own Windows infrastructure and validate your applications, users and peripherals before choosing a deployment model.

Further reading

back to top of the page icon