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

Remote-App lost focus / Screen/Window jumping

$
0
0

Hi everybody,

we have a new Terminal Server with Remote-Apps and a very interesting problem.

 

Host: ESXi 5.5

Guest: Windows Server 2012 R2

Remoteapp: CAS (not importend, all Remote-Apps have the problem)

Client-OS: Win7 and Win 8.1

 

Now the problem:

 

A Remote-App is started on a client - this works fine. The Remote-App opens a lot of windows (new mail, customer informations and so on) and it happens that the active windows lost the focus and jumps into the background and another windows is in front with the focus.

The problem is not reproducible and with this caution it is not possible to work with the Remote-App.

I found following hotfix (http://support.micro...b/2964832/en-us) but it is not applicable to the clients.


If somebody needs additional information, i will be available.

Thanks for your help and time!

Kind regards

srkonus


Windows 10 and RDS 2012 - RemoteAPP Window Invisible

$
0
0

I have a RDS 2012 R2 setup that I connect clients to through the RDWeb URL. 99% of my clients are Windows 7, and the app we are using has a logon window that would be invisible when the users launched the app. I figured out that if I uninstalled KB2830477, then the logon window would become visible to my windows 7 users. So I removed the KB on all my clients, and everything was happy.

Now, I'm starting to get some Windows 10 clients, and they are having the exact same issue. The app launches fine, but the logon window is invisible. You can actually click where the username/password is supposed to be entered, and enter your credentials (this was also how it was for win7 clients until I removed the KB), and then login and everything seems to work fine. But the initial window is invisible. I have tried removing any Windows 10 updates, but this does not seem to fix the problem. Any ideas on a fix for this? 

Win2008R2 SP1 Application crashes when enumerating DLL functions via tlbinf32.dll

$
0
0


Hi,

I need to investigate some IT environmental problems in our Terminal server environment. We ourself don't manage this, it's a contractor that deals with all of the IT stuff. It must be some influence from GPO or virus scanner etc, becasue the problem occurs also on a clean VM they made for testing purposes. Because that new VM still follows the rules of the managed environment I think this is a systematic problem and not a coding error - if I install Windows 2008R2 on my own test machine I don't see this problem.

The problem itself: 

in our "managed" productional environment we have an application we develop by ourself. The application has a Richtext editor that can help VB scripting by reading out the "public" functions from two DLL they come with  our applicaiton. The readout is done with the Tlbinf32.dll which is part of the operating system. By doing this the application crashes.

In an "unmanaged" test environment the problem doesn't occur, debugview and process monitor just stop, but don't show any particularities or even errors.


IT architect - Terminal servers, virtualizations, SQL servers, file servers, WAN networks and closely related to software devleopment (8 years + experience in VB, C++ and script langugaes), MCP for SQL server and CCAA for Xenapp 6.5

W2012R2 - Remote desktop - certificate ?

$
0
0

Hi,

i have many rds (some with only rdsh role, and others configured with broker)

I just discovered that there's always a certificate for remote desktop.

My pb is that the certificate expire in 3 months and that i never configured this certificate (i don't have any certificat role configured).

Is that something which is managed directly by server ?

Thanks for your help,

Y

Cannot Establish Remote Desktop Connection

$
0
0

Dear all,

I have two machines, both with Windows 7 Professional installed with all updates installed. They both have ample memory and are on the same LAN in same IP address range and can ping each other. Both have firewalls temporarily disabled, and remote desktop enabled. One machine had a few Group Policy changes that affected RDP, but these have since been returned to "Not Configured" state.

With all of this in mind, can anyone suggest why I can RDP from one machine to the other, but can't establish a connection the other way? The machine that cannot be connected to is the one that used to have restrictive group policy.

Thanks

Error 0x80004005 Office 2016 on RDS

$
0
0

Has succesfully installed Office on both the session hosts as specified in artichle https://technet.microsoft.com/en-us/library/dn782858.aspx. 

As long as i only use one host it all work prefect, but if I get logged onto host 2 I get this error.

It still works if i press OK. but the message keeps popping up if I happends to switch host again.

Any help or suggestions is appreciated.

Error when using RemoteFX for Remote Desktop Session Host

$
0
0

Hi all,

I have come across an error while using RemoteFX for Remote Desktop Session Host and would like some help in understanding it better.  As far as I can tell the error occurs when Remote Desktop Connection receives an RDP surface command while running within a locked session. This causes RDC to crash with the message "An internal error has occurred". I have only seen this error since upgrading Remote Desktop Connection to version 6.3.9600.  I don't believe this is a server issue as I can recreate the same problem connecting to an open source FreeRDP server using the same client.

To reproduce this issue I have the following setup:

Windows Server 2008 R2 Standard SP1 configured with Remote Desktop Session Host and RemoteFX enabled via group policy
Windows 7 Professional SP1 running Remote Desktop Connection 6.3.9600

I open a connection from the Windows 7 machine to the server using Remote Desktop Connection.  I confirm RemoteFX is enabled for the session by viewing the RemoteDesktopServices-RemoteDesktopSessionManager logs using Event Viewer. At this point the session appears to be operating normally.
I then lock the Windows 7 session with Remote Desktop Connection still running and visible on the desktop.  After a couple of minutes, I unlock the session and Remote Desktop Connection shows a dialog with "An internal error has occurred".  I believe that the error appears when the clock in the remote session changes, causing a surface update to occur.

Is this a known issue with the Remote Desktop Connection application?  It did not appears to be a problem with previous versions.  Are there any workarounds or will a new version of the client be made available in the future?

Thanks,

Duncan Williams

RDweb App Issue

$
0
0

Hello all,

I am having an issue with a select number of Windows 7 machines. I am testing the deployment of RDweb applications and more specifically Microsoft Dynamics (Great Plains). Some of the pc's constantly minimize the pop-up windows within the applications while others do not. Even the initial login window for the application is minimized once launched from the site. I can't think of what would cause this.

The specs are the same Win 7 Pro with IE 11.

Anyone ever experience an issue similar? I did find a couple knowledgebase articles such as

KB2384602 but they failed to produce a resolution and this particular one gave me any error that the update is not applicable to my computer.


The connection was denied because the user account is not authorized for remote login

$
0
0
Using Terminal Server 2008 not able to get non administrator users to login to the remote desktop. Have tried from Windows server 2008 and from Windows servers 2003. Get error login in "The connection was denied because the user account is not authorized for remote login" from Windows Server 2008. Error "The requested session access is denied" from Windows Server 2000.

Another Black Screen RDP Error (Session ID 114)

$
0
0

We are running a two server RDS solution for a client. Both machines are 2012 r2.

Occasionally, one of our clients' employees logs in and gets a black screen, and they are unable to do anything until we reboot the server. This is not feasible in a live environment, and a user can be shut out for the whole day before we can schedule the reboot that night.

Here are some characteristics of the black screen issue:

- The screen is entirely black within the remote session.
- Pressing things like Ctrl + Alt + Del and Ctrl + Alt + End do not bring anything up. The mouse may briefly get an hourglass, so it seems like something might be happening, but the black screen doesn't go away.
- Forcing the user to sign out using administrative access does not resolve the issue.
- Deleting the account and recreating it does not resolve the issue.
- All our graphics drivers are up to date.
- Unchecking 'Persistent bitmap caching' does not resolve the issue.
- I've played around with group policy, and enabling and disabling UDP to various degrees. This does not resolve anything.
- We made minor progress by changing the display configuration in the Remote Desktop Connection app to a smaller size desktop (such as 640 x 480). The screen will sometimes (not always) appear, but only partially. Clicking the start button can cause part of the screen to go black. Signing out from this degraded session didn't do anything, and this ultimately didn't get us any closer to resolving the problem.

- The black screen only ever happens to one user at a time, and it is the user given Session ID 114.

I've read only a couple other posts about session ID 114. There is no way to predict when an ID will be doled out to a user, and there is no method that I've seen so far that can completely prevent a user from getting a certain ID. The best workaround we have to date is to create a dummy account, force sign out the affected user, and sign in with the dummy so it takes over that ID.
This only works until a reboot, when Session IDs will get reassigned. This also requires a failure in order to make the change, which is not an ideal situation.

According to this thread (https://community.spiceworks.com/topic/693490-black-screen-at-remote-desktop-login-to-server-2012-r2), the poster was in contact with Microsoft and they said there is no solution. I want this to be recorded in writing by Microsoft itself if that is the case. If a solution or better workaround has been found, please let us know.

Upgrading to RDP 8.0 on Windows 7 SP1 Does Not Work When Machine Is Host

$
0
0

Hello,

I'm trying to understand some confusing behavior I've been seeing after upgrading my Windows 7 SP1 machine to use RDP 8.0 as per the instructions.

Some digging has led me to believe these updates (along with the Local Group Policy changes) will configure both the RDP Client and Host to enable the new protocol (8.0).

However, when I try to connect to this machine from a Windows 8 device (supporting RDP 8.0 by default), I do not get the "Connection Quality Indicator" that's supposed to tell you you're getting RDP 8.0.

In other words, that little signal strength bar isn't there for me. The instructions say if I don't see this, it's not RDP 8.0.

Here's what I don't understand--if I use this Win 7 machine to connect to a Win 8 machine, the connection quality indicator DOES appear, and the dialog box is there as well. But connecting TO this machine does not. It's led me to believe that the RDP 8.0 is working for this Win 7 machine as a RDP client but not as a host.

I've followed the instructions precisely: I installed the hotfix KB2574819 and then the RDP update KB2592687 and changed both group policy settings. I've restarted my machine several times. I even threw in the upgrade to RDP 8.1 in an attempt to make it work. I know that the updates got applied because selecting

Remote Desktop Connection > About

shows me 'Remote Desktop Protocol 8.1 supported.'

My group policy has the 'Enable Remote Dektop Protocol 8.0' setting enabled, as well as 'Select RDP Transport Protocols' (set to both TCP and UDP).

Thoughts?




Users can no longer launch RemoteApp application all of a sudden

$
0
0

Hi folks. We have a weird one here. We have  Server 2008 R2 set up with Terminal Services. We have 13 users connected at any given time (no domain, pretty simple setup). All users are Administrators because we have an application they all run (POS app) that requires it. We have the POS app in the RemoteApp list and created RDP connections for all users so they could launch the app remotely. Everything was working fine, then suddenly all are getting this error:

The program did not start on the remote computer. For assistance, contact your system administrator.

Other strange tidbits:

1) The server Administrator account works just fine, but the other users don't, even though they're all local administrators.

2) We tried launching other apps through RemoteApp. Notepad.exe didn't work, but calc did for all users. 

3) When users get the error above, the Server shows them as connected but nothing happens when relaunching the RDP file, very frustrating. We have to boot them off from the server to get them to retry.

