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
You might first see whether just fair-queue is sufficient, e.g.
policy-map sample
class class-default
fair-queue
int x
service-policy output sample
If not, then you can try this generic policy, but you'll need to match your RDP (which might use ACL and/or NBAR).
class-map match-any foreground
match
policy-map sample2
class real-time
priority percent 30
class foreground
bandwidth remaining percent 89
fair-queue
class background
bandwdith remaining percent 1
fair-queue
class class-default
bandwidth remaining percent 9
fair-queue
In sample2, be very careful what traffic you match for real-time and foreground. Such traffic shouldn't be very bandwidth demanding, and it shouldn't be delayed relative to other traffic. The background class might be used for non-time-critical bulk data transfers, e.g. FTP. Basically, most traffic will continue to use class-default except when you need or desire to prioritize or deprioritize.
