Quantcast
Channel: Remote Desktop Services (Terminal Services) forum
Viewing all 27765 articles
Browse latest View live
↧

RemoteApp "Jumping" to Second Screen

June 12, 2018, 12:37 pm
$
0
0

Setup

I have Server 2016 set up with Remote desktop Services.  Its primary function is to deploy one particular application, installed on the server, with RemoteApp.  The Configuration for the workstations is being pushed out with a GPO, and RemoteApp shortcuts are successfully being placed in the Start Menu.  We have approximately 50 Users utilizing this application, and for 95% of them this works perfectly.

Issue

While running the application on one monitor (right), under certain circumstances, the application will jump to the second monitor, maximize, and "appear" to be frozen (no response to mouse movements). We have a remote control software used for troubleshooting.  When we shadow the console on the users workstation, you can clearly see the application is open on the second monitor (left).  When we shadow the users' session on the server, the application appears to be maximized on the right.  Restoring the window restores the window to the right monitor, both on the workstation console (jumps) and server session, and regains control.

Attempted Resolutions

We have attempted video driver updates, alternate graphics adapters, complete windows updates, restoring older versions of mstsc.exe (for Windows 10 1803 users, per another hotfix), and switching primary monitors and resolutions.  The problem still arises.  Problem only exists for particular users for dual screens.  User A and User B have identical hardware and dal screens, but problem only exists for User A.  User C has a different make & model desktop, and User D has a laptop with a docking station, and both C & D experience the same issue.  We cannot duplicate the issue on workstations that aren't experiencing it already.

↧
Search

Remote Desktop Gateway Service

August 19, 2009, 3:04 am
$
0
0
Hi,

I'm having some trouble with Remote Desktop Gateway services in Windows 2008 R2 RTM Standard. TS Gateway worked perfectly in Win 2008 but it is not working in R2. I have the following logged. It seems like the Network Policy server cannot find the domain controllers. We are running windows 2003 AD and there are no connectivity issues. As I said, Windows 2008 TS Gateway worked perfectly. any help is appreciated!

Log Name:      System
Source:        NPS
Date:          18/08/2009 15:18:33
Event ID:      4402
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      computer.mydomain.internal
Description:
There is no domain controller available for domain mydomain.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NPS" />
    <EventID Qualifiers="49152">4402</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2009-08-18T14:18:33.000000000Z" />
    <EventRecordID>936</EventRecordID>
    <Channel>System</Channel>
    <Computer>computer.mydomain.internal</Computer>
    <Security />
  </System>
  <EventData>
    <Data>mydomain</Data>
  </EventData>
</Event>
↧
↧

RDSH Farm on Windows Server 2019 but Windows 7 users are not able to connect to RDSH 2019 farm

May 3, 2019, 3:36 am
$
0
0

Hello Friends, 

i have deployed new RDSH 2019 farm with 2019 RD Web , Gateway & Broker server farm in my local infrastructure. we have couple of user who are still on Windows 7 SP1, but when they try to access  new 2019 RDSH farm they are not able to access with warning as below.

[Window Title]
Remote Desktop Connection

[Content]
Your computer can't connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance.

[OK] [Help]

my Windwos 7 computer is fully updated and  i have also applied  RDS version 8.1 to my windows 7 computer. still no luck, let me know if any one else is facing simile issue.  

Thank you, 

@mar




↧

Win server 2016 Reboots everyday @ 9

May 3, 2019, 5:02 am
$
0
0

Hi guys i was wondering if you could help me out with a reboot issue.

I have a windows Server 2016 terminal server installed in my test environment with an activated license but the server keeps getting rebooted and i did not configure it.  Any idea what this could be?

I already checked if it was a Windows update issues but it does not seem to be.

I get the following error message:

The process C:\Windows\System32\svchost.exe (C6) has initiated the restart of computer C6 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Other (Unplanned)
 Reason Code: 0x0
 Shutdown Type: restart
 Comment: A remote client is trying to shutdown this machine through Remote Desktop Services

