Hello, at the moment we are running a terminal Server farm connecting to a 2008r2 licensing server. We have Software assurance for our rds licenses. But now we are intalling 2016 ts server and therefore need to migrate to a 2016 licensing server.

Now we need to migrate the existing licenses to a new 2016 server.

I would firstly install a new 2016 server and then configure the rds liscensing role. But what are the further steps?

Can I then immediatly enter the MPSA Account Number to the new server and install the licenses, having the 2008r2 server at the same time running with the same MPSA contract number? And then only after successfully installing the licensenses on thte new server, remove the role from the old 2008r2 licsensing server?

Can the 2008r2 ts servers then connect without problems to the 2016 licensing server after editing the gpo?

Hope someone can give me advice, as I want to prevent running into any problems during our short maintenance time.

Best regards

Oliver

Hi 

not sure if this is the correct area or if it needs to go to an azure forum

I have recently installed Azure NPS Extension onto our current remote desktop gateway setup. everything seems to work fine, I am able to enter my credentials and then approve the connection on the phone however after that the credentials prompt comes up again. it does go through after entering it again however it is an extra step which doesn't happen when using it without 2 factor.

I cannot find anyone having the same issue. please let me know if you have any ideas why the prompt would come up twice.

thank you.

Mahesh

Hi,

We have two RD gateway servers on different sites and now we need to cluster these two servers for high availability. I couldn't able to find the related article anywhere. 

Can anyone point me to the correct article?

Regards,

Mahi

Hi,

<g class="gr_ gr_13 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="13" id="13">i</g> am using C#.NET code to get Remote session information. we use cassia.dll to get the same.

while running this code found some abnormal <g class="gr_ gr_150 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="150" id="150">behaviour</g>,  where application stuck on <g class="gr_ gr_191 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="191" id="191">code</g> of getting session information.

so wondering what could be the issue which creates stuck or hang issue while getting session information

- if <g class="gr_ gr_734 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="734" id="734">mahine</g> is <g class="gr_ gr_759 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="759" id="759">logeed</g> of, restarting, <g class="gr_ gr_983 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="983" id="983">showndown</g> any of this can cause hang issue in <g class="gr_ gr_1190 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="1190" id="1190"><g class="gr_ gr_1188 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="1188" id="1188">application</g> ?</g>

Thanks

Looking to add HA to an existing RDS 2016 environment for about 50 users. Obviously, for RDS HA, the SQL database becomes a point of failure.

My question has to do with setting up SQL as a cluster as simply as possible, as this is a fairly small RDS environment.  Creating a SQL cluster requires shared storage, so I would like to use SQL 2016 Standard and the SMB shared storage option (avoiding SANs, iSCSI volumes, or even Windows Shared Storage Spaces).  To keep the network as simple as possible, I'd like to have the cluster nodes for SQL also be the SMB file share for the data.

I haven't specifically read that you cannot have a 2 node windows cluster with SQL Standard and an SMB file share installed simultaneously, and the SQL use that SMB share for the databases.  However, I would like confirmation on such a configuration before I spend time on it.

It just seems nutty and a resource overkill, not to mention only adds to the network complexity, to need to create yet another 2 node cluster just for the SMB file share for SQL to use.

Please advise, and thank you in advance.

Hi, I am getting this message when one of our users connect to the RDS Host server:

Error during driver installation. Result = 0x80070422 for devnode"TERMINPUT_BUS\UMB\2&2C22BCC9&0&SESSION137MOUSE0"

Event ID 121:

Hi All

Is there any way to force the RDS of Windows server 2008 SP2 to use TLS1.1 or 1.2?

Microsoft has released an update to add TLS1.1&1.2 support for RDS of Windows server 2008 SP2, we can safely disable TLS1.0 without breaking RDP connection after installed this update. However, since many other applications on server still need to use TLS1.0, we have to remain TLS1.0 for other applications and force RDS to use TLS1.2 to meet PCI DSSv3.2 policy.

As checked RDP-TCP property with "tsconfig", there is only 3 options for security layer(RDP security layer/Negotiate/SSL/TLS1.0) and cannot set TLS1.1 or 1.2 here.

Is there any way to set it in registry, group policy or other places?

https://support.microsoft.com/en-us/help/4074621/add-rds-support-for-tls-1-1-and-tls-1-2-in-windows-server-2008-sp2.

Hi,

I have scoured the internet for a solution to this issue however I have had no luck and have spent a lot of hours trying to get this sorted.

We have a client who uses RDS via RemoteApps. 

Their environment is as per below:

Broker Server

Licensing Server

Gateway Server

4 x RDS Host Servers

All servers are running Server 2012 R2

Users experience issues of receiving the below error message when they try to launch an application via the RemoteApps webpage:

When they sign out and back in it works fine.

I have investigate the error logs and only receive the generic Microsoft event ID's 40 / 41 and reason codes which give no valuable information.

