Remote Desktop Services Default Connection issue

when i am login to Remote Desktop Services Default Connection issue i was unable to see icons which were displaying in internet explorer. It is showing blank. please give me solution as soon as possible.
i have the screen shots of both IE and mozilla
thank you

You can attach screen shots here if you post a reply to your original question. The attach form appears below the textbox where you type your reply.
Could you describe the steps to reproduce the problem. First you make a remote desktop connection, then you run Firefox on the remote host, and the problem is in Firefox on the remote host? If Firefox on the remote host accessing a site on your LAN, or on the web, or using a protocol other than http (such as file or ftp)?

Similar Messages

Remote Desktop Services Collection Creation Issue

Hi Guys;I've set up an RDS environment consisting of 5 servers "Session Host, Gateway, Webaccess, License Server, & connection broker"The Webaccess and the GW servers are in the DMZ, all the required ports are open on the FW, and Windows firewall is disabled on the all servers "service is on though". All servers are on 2012 R2, SQL 2012 Express is installed on the Licensing server. Everything went smooth till the Collection Creation phase, where I'm getting the following:1. Warning: CorpRDSHP11 "Session host server" The property UserAuthenticationRequired is configured by using Group Policy settings. Use Group Policy Management Console to configure this property.2. When I access the WebAccess through the link "https://webaccess.domain.com/RDWeb/";, I don't see anything under Current Folder!Please help.Thanks.
This topic first appeared in the Spiceworks Community

You can attach screen shots here if you post a reply to your original question. The attach form appears below the textbox where you type your reply.
Could you describe the steps to reproduce the problem. First you make a remote desktop connection, then you run Firefox on the remote host, and the problem is in Firefox on the remote host? If Firefox on the remote host accessing a site on your LAN, or on the web, or using a protocol other than http (such as file or ftp)?

Adobe Acrobat X on Server 2003 (using remote desktop services)

Hi guys,
I need to purchase a copy of Adobe Acrobat for Windows Server 2003 for use in Microsoft Dynamics GP 2010, as well as everyday Acobat read/write tasks. There will be about 4 or 5 simultaneous users connecting to the server using RDP (via Windows Vista and 7).
My question is, will a single copy of Adobe Acrobat X Standard suffice or work properly on Windows Server 2003 for all users?
I can't seem to find any information on Adobe Acrobat X and terminal services (or Remote Desktop Services).
Hope I've made sense, and any help will be appreciated
Thanks
-Rhydz

Hi,
What Word prompts when user attempts to login with the original account? Any error messages?
Since the feature will work if you create a new account, have you ever compared the property of these two accounts? Maybe the security or permission setting during the creation process?
We lack testing environment here for this kind of issues, and we have another dedicated support teams in
Microsoft Office 365 Community. I would suggest you to post there, where you can get more experienced responses:
http://community.office365.com/en-us/f/default.aspx
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Thanks,
Ethan Hua CHN
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer

Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer, And when Installing network printers from the domain controller it reports it cannot connect to printer. I can ping all
network devices. I can connect to the internet.
On boot I get a netlogon 5719 error followed by service control manager errors 7023,7001 and a group policy error 1129.
Clients can connect to the remote application and RDP operates to connect to the server internally and externally.
The domain controller is another server 2008r2 box. I have scoured the internet but have not found any solutions that work yet.

Hi,
After referring to your post, it can be identified that the issue which you are facing is mostly due to some network issue in your environment. Please recheck your network connection issue between computer and domain controller.
Can you able to ping with IP address and also with fully qualified name of a domain controller in the users' and computers' domain. If it fails states that name resolution issue with computer and domain controller. Are you using MS DHCP Relay agent then there’s
available Hotfix for the particular Event ID. Please go through this KB 2459530 to fix the error event ID.
As per the net logon error 5719 which you are facing states that the client component of Netlogon was unable to locate a DC for the domain it was trying to perform an operation against. Below is one of the reason. If this is being logged on a DC and the event
refers to the DC's own domain, something might be preventing the client component of Netlogon from starting a network session (to itself or to another DC in the domain). The following event 7001 & 7023 states start & stop operation service. Please
go through beneath article for more details.
1. Event ID 5719 is logged when you start a computer
2. Netlogon 5719 and the Disappearing Domain [Controller]
3. Event ID 1129 — Microsoft-Windows-GroupPolicy
Hope it helps!
Regards.

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!