Event id: 1074

User: System

↧

batch file issue

May 3, 2019, 6:09 am
$
0
0

Hey

I have a few creative studens, who had created some batch file.

One of them give the access to whole path c:/ trough the file explore .with this command:  start %windir%\explorer.exe "C:\"

Im running some batch files my self for all the users, so i wont block for batch file running. 

How do I stop or block for these creative studens. :-(

King Regards
Jerry

↧
↧

Terminal Services Licensing Errors Windows Server 2012 R2

May 3, 2019, 8:01 am
$
0
0

Can you offer up some suggestions regarding the following System log events? We are seeing these errors frequently on the Windows Server 2012 R2 server which is hosting the Remote Desktop license server.

1. Are these warnings and errors concerning and require action to correct? If so what steps?

2. What end user experience symptoms (other than the posted messages to System log) would we expect to see?

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          4/29/2019 11:12:28 AM
Event ID:      4105
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      MSRDSLIC.mydomain.com
Description:
The Remote Desktop license server cannot update the license attributes for user "useraccountname" in the Active Directory Domain "mydomain.com". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "mydomain.com".
If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.
If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.
Win32 error code: 0x80070005
Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          4/30/2019 5:51:17 AM
Event ID:      44
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MSRDSLIC.mydomain.com
Description:
The following general database error has occurred: "ESE error -1003 JET_errInvalidParameter, Invalid API parameter."
Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          5/1/2019 11:46:41 AM
Event ID:      4106
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      MSRDSLIC.mydomain.com
Description:
CAL reporting: Windows Server 2012 : RDS Per User CAL - Installed: 850, Issued: 881

In addition, I can confirm that, per instructions in event 4105, the license server is not a domain controller and the computer account is a member of the built-in "Terminal Server License Servers" group.

A similar question TechNetForumTopic, SysAdminTipBlog, and MsITprosBlog refers to a solution involving old accounts for long-term employees who are appearing in event 4105. I have validated that many of them are old enough that they likely existed back when this domain was at the 2003 functional level (it is now at the 2012 level). However, these users are not reporting any symptoms, so the event 4105 seems to not cause any downside other than logging the event. (Which goes back to my original questions, what symptom effect should we be seeing?)

Thanks in advance for your assistance.

↧

"Terminal Services license server group" is not added to user accounts in Windows 2003 domain

February 11, 2009, 4:11 pm
$
0
0
We have a Windows 2003 domain and have just set up some terminal servers using a Windows 2008 terminal server licensing manager server in the domain (we are using per user licensing). This license server is not a DC.

Our problem is that mostusers will not be assigned licenses from the license server and the eventviewer says:

The Terminal Services license server cannot update the license attributes for user "XXX" in the Active Directory Domain "mydomain.intern". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "dirnat.intern".
If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.
If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Terminal Services Licensing service to track or report the usage of TS Per User CALs.

Well, sure enough the server in question was not member of the "Terminal Server License Servers" group at first but was added. Restarted (both ts and licensing servers) and the situation is still the same.

A little further investigation shows that this problem occours for apx 3 out of 4 users. Checking users permissions with powershell get-adpermission reveals that the group "Terminal Server License Servers" is present with some special permissions on the accounts who works, and is absent on the rest. At first it looked like it was a inheritance problem, but the users OU shows no trace of the "Terminal Server Licensing Servers"-group.  Interestingly enough all newly created users gets the correct permissions which makes me think that the permissions are added as a part of default settings from the AD-Schema. I can see that the "Terminal Server Licensing Servers"-group is present with permssions on the users objevt, but the AD Schema mmc-snapin doesnt seem to be able to list which particular permissions this is.

Anyway - at one point a job must have been triggered that tried to set these permissions for all user accounts (?) in my domain, but it must have stopped at one point. Is there a way I can trig this manually?  Or is there another way to get this done by the book?

I was thinking I could simply set the permissions manually through powershell and hope for the best, but I really don't like doing that in case this is a sign that something else is wrong with my AD. I suspect this because profile-folders seem to be inconsistent on some users (some are created as USERNAME.V2 while others are created as USERNAME.DOMAIN.V2 and some users gets both of them and the TS keeps alternating between them..) Strange thing, but perhaps this is all connected.

Anyone have a suggestion here?. Should I fix the accounts with a set-adpermission command or choose another approach?

There seems to be others with quite similar problems in this thread:




↧

Event ID 4105 - Need to fix corrupted DACLs

January 27, 2012, 8:37 am
$
0
0

I'm receiving event id: 4105 on my RDS license server event logs.  I've determined that I have a corrupted DACLS because I have reviewed the following articles:

http://support.microsoft.com/kb/2030310

http://itinternals.blogspot.com/2012/01/resovling-event-id-4105-terminal.html

Basically if I follow these directions:

Make sure, the domain group "Terminal Server License Servers" has the following permissions to the active directories users:
- Open Active Directory Users And Computers
- Tick View -> Advanced
- Right click on the root of your domain and select properties.
- Select the Security tab.
- Check if "Terminal Server License Servers" is listed with special permissions. If not, click on "Advanced" and add the domain group "Terminal Server License Servers", select "Applies onto" "User objects", then tick the permissions "Read Terminal Server License Servers" and "Write Terminal Server License Servers".

I don't see "Read Terminal Server" or "Write Terminal Server"

The solution suggested in the MS article states the following resolution:

Windows Server 2003 level Schema

dsacls "CN=XXXX,OU=XXXX,OU=XXXX,OU=XXXX,DC=XXXX,DC=XXXX,DC=XXX" /G
"BUILTIN\Terminal Server License Servers:WPRP;terminalServer"

When you grant the permissions on a container, you should use the following command:
dsacls "OU=XXXX,DC=XXXX,DC=XXXX,DC=XXX" /I:S /G 
"BUILTIN\Terminal Server License Servers:WPRP;terminalServer;user"

 

My question is, am I really typing XXXX or do I need to determine what my CN, OU, DC are?  It's not clear what I should be typing to replace the X's if that I what I should be doing.  Can anyone help?

 


↧
Search

Server OS 2016/2019 Session hosts (RDS) problems with Remote Desktop Services is currently busy

April 24, 2019, 11:10 am
$
0
0

Dear colleagues and support.

That is not something that was solved here, I found a couple of similar problems with 2008r2, but it cannot be applied to latest OS. And problem described in other topics are a little different

Our case:

We are using large infrastructure based on many Servers 2012r2 all in one RDS servers (Broker, Web, SH is installed at every server). Many servers published behind some load balancer.

As we have a lot of servers in farm - we have a redirected profiles configured (over GPO) and placed at DFS.

We started testing 2016 servers, and our test group start reporting problems with "Remote Desktop Services is currently busy".

Usually problem solved itself in 1-2 min, user have to try several times before he is able to connect. There was no hanged user sessions or something like this or some useful even log as i can see.

There was no solution for 2016 problem over the internet, so I was hoping to find it with 2019 server.

But we are able to reproduce problem even on "clean", powerful (8 cores, SSD, 32 GB RAM), freshly installed server with single role (RDS) on it for the minimal number of users (1-2 users online)

So that is not something like server load or not enough resources.

I assume it is related somehow to redirected profiles or some service really "busy" with what? But why it is working stable for 2012R2 and has such problem with 2016/2019? May be we can adjust some parameters, timeouts or something like this?

Do we have any workaround for this except disabling redirected profiles or living forever based on 2012 r2 (that is not an option when you have a farm for 1000 users online and many member servers behind balancer)

Many thanks for your ideas!

Regards,

Sergii V


↧
↧

2019 RDSH - not able reconnect to Disconnected session, every time new session (with fSingleSessionPerUser=0)

May 3, 2019, 10:46 am
$
0
0

Hello colleagues

When we are doing such config (enable multiple sessions per user):

Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Connections

Restrict Remote Desktop Services users to a single Remote Desktop Services session     Disabled

We are not able to reconnect to any disconnected session that was running previously.

It seems that it was mentioned here for Inside build, but we have same...

https://techcommunity.microsoft.com/t5/Windows-Server-Insiders/Bug-no-reconnect-to-disconnected-session-with/m-p/282056/highlight/false#M829

Any solutions for this problem?

Regards,

Sergii V

↧

Windows Server 2016 RDSH Intermittent BSOD (DRIVER_POWER_STATE_FAILURE)

April 30, 2019, 7:17 am
$
0
0

Hi,

Not sure if this should be asked here or not. If I have submitted in error, please let me know and I will redirect my query elsewhere.

We have an RDS platform (single GW/CB/Lic server - Windows Server 2016, 3 RDSH servers - also Windows Server 2016). The platform is accessed using HP Thin Clients via the Gateway's RDWeb feed. The clients connect fine and all applications and hardware devices appear to work correctly.

However, intermittently (doesn't seem to be any rhyme or reason that I can ascertain) one of the servers (it can be any of the three) will BSOD with a bugcheck of 0x0000009f (DRIVER_POWER_STATE_FAILURE). The server automatically reboots after a period of time and then works normally. Sometimes the BSOD happens only once, but then other times it will BSOD three or four times in a row shortly after coming up from the previous BSOD reboot.

From what I can gather, Windows is attempting (and failing) to instruct some device attached to the system (presumably via one of the remote sessions) to enter into a power saving mode and BSODs as a result. I have disabled USB power saving on the server but this does not resolve the issue. I have tested one of the RDSH servers by removing it from the connection pool and left it running without clients for a number of months and it has so far not given me any problems.

I took the MEMORY.DMP file (which is available for anyone to peruse upon request) and tried my best to analyse it using the tools available, and it seems to point to hidusb.sys, though I am unsure as to how to trace the problem any further.

All RDSH servers are patched with latest crticial/security patches as of a week ago.

Any possible thoughts as to avenues I could explore to diagnose/resolve this issue?

Thank you in advance for any advice you might be able to offer.

↧

Azure RDS HTML5 Web Client Unable to Access Gateway

May 3, 2019, 3:49 pm
$
0
0

We have a RDS (Remote Desktop Services) deployment, and recently went through the process of installing the HTML5 web client as per the directions at:

https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-web-client-admin

Our deployment is hosted on domain A, which has an active directory instance. There is also domain B with its own active directory instance, there is a two way trust between the two.

The problem we are having is that the traditional RD Web Access works fine for all users, but when users from domain B log on to the HTML 5 web client and try to open an app they get a message "We couldn't connect to the gateway because of an error". At the same time the browser console shows the following error:

Connection(ERR): The connection generated an internal exception with disconnect code=GatewayProtocolError(52), extended code=, reason=Gateway tunnel authorization failed with error code=2147965403

During troubleshooting we’ve tried:

  • Verified that required ports are opened.
  • Disabling all firewalls between gateways, brokers, and session hosts – same error.
  • Re-applied the publicly trusted cert to the HTML5 client (via Import-RDWebClientBrokerCert) – same error
  • Verified that the proper cert was bound to the HTML5 client – same error.
  • Enabled NTLM by setting the GPO: Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> Network Security: Restrict NTLM: NTLM Authentication in this domain. To “Disable” (within same domain as RDP) – same error.
  • Ran regsvr32 wksprtps.dll (dll was already registered, but tried it anyway)
  • Verified that the required KB4025334 from July of last year was installed or not necessary (OS was up to date)

Any ideas on other areas we can look at?

↧

VDI Shutdown inactive machines

April 20, 2019, 11:40 am
$
0
0

Hello,

Is there any documented approach to minimize the number of running VDIs?

I'd like to :

  1. Schedule starting the machines early in the morning.
  2. Schedule shutting down the machine after working hours.
  3. Allow the users to start their machine without admin support.

1 and 2 are easy, my concern is with 3. or any other recommended approach.

Thanks

↧
↧

Ghost typing the letter G

March 9, 2019, 9:35 am
$
0
0
We have a 2016 standard server to which a few employees connect to for Terminal Services. Only one client using Windows 10 has suddenly developed an odd problem. The letter "g" keeps being printing. It doesn't happen on the computer itself, just in TS. I removed all peripherals thinking maybe there was some signal being transmitted from there, but still happens. Any ideas?
↧

Récupérer licence Licence Remote Desktop

May 2, 2019, 2:37 am
$
0
0

Bonjour , 

par erreur nous avons désinstallé la licence  sur le RD licencing Manager . nous avons essayé de réinstaller la licence   on a message que la licence est déjà activé . 

Est ce qu'il y a une solution pour récupérer la licence  ?

Version Windows sever : 2012 R STANDARD


↧
Search

Windows 2019 server not retaining memory of local printers in terminal server

April 22, 2019, 1:52 pm
$
0
0
I am running a Windows 2019 Server Trial edition.  Working well EXCEPT for the printers is not retaining the port memory.  Every time a new session needs to occur, as Admin I have to hunt down where the printer is.  Why is this happening?
↧

RD Web Access Apps only displaying after hitting Show Details.

April 25, 2019, 9:07 am
$
0
0

Hello,

We currently have a setup where we have a server with the web access and RD gateway roles installed.  They point back to a broker that has multiple applications defined that users can use through a browser (using the web access URL.)  The issue we are having is that the user will click the application, it will establish a connection, but hang until you click show details.  Once that has happened it will show the domain page and load the application.  Does anyone know how to make the application automatically display instead of having to click show details?

Thanks

↧
↧

Unnamed Disconnected Sessions - 2012R2 Sesion Hosts

April 26, 2019, 12:47 am
$
0
0

Dear Microsoft,

We are getting error on rdp services and in task bar users there are User4 Disconnected cant log off.

The task you are trying to do can't be completed because remote desktop services is currently busy. Please try again in a few minutes. Other users should still be able to log on.

Please help on this support.

↧

Certificate issue: the remote computer cannot be authenticated due to problems with its security certificate. " Error code - 0x80072f8f, 0x20

April 26, 2019, 12:43 pm
$
0
0

Hello Team,

I have the below issue:

Here is my RDS environment:

I have only one server 2012 R2 standard with the below roles installed 

  • RD connection broker,
  • RDSH,
  • RD Licensing and
  • RD web access

I have published few remote apps and I was able to access them using RD web feed till yesterday. 

Example :https://contoso.com/RDWeb/Feed/webfeed.aspx

I do have installed the SSL certificate on my server and provided the same to RD web. 

But today while I use the same url to access the remote apps I get the below error message 

"The remote computer cannot be authenticated due to problems with its security certificate. security certificate problems might indicate an attempt to fool you or intercept any data you send to the remote computer"

Error code - 0x80072f8f,0x20

Now I can only access the remote apps through RD web access ( https://FQDN/RDWeb)

Please help me in fixing this issue. 

Any help would be much appreciated.

Thanks

SM



 
↧

Terminal services login issue

April 27, 2019, 7:52 am
$
0
0
Once the server has started, you can log in to it. However, after some time, the server will stop accepting log ins from both the console and RDP and will just sit on "configuring remote session". I have had this on many Server 2016 servers with remote desktop services installed. If you leave RDP to sit on this message it eventually errors with an 'internal error occurred' message.
↧
Viewing all 27765 articles
Browse latest View live
Search