I am leaning towards this being a networking issue but am unsure.

If anyone has any ideas please let me know.

Cheers,

When try to connect from public network to RDS 2016 environment web page is loaded, but when try to connect on RDP clinet, it will ask for credentials and after that it will connect to remote machine. Error shows as " your computer can't connect to the remote computer because remote desktop gateway server is temporarily unavailable"

When checking on error log found that even id 312 on gateway server

The user "abc@xyz.com", on client computer "xx.xx.xx.xx:2985", has initiated an outbound connection. This connection may not be authenticated yet.

I tried the registry key fix recommended for 2012 server (HKLM\SYSTEM\CurrentControlSet\Control\Lsa) and (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\TerminalServerGateway\Config\Core) but no joy. It did not work for 2016 server. Please help.

we have RDS installed in Windows 2016 standard edition and use session-base desktop deployment.

It was working fine for about one year. About two weeks ago, we started to have the following issue:

This computer can't connect to the remote computer.
The two computers couldn't connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support. 

When this issue happens, we find some users are disconnected in the RDS-Collections-QuickSessionCollection. But we cannot log/sign off those users, they are always showing there.

BTW, we can sign of those users in the Task Manager-Users. 

We can solve this issue by restarting the server. How to fix it without restarting the server?

Thanks!

Hi,

We have a RDS server ( Windows Server 2012 ) connected to a DC controller ( Windows 2016 ) : frequently users can't login because domain can't be reached.

We already pushed the server in the domain again but problem remains, the events logged are

- 36887 schannel

- 1061 : remote desktop session host server was unable to retrieve users licensing information from AD. Error 0x8007054b

- 5719 NETLOGON

After sometime ... adn without changes users can login again.

What could the problem be and how could we solve that ?

Best regards

Dirk

Greetings.

I work in an industrial facility, where we have several devices connected via RDS to a VM running Server 2012 R2. 

This Monday (7/30/2018) a technician had to cycle power on one of the devices (a thin client) and when it rebooted it would not reconnect as normal.  This failure stopped production for nearly three shifts - which is pretty significant.

The Event Log entry said "RDP: No valid license available".  I logged on to the server and found that ALL of the licenses in the "Installed RDS Per Device CAL" group were gone - the group was empty - and that all the devices were now showing up in the "Temporary RDS Per Device CAL" group.  All the devices licensing in the temporary group were also expired.

After working with MS clearinghouse folks, I was able to figure out how to deactivate and reactivate the license server - and install new licensing - but I am now obligated to tell my management how we can prevent this from happening again.

So, my problem statement is something like: "At some point in early April (or late March", we 'lost' the retail purchase "Installed RDS Per Device CAL" licenses - and so, all the devices switch to temporary licenses.  When those temporary licenses expired, we were vulnerable to losing connection - should power be cycled on one of the devices.  We did, eventually cycle power on one of the devices - which shut the system down.

So, I am reaching out to Microsoft to help determine why the licenses just "disappeared".

Thank you!!!!

Hi there,

has anybody heard/does anybody know whether the graving COM/.NET bug in KB4345418 does affect Remote Desktop Services deployments or not?

I've installed several Windows Server 2016 VMs last week, made a new RDS deployment and built half of it. The early deployed servers had like May Cumulative Update installed.

Now I want to add the second RDWA server as well as additional RDSHs - and the only thing I get is "Microsoft.RemoteDesktopServices.Common.RDManagementException" during the configuration phase. That means role installation and reboot via Server Manager passes but then it throws at the beginning of the configuration phase.

I've also tried adding the RDMS logging registry values but the expected "RDMSDeploymentUI.txt" doesn't exist in C:\Windows\Logs. The "RDMSUI-trace.log" gets written but doesn't contain helpful info.

As the 2nd RDWA as well as the other RDSH candidates have been patched to KB4345418 meanwhile and since .NET and COM are essential parts of Windows management and operations I suspect there might be a connection here.

I can only pinpoint two essential events that happened after the first RDWA and RDSH were added successfully:

• The RDCB server was HA'ed
• All RD servers including RDCBs as well as the undeployed candidate servers were patched to KB4345418

