DESKTOP / ACCESS
VMware View
Desktop virtualization
A centralized desktop, application, profile and access-policy platform providing consistent workspaces for fixed offices, branches, remote users and controlled endpoints.
Classify desktops by how people work
One desktop specification does not fit every user. Standard office, mobile access, software development, graphical design and temporary collaboration have different CPU, memory, GPU, peripheral, data and network requirements. User classification determines pools, application delivery and endpoint choices.
- Standard office users Browsers, productivity tools, business systems and common peripherals need reliable sign-in, printing, files and audio-video.
- Mobile and branch users Access from different locations requires attention to network variation, authentication, session continuity and local-device boundaries.
- Development and professional users Compilation, simulation, design and data work may require more compute, GPU, storage performance and specialized licensing.
- Temporary and external collaboration Time-bound users receive restricted desktops, applications and data with explicit expiration and revocation.
The complete path from endpoint to desktop pool
Users connect through a client, browser or thin endpoint. Access and identity policy directs them to the appropriate pool. Underneath, compute, storage, networking, virtualization management and data protection remain essential; capacity limits in any one layer affect experience.
Users and endpoints enter through identity and policy before reaching assigned desktop pools.
Separate images, applications and user data
When the operating system, applications and user data are mixed inside one desktop, updates, recovery and capacity become difficult. A layered design keeps the base image maintainable, delivers applications according to need and preserves settings and business data through an appropriate method.
Base image
Control operating system, drivers, security settings and common components and validate compatibility in a test pool before release.
Application delivery
Choose image installation, grouped delivery or another manageable method according to compatibility, licensing, performance and update frequency.
Profiles and data
Define how user settings, desktop files, shares and business data are stored, synchronized, protected and handled during offboarding.
Pilot, migration and rollout
VDI experience must be validated by real users. A pilot covers different networks, endpoints, applications and peripherals; sign-in, application response and feedback then inform resource changes before later groups move.
A pilot turns access, workload and support assumptions into evidence before the next group moves.
-
01
User and application discovery
Confirm roles, concurrency, applications, data, peripherals, locations, networks and security.
-
02
Architecture and capacity design
Define access, pools, images, compute, storage, networking, backup and management.
-
03
Pilot environment
Test sign-in, applications, peripherals, audio-video, network change and recovery with representative users.
-
04
Group migration
Prepare identities, data and endpoints by department or work pattern, train users and complete business validation.
-
05
Operate and optimize
Observe concurrency, resources, sign-in, storage, protocol and user incidents and adjust pools and capacity.
Security and access boundaries
Centralized data does not remove the need to control identities, sessions, clipboard, printing, USB, screens and external access. Policy should fit the work: universal blocking can make the system unusable, while default openness can expose data.
- Identity and device conditionsSet authentication and entry according to location, user type and device trust, avoiding long-lived shared accounts.
- Session redirectionDefine clipboard, drives, USB, printing, audio-video and local-file access and record approved exceptions.
- Pool and data assignmentUsers receive only required pools, applications and data, with review after job changes.
- External accessUse appropriate gateways, certificates, identity and logs rather than exposing internal management services directly.
Questions specific to this solution
Should every employee use the same virtual desktop?
No. Users are classified by applications, resources, peripherals, network and data, and some may retain physical endpoints.
Can virtual desktops support design and graphics applications?
Where compatibility and capacity allow, GPU and professional resources can be planned, but real software, models and peripherals need pilot validation.
How does a poor remote network affect experience?
Latency, jitter, loss and bandwidth affect image, audio-video and input response and need protocol and access-path testing.
Is user data automatically protected?
Centralization changes location but does not replace permissions, backup, recovery, export and endpoint-redirection controls.
How can one image update avoid affecting everyone?
Images and applications use test pools, small releases, change windows, validation and recoverable previous versions.