4) We tried clearing out TCP/IP folders and this helped some users connect once, but they weren't able to connect again. Super odd.

5) All users can connect via regular Remote Desktop connection (no RemoteApp) and launch the application on the server.

6) No mapped drives, old citrix install, or other common causes we could find.

7) We can't notice anything in the environment having changed.

Help!

"Because of an error in data encryption, this session will end"

$
0
0

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:

  1. Start Registry Editor.
  2. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
  3. Under this registry subkey, delete the following values:
    • Certificate
    • X509 Certificate
    • X509 Certificate ID
  4. Quit Registry Editor, and then restart the server.

Does anyone have any suggestions please as I'm at a total loss what is happening here.

Thanks.

Bypass RDS - RemoteApp - Shell Access

$
0
0

Hello Technet Guys, 

I've created a PoC environment to test the RemoteApp feature of the RDS. Before trying to publish the applications and system of my company, I've decided to do some penetration testing activity. The result is not so good....

I've published the calc.exe using the RemoteApp, and by using the Help Menu, I could gain access to the machine' shell.


Have a look:

01 - https://social.technet.microsoft.com/Forums/getfile/830818

02 - https://social.technet.microsoft.com/Forums/getfile/830819

03 - https://social.technet.microsoft.com/Forums/getfile/830820

