Qos DSCP value 46 gone, after enabling Remote Desktop Services on Windows 2012 R2 Standard

Hi,
After installing a clean Windows Server 2012 R2 with
all Windows updates I have setup Policy-Based QoS for tagging defined traffic,
in the test case all traffic to one specific ip address. Whireshark logging
displays the correct configured (46) dscp value so the group policy is
working fine. After installing Remote Desktop Services the Policy-Based QoS is
still in place but Wireshark results that the value is 0.
Can somebody explain why this happens and how to solve
it?
Regards, Edward

Hi Edward,
Thank you for posting in Windows Server Forum.
Did you find any related error for your case?
By default, Windows traffic has a DSCP value of 0. Network routers use the DSCP value to classify network packets and to queue them appropriately. The number of queues and their prioritization behavior needs to be designed as part of your organization's QoS
strategy. For example, your organization may choose to have five queues: latency-sensitive traffic, control traffic, business critical traffic, best effort traffic, and bulk data transfer traffic.
More information, please see:
Policy-based Quality of Service (QoS)
http://technet.microsoft.com/en-us/library/dd919203(v=ws.10).aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

High availability SQL Server requirements for Remote Desktop Services in Windows Server 2012

Good night,
Thanks for reading this question, I do not write much English.
I am implementing Remote Desktop Services in Windows Server 2012, I need to know the size of the database to create and feature on the .mdf and .ldf, I searched in different microsoft link but I have not received a response.
Kindly appreciate your cooperation and attention.

Hi Alejandro,
I am implementing Remote Desktop Services in Windows Server 2012, I need to know the size of the database to create and feature on the .mdf and .ldf
If you want to know the size requirements of .mdf abd .ldf files, since they are parts of SQL database, I suggest you refer to SQL forums below to get more professional support:
https://social.technet.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlgetstarted
https://social.technet.microsoft.com/Forums/sqlserver/en-US/home
In addition, here are some articles regarding RDS deployment for you:
Remote Desktop Services Deployment Guide
https://technet.microsoft.com/en-us/library/ff710446(v=ws.10).aspx
Remote Desktop Services (RDS) Quick Start Deployment for RemoteApp, Windows Server 2012 Style
http://blogs.technet.com/b/yungchou/archive/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style.aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Guideline of installing remote desktop services in window server 2012 r2

Hi,
I tried to install remote desktop services in window server 2012, I joined my current domain ( in window server 2003).
During installation, it require me to promote my server to domain controller? This is one of the requirement for remote desktop services?
If I didnt join any domain, it prompt me I must join a domain.
Anyone can advise me? provide me a steps by steps guide will be perfect!
Thanks

Hi GP_IT001,
In your current network do you currently have a domain controller? You mentioned that you "had" a Domain Controller running Windows Server 2003.
Am I correct in thinking that you no longer have this server?
As this article mentions:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/f3d0543a-edab-4eb2-8360-3658a3351bb0/licensing-issue?forum=winserverTS
You will need a domain environment which means you'll need a server that is a domain controller, and I believe that it will also need to operate Windows Server 2012 or above. You could, if you wanted, setup a new server (virtual or physical) as a domain
controller and use that if you wish.
Best regards,
Please remember to mark the replies as helpful if they help, or as answers if they answer your question. Please also unmark the answers if they provide no help.
Zach Roberts
Independent Microsoft Community Support Advisor
Disclaimer: I don't work for Microsoft. Any advice given is my own and does not represent Microsoft.
Follow me on Twitter:
@WindowsZach

How to use Remote Desktop Service in Windows Azure

Good day
Hi! im kinda newbie when it comes to windows azure, I would like to ask if how can we use the RDS CAL in windows azure?

Hi,
Please visit the URL below for detailed instructions on using/configuring RDS CAL.
http://blogs.technet.com/b/keithmayer/archive/2013/09/04/step-by-step-remote-desktop-services-on-windows-azure-a-cost-effective-alternative-to-desktop-as-a-service-part-2.aspx
Regards

How enable remote desktop gateway manager server 2012 essentials

how enable remote desktop gateway manager

There is a DISM command,
dism /online /disable-feature:Gateway-UI
http://support.microsoft.com/kb/2472211/en-us
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

How do I remote control a user in remote desktop services in Windows Server 2012?

