Quantcast
Channel: Remote Desktop Services (Terminal Services) Forum
Viewing all 27656 articles
Browse latest View live

Troubled Remote Desktop Connection to Windows Server 2016

$
0
0

The problem I'm seeing is that I have Windows 10, Windows 7, and Mac, all with RDC clients trying to connect to a Windows Server 2016.

With any Win7-8-10, when an initial connection to the 2016 server is made, the RPC server crashes and renders the server inaccessible for about 10 minutes.

I found that, when I use the Remote Desktop Client VERSION 8  on the Mac, it works just fine.  I also have a version 10 that shows the same problem.

After 10 minutes in locked state, it seems that the RPC server comes back alive and I can connect again - and now, I am connected to the previous connection.

I am guessing nothing else anymore. I disabled Audio services, firewall is open (otherwise it would never connect), works just fine with RDC version 8 so, obviously Terminal Services is running, there are no bad files or something alike.

IT IS the version 10 of RDC that made things bad; or it is Windows 2016 that set something unexpected ? Any registry setup that could improve things ?

What are your experiences with this ?


Remote Desktop not working anymore on Windows 10 & Windows 7

$
0
0

Hi,

since a few days, we have issues while trying to connect from Windows 7 & 10 clients to a Windows Server 2012R2 RD Farm.

RD farm is composed of two RD session hosts + 1 RD Gateway.

Windows 10 clients are build 1809.

The clients and the servers are in different domains with one-way trust. It worked just fine until a few days ago, when clients started getting the below error message. In the TerminalServices-Gateway/Operational log file, I can find a lot of 312 and 313 events which indicate that connections are not authorized.

I have no clue what changed as compared to when the connections where working fine.

We introduced the Microsoft Remote Desktop app as a workaround, and strange enough that works, but it is not liked very much by our users cos it has some drawbacks.

Can anyone help me, or point me where to look at?

Thanks,

RDS windows 2012 windows 10 remoteapp hung issue

$
0
0

Hi,

I am currently having alot of issue with RDS windows 2012 on windows 10 1803 (All servers and client PCs are patched up to July 2019). The issue started around 26th July and I have restarted all servers and nothing changed recently in our network.

The issue is happening within the network and also off the network. I have tried to removed some of my

Following is what I have on windows 10 pc for updates.

Could someone let me know if you also recently started seeing this issue?

thank you ver much

Pwint

Can the number of RDS admin's be increased from 2 or is this a hard limit per server?

$
0
0

Hi Team,

Im trying to determine if  the number of RDS admin's be increased from 2 Admins per server  or is this a hard limit ?

Cheers

Dean

Migrate connection broker 2016 to 2019

$
0
0

Hi,

As RDS 2019 upgrade documentation seems to be non existing, I thought I'd ask this question here. Is it still necessary to migrate a connection broker from version 2016 to 2019 by doing an in place upgrade of the machine as was the case with 2012 to 2016? As the connection broker role is basically the same in both versions, I thought it might be possible to place the 2016 broker in HA mode, add a 2019 broker and remove the 2016 machine after that.

Is that possible?


RD gateway not working after windows update- your computer can't connect to the remote desktop gateway server. Contact your network administrator for assistance

$
0
0

I have about 200 users running mostly remoteApp from many different locations. 95% of them work fine. I do have RDGateway but it is configured to bypass the RDGateway in the setup if it can connect to the broker. Things have been working fine for the past year or so. Recently on the last set up updates for windows 10 machines, they receive the error "Your computer can't connect to the remote desktop gateway server. Contact your network administrator for assistance" as soon as they try and launch and RemoteApp application.

The fix is this.

https://appuals.com/fix-your-computer-cant-connect-to-the-remote-desktop-gateway-server/

It forces it to disable UDP and use HTTP instead. As far as I can tell nothing has changed on the network and UDP is still open and clients are able to connect to it.

Has anyone ran into this?

Remote Desktop Services Profile tab - User properties in Active Directory

$
0
0

I have a single domain controller. I am setting up profile path in Remote Desktop Services Profile tab for Vaidee(user). I have allowed vaidee to logon locally and through remote desktop services. I added him to Remote Desktop Users group. Even though he is not a domain admin, he can still login to the domain controller. When Vaidee logged in to the domain controller using Remote Desktop connection, the profile is not created in the specified location(C:\RemoteProfile\Vaidee).

