Just discovered a problem trying to shadow thin client terminals on newly installed 2012 Server R2.
In Server Manager, if I select Shadow, I receive the message "The session ID does not specify a valid session"
If I run the powershell command mstsc /v:<server name> /shadow:<session ID> I get the same.
When I list the RDP sessions it displays them as session ID 6 and 7
If I run the mstsc command line and use session number 4 it actually will connect to the desired terminal???
Somehow it looks like the incorrect session ID is being reported.
Anyone else experience this??? Very frustrating....