Hello,
we currently operate in a 2008 R2 environment with the majority of clients connecting to our terminal servers. We use the remote control feature in terminal services manager to connect to a users session when a user phones our helpdesk with
a question / issue.
Just today I've installed 2012 server on a hyper-v virtual machine to have a play with it. I've installed the Remote Desktop Services and noticed this remote control feature is gone. I can still log off or send a message to a user, but I can
no longer remote control their session.
I've seen one or two other posts stating this feature has been removed completely.
So, a couple of questions:
1. How on earth do I "shadow" or connect to a users session now?
2. If I have to go third party to get this functionality back, what's the best software on the market for this and does it support remote connecting of users who have their RDP session span multiple monitors? (2008 R2 doesn't)
3. Will Microsoft ever bring this feature back? as at this stage I doubt we would move to 2012. This is the one feature that is crucial to the day-to-day running of our helpdesk.
Cheers.

A large percentage of our IT support business is through remote management. Most of our large enterprise customers are Terminal Server environment (now called Remote Desktop - why does Microsoft have to change EVERYTHING - how would they feel if I changed
the colour of the sky from blue to red just because I could?).
Last week, after much expense to the customer (and realising that there WOULD be some cosmetic headaches to contend with Server Management) we installed a new "Remote Desktop Server" for them and shifting them from 2003 - a big leap so we discovered.
During deployment it came as a HORRIFIC surprise that we could not remote control user's sessions!
Yes, we ARE to blame for not fully realising the cock-up Microsoft has made for us. We should have fully researched every detail of what changes they made and what they have robbed us of.
Firstly, the removal of the ability to fully manage user's sessions came as a HUGE blow!
The remaining multiple issues that followed (including the hugely cumbersome and SLOW way of accessing user's sessions and the false information that the console was reporting users logged in when they had already logged out) suddenly resulted in us decommissioning
the new 2012 installation in favour of a 2008 R2 installation.
Some may ask; Why not use "Third Party" apps to counteract the issue? Firstly; why spend MORE and why use a third party app that "is as" cumbersome to use just because of a freaking feature that Microsoft deemed a "security risk" - for G.D sake!
We have now been directed by management to convince customers that a move to 2012 is NOT recommended - good choice boss, I love you!
The question is; will Microsoft re-implement this feature and fix Server Management performance/accessibility in a future release before 2008 R2 is no longer available? Probably not - it looks like their stubbornness to forge ahead with their craze mind-set
of transforming their products into something that is now annoying millions (including their bloody push towards everything-cloud which NONE of our customers want anything to do with).
Microsoft! Get us back on to your side and take a step back, take a deep breath and listen to consumers!

Windows 2008 R2 Remote Desktop Service Role pickup 2012 RDS License Server.

I am installing Citrix onto a Windows 2008 R2 server as part of this I need to setup the RDS Role on the same box and then point it to the Windows RDS License server.
Our plan is to have a Windows 2012 License server for RDS Licenses i.e. install 2012 RDS Licenses.
I was wondering if it was possible for a 2008 R2 RDS role to pick up 2012 RDS Licneses from a Windows 2012 RDS Server?
Many thanks,
Steve

Hi Steve,
Thank you for posting in Windows Server Forum.
Yes, agree with TP’s comment. You can also check below interoperability matrix link for details.
RDS and TS CAL Interoperability Matrix
http://social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Enable Remote Desktop Connections with PowerShell

What is the easiest way to enable remote desktop connections on Windows 7, with powershell?

Use Shay Levy's "Remote Registry PowerShell Module", and modify the value of the "fDenyTSConnection" value in the
key "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" on the remote box to "0"
The Windows 7 box will need to be rebooted before it will take effect.
See http://oreilly.com/windows/archive/server-hacks-remote-desktop.html
Or, grab Michal Gajda's script "Enable-RDP.ps1" in the gallery :)
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer
My Blog: http://unlockpowershell.wordpress.com
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ("6B61726C6D69747363686B65406D742E6E6574"-split"(?<=\G.{2})",19|%{[char][int]"0x$_"})

Enabling remote desktop access to a simple windows 2012 datacenter edition server

Hi,
I am a complete noob to server administration. I installed a windows 2012 server initially as a workgroup. All i need is to enable a user to remotely access my server(using remote desktop). The firewall that I use is Gibraltar.
I read that to enable remote desktop services my server has to be part of a domain. So i promoted my server to a domain name controller. Using active directoty I added a user to the domain. I also read that to make remote desktop more secure, I have to request
the user to login through a VPN.
Now here is where I am completely lost. Do i really need to move my server to a domain, if the user just wants access to this server and nothing else? Should i restrict remote desktop access only through VPN
and if so, how can i do that? Further, the server dashboard gives me notifications about 'remote desktop licensing' not configured. We got the software as a campus licensing and I am not sure how to configure the remote license server. Any opinions are highly
appreciated.

If you're just trying to setup this to allow administration access then I don't believe you need it to be a member of a domain. There's a difference between allowing remote desktop access for administration, and setting up full terminal services access for
multiple users. The latter requires a lot more work and licensing unlike the former.
To simply allow admin access, open an explorer window and right click on Computer, then select properties. In the System window that appears, click Remote settings on the left. Now in the bottom half of the window select "Allow remote connections to this
computer" and leave the option requiring NLA in place. Click Select Users..., you'll see that the administrator user already has permissions to connect, so if you're only planning to connect with that then you're finished, otherwise find those users you
want to grant access.

Install Remote Desktop Services Failed on Windows 2012 Server

I understand RDS is not recommended on DC due to security consideration. However since I want to play it at home, it is not much a concern. Such scenario works fine on Windows 2008 R2. But on Windows 2012, the RDS (session-based, have not
tried VDI, but expect same result) installation always fails and is incomplete on DC.
In \Administrative Tools\Terminal Services, I only have RD Licensing Diagnoser and RD licensing manager. The remote desktop service management service cannot be started (Error code: 0x88250001). Is there any extra configuration needed for RDS
working on Server 2012 DC or before the installation? Thanks.
Update: this issue has been solved in Windows 2012 R2 Server. According to
http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
"Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller. In addition, we published
guidelines for how RD Session Host could be used without the RD Connection Broker."
The guidelines (http://support.microsoft.com/kb/2833839/en-us) primarily apply to Windows 2012 Server.

Asinine. Simply Asinine. Microsoft took it out because of $GREED$.
RemoteDesktop has become so popular, they had to break it to make more money. Thats why they discontinued SmallBusinessServer.   If this practice is so tabooo... Why did MS go the opposite direction with SBS 2011 Premium Cal's? SBS2011
had DC, Exchange, RDS and Sharepoint,SQL, RemoteWebWorkplace, OWA all working in perfect harmony. It is an untrue statement then, that it was "allowed but not recommended"
Now you by Server2012 (core + two virtual) and its not enough for all this.
You need at least another $700 for another sever licence to have it all
and who knows if SQL will run on a DC, or Exchange, or R-DERP server. Another reacherous bridge to cross.
By far, the absloute worse release since Millennium. The product is not ready for production, we broke our rule of waiting until the first SP1 upgrade for this and Exchange 2013. Problems with USB drivers and networking running extreamly slow.
Our 2003 SBS server was at least three times as fast, and this server has SAS and SSD drives running. It can't get out of its own way, and IE10 is the most unstable piece of crap to come out of Redmond. Open wide and swallow - Mother Microsoft
knows whats best for you. YOU WILL EAT OUR SLOP AND LEARN TO LIKE IT.   Server2012 AKA "METRO-SERVER"
Now here I sit after 50 Hours back to back setting up a new R-DERP server 2012, AD, Have my RDP licences in my hand at $100 each, and WTH does Microsoft care if I install it on my DC. ITS MY DC. And the cost savings versus the "risk" was
previously MY decision.
Sure, I can install a couple of Virtual HyperV sessions but they are so tempremental to a power-outage in a small business its not worth it. I have to double up my server hard drive resources, buy a $800 battery backup unit and make sure to attach
the cable, and even then, if that Bi**H does not shut down properly, one bit goes awry in a VHD or VHDX file and you are screwed. Restore from lastnights backup and forget about todays work. Not to mention it will probably take a half day to try
to fix it, then recover it then tell the 30 users they lost a days worth of work.
HYPER-V is for test servers and has no place in a small (micro) business environment. 5-30 users.
Microsoft's solution, buy another server. Need Exchange? Buy another server or take the risky cheapskate route and spin up some VHD's. Might as well put a gun to your head and play russian roulette, at least you know you have a one in six
chance of failure. With MS, its a 100% failure for a dirty shutdown power loss, motherboard blows, memory goes corrupt in a few years, your conventional method of recovery is gone, and you have some upchucked VHD file to try to recover some of TODAYS
data from.
Screw server 2012 forever.
I will sell 2008 and SBS2011 Premium unitl it rots in hell like XP (of which there is NOTHING wrong with for the average, WORD, EXCEL, OUTLOOK and QUICKBOOKS that all SMB's use. Its MS $GREED$ Grab the world by the B**ls and squeeze with all
your might to squeeze every dime you can out of *SMB* because big business is going to run thier 2003 Exchange and 2008 servers into ground before they switch to this garbage.
YOU CANNOT INSTALL EXCHANGE 2013 on DC , OR on R-DERP server.
Go buy another server license and server or MOVE TO THE CLOUD and get fleeced every month.
I have 30 DC/R-DERP/Exchange and SBS2011 Premium servers all running for years in perfect harmony, locked down with security so the users can't even WIGGLE with something they are not supposed to work with. They get their apps, cannot install anything
and all these servers are running just fine behind the firewall and perfectly save. The track record of this combination is 100% stable and is up 24/7/365 with no problems. Do yourself a favor and throw this 2012 into the river, you don't need
any weights because it is LEAD and will sink to the bottom by itself.
Why, you ask? Official is "Its for your protection" The real reason? To sell you more $700 server licences.
Maybe for SMB, we start selling Linux NAS Servers, host the Exchange in the cloud and be hearded like cattle to the Microsoft slaughterhouse. One way or another, you are going to bleed.    A little each month to move to the cloud, or
a small fortune if you want to have it in house. Microsoft wants it to be more expensive to have in house. No more buying a server and running it for six years before you upgrade. They can't have in house servers competing with their cloud,
and small businesses are the low hanging fruit ripe for the pickin'.

Windows 2012 R2 Active Directory Domain Services and Remote Desktop services Role on the same server.

Findings:
Currently, Windows 2012 R2 AD DS role and RDS With Broker services can only seem to coexist properly in a new domain not an existing domain. Any attempt to add to an existing domain causes internal database user access denied issues and any attempt to
adjust rights and circumvent is dubious at best.
The escalation technician said it best. Out of 50 clients that want to do this, they end up not being able to help 5 right off the bat for whatever reason. As for the other 40 they might be able to help by running reports, adjusting rights and trying to add
the roles until it works. This can end up being a 20 day process. Basically they are playing whack-a-mole with user rights and permissions until something sticks.
We tried creating an OU where any other domain policies would not be inherited to see if that was the issue, a fresh install with different sequence of adding the Roles, no effect.
Given the errors I witnessed when running procmon and then trying to add the roles, the NT System and the Windows Internal database user had access denied issues on 100+ registry keys when trying to add the roles. After that the system is not behaving normally.
The errors displayed almost mirror the errors that would occur on Windows 2012 when those two roles would be added which of course is officially NOT supported on that system.
This blog needs serious revision:
http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
This is the excerpt from that blog: Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller. In addition, we published
guidelines for how RD Session Host could be used without the RD Connection Broker.
Microsoft Support was curteous and helpful and they were the ones who advised cutting our losses, which mirrored my hunch after seeing what was transpiring in the system. They refunded my money for the support call.
For me, it was an opportunity to find out if there was any way to configure Windows 2012 R2 in the Same manner that it was setup as Windows 2008 R2 and lay that to rest. The coexistence is poorly implemented. It is as if there was a reaction from all the deprecation
of bread and butter features such as shadowing in TS and the coexistence of AD DS and RDS to where those features were re-added haphazardly. (I have no complaints on shadowing on Windows 2012 R2 it works, just do not like having to go to server manager to
use it).
I opted for virtualizing the Domain controller to eliminate the incompatibility issues and that is what I will be doing from now on. I found free solutions for backing up and reporting for virtual machines as well as the suggested procedures for configruing
a Domain controller as a virtual machine on a Hyper-V environment and I will be sticking to those. Thus far the setup has been operational.
I am not allergic to virtualization, but for really small setups it adds additional time and considerations but if that is how it has to be done, so be it. Windows 2008 R2 days are numbered and since we can usually squeeze 5-7 years on quality server equipment,
buying a Windows 2008 R2 setup now is a borderline disservice in my opinion.
Hopefully someone finds this useful and saves some time.

Hi,
Thank you for posting in Windows Server Forum.
Do you need any other assistance?
Based on your description, you are describing your story of successfully implementing RDS server with AD role and more regarding all RDS related scenario. For shadowing feature, you can use with command also. Below is the syntax to shadow a session.
mstsc /v:<ServerName> /shadow:<SessionID>
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Remote Desktop Service.

Hi,
last 1 year i was using remote desktop connection from my office to home, (work from home using public IP with RDP service ) but now i am getting an error message. I can able to login into the system everything work fine, before getting to the desktop i
am getting this error.
" Because of a protocol error, this session will be disconnected. please try connecting to the remote computer again. "
Thanks in advance.
With Regards, Santo Antony

Hi Ruchir,
Thank you for posting in Windows Server Forum.
Yeah, agree with "DJamesS"; if you need RDP session for administrator usage then you don’t need any extra RDS CAL. But if you want more than 2 RDP connection simultaneously then you need to install RDS CAL (per device or per user; as per your requirement).
Also you need to activate the license server before installing RDS CAL. For additional details, you can go through beneath thread.
Enabling more Remote Desktop Connections in Windows
2012
For RD Licensing configuration you can also refer this article.
Hope it helps!
Thanks,
Dharmesh

Users not showing in Terminal Server Under Remote desktop services manager and Task Manager

Hi All,
I have a problem here in Terminal Server. I can not see the users logged in to Server but i know users are accessing the files and currently working.
1. From the Task Manager-- Show processes from all users displayed all the processes accessing by users.
2. From the Task Manager-- From Users Tab--No users list at all
3. From the Command Prompt- Query users-- No information
4. From the Remote desktop services Manager-- used with IP/Host name-- Still can not see the users list and processes. So i can not kill the session if needed.
Enviroment:
TS CALS 20 currently accessing 15 users
VM-WARE GUEST: 2008 RS Terminal Services/Remote Desktop services installed
Windows up to date-- Just updated last month
Problem is here for long time. Just couldn't find the time to trouble shoot.
UMESH DEUJA MCP,MCTS,MCSA,CCNA

Hi,
Thank you for posting in Windows Server Forum.
As you have tried many steps, I suggest you to try below command line and power shell command if successful in your case. Please try below command with Admin access:
qwinsta /server:<servername>
To kill a session use rwinsta to delete the session specifying the ID number:
rwinsta /server:computer01 3
Here's the list of command line tools for Remote Desktop Or, you can use PowerShell:
Get-RDUserSession and Disconnect-RDUser
Please check the list of Power Shell command from
this link.
Hope it helps!
Thanks,
Dharmesh

[Forum FAQ] Available updates for Terminal Services/Remote Desktop Services

The table summarizes the available hotfixes and updates for issues that can occur in Terminal Services/Remote Desktop Services.
Terminal Services (Remote Desktop Services) in Windows Server 2008
KB
2312539
Remote Desktop Services (Terminal Services) on Windows Server 2008 R2 SP1
KB 2601888
Remote Desktop Services in Windows Server 2012
KB 2821526
Remote Desktop Services in Windows Server 2012 R2
KB 2933664
Thanks for the suggestion of
armin19.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

I'm interested in that issue as well as a lot of our Clients would like to deploy Adobe Creative Cloud apps in their Enterprise. As I'm a Citrix virtualization engineer I'd like to have an official Statement from Adobe whether or not their products can be licensed and installed on either Citrix XenDesktop (formerly XenApp) Servers and/or virtual Desktops (VDI Environment). This questions Needs answering from both a licensing as well as technical Point of view. So please Adobe, share your knowledge with us.
Alex

Unable to enable remote desktop (XDMCP) after jumpstart Solaris 10 U9

Hi,
I have installed Solaris 10 U9 using the jumpstart.
I would like to have enabled remote desktop (XDMCP) after installation.
But Solaris 10 U9 has this option disabled:
# ps -ef | grep dt
root 858 450 0 04:56:05 console 0:00 grep dt
root 730 1 0 04:41:39 ? 0:00 /usr/dt/bin/dtlogin -daemon -udpPort 0
I have copied dt config files to /etc:
# mkdir /etc/dt/config
# cp -r /usr/dt/config/* /etc/dt/config/.
Then in /etc/dt/config/Xconfig I've uncommented and added port number:
Dtlogin.requestPort: 177
After reboot this change in Xconfig doesn't enable XDMCP.
Do you know what to change to have XDMCP enabled after jumpstart installation?
Thanks,
Daniel

By default xdmcp will start on udp port 0. normally it should listen on 177.
Try this. you should be able to login through xdmcp after this.
#svccfg -s cde-login setprop 'dtlogin/args=""'
#svcadm restart cde-login

Qos DSCP value 46 gone, after enabling Remote Desktop Services on Windows 2012 R2 Standard

Similar Messages

Maybe you are looking for