Is there anything that I am missing?

Help me!

access to session host error

$
0
0
Hi , i have added a user  in "user groups of session collection properties" . but he is getting "the connection was denied because the user account is not authorized for remote login" when he clicks on the session host in rdweb page. should i add the user in some other place to give him access to the session host? kindly clarify

cannot activate licence in server 2019 for rds because it says I haven't specified the type of user I have installed

$
0
0
cannot activate licence in server 2019 for rds because it says I haven't specified the type of user I have installed even thought the cals have been installed and the server has been activated cannot find how to specify this anywhere what a pain in the"neck"

Problem with Windows Server 2012 R2 RDS farm

$
0
0
Good afternoon.

There is a terminal farm with 3 session hosts, 1 connection broker and 1 session host for browsers and various SOFTWARE (this session host lives in a separate collection).

Recently the host for browsers began to fall off periodically from a farm is session, on a host there are errors of the following type:

"Remote desktop connection broker on server one is TSGW02.local.local returned an error when notifying to disconnect the session.
Session ID: 153 
Error: the RPC Server is unavailable. "

"Remote desktop services was unable to join the connection broker on server one-TSGW02.local.local.
Error: the Current asynchronous message was dropped by the asynchronous dispatcher because there is a new message that will override the current one."

"A TCP/IP error occurred while trying to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. 
This error typically occurs when an outgoing connection is opened and closed at a high frequency, causing all available local ports to be used, and TCP/IP must re-use the local port for the outgoing connection. 
To reduce the risk of data corruption, TCP/IP requires that there be a minimum amount of time between serial connections from a specific starting point to a specific endpoint."

"An error occurred while processing group policy. Windows was unable to apply WMI filter on group policy object 'cn={981F11B1-2073-4F7A-8D1E-760047BAF4D8},cn=policies,cn=system,DC=local,DC=local'. 
Possible causes include disabling RSOP, disabling or stopping the WMI (Windows management Instrumentation) service, and other WMI errors. 
Verify that the WMI service is started and that the service is set to start automatically. New settings or GPOs cannot be processed until this situation is corrected."

"The host server for the session connect to remote desktop cannot communicate with the license server for the rd one-tsgw02.local.local. 
Verify that the remote desktop licensing service is running on the license server, that the license server accepts network requests, and that the license server is registered in WINS and DNS."

Nothing was installed or changed on the session host (since its normal operation). 
Antivirus installed Kaspersky, base current, finds nothing. Physical servers also have no complaints (Hyper-V cluster, tried different nodes, including datastores). 
At the time when the problem occurs (in the diagnosis) turned off the antivirus, as well as the built-in firewall - to no avail.

The most interesting thing is that if you make a wmi request from the connection broker , for example get-wmiobject Win32_OperatingSystem, then the problematic host responds and gives information.
If you try to make the same request from the problematic host anywhere (to the same broker), then you receive an error that WMI is not running on the remote host, or problems in the firewall.

What could be the problem?

Cannot add RDS licenses to Windows 2019 license server

$
0
0

I am trying to move from a Windows 2016 RDS license server to a new Windows 2019 RDS license server - my understanding is this is required in order to start using Windows 2019 RDS services (2016 license server cannot offer 2019 CALs).  So I built a brand new Windows 2019 server, installed the RDS licensing role on it, and successfully activated it.

When I try to add licenses it tells me:

The licensing agreement data provided to Microsoft is not valid. Check all the information you provided, make any necessary corrections, and then resubmit your request. If the problem persists, try using a different connection method.

