I configured and setup RDS licensing on server1 and in the licensing manager I can see there are a total of 5 User license with 0 issued.
So I logged into Server with different user accounts and it still shows 5 available and 0 issued. I'm not sure why it doing this.
Our end goal is to spread these 5 user CALs out over 3 servers.
Is it possible to share the RDS licenses across multiple servers? We have one server that has 5 RDS licenses and we are going to be splitting its duties with a new VM that we are creating.
Can we share those 5 licenses so that 3 users can RDP into one server-A and 2 users can get into server-B? Right now we have 5 users all set to be used on server-A.
Hello, I have a question:
does RDP protocol supports TLS 1.1. I did find similar question for TLS 1.2:
http://social.technet.microsoft.com/Forums/en/winserverTS/thread/e308a2ac-2443-4a24-abc7-fab6079fac86
We have Windows Server 2012 R2 Remote Desktop (RD) Gateway servers within an DMZ and a combination of 2008, 2008 R2 and 2012 R2 terminal servers (session hosts) on the internal network.
Access to the terminal servers in the internal network using the RD connection client is via the RD Gateway servers.
We do not have RD Web Access or connection brokers deployed.
Does RD Gateway Support RSA SecurID without TMG?
Thanks,
Darren
I got a Windows Server Standard R2 2012 role as terminal service server with per user license access.
Users are facing problem not able print in remote session if another user login with same username.
Example:
When a user A login as Account username XYZ, if another user B login with same username XYZ, immediately
user A will not able to print. So user A have to logout and login again for print, but this will causing user B can't print when user A is login again with same username.
Hello,
I want to install a working VDI Environment but the last three days were just full of failures. This Forum is my last Resort or I have to pray for a miracle. Here is what I want to do:
I want to deploy an RDS Server so that I can provide eight virtual Windows 7 machines for my employees. They should use a small Thin Client which will connect to the RDS Server which will then redirect them to a free Windows 7 machine they can work on. After they log out from that machine, it will be reset to its default state.
Here is what I did so far:
I installed a Domain Controller which also does the DNS.
I installed a new Server 2012 machine and put it into the Domain of said Domain Controller. In addition I gave both Servers a static IP Adress and everything works fine up to this point. They can find each other, and they can connect to the Internet and other Computers in the same Subnet.
Now I installed the RDS on the Server 2012. I did that by using the wizard the Server Manager provided, and I selected virtual machine based deployment. After that I installed all the necessary roles (Connection Broker, virtualization Host and Web Acces) on the same machine, as I only want to use one machine for all that. The Setup then runs trough all of this just fine, and installs every role without any problems at all.
After the Installation, I set up my Hyper V environment. So I installed a template machine with Windows 7, updated it and installed all the programs I wanted on that template. Then I did a sysprep and created a Collection with the Server Manager. I chose my template and created 7 other machines, which are all part of that collection.
The Problem I have now, is that I don´t know what to do next. I installed an RD-Gateway and an RD-Licensing too. Activated both of them just fine. But whenever my Thin Client wants to connect to the RDS there are two possible outcomes:
1. They do a remotedesktop session to the Server itself, which means I will not connect to any of the Windows 7 machines but the Server itself, giving me full access to all the configuration Options via Server Manager. Of course I don´t want that for my employees.
2. It connets itself to the first Windows 7 machine, all the time. If a second user wants to connect to it it will kick the first one out, and then build up the connection with the first Windows 7 machine for the new user.
2.5 another Problem I have is that I want to connect the Thin Clients just to the Windows Login Screen. The user should start his Thin Client, this Client should automatically connect to the RDS and the Connection Broker then assigns a free Windows 7 machine to the user, where he can then log in with his normale AD Account and Password. The Problem is though, whenever I configure my thin Client to automatically connect without asking for a user account and Domain first, the Server seems to reject that request.
So my question is, what am I missing? I have looked through all the available Options on the RDS Server Manager and can´t find anything else I could do. Is it normal that under Tools -> Terminal Services -> I only have three Options? One for the Gateway Manager and two for the licensing? Is there a way to configure the Connection Broker? The only Option I have for him is to configure high availability which is just adding more Connection Brokers isn´t it? So I haven´t done that.
Any Help would be much appreciated
Hi
I am unable to browse \\tsclient\c (or any drive) or Print using EasyPrint on a specific Windows 7 workstation from an external 2012 RDP Server. Others Windows 7/8 workstations work as expected with/without admin rights.
This workstation has local domain admin rights and is joined to the local domain. The RDP server is entirely separate to this domain and has no links or associations.
I am at a loss to even find a starting point to attempt to solve this. It must be something specific to the local PC but I can't see any error log messages to help.
Any help would be appreciated.
Thank you.
EDIT:
After writing this I thought I'd try accessing the Remote Desktop using the MMC snapin. This worked first time - printing and drive browsing.
Therefore, this leads me to the conclusion it must be something to do with mstsc.exe or a local variable that is affecting it. It is v6.3.9600.16415 dated 02/10/2013 00:31
We are running windows 2008R2 with with TSG running. Everything has been running fine since it was set up a few years ago, however out of the blue we are receiving the following error:
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.We have tried removing and re-adding the TS Web Access component, however it simply returns the same error. As you can see it's falling over on a closing brace, however it seems from the file (Default.aspx) that the closing brace is required.
I have checked all the correct pages are in IIS as well. I'm a bit stumped and would like to see if anyone has come across this before.
I have errors on all 3 of my terminal servers. When this occurs, new users are not able to login and existing sessions can't be reconnected.
The errors I see in the log when this occurs:
Winlogon 4005
The Windows logon process has unexpectedly terminated.
I also see this one in the TerminalServices-LocalSessionManager logs:
Event ID 20
Attempt to send disconnect message to Windows video subsystem failed. The relevant status code was 0x80070102.
The server will work fine after a reboot, but this has been quite problematic for us over the past few months.
I can't really find any info on the Event ID 20 log entry so I'm hoping someone at MS will notice this thread and pass along some assistance.
All clients are Win7 SP1. We have about 20 thin clients. I noticed yesterday that they have RDP v7.1 so we're in the process of updating them to 8.1 today.
RDP on win10 is now confusing. Pressing ALT+F4 closes the RDP window when it's a window. When maximized it closes the window inside the RDP. When docked to the side it does that too. When fullscreen, it closes RDP window instead. That is insanely confusing.
Back/Forward on the mouse don't work at all
Can it just not send all keys into the RDP? Or make an option too. It's just so confusing as to when the keys are sent (like ALT+F4) to the guest and when they are sent to the host.
Help!
We recently rolled out an updated version of a golden image to a pooled desktop collection via Tasks > Recreate All Virtual Desktops under Server Manager > Remote Desktop Services. The task could not complete (we found later due to DHCP pool exhaustion), so it was cancelled, attempted again, and cancelled again. After resolving the issue, Recreate All Virtual Desktops succeeded.
We now have three images in the Virtual desktop template export location: one under ...\IMGS\__1, another under ...\IMGS__\2, and the working version ...\IMGS\__3. How do we get rid of __1 and __2? Can we simply delete them, or is there more to it than that?
Thank you in advance!
Ryan
I have a 2012R2 Standard install.
Added the RDS roles. This server is licensing, broker, web access and session host.
License server is activated and has 12 RDS Per-User licenses installed.
I have 1 collection, which is just RDP to this server: (pic to follow)
Everything looks like its working. I downloaded the RDP file from the rdweb site. If I connect via a Win 7 box, I see the "connected to remoteapp and desktop connections" popup.
I see in the license server that it has issued 4 of the 12 licenses (which is correct for now): (pic to follow)
config: (pic to follow)
But when the 3rd person tries to connect, it just hangs in "securing remote connection" and never connects (doesn't give the "which user to bounce" message either).
I tried spinning up another session host temporarily. Same deal - I could see up to 2 people connected to it, but the 3rd just hung. I even added the connection broker/rdweb roles and only used the license server from this existing server (thinking this might be a connection broker issue).
Any ideas?
Is there any way to force RDP to use TLS version 1.2 since I would ideally like to switch to the Suite B TLS ciphers e.g. TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384. I have always felt rather lukewarm about AES-CBC mode in TLS since the padding oracle attacks were demontrated a few years ago (2003ish). OK there are (probably?) effective countermeasures in all current software stacks (I really hope that includes schannel) but we all know well meaning people can go back and "clean up" old code. Anyone for a Debian random number? ;) More seriously, it would be good to be able to configure this for those situations where a specified secuirty level is a requirement of a contract and while the NSA doesn't have much say in things this side of the water their standards can be a good reference point.
I have already added the following to the registry on both server and client:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"DisabledByDefault"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server]
"DisabledByDefault"=dword:00000000
However, the client flatly refuses to connect with a TLS1.2 dialect - always only TLS1.0. Has anyone found a way of doing this? If not, are Microsoft planning to update the client any any point?
Hello,
We have a situation where users are reporting (with screen shots) that when they launch a Pooled Win 7 Virtual Desktop by clicking the icon on RDWeb they are actually logged into 1 of our Connection Brokers that is also a RDSH serving up RemoteApps. Our environment is 2012 R2, 2 CBs in HA mode, but only 1 is also an RDSH.
I have screen shots showing date/time but find nothing in the RDSH/CB event log that shows a problem.
Any ideas what would cause this and/or how to troubleshoot it further?
Thank you for any assistance.
Hello,
We have a 2008 R2 Remote Desktop Services environment that was recently updated from IE9 to IE11 through Windows Update and now user iexplore.exe*32 processes are using up 25% of the CPU per user. This is causing the servers in the farm to be heavily utilized. Reporting shows that this was not an issue before the update. I've researched and found a suggestion making sure that three KB's were installed in the correct order. I uninstalled them, installed them in the correct order and we've not seen any improvements.
Those KB's were:
Any idea's?
Thanks,
Kurse21
Hello,
I have a Windows 2012 R2 RDS Deployment with 2 Connection Brokers in HA Mode. I understand this is an Active/Active configuration so why do we have this menu option?:
Hello,
I'm trying to write a simple rdp client. I cut rdp file to the minimum number of parameters that are necessary to run the application in our environment with "seamless" application mode. Content can be divided into two parts: the connection to the TS infrastructure and the application's startup:
rdp.Server = "connectionbroker.domain.local"; rdp.UserName = "mjakubowski"; rdp.Domain = "domain"; rdp.AdvancedSettings8.ClearTextPassword = txtPassword.Text; rdp.SecuredSettings3.StartProgram = "calc"; rdp.TransportSettings3.GatewayUsageMethod = 1; rdp.TransportSettings3.GatewayCredsSource = 0; rdp.TransportSettings3.GatewayProfileUsageMethod = 1; rdp.TransportSettings3.GatewayHostname = "gateway.domain.local"; rdp.AdvancedSettings8.LoadBalanceInfo = "tsv://MS Terminal Services Plugin.1.SOS"; rdp.Connect();
rdp.Server = "rdsh.domain.local"; rdp.UserName = "login"; rdp.Domain = "domain"; rdp.AdvancedSettings8.ClearTextPassword = txtPassword.Text; rdp.SecuredSettings3.StartProgram = "calc"; rdp.Connect();
.. and give user permission to interactive login - i have bare remote application in my rdp client's window.
My problem - how to get AxMsRdpClient8 to connect to the connection broker (treat server like a TS connection broker, rather than RDSH server - similar to "use redirection server name" in .rdp file)?
Running Windows Server R2 Standard Edition on a Lenovo ThinkServer. Trying to get licensing mode set up, and we're not running in a domain setting. One server, 10 user network, so no real need to set up a DC that I can see.
Trying to set up licensing mode before the 120 day grace period expires. We're using a per device licensing mode. I thought installing the licenses took care of setting up licensing mode, but it apparently doesn't.
Anyway, when I fire up Server Manager, and navigate to the section that pertains to Remote Desktop Services, I get a "you must be logged on as a domain user to manage servers and collections." When I ran the "Configure your server" wizard when setting up the new server, it didn't show Active Directory as one of the requirements for setting up Remote Desktop Services.
What steps do I need to take to set up licensing mode? What do I specify as a licensing server? When I set up our old Server 2003 server, it filled in the licensing server information automatically.
-=> Carroll McAllister <=- coming to you "almost live" from Searcy, Arkansas