Server 2012: Remote desktop licence manager not issuing licences

Hi,
I am battling with an problem which i cannot seem to resolve and no other forums actually come to a conclusion on how to resolve this problem!
I have a windows server 2012 server which is NOT part of a domain.
I have installed Remote Desktop Services and also installed the Remote Desktop License manager and i just cannot get the license manager to issue cals when users connect remotely via RDP
I have installed an extra two CAL's and tried using them as both a "Per User" and also "Per Device" but still does not work.
I have now run out of my grace period and cannot connect to the server at all
I have also tried changing some gpo's with no luck,
Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
"Use the specified RD license servers" = myservername
"Set the Remote Desktop licensing mode" = Per User
How can i fix this?
Thanks

Hi,
Thank you for posting in Windows Server Forum.
Have you seen that you have activated RDS License server before installing CAL?
Please check that the License Server should be part of ‘Terminal Server License’ group in Active Directory Domain Services. You can also configure RD License server manually by powershell commmand. Please check below article for information.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
In addition, please install below Hotfix and verify the result.
No RDS license when you connect to an RDS farm in Windows Server 2012
http://support.microsoft.com/kb/2916846
Hope it helps!
Thanks.
Dharmesh Solanki

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

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'.

Remote Desktop Services that require Native SQL Server Client in Windows Server 2012?

I have somehow gotten really confused on this.. Is the Remote Desktop Connection Broker the only Remote Desktop Service that requires the SQL Native Client to be installed in Windows Server 2012 (r2) ?

Hi,
If you plan on configuring RDCB in HA mode then the SQL native client is required. The other RDS role services do not require it.
-TP
Is High Availability Mode enabled by Default?

2008 R2 Remote Desktop Services Problems With Older RDP Clients

I recently deployed a new 2008 R2 server to serve as a Terminal Server (Remote Desktop Services) for about 30 people. The new server is replacing a 2003 server. I expected the new machine to be a considerable upgrade and was looking forward to happy people
and less problems. Reality is I am finding several unexpected headaches - discouraging considering the amount of money we have spent on the new machine.
Most of the users connect via HP thin clients, they are the T5510, T5520 and T5530 thin clients. What I have found is performance issues when connecting via these thin clients. I believe the RDP client on these thin clients is RDP 5.5 or earlier. And I do
not believe it is possible to upgrade the RDP client version on the thin clients - I guess they are to be seen as "disposable".
The performance issues are: black blocks appearing when connected - and I have deselected bitmap caching - makes no difference. When typing in certain places the display of the typed characters could not keep up with the user. And lastly I have a weird thing
that just popped up today; where if the user goes to Google it freezes up their entire environment - I cannot even remote control the user/session - why this came up today and was not a problem before I am not sure.
With all of the above issues I have found that the problem goes away or does not exist if I connect to the server using an RDP client on an XP or 7 computer. So I have to conclude the RDP client is the problem.
Does anyone have information on this? Is there anything I can do as far as configuration on the server to allow me to use these older RDP clients? Do I have any alternative other than buying new thin clients?
thanks!

