MCN, Québec and La Poste du Burkina Faso
SUP-06 — Diagnosing and resolving access incidents for virtualized Citrix applications
Diagnosis of Citrix connections, sessions and applications: Citrix Workspace, StoreFront, Delivery Controller, VDA, Active Directory, Director and Studio in a conceptual published-applications architecture.
- Period
- 2015 – present
- My role
- N2/N3 IT support and systems / infrastructure administration
- Organization
- MCN, Québec and La Poste du Burkina Faso
Technologies
- Citrix Workspace
- Citrix Director
- Citrix Studio
- Citrix Virtual Apps and Desktops
- Active Directory
- Windows 10/11
On this page
- Recruiter summary
- Context, objectives and documented responsibilities
- Architecture A — Citrix Virtual Apps and Desktops
- Architecture B — User journey
- Architecture C — Authentication and authorization
- Architecture D — Citrix incident diagnostic tree
- Resolution method
- Session management, documentation and demonstrated skills
Recruiter summary
SUP-06 makes visible a Citrix virtual-applications support method based on documented work at the MCN and La Poste du Burkina Faso: connection-incident diagnosis, user-session tracking, access-issue resolution and application-execution issue resolution. It first locates the break in the user journey — Workspace, authentication, StoreFront, Delivery Controller, VDA or application — before choosing the relevant check and tool.
Context, objectives and documented responsibilities
A Citrix application may be inaccessible for different reasons: the client does not connect, user authentication fails, the app is not enumerated, the session does not launch, the VDA is unavailable, or the application freezes after launch. Treating every symptom as one failure delays resolution. The objective is to qualify the symptom, isolate the component and restore service within authorized scope.
Documented work: connection-incident diagnosis; user-session tracking; access-issue resolution; and application-execution issue resolution.
Architecture A — Citrix Virtual Apps and Desktops
| Component | Support role |
|---|---|
| Citrix Workspace | User client to access the store and start a resource |
| StoreFront | Authenticates/guides store access and presents authorized resources through configured flow |
| Delivery Controller | Enumerates and brokers resource launch to available VDAs |
| VDA | Agent on application server that hosts user session and published-app execution |
| Citrix Director | Session/state view and operational diagnostic information |
| Citrix Studio | Administration/configuration tool; changes remain subject to authorized procedure |
| Active Directory | Identity, groups and authorization contributing to published-resource control |
Architecture B — User journey
- User opens Citrix Workspace.
- Authentication follows configured mechanism and Active Directory identity.
- StoreFront and Delivery Controller enable resource enumeration.
- User selects a published application.
- Controller brokers session establishment on a VDA able to receive the request.
- VDA runs the application in the user session.
Architecture C — Authentication and authorization
Active Directory contributes user identity and groups that may control published-resource access. An application not being visible may relate to authorization, the published resource, enumeration or user context; it alone does not prove a Workspace-client issue. Group, permission or resource corrections remain subject to organizational rights and process.
Architecture D — Citrix incident diagnostic tree
Resolution method
| Symptom | Relevant checks | Diagnostic tools/components |
|---|---|---|
| Cannot connect | Workspace, store access, identity and authentication | Citrix Workspace, StoreFront, Active Directory, authorized network checks |
| Application not visible | Enumeration, groups and resource authorization | StoreFront, Delivery Controller, Active Directory, Citrix Studio under authorized access |
| Launch failure | Resource state, VDA availability and session brokering | Delivery Controller, VDA, Citrix Director |
| Disconnected session | Session state/history, reconnection conditions and VDA | Citrix Director, VDA and user context |
| Unresponsive application | Session, app process, VDA state and app symptom | Citrix Director, VDA, application and specialist team when required |
| Permissions | Identity, groups and published-resource access | Active Directory, StoreFront, Controller, authorized IAM procedure |
Resolution follows the check that isolated the fault. It does not automatically imply disconnecting/resetting a session, changing Studio or changing Active Directory. Outcome is validated with the user and documented in the designated tracking tool.
Session management, documentation and demonstrated skills
Director supports session-state tracking and correlation between user symptoms and Citrix components. Useful documentation retains observed message, time, resource, scope, completed checks, implicated component, authorized action and validation — without publishing usernames, named screenshots or production identifiers.
| Area | Demonstration |
|---|---|
| Citrix Virtual Apps and Desktops | Understanding Workspace, StoreFront, Controller, VDA and published-application journey |
| Citrix Director | User-session tracking and incident diagnostics |
| Citrix Studio | Understanding administration-tool role without claiming production changes |
| Active Directory | Diagnosis of identity, groups and rights linked to resource visibility |
| N2/N3 support | Symptom qualification, focused escalation, controlled resolution and user validation |
| Documentation | Non-sensitive technical evidence and reusable solution records |
- Documented work covers Citrix connection, session tracking, access and application execution.
- Four diagrams originate from Mermaid sources and are exported to SVG.
- No Citrix site, server, VDA, store, AD group, resource, URL or real topology is represented. Capacity, availability and timing information is not published to protect the operating context.