There are ideas how to mark traffic incapsulated in RDP?

[Anton Pestov]

Idea such,

There are policies of prioritization of RDP for operation with the virtual machines (VM). Some users use disk-mapping over RDP for downloading of files from the VM to themselves on the external disk connected to port of the thin client. As soon as the user starts downloading files of large volume, they, naturally, get to a priority flow of RDP, loading all priority channel!

Whether there are any methods of separation similar (incapsulated in RDP) traffics in a separate flow? That is to leave in a RDP flow only 'picture' transmission. And all remaining, incapsulated in RDP (disk-mapping, printer-mapping and other), to select in separate less priority flow.

[Joseph W. Doherty · Accepted solution]

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

As an aside, Citrix has internal tags ("visible" to NBAT) so you can tell if the traffic is "screen scraping" vs. disk copying and/or printing, etc.

With RDP, if you have a Cisco device that does per flow policing (e.g. 6500 series) you could treat high usage flows differently.  Otherwise, you might also try looking at the packet's size.  If it's a maximum size packet it might be part of a bulk flow packet train and could be treated differently too.