From your description, I also agree that the problem may be in the top RDP client.
1.
HP Compaq t5510 Thin Client:
Operating System: Microsoft Windows CE.NET
RDP Client: Remote Desktop 5.1 Add-On
2.
HP Compaq t5520 Thin Client:
Operating System: Microsoft Windows CE 5.0
RDP Client: Remote Desktop 5.5 Add-On
3.
HP Compaq t5530 Thin Client
Operating System: Microsoft Windows CE 5.0\6.0
RDP Client: Remote Desktop 5.5 Add-On
We can try to optimize two ways.
1.
Upgrading Driver – Network for Thin Client
(1) HP Compaq t5510 Thin Client:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=420576&prodTypeId=12454&prodSeriesId=420575&swLang=13&taskId=135&swEnvOID=1054
(2) HP Compaq t5520 Thin Client:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=500833&prodTypeId=12454&prodSeriesId=500832&swLang=13&taskId=135&swEnvOID=2051
(3) HP Compaq t5530 Thin Client
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01087297&prodTypeId=12454&prodSeriesId=3341951
Upgrading RDP to the latest version of HP Web site.
Let thin clients use to connect to the Remote desktop server with low load.
(1) Open the Remote desktop client in customer’s Thin Client
(2) Click Advanced option. In choose your connection speed to optimize performance area, you can select the low load option. For example, modem(56kbps).
I noticed that you have deselected bitmap caching in Remote Desktop Client options, but makes no difference. You can try again. Then please remember disconnect idle sessions and rational allocation of resources in Terminal Server.
Technology changes life……

Windows 2008 R2 Standard Remote Desktop Users cannot Connect

I have a windows 2008 R2 Standard Terminal Server and some users aren't able to connect even though they are in groups that are in Remote Desktop Users on the local computer. I checked the local security policy setting "Allow log on through Remote
Desktop Services" and I see that Remote Desktop Users is a member of this group. Inside of Remote Desktop Users we have DOMAIN\Domain Users and DOMAIN\Terminal Users. Most of our users are in both groups, but there are still some people that
aren't able to connect via Remote Desktop to this computer. There are no users in "Deny logon through Terminal Services."
Thanks!

Hi,
Thank you for posting in Windows Server Forum.
Is it happens to all users or any particular group of users?
Please check by creating new user add them to “Remote Desktop Users” group and then see whether that test user can remote desktop to the server.
It also might happens that you may be limited in number of users or some connection issue or may be firewall setting issue. Please go through beneath article for information.
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2477176
Hope it helps!
Thanks.
Dharmesh Solanki

Remote Desktop Services error

We have a user that uses a new mac book air to connect to our terminal servers using the remote desktop services feature in Windows Server 2008 R2. She is using the standard Rdesktop client supplied by Microsoft.
While she is working sometimes the rDesktop session closes without reason. With other people on a different profile this doesnt happen.
Any ideas what I could check and where to check? or is this a common issue?

Hi,
I do not have such issue in my experience. Please check the log file for further research.
Microsoft Remote Desktop -> About Microsoft Remote Desktop -> Send log via email
Thanks.
Jeremy Wu
TechNet Community Support

Intermittent Disconnects for clients of 2008 R2 Remote Desktop Services

Hello, I have an issue that I am trying to work on for a client who is experiencing intermittent disconnected sessions when logged into a Windows 2008 R2 Remote Desktop Services (RDS) server.
As I mentioned, the disconnect is intermittent in nature and almost appears to be network related, although I cannot find any data in the Application, System, or application specific logs to support that.
The RDS server overall does not exhibit any error, but the user's session is briefly interrupted and then restored. I would like to be able to gain some additional information about what is going on under the hood, but I am having trouble finding any
details on how to turn on debug logging for Terminal Services (er, RDS) on 2008 R2.
Can someone provide some additional details on what kind of logging or other means that I can take on this server in order to gain some additional insight?
Thanks in advance for any advice.

Hi,
There are certain reason for which the client get disconnect from the server. The following are some of the commonly seen symptoms:
• You may be limited in the number of users who can connect simultaneously to a Remote Desktop session or Remote Desktop Services session.
• You may have a port assignment conflict.
• You may have an incorrectly-configured Authentication and Encryption setting.
• You may have a certificate corruption.
More information.
http://support.microsoft.com/kb/2477176
If you want to have log for login\logoff for the client on server end then you can get the information from below log.
Event Viewer>Application and Service Logs>Microsoft>Windows>TerminalServices-LocalSessionManager>Operational
Hope it helps!
Thanks.
Dharmesh Solanki
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]

