Citrix in India — Virtual Apps, Desktops & ZTNA

Application delivery exposes selected applications, while a desktop provides a broader working environment. Choose based on user tasks, application compatibility and administration rather than assuming every user needs a full desktop.

Not necessarily. The selected architecture can still depend on application hosts, identity, connectivity and other components. Document who hosts and maintains each part of the design.

Real applications, user profiles, printing, peripherals, connection conditions and concurrent usage. Measure the workflow from sign-in through normal work, not only the initial desktop connection.

Define who may initiate sessions, which devices are accessible and how consent, authentication and logging work. Separate attended support from unattended access. Restrict permissions to the support task and review access when staff or suppliers change.

Evaluate supported devices, network conditions, administrator controls and the actual support workflows. Test session initiation, file transfer if required, permission limits and disconnection. Check that users understand how to identify and approve a legitimate support session.

Confirm licensed users, concurrent sessions, managed devices and required administrative capabilities. Check renewal terms and allowed use under the current plan. A free or personal-use offer should not be assumed to cover a business support operation.

Start with your current environment, the business problem, quantities and intended timeline. List technicians, supported devices and expected concurrent sessions. Specify attended or unattended access and authentication requirements. Define user consent, recording where applicable and access-review owners. Request a written scope that separates product entitlements, implementation work and ongoing support. Keep passwords, licence keys and sensitive customer data out of an initial enquiry.