Dear Folks
Need your support for configuration RDS Services in our company, currently we running RDS with the following configurations, and wanted to add more RDS session host server.
Looking forward to your prompt response on this
Dear Folks
Need your support for configuration RDS Services in our company, currently we running RDS with the following configurations, and wanted to add more RDS session host server.
Looking forward to your prompt response on this
Hi,
Can i use License Cal 2019 on windows server 2016 ?
IT Helpdesk
Hi All,
Have a nice day!
I wang to deploy RDS environment, and publish it to public network, so that colleague connect it at home.
Question is: how to configure Gateway server and publish Web Access? Is there any detailed guidance?
Thanks a lot!
Hey guys,
I guess a simple (stupid) question for the RDS specialist.
We have one broker and several Session Host servers. There is a DNS entry, lets say "RDS.Domain.local" which is setup for Round Robin. The A record is created multiple times for every RDSH server. So users will use this DNS name to connect to the
farm.
When i want to make the broker HA i have to setup Round Robin also for the brokers. Lets say i create a record called "Broker.domain.com". How does a user connect to the farm after the broker HA setup? Will he/she still use "RDS.domain.local"?
I will use an external CA given certificate for the broker setup, like for example *.domain.com. This will be setup during the 'Broker HA setup' for Single Signon and Publishing. Can i still use "RDS.Domain.local" to connect to the RDS farm from a
user point of view? Or will i end up in conflicts because i use .Domain.local (RDSH) and .Domain.com (Brokers)?
Thanks for the answer.
Kr,
AJ
Hi
I am getting bellow error message while accessing my RDS server. Please help me to find out "Farm name"
[Window Title]
Remote Desktop Connection
[Content]
Remote Desktop Connection cannot connect to the remote computer.
The remote computer Jet-ABC123.ABC.asp that you are trying to connect to is redirecting you to another remote computer named Jet-ABC124.ABC.asp. Remote Desktop Connection cannot verify that the computers belong to the same RD Session Host server farm. You must use the farm name, not the computer name, when you connect to an RD Session Host server farm.
If you are using an RDP connection provided to you by your
administrator, contact your administrator for assistance.
If you want to connect to a specific farm member to administer it, type "mstsc.exe /admin" at a command prompt.
[OK]
Thanks
Was checking online to see if RDS User Cal for Win2016 will expire.
Based on my research, RDS User CAL on Win2008 will expire: https://social.technet.microsoft.com/Forums/en-US/0d779acf-e990-477c-9923-7c3ecdd0768b/do-windows-server-2012-standard-rds-user-cals-expire?forum=winserverTS. Is this still valid for Windows 2016's RDS User CAL?
Jabez Gan [MVP] - http://www.msblog.org Contributing Author for: (Sybex) MCTS: Windows Server 2008 Applications Infrastructure Configuration Study Guide: Exam 70-643
I have an Azure Windows VM, running Windows Server 2016 DataCenter. I followed the steps here by @braddupuis on how to allow more than 2 concurrent RD users on my server. link: <edit: still unable to post links but thread title isEasiest way to enable more than 2 concurrent RDP sessions on Windows Server 2016>
the step worked and I now have 3 concurrent users, but I have a couple of questions on this:
1. does this need additional license? There is no licensing manager installed on the VM, the licensing diagnostic shows there is no licensing server setup.
2.as per the same thread, there is a 120 day trial period. Where can I see this and what happens after 120 days?
2.1 will all of the users not be able to login or will it revert back to just 2 concurrent users?
Thank you in advance for any response.
All of a sudden my Windows 7 x64 computer is unable to connect to random Windows 2008 R2 servers via Remote Desktop.
I can connect to the same servers from other Windows 7 machines.
The only fix I've come across so far is this, except that key doesn't exist on either my machine or on the server(s):
To resolve this issue, follow these steps:
Does anyone have any suggestions please as I'm at a total loss what is happening here.
Thanks.
Hi,
we're facing the following issue while trying to add new Remote Desktop Session Hosts into
a session host collection : "Unable to retrieve the session collection properties".
The server can be added into the deployment but can't be added into the session host collection and the message above
is returned. This error never happened before and is ennoying as we need to deploy more Servers/Collections.
A collegue noticed that adding a couple of servers at once (from the GUI) succeeded ...
I can't find anything related on EventViewer (Brokers / DataBase server)
Is this a known bug ? I can't find anything related on Microsoft support.microsoft.com
Any help would be much appreciated, Thanks.
MCTS Windows Server Virtualization, Configuration
Dear Support,
I have one more concern, We have Remote desktop Licenses 10 users activated in Win Server 2008 r2 OS. Now we have purchased Remote Desktop license 2019 - 15 users. We tried to downgrade to 2008 r2 to activate, it is not activating. After We know that Remote Desktop license 2019 downgrade up to 2012 r2 OS.
Kindly advise us is any possibility available currently activated Remote desktop licenses 10 users, upgrade to 2012 r2.
Hi,
We are currently running Terminal Server on Windows 2008 R2 Server.
Management would like to add another 200 licenses (In addition to current 15 one).
Just would like to seek your advice that can the latest license of RD Gateway Server be applied to Windows 2008 R2 Server ?
Thanks
Hi Guys,
Wondering if there's anyway we can allow users to connect to a workstation from the new HTML 5 Web Client? From all my research and playing with the product, it seems only RD Session Hosts and Virtual Desktop hosts can be added to the portal. Seems like such a waste as we have this HTML 5 RDP client that would be perfect for our needs, except we can't publish extra RDP endpoints.
Tom
Tom Wardrop
Hi everyone,
I have a 2019 Server farm that is having issues with the new webcam redirection feature.
When a webcam client connects, I see the webcam in device manager under "Remote Desktop Camera devices", but when I attempt to use the webcam nothing shows but a blank screen, or in some instances I get a privacy error (privacy has been set to allow all apps in Privacy->App Permissions->Camera on both the client and the server).
On the server I looked in Event Log viewer under "RemoteDesktopService-RdpCoreTS" and saw Event 132:
"A channel RDCamera_Device_0 has been connected between the server and the client using transport tunnel: 0."
Quickly followed by Event 148:
"Channel RDCamera_Device_0 has been closed between the server and the client on transport tunnel: 0."
I'm not sure how to debug this from here. Any help would be appreciated.
I've experienced this with Windows 10 LTSC 2019 and newer, on a Microsoft Surface 2 Pro, and other clients with logitech webcams.
Hello!
Im having some "problem" With the terminal services servers at the company.
The current setup goes like this:
2 AD controllers (these are not the terminal servers)
2 servers with licensing role and other mandatory roles for terminal services, both belonging to the "Terminal Server License Servers" (the group is in another language so maybe its not the exact name)
1 of the servers has 15 licenses and the other one(not being used at the moment) has 2x5 licenses.
Licenses were installed as soon as the roles were isntalled so no "grace period" was expired and they have been working for a long time like this, so even if the grace period was used, it would have expired by a long time by now.
A few months ago they were working normaly, but now ive started noticing something strange.
All the users in my remote desktop group can connect using RDP, but the server is not issuing a license for their user (all of our 25 licenses are per user).
For example: there are some users (lets say "remote1") that were given a licence..(I willl attach image), but other users that are currently connected "remote2" (they connect almost everyday to work) are still not getting a license, for
some reason and the server still allows them to work normaly.
Now to the question:
Is this a bug?
Are there a set of requirements for the server to issue a license for that user? (a given amount of time, number of conections, or other activity?)
I have looked around in other forums/posts and all I found was common problems, like not getting a conection due to server not giving a license, or server being missing from the licensing group, etc.
I'm posting here because i dont want more users being able to connect than the amount of licenses we have.
Thank you so much for the support!
Good morning,
I have a simple, and possibly dumb question. If I unplug my mouse from my host machine, can I still use a mouse on my remote desktop?
Thanks,
Hello,
First of all I'm new to the subject of server systems administration, so please don't be to harsh.
I have problem with CAL RDS licences. My configuration is without active directory and without a domain. I know that in this case I'm able to use only CAL RDS for devices. However I have a few of them for users. So I thought of the solutions described below:
My solution:
I will setup active directory and the domain without the intention of using it. Then I will setup RDS services with CAL RDS for user configuration, also I will create RDS users accounts. However none of the computers in the network will be connected to the domain. Also I have only one physical machine, so it will be running as domain controler, and licence server for RDS services.
By doing so I hope to achieve ability for users to connect to the server using RDS, and to avoid using active directory in the network (I'm to green for changing configuration of the entire network to make use of active directory). But I don't know if this is possible - connecting to the server using RDS on the computer that isn't part of the domain.
Please help.
Hello,
This is what I suspect:
I think the web server (and gateway) is returning a RDP file to my external home computer that does not have the gateway information saved in it. But I can't confirm this, not sure how. Your thoughts? Any tips? Do you think I'm on the right track?
This is a new build, has never worked 'properly'.
This works:
This does not work:
what the heck, right?
What the heck, right? Its like the webserver is sending a RDP file to my home PC without the gateway settings included. But I cant find out how to confirm that.
Any tips or suggestions?
Hi,
We are running Terminal Server on Windows 2008R2 Server.
Currently, there are a number of users are using it. However, from both "Remote Desktop Service Manager" and "Task Manager", we cannot find out those users.
Is there any suggestion ?
Thanks