1Y1-200 · Question #74
Scenario: An error is displayed in Citrix Director when a Citrix Administrator attempts to shadow a user connected to a desktop hosted on a server OS machine. Shadowing does NOT start. What is the…
The correct answer is A. Remote Assistance is NOT enabled on the server OS machine. See the full explanation below for the reasoning.
Question
Options
- ARemote Assistance is NOT enabled on the server OS machine.
- BCitrix Receiver is NOT installed on the administrator's workstation.
- CThe administrator does NOT have the Help Desk role in Citrix Studio.
- DRemote Desktop is NOT configured on the administrator's workstation.
How the community answered
(36 responses)- A83% (30)
- B8% (3)
- C3% (1)
- D6% (2)
Community Discussion
7
Samuel O.Apr 30, 2026A is correct. Shadowing in Citrix Director relies on Windows Remote Assistance under the hood, so if Remote Assistance is not enabled on that server OS machine, Director has no mechanism to actually initiate the session and throws the error right there before it even starts.
Imani T.Feb 25, 2026A is the right answer. Shadowing in Citrix Director relies on Windows Remote Assistance under the hood, so if Remote Assistance is not enabled on the server OS machine hosting that desktop, Director cannot establish the shadow session and throws an error before it even starts.
Carlos M.Mar 22, 2026C is the trap here because your first instinct is to blame permissions when shadowing fails, but the Help Desk role controls what the admin sees in Director, not whether the underlying shadow session can actually launch. The real culprit is A, Remote Assistance not being enabled on the server OS machine, because Citrix Director shadowing on a server OS VDA depends on Windows Remote Assistance to initiate that session.
Hiroshi T.May 4, 2026Correct on A. Citrix Director relies on Windows Remote Assistance (not Remote Desktop) to broker the shadowing session, so if Remote Assistance is disabled via Group Policy or the system properties on the server OS machine, Director throws that error before the shadow can even initiate, per the Citrix Director 7.x documentation on session shadowing prerequisites.
Kemal J.Mar 3, 2026Windows Remote Assistance powers Director shadowing, so yeah, A is your culprit, not some role assignment.
Grace U.Mar 16, 2026I went straight to C because "no permission" errors always feel like a role thing, but then I remembered that Citrix Director shadowing on a server OS machine actually hands off to Windows Remote Assistance under the hood, so if that feature is disabled on the machine itself, Director throws an error before permissions even matter, which points right to A.
Kemal J.Mar 17, 2026Right, and if you pull a CDF trace with the Shadowing and RemoteAssistance modules enabled you will see it bomb out at the WRA handoff long before any Director RBAC check even runs, which is why candidates who memorize "permission error equals role problem" get burned by this question every time.