04 - https://social.technet.microsoft.com/Forums/getfile/830821

05 - https://social.technet.microsoft.com/Forums/getfile/830822

06 - https://social.technet.microsoft.com/Forums/getfile/830823

PS: I cannot upload the images on the body of this Forum. As my account is new, Microsoft is blocking me.

I dont want to implement others controls (like AppControl) to have a workaround and solve this problem. The perfect scenario would be to have access only to the Calc.exe and no other application.

Microsoft has done some kind of job to block this bypass?

Regards, 

Leandro Soares


Connecting to windows 2012 server

$
0
0

I cannot connect to my window 2012 file server using remote desktop services

keep getting the following error:

THE REMOTE SESSION WAS DISCONNECTED BECAUSE THERE ARE NO REMOTE DESKTOP LICENSE SERVERS AVAILABLE TO PROVIDE A LICENSE

Can anyone help


RDS 2012 Remote App Certificate Error

$
0
0

I configured RDS on a single server 2012R2 server using the instructions here (minus the load balancing part) https://msfreaks.wordpress.com/2013/12/09/windows-2012-r2-remote-desktop-services-part-1/

When I launch apps from RemoteApp I get a warning that my certificate is not trusted. I installed the same GoDaddt SSL cert on all roles, the cert matches my URL (remote.mydomain.net) Is it possible to get rid of this cert issue? This will be used on non-domain joined computers at my users homes.