Allow log on through Remote Desktop Services Group Policy for Domain Controllers

Hello,
We want to allow our Helpdesk Operators to be able to connect to Domain Controllers with the Remote Desktop Services. This is by default not allowed but according to many sites, it should be able to configure by using a Group Policy.
We made a new Group Policy with the setting 'Allow log on through Remote Desktop Services' and 'Allow log on locally' (as an extra for testing) and applied Security Filtering to only use it for a specific Security Group. Our test user is a member of this
security group and should be able to access the Domain Controllers now. However this isn't working.
The error message we receive upon trying to connect:
The connection was denied because the user account is not authorized for remote login.
For troubleshooting, we also applied the Security Group for that setting in the Default Domain Controllers Policy but that doesn't seem to work either. We want to avoid customization on our Default Domain Controllers Policy but this was just a test case
for solving our problem.
What should we do to solve our problem?
I hope to hear from you soon.
Thanks in advance.

Hi, I just found out what the problem was. This site helped me alot:
http://blogs.technet.com/b/askperf/archive/2011/09/09/allow-logon-through-terminal-services-group-policy-and-remote-desktop-users-group.aspx
In my case, I had the group added to the Allow Logon Through Remote Desktop Services but was not added to the Builtin\Remote Desktop Users group. After knowing this I made some changes to our situation and are now using the builtin\Remote Desktop Users group
rather than a new self made Security Group. I also added the Remote Desktop Users to the Allow Logon Through Remote Desktop Service in the Default Domain Controllers Policy as this is not done by default. By default only the Domain Administrators are able
to logon through remote desktop services.
You do not need the 'Log on Locally' permission within the Group Policies.
In short:
Add the desired users/groups to the 'Builtin\Remote Desktop Users' security group.
Add the 'Builtin\Remote Desktop Users' security group to the 'Allow Logon Through Remote Desktop Services' within the 'Default Domain Controllers Policy'.
Thank you anyway for the fast reply.
Have a nice day!

Is it possible to get Remote Desktop Services running when in Sysprep Audit mode in 2012r2?

Hi,
I'm setting up some images for 2012r2 and personally like to be able to access the machines via RDP. I have broken out of the OOBE by pressing
CTRL+SHIFT+F3, however, even though RDP is enabled (System --> Remote Setting) and running (Services --> Remote Desktop Services),
when I run 'netstat -a', I cannot see any process bound to port 3389, as such I cannot connect. Have restarted the services just in case, but no dice.
I most the other OS setups (Windows 7, 208R2) this is fine (assuming you update either the password in audit mode or enable RDP login with a blank password), but the fact that nothing is listening
on 3389 means that no matter what I do, I will not be able to connect.
Is there any reason why this is the case?
Cheers
Chris
Chris

Hi Chris,
Thank you for posting in Windows Server Forum.
Can you ping successfully the respective server?
Initially check whether there is any firewall rule set which is blocking your connection. Please try to change the RDP port from following registry key and verify whether you can get access.
To change the port assigned to RDP:
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
1. On the Remote Desktop server, open Registry Editor. To open Registry Editor, Start Run, type regedit, and then click OK.
2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
3. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Remote Desktop server\WinStations
Note: RDP-TCP is the default connection name. To change the port for a specific connection on the Remote Desktop server, select the connection under the WinStations key.
1. In the right-pane, double-click the PortNumber registry entry.
2. Type the port number that you want to assign to RDP in the
Click OK to save the change, and then close Registry Editor.
For more information you can refer following article (Point 2: You may have a Port assignment conflict).
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2477176
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]

Remote Desktop Services Default Connection issue

Similar Messages

Maybe you are looking for