Skip to content

Latest commit

 

History

History
35 lines (24 loc) · 1.76 KB

Readme.md

File metadata and controls

35 lines (24 loc) · 1.76 KB

AVD \ WVD Shadowing

Providing Remote Support, Shadowing, for a WVD Session is currently not available 'Out of the Box' in AVD

To Shadow a use you can use either Remote Assist or MSTSC, on a Client Device Remote Assist is enabled by Default but needs to be enabled in a Server OS

Remote Assist

The following command is used to run MSTSC:

msra.exe /OfferRa 'Session Host FQDN' 'Users UPN':'Session ID'

MSTSC.exe

The following command is used to run MSTSC:

mstsc.exe /v:'Session Host FQDN' or 'IP' /shadow:'Session ID'

There are two additional, optional switches

  • /noConsentPrompt
    Allows you to connect to the users session without them being prompted to all the connection
    Note: If the GPO Setting Set rules for remote control of Remote Desktop Services user sessions is set to force the Consent Prompt then this switch has no effect
  • /Control
    Allows you to interact with the users session (if not set – a users session is in view mode only)

This means Support have to find out the Users UPN, which Session Host the User is connected too and their Session ID to be able to run this command

Therefore, I wrote these PowerShell scripts to automate this process

Version Description
v1.0 Initial version that only supported the Fall Edition, using a Service Principal ID to connect to the WVD Management Plane
v1.1 Updated to allow Authentication to the WVD Management Plane to be via User Account as well as Service Principal ID
v2.0 Updated to support both the Fall and Spring Releases of WVD
v2.1 Bug Fixes Applied
v3.0 Updated to Support the Use of Remote Assist as well as MSTSC
Updated to support AVD being hosted in more than one Azure Subscription
Support for Fall Release REMOVED