John Marcum | Microsoft MVP - Enterprise Client Management
My blog: System Center Admin | Twitter:@SCCM_Marcum | Linkedin: John Marcum

Limit number of sessions per user or group

$
0
0

Hi.

I´m working on a project where I need to allow multiple sessions ( already done ), but limit the number of concurrent sessions on a RDS farm...

At the moment, we're using only one RDS server ( R&D stage ), but in the future, there'll be a farm with RDS Connection Broker and many RDS Session Hosts.

I've come to the conclusion that the best approach is to create a custom GPO, apply to the RDS Session Hosts, and use a vbscript or powershell to block the logon when the number of sessions reaches the defined limit.

I'd like to achieve a group based ( Groups: 1RDSsession, 2RDSsession and so on ... ) user logon limit. I have some ideas in mind for a single server, and a possible solution for a farm.

But before spending time on this "adventure" ( I really like this kind of challenge :) ), I'd like to know if Windows2012 provides any means for doing this kind of control.

I know there's a per server sessions limit, but that doesn't solve my problem.

Thanks in advance!

Windows RDS cal problem

$
0
0
I would like to add RD license to terminal server, however, it has an error message that said already installed, please advise

Connection to remote desktop/apps failing via RDWeb

$
0
0

Hi,

2012 R2.

I have connection broker, gateway and web access on same box.  A collection has been create with access to two session hosts.  The rdp connection is presented in RDWeb.  When clicking on this it attempts to connect but immediately fails.  If I manually create an RDP session to one of the session hosts in the collection and specify the gateway server it works correctly.

Error wise all I see on the CB is:

TerminalServices-SessionBroker-Client

Remote Desktop Connection Broker Client received request for redirection. 
User : xxxx
RDP Client Version : 5

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : xxxx
Error: Element not found.

Remote Desktop Connection Broker Client failed to redirect the user xxxx
Error: NULL

under TerminalServer-SessionBroker

RD Connection Broker failed to process the connection request for user xxxx
Error: Element not found. 

So this all looks like a connection broker issue but I cannot see any more clues as to what is causing it...

On the session host the following is logged:

Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker.
User : xxxx
Error: Remote Desktop Connection Broker is not ready for RPC communication.

there is a firewall between the CB and the session hosts so perhaps a required rule is missing?

Any ideas?

Thanks


Session Host doesnt close UPDs correctly

$
0
0

Hello.

So i have this RDSH running which is configured to use UPD.

Works well, but some users have problems with their Profiles not getting closed properly, and the user gets a temporary profile the next time they log in..

only one of those 3 users is currently logged in and if one of the others tries to log in he gets a temp profile. Only when I manually close these file sessions, the user can once again login correctly.

Is there a known issues with termnialservers not closing profiles correctly?


Viewing all 27656 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>