Explore English articles for this topic.
Only needing fixed business applications and needing a complete working environment are different delivery requirements. Citrix DaaS supports application and desktop virtualization, but the actual choice should verify files, input methods, printing and multi-program collaboration.
Citrix DaaS can manage local or cloud resources. DaaS cannot be simply understood to mean that all desktops must be moved to the public cloud. The comparison focuses on control management, resource locations, networks, and the day-to-day tasks undertaken by the organization.
The official Citrix overview distinguishes between cloud management services and resource locations hosting application desktops. After understanding these two layers, you can determine which ones are maintained by the service provider and which ones are still the responsibility of the organization. You can also avoid thinking that the subscription includes all machines and storage.
The pilot should include real applications, different terminals and working hours. Hosted desktops eliminate some of the infrastructure work, but application licensing, peripherals, identity and user support still need to be arranged by the organization itself.
Pools are located on non-persistent desktops, and user information cannot rely solely on the current session temporary directory. The boundary between persistent data and standard images should be designed according to official management methods, and the recovery test should be passed before users can save the official results.
First confirm the service area, account qualifications, data location and organizational data policy, and then talk about network experience. Being able to open the official website is different from being able to legally purchase and meet business requirements. Overseas configuration tables cannot be regarded as cross-regional performance guarantees.
WorkSpaces is a hosted desktop product, and EC2 is closer to the underlying computing resources. The self-built method also needs to handle desktop access, identity, policy, authorization and ongoing maintenance by itself. You cannot just compare the cost of one instance.
Administrators need to prepare identities and resources according to official deployment requirements before allowing employees to connect. Downloading the client does not mean that users already have a WorkSpace, nor does it mean that their account meets the usage conditions of the region and organization.
The official fee page explains fees by product and model. When calculating, you should distinguish between licensing, running and ongoing resources. The cost implications of client disconnection, user logout and resource stoppage need to be clarified, and cannot be estimated based on the time you spend staring at the screen.
The official documentation uses Personal and Pools for persistent and non-persistent desktop needs respectively. The long-term personal environment and the standard environment allocated by session have different storage methods and operation and maintenance, and should not be selected based on the starting price alone.
Automatic scaling must be coordinated with working hours, concurrency, and session status. Success cannot be proven solely by changes in the number of machines. Microsoft outlines the direction of automatic scaling, and the actual implementation should be designed and verified according to the current functional documentation.
The cost of AVD cannot just look at the unit price of a virtual machine. Licensing, session hosts, data storage, network and management operations should all be checked at the same time, and resource utilization for pooled and individual desktops is also different.