So either something is wrong/went wrong with the RDCB HA (but I don't get any other errors) or, for me a bit more likely, the hotfix issues are somehow impacting the manageability/deployment.

I've tried to uninstall KB4345418 from the 2nd RDWA candidate plus reboot but to no avail; regrettably, because of the way my deployments are structured, the RDCB servers had already gotten their "dism /Online /Cleanup-Image /StartComponentCleanup" thus making removal of the hotfix impossible.

Maybe it's also something totally different from the hotfix but I'm puzzled and in the dark here, not knowing how to proceed/better diagnose this.

For the time being cutting the whole RDS deployment down and starting fresh is out of the question especially since it is likely I might hit the same problem again.

Maybe someone of you has experience with this exceptions on 2016 or maybe even connections to the dev team regarding the current hotfix situation. Or someone that has patched their servers but is still able to add new RDWAs or RDSHs.

Regards and thanks a lot in advance,

Markus

Hola, tengo la siguiente situación:

1. Tengo instalada una aplicación en mi servidor de aplicaciones.

2. Esta aplicación la tengo publicada en mi Collection del servidor y desde un espacio de trabajo accedo por RemoteApp a dicha aplicación.

3. En esta aplicación debo configurar una conexión que apunta a un servidor el cual me permite traer la información requerida que se mostrará en la aplicación.

4. Según el punto anterior, tengo configuradas en la aplicación dos conexiones diferentes hacia el mismo servidor.

(Aquí inicia mi consulta como tal)

5. Requiero tener dos instancias de la aplicación ejecutándose en simultáneo. Una instancia de la aplicación se conecta a una de las configuraciones internas según el punto 4, y la otra instancia de la aplicación apunta a la segunda conexión configurada.

6. Cuando accedo remotamente a mi servidor de aplicaciones, puedo ejecutar las dos instancias de mi aplicación cada una conectándose a las configuraciones del punto 4.

7. Sin embargo, al intentar hacer esto ejecutando la aplicación desde el entorno de trabajo vía RemoteApp, ésta no me permite tener dos sesiones en simultáneo ya que dice que otro usuario está conectado.

Según mi análisis, cuando ejecuto la aplicación vía RemoteApp aparecen dos árboles de procesos y en cada uno aparece el .exe de mi aplicación, mientras que cuando ejecuto la aplicación en el servidor directamente solo hay un árbol de procesos donde aparecen las dos instancias .exe de la aplicación ejecutada.

¿Es posible que cuando ejecuto la aplicación vía RemoteApp los dos procesos .exe queden bajo el mismo árbol de procesos como cuando lo hago directamente en el servidor?

Espero haberme hecho entender.

Gracias.

It seems that I am unable to connect to a computer on my network with the Remote Desktop App (trusted Windows Store App on my Windows Laptop or from the iOS App store on my iPhone), while I am able to connect successfully to it from Remote Desktop Connection (old Windows app).

The remote computer is joined to Azure AD (Windows 10 Pro, up to date; again, this works from the old Remote Desktop Connection application on Windows).

Can anyone tell me if connection to a machine joined to Azure AD is supported on the Remote Desktop App or if there is something I need to do to configure it properly?

Thanks.

Hello,

I encounter following problem - when admin tries to connect/control another session on the terminal server (from the server) - windows opens but has only black screen. The RDS farm is based on Windows Server 2016.

Any ideas?

Thank you!

Hi Guys

Seeking clarity if it's possible and anyone has come across this scenario.

We have a Windows 20018 R2 based RDS License Server that has free CALs. The installed CALs (CAL Version) read as "Windows Server 2008 or Windows Server 2008 R2 : Installed TS or RDS per User CALs".

My Windows 2008 / Windows 2008 R2 and even Windows 2012 R2 server RDSH servers are able to contact the license server and get license issued. However, I recently enabled RDSH role on Windows 2016 servers (the only other difference is that these new RDSH servers re in Azure and my license server is on-premises). The new Windows 2016 RDSH servers are not getting the license even after pointing them to the on-premises license server using Server Manager.

I've followed the article https://social.technet.microsoft.com/wiki/contents/articles/16164.rds-2012-which-ports-are-used-during-deployment.aspx to allow port communication through Network Security Groups (NSG) in Azure.

This is the error I see on the RDSH severs:

Is it even possible that the existing Windows 2008 / R2 CALs can be consumed by Windows 2016 RDSH servers?

If yes, what else could be the cause of the issue and possible fix.

Thanks

Taranjeet Singh

zamn

Hello,

A couple of my users want to use RDP to do their work, but recently they have been getting this error. 

This is simply trying to get onto a workstation. So in my use case the user is just trying to RDP onto a Windows 10 Enterprise Edition (they are trying to log onto their computer from home), not a Windows Server or anything like that.

https://support.microsoft.com/en-us/help/4295591/credssp-encryption-oracle-remediation-error-when-to-rdp-to-azure-vm

In my research I've found that I can get around this by going into the the group policy editor and going toComputer Configuration > Administrative Templates > System > Credentials Delegation,and then trying to change the Encryption Oracle Remediation policyto Enabled and then change the Protection level to Vulnerable. 

But when I go into the group policy editor the Encryption Oracle Remediation policyis not there. 

So I am not sure what I can do to fix this, all I want is the ability to remote into a Windows 10 machine, I have tried from multiple computers that reside on my network (and on a VPN as well) can RDP into other computers, except for my user's one workstation. Is there something I can reinstall on my user's workstation or repair to let computers RDP connect to it? 

-Thanks