I am using "Other" as the agreement type and then our "PURCHASING ACCOUNT NUMBER" as the code which I got from the Business Center website (https://businessaccount.microsoft.com/Customer/LicensesAndServices/)

I have tried both automatic and web browser (from my PC just to eliminate any firewall/proxy issues from the RDS server) methods - but all methods fail.  Before I tried the last resort of calling MS and doing the activation that way, I figured I would post a question to see if anyone has any suggestions.

Thanks

NK


Unable to add RDSH to existing Collections

$
0
0

Current Setup

2x RDS Brokers – Server 2012 R2

1x RDS SQL Database / RD License / RD Web Access / no RS Gateway configured

Round Robin DNS configured to both Brokers – working as intended

5x RDSH 2012 R2 servers for PROD collection

2x additional RDS 2012 R2 servers yet to be added

The environment is used to connect to either a DEV, TEST or PROD app. Separate collections are setup for each. Domain Users have access to the collections and apps. Security to the apps is handled by the app itself with separate login requirements.

The Problem

I have built two new RDSH servers to help with capacity as the number of users has increased dramatically since the solution was released many years ago. When I try and add these new servers into the current PROD collection, I get an error “Unable to retrieve collection properties” and the wizard ends.

However, and here’s the odd part.  When I create a new collection, I can add the two new servers plus one of the other PROD RDSH servers (I removed it as part of testing) to the newly created collection. I also have the same problem if I try just adding one of the old RDSH servers too. If I remove one of the RDSH servers from this Test Collection I can’t then re-add it back again. I have to scrap the collection completely and build a new one.

I’ve switched RDMS logging on and the logs don’t tell me anything I don’t already know – copy of log below (redacted server names). All servers im testing with are at the same current patch level too.

AddRemoveSessiontoCollectionWizardTask.Execute::<exisitingserver.domain.com>

RdmsUI: RDManagement\Add-RDSessionHost -CollectionAlias TEST -RDSHServer System.String[] -RDManagementServer <Broker1.domain.com>

AddRemoveSessiontoCollectionWizardTask.Execute:: RDMSModel.Instance().RdmsServerName-<Broker1.domain.com>

CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Progress : 0 - -1% completed

CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Add-RDSessionHost - 0% completed

CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Progress : 0 - -1% completed

CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Verbose: Input - -1% completed

CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - Verbose: Input - -1% completed

CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - InlineScript - -1% completed

CommandLetExecutor: Job Progress Received for cmdlet: RDManagement\Add-RDSessionHost - InlineScript - -1% completed

RdmsUI: Workflow 'RDManagement\Add-RDSessionHost' failed: System.Management.Automation.RemoteException: Unable to retrieve the session collection properties.

RdmsUI: Job finished for cmdlet RDManagement\Add-RDSessionHost

Has anyone encountered this problem before and if so, how did you solve it? Is this an issue with the RDS SQL database?  If so, is there way I can fix it? Restoring isn’t an option as we don’t know how long its been like this and would take far too long in going through backups.

Thanks

Microsoft Edge access the to RD Web Access site - RDP and wrong credentials

$
0
0

We have RD Web on 2016 server (we use this server for administrative work on our network).  The users access from RD Web from  their desktops(using standard user credentials). When logging in to RD Web, the users us their administrative accounts (domain admin). 

The users are able to run the remoteapps using IE11.

When using Microsoft Edge, accessing the remoteapps, RDP file is downloaded. I don't mind that.  But, the connection wants to use the standard  credentials instead of the admin account used to logon to web server. This does not happen in IE11. 

How do I solve the credential issue in Microsoft Edge with the Remote Apps?

Thank you.

RD Client on IPad : disconnected from server with error code 0x00000003

$
0
0

Hi

we have Windows server 2016 based remote desktop services setup there is a session host assigned to each user (server as a desktop) and we got single gateway server which is also connection broker.

when we try to connect from Ipad which is on latest IOS version 9.3.5 with RD Client APP version 8.1.34.1707311425when we download RDP file from RDWEB first time it works fine,  but then we go back to RD Client app and try to connect again it always comes up with this error disconnected from server with error code 0x00000003

having checked event log on Gateway/connection broker server I see following 4 warnings logged for each connection attempt from iPAD.

1. The network characteristics detection function has been disabled because of Reason Code: 2(Server Configuration)..

2. Interface method called: SendLogonErrorInfoToClient(WinlogonStatus: 0x80070005, ClientError: 0xffffffff)

3. TCP socket READ operation failed, error 64

4. RDP_TCP: An error was encountered when transitioning from StateUnknown in response to Event_Disconnect (error code 0x80070040).

so far we not had any issues connecting from windows machines or even Mac machines using RD Client App.

its only happening while connecting from Ipad.

can somone advise any fix please

thanks

Harry

RD Session Host and Virtualization Hosts

$
0
0
Hello, I am currently running a Remote Desktop Session Host Farm (with additional servers for Connection Broker, Web Access, and Gateway).  Everything in this Session Host Farm is working great.  However, we now want to add some Virtualization Hosts, but the option is grayed out? Can a RD Virtualization Host cluster not use the same broker as RD Session Host farms?  If not, how do I use my existing Web Access Server and Gateway Server with a second broker, for Virtualization Hosts? Thanks!

Bogus error: “The remote computer requires Network Level Authentication, which your computer does not support.”

$
0
0

Hello, 

We have Windows 2008 R2 servers with SP1 fully patched and Windows 7 SP1 desktops also fully patched. We enabled NLA (Network Level Authentication) via group policy recently after we decommissioned our last 2003 R2 server. We can connect to all of our 2008 R2 servers via remote desktop except for one. We get the error: 

“The remote computer requires Network Level Authentication, which your computer does not support.”

We are using other 2008 R2 servers and Windows 7 desktops to try to connect to the server. They all support NLA. But we still get the message. We rebooted the server from the console. That still did not resolve it. We could turn NLA off in the group policy at least for this server but we need it turned on for compliance reasons. 

Any suggestions on what the issue is? 

Thanks. 

Remote desktop disconnections

$
0
0

Hi,

We deployed a virtual hybrid RDS architecture as follow:

- 2 Domain Controllers on 2016 (Licence server)

- 1 Broker on 2016 (no gateway)

- 3 Application server used as remote app on 2012R2

- A cluster of 2 TSE servers (RDSH) on 2012 R2

It works almost well i just got a little problem, sometimes when we try to connect on remote app ou directly via RDP we got a connection error, like when the server is offline, but when i ping ther server during the blocage i don't lose any packet.

When we try a second time it works as usual.

I tried to troubleshoot it myself, found some event (227) on the broker and the RDSH (110/226) found nothing that can resolve that on google, or maybe i'm just not looking to the right spot.

Could you me find out what's the matter ?

Windows 10 1903 remote-app repeating keystrokes

$
0
0

Hi,

All our win 10 1903 clients, immediately after been updated from 1803 to 1903 start repeating keystrokes in remote apps. Servers are 2012 R2. RemoteFX cannot be disabled on session hosts servers since that solution causes problems to some of the apps running. Any one facing the same problem ? Any solution?

Blank Windows / White Bars when using Remote Apps

$
0
0

I am having an issue, exactly as described in a Spiceworks post, 1962989-rds-remoteapp-server-second-empty-window-opens-when-clients-connect, I cannot post links yet.

However, that posters solution of it being a firewall config issue is not the case for me.  

Basically, at random times throughout the day, users will suddenly get additional RDP windows that suddenly appear in their taskbar, that do not state any particular program, and when you click on one, all it displays is a white bar where you'd think the top of the Window would normally be.  These additional blank windows cannot be closed, not even forcefully from the client side.  The only way around it is to have the user log completely out of all remote apps and disconnect, and wait a minute, then sign back in.  (Server is set to log off disconnected users after 1 minute in order to work around this incredibly irritating issue).  

I've modified keep alive timeouts, changed physical firewalls, RemoteFX settings, and even ran network traffic analyzers between both the server and the clients to see if packet loss was an issue, and it is not.

Server is Windows 2016 hosted on AWS.

Clients are all Windows 10 v1803.  


Windows 10 1903 RDP With OpenGL 3.0 Application

$
0
0

I need to use Windows 10 RDP from my primary computer running Windows 10 Pro version 1903 to control my headless media server also running Windows 10 Pro version 1903. This was working fine until I upgraded the media server from 1809 to 1903. At that point the ROON application (full Control, Core, and Output PC x64) would no longer start, complaining that it needed OpenGL 3.0. Sure enough, the Remote Display Adapter used on the 1903 RDP client says it only supports OpenGL 1.1.

So, why did this only start happening on version 1903, and what can I do about it other than stop using RDP and install TeamViewer or one of the other alternatives?

RemoteFX looks like it could be a solution, and MS seems to think it is a solution, but I cannot find any documentation of how to set up RemoteFX on Windows 10 to use for a RDP session with a different computer, rather than with a virtual machine on the same computer.

If anyone can provide help, I'd certainly appreciate it. 

(moved from the Windows 10 Installation, Setup, and Deployment forum based on advice there)

Viewing all 27656 articles
Browse latest View live