Hybrid work has evolved from a short-term response into a permanent operating model. Employees expect secure and responsive access from any location, while IT teams must control infrastructure costs, protect organizational data, support new platforms, and manage increasingly complex environments.
In this edition of Ask the Expert, we examine how Parallels RAS 21 addresses six challenges facing modern IT teams:
- Unpredictable cloud costs
- Security controls that affect performance
- Multi-domain administrative complexity
- Disruptive network interruptions
- Rapid platform change
- Secure Gateway scalability
Challenge 1: Unpredictable Cloud Costs
The problem
Cloud-hosted desktops provide valuable flexibility, but spending can become difficult to predict as organizations add users, workloads, host pools, and geographic regions.
Without sufficient visibility, IT teams may struggle to answer important questions:
- Which resources are driving monthly costs?
- Are virtual machines running when they are not required?
- Are workloads correctly sized?
- Which departments or user groups consume the most resources?
- Are scaling policies reducing costs or simply moving them?
The Parallels RAS 21 approach
Parallels RAS 21 introduces Cloud Cost Insight capabilities designed to turn Azure consumption data into more useful operational information.
The dashboard can help administrators:
- Review Azure Virtual Desktop resource consumption
- Examine costs across host pools and time periods
- Identify idle or underused resources
- Compare usage and spending patterns
- Estimate future costs based on current consumption
- Find opportunities for rightsizing and autoscaling
Why it matters
Cost information becomes more useful when it can guide action. For example, identifying session hosts that remain active outside business hours could support a revised scaling schedule. Discovering consistently underused machines could indicate that the selected virtual machine size is larger than necessary.
Expert recommendation
Review cost and utilization information weekly during the first three months after deployment. This creates an operational baseline and helps the team identify waste before it becomes embedded in the environment.
Cost data should also be reviewed after:
- Major user onboarding
- Application migrations
- Changes to virtual machine sizes
- Scaling-policy updates
- New regional deployments
- Seasonal workload changes
Challenge 2: Security That Affects User Experience
The problem
Security controls are essential, but poorly designed access processes can introduce latency and friction.
Users may experience:
- Repeated authentication prompts
- Slow VPN connections
- Additional latency when accessing applications
- Inconsistent policies across devices
- Authentication steps that do not reflect actual risk
When security controls interfere with work, users may seek shortcuts that create additional risk.
The Parallels RAS 21 approach
Parallels RAS 21 enhances multifactor authentication with contextual information that can support more intelligent access decisions.
The platform can capture a client’s public IP address during authentication and pass relevant information through RADIUS attributes. Organizations can then use location and network context to design adaptive policies.
A typical model might include:
Access context
Example policy
Trusted corporate network
Streamlined authentication
Recognized remote location
Standard multifactor authentication
Unknown or higher-risk location
Additional verification
Prohibited region or network
Deny access and alert security
Contextual authentication can be combined with:
- Windows Credential Manager integration
- Fine-grained clipboard controls
- Device and client policies
- Conditional access rules
- Centralized authentication logging
Why it matters
The objective is not to reduce security. It is to apply the strongest controls where the risk justifies them while avoiding unnecessary friction for known, trusted scenarios.
Expert recommendation
Map common user locations, networks, devices, and working patterns before configuring contextual access.
Begin with a limited number of understandable security tiers. Overly complex policies can become difficult to test, explain, and maintain.
Challenge 3: Multi-Domain Administrative Complexity
The problem
Large organizations frequently operate across multiple Active Directory domains because of:
- Mergers and acquisitions
- Geographic separation
- Business-unit autonomy
- Regulatory requirements
- Legacy infrastructure
- Transitional modernization projects
In these environments, administrators may spend significant time switching between domains, validating credentials, managing templates, and troubleshooting resources that no longer belong to the expected host pool.
The Parallels RAS 21 approach
Parallels RAS 21 introduces management improvements for complex domain structures.
These include:
- Organizational-unit browsing across domains
- Domain credential validation during template creation
- Agent-version checks before creating templates
- Notifications when agents require updates
- Recovery and reassignment of orphaned hosts
- More centralized administration of cross-domain resources
Why it matters
Early validation can prevent failed provisioning tasks and reduce time spent troubleshooting avoidable configuration errors.
Recovering an existing host instead of deleting and recreating it can also reduce disruption, particularly when the machine already contains required applications or configuration.
Expert recommendation
Before enabling multi-domain functionality:
- Document every domain and trust relationship.
- Identify the administrators responsible for each domain.
- Map organizational units used for RAS resources.
- Standardize resource and template names.
- Confirm how credentials will be protected and rotated.
- Test cross-domain operations in a non-production environment.
Challenge 4: Network Interruptions and Session Recovery
The problem
Even well-designed networks experience interruptions. Users may move between Wi-Fi and mobile networks, reconnect to a VPN, enter an area with weak coverage, or experience a temporary ISP issue.
The result can be particularly disruptive when users cannot tell whether:
- The session is reconnecting
- The application has stopped responding
- Their work has been lost
- They need to restart the client
- The problem is local or platform-wide
The Parallels RAS 21 approach
Parallels RAS 21 improves the reconnect experience across published applications and full desktop sessions.
Enhancements include:
- Clear reconnection status messages
- Visual feedback through a temporarily greyed session
- More consistent reconnect behaviour
- Preservation of session state during short interruptions
- Policy-based URL redirection during farm migrations
Why it matters
Users are more likely to wait for recovery when the interface clearly communicates what is happening. Preserving the existing session can also protect unsaved work and reduce unnecessary support calls.
Policy-based URL redirection can simplify migrations by moving users to a new farm without requiring everyone to update bookmarks or manually enter a new address.
Expert recommendation
Configure session-persistence and timeout policies according to user behaviour.
Mobile and field users may need longer reconnection windows, while users on stable office networks may not require the same session duration.
Test:
- Wi-Fi-to-mobile handoffs
- Temporary internet loss
- VPN reconnection
- Device sleep and resume
- Client restarts
- Gateway failover
- Farm migration and URL redirection
Challenge 5: Keeping Pace with Platform Changes
The problem
IT teams must continuously assess new versions of server operating systems, desktop operating systems, mobile platforms, profile-management tools, and remote-access clients.
Each new release creates questions:
- Is it supported?
- Does it require a platform upgrade?
- Will existing applications continue to work?
- Is the client ready?
- How will it affect profiles and policies?
- Can it be introduced without disrupting users?
The Parallels RAS 21 approach
Parallels RAS 21 expands support for newer server, desktop, and mobile platforms.
The release is positioned to support or prepare organizations for technologies including:
- Windows Server 2025
- Newer macOS releases
- Newer iOS and iPadOS releases
- Updated FSLogix profile containers
- Microsoft’s evolving Windows application experience
- Updated High Availability Load Balancer components
Why it matters
Earlier platform support can reduce the delay between a vendor release and production adoption. This is particularly important when a new platform is tied to security, compliance, hardware, or application requirements.
Compatibility does not eliminate the need for testing. Application behaviour, device redirection, profiles, peripherals, and authentication processes should still be validated.
Expert recommendation
Maintain a joint technology roadmap that includes:
- Parallels RAS releases
- Microsoft server releases
- Windows client changes
- macOS and mobile-platform updates
- FSLogix changes
- Browser requirements
- Certificate renewals
- Application dependencies
Schedule platform updates according to tested business requirements rather than adopting every new release immediately.
Challenge 6: Secure Gateway Scalability
The problem
As more users connect through web portals and remote clients, Secure Gateway infrastructure can become a bottleneck.
The traditional response is to add more gateway servers. Although horizontal scaling can increase capacity, it also increases:
- Compute costs
- Operating-system management
- Patching requirements
- Monitoring volume
- Architectural complexity
- Load-balancing dependencies
The Parallels RAS 21 approach
Parallels RAS 21 includes Secure Gateway performance improvements intended to increase session capacity and responsiveness.
Potential benefits include:
- Better resource utilization
- Higher concurrent-session capacity
- Reduced infrastructure footprint
- Improved web portal responsiveness
- Lower latency for browser-based connections
- Reduced hosting and operational costs
Expert recommendation
Upgrade and benchmark the existing gateway environment before adding more instances.
Measure:
- Concurrent sessions
- Processor and memory utilization
- Authentication time
- Portal response time
- Connection latency
- Network throughput
- Gateway errors
- Load-balancer health
The results will indicate whether the organization requires additional gateway servers, larger instances, revised policies, or a different distribution model.
Example Modernization Roadmap
Consider a regional financial institution with approximately 1,200 employees, multiple Active Directory domains, significant Azure spending, and users distributed across office and remote locations.
A phased Parallels RAS 21 modernization program could look like this.
Phase 1: Cost discovery
- Enable Cloud Cost Insight
- Establish a cost and utilization baseline
- Identify idle resources
- Review oversized virtual machines
- Implement initial scaling changes
Phase 2: Security improvement
- Map user locations and network patterns
- Configure contextual authentication
- Integrate credential-management capabilities
- Apply clipboard and data-transfer controls
- Pilot the policies with selected departments
Phase 3: Administrative simplification
- Document domain trusts and organizational units
- Consolidate multi-domain workflows
- Validate domain credentials during provisioning
- Update outdated agents
- Recover and reassign orphaned hosts
Phase 4: User-experience optimization
- Enable improved reconnection behaviour
- Review session-persistence policies
- Test common network-interruption scenarios
- Configure URL redirection for planned migrations
- Monitor help-desk incidents after rollout
Phase 5: Platform modernization
- Validate Windows Server 2025
- Test supported desktop and mobile clients
- Review FSLogix compatibility
- Benchmark Secure Gateway capacity
- Retire unnecessary infrastructure where appropriate
Key Takeaways for IT Leaders
Parallels RAS 21 focuses on challenges that extend beyond basic application delivery.
Financial visibility
Cloud Cost Insight can help teams move from reactive cost reviews to continuous optimization.
Context-aware security
Authentication decisions can reflect network and location context instead of applying identical friction to every connection.
Administrative efficiency
Improved multi-domain workflows and early validation can reduce manual effort and provisioning errors.
Session resilience
A clearer reconnect experience helps users recover from temporary network problems without immediately contacting support.
Platform readiness
Broader platform support helps organizations align application delivery with Microsoft, Apple, and profile-management roadmaps.
Gateway efficiency
Improved Secure Gateway performance may allow organizations to support more users without increasing the infrastructure footprint at the same rate.
Planning a Parallels RAS 21 Deployment
Pre-deployment checklist
Before upgrading or deploying, confirm that you have:
- Audited current Azure spending
- Reviewed host utilization
- Mapped user locations and access patterns
- Documented domain structures and trust relationships
- Identified frequent user complaints
- Reviewed current platform versions
- Assessed Secure Gateway performance
- Confirmed backup and recovery procedures
- Tested the upgrade in a non-production environment
- Prepared a rollback plan
Suggested priorities
Quick wins
- Enable Cloud Cost Insight
- Review idle and oversized resources
- Configure an initial contextual MFA pilot
- Enable domain credential validation
Medium-term improvements
- Consolidate multi-domain workflows
- Optimize reconnection policies
- Review Secure Gateway capacity
- Implement improved monitoring
Strategic initiatives
- Align Parallels RAS upgrades with the Microsoft roadmap
- Implement more comprehensive autoscaling
- Modernize session-host operating systems
- Optimize the user experience using operational data
Expert Q&A
We currently use an earlier Parallels RAS release. How should we approach the upgrade?
Begin by reviewing the official release notes and compatibility requirements for your exact starting version.
A controlled upgrade should include:
- Backing up the existing configuration.
- Documenting the current environment.
- Testing the upgrade in a representative non-production environment.
- Validating custom policies and integrations.
- Upgrading the required RAS components in the supported sequence.
- Updating endpoint clients where necessary.
- Testing authentication, application launch, reconnect, printing, profiles, and peripheral redirection.
- Monitoring the production environment after the change.
The required duration will depend on the environment’s size, availability architecture, integrations, and change-management requirements.
How quickly can Cloud Cost Insight identify savings opportunities?
Visibility begins as soon as sufficient consumption data is available. Idle resources, oversized hosts, and inefficient schedules may become apparent quickly, but optimization decisions should be based on representative usage data.
Review at least one complete business cycle before making major capacity changes.
Does contextual MFA require additional infrastructure?
The answer depends on the organization’s authentication design. Parallels RAS can work with existing RADIUS and identity-provider infrastructure, while contextual IP information can be obtained through supported lookup options.
Confirm licensing, integration, privacy, and data-residency requirements with the relevant vendors before implementation.
Must every Parallels RAS 21 feature be enabled at once?
No. A phased rollout is generally safer.
Organizations can begin with the features that address their most urgent problems, such as cost visibility or contextual authentication, and introduce other capabilities after testing and operational review.
Final Thoughts
Hybrid work is no longer defined simply by whether employees can connect remotely. Success now depends on whether the environment is financially sustainable, secure, resilient, manageable, and ready for continuous platform change.
Parallels RAS 21 brings together capabilities intended to address these concerns: cloud-cost visibility, contextual authentication, multi-domain administration, improved reconnection, broader platform readiness, and more efficient gateway infrastructure.
The strongest results will come from treating the upgrade as an operational-improvement program rather than a software installation. Establish measurable goals, document the current environment, deploy features in phases, and validate results against cost, security, performance, administration, and user-experience metrics.
XenTegra India can help organizations assess their current application-delivery environment, plan a Parallels RAS 21 deployment, and design a secure hybrid-work platform aligned with business and technical requirements.