I have an issue with old Windows CE devices connecting to an new Windows 2016 terminal server. The old CE devices use the older login where you get connected to the server and then authenticate, as opposed to RDP 6, where is prompts you for credentials.

The CE devices are only 240x320 touchscreens (Old Motorola MC9090 RF guns), so what happens on the display is the username and password field are cut off, and users have a difficult time selecting these fields.

Previous Windows 2008, the login screen had a different orientation, so it was more user friendly for those devices. Any one have any ideas if its possible to rearrange the screen or change resolution on just this screen? 

I have tried just about everything and would really be disappointed to have to revert back to 2008 R2, just because of a login screen. Updating or getting new devices are not possible at this time. 

I have also tried:

• to auto login the account - i know not secure, but could not get it to work
• remove user profile picture - was not able to get the image removed.

This is a picture of what is displayed:

Thanks for any help on this.

Hi:

Please see attached image below. 

On this Windows Server 2012 R2 w/RDS deployment, the RD Licensing Diagnoser shows an error that the license server does not have any installed licenses with Product Version: Windows Server 2012 and Licensing Mode: Per User.

However, on the same page as you can see in the screenshot, it shows the license server cfg. details with License Type: RDS Per User CAL, License Version: Windows Server 2012, Installed: 5, Available: 0. We purchased and installed 5 CALs on the license server and it's showing those 5 CALs, so why does the RD Licensing Diagnoser show this error when it's showing the licenses on the same page??? 

Thanks very much for any input on how to fix this issue.

Bob H.

Bob Herman IT Tropolis

We are looking for an expert consultant to set up Windows RDS server at our Anaheim, CA office. This will be accessed by our staff from around the world for accessing various applications, including Office 365.

The need is immediate. Any contact information will be greatly appreciated.

Hello everyone,

First of all, if this topic is in the wrong place, please tell me, I will move it. I don't know if it's a Linux,Windows or Citrix issue, but I hope someone would help me and provide usefull insight.

I have an issue regarding Linux endpoints and TS licences. Here are the details :

- Citrix Xenapp 7.15 CU2 infrastructure (1 DDC, 2 VDA) on Windows Server 2016 standard, no Netscaler. Users connect and get a published desktop with everything they need.

- Around 20 Linux endpoints (Debian 9.2, Linux receiver 13.10).

- TS CAL per device.

When the Linux endpoints connect, the TS license server issue only temporary licences. The linux endpoints appear multiple time in the license manager, but always as temporary.

The event viewer on the VDA shows the EventID 1028 (The terminal server client <client name> has been disconnected because its license could not be renewed. ) and users are disconnected every hour. The event viewer on the TS licence server shows nothing in its event viewer regarding license issuing.

As I understand, every device is identified through a unique Hardware ID. It is stored in a registry key on Windows devices, and (I think) in the /etc/machine-id file on Linux devices. I have double checked, all my Linux endpoints have a unique machine-id.

I managed to get a small powershell script to check the hardwareid tag for the endpoints connected to my TS license server. The result of the script shows several different hardwareid for the every devices.

I have tried to rebuild the licensing server, delete the ~/.ICAClient rep, but with no luck.

If anyone have any usefull information about how is generated the TS license hardwareid for Linux endpoints, I will be very gratefull.

PS: This post is also on the Citrix forum.

I know I can hide the c: and d: drives via group policy in RDS, but is there an easy way to hide network drives that are mapped on the client endpoint.

The clients have a V: drive mapped which they need on their local endpoint but when then they log into the RDS session it maps it again.  I'd prefer they only see the one mapped as part of their RDS login.

Hello,
I am wondering if its possible to achieve the native client resolution if host has a different resolution without seeing black stripes on the sides or being stretched (because resolutions do not match I believe).

-------------------------------------------
Host: HP Workstation; Win7 Ultimate SP1 x64 ---> HP monitor with native resolution of 1280x1024. (video card is an NVS 310 which supports higher resolutions)

Client: HP ThinClient; Windows 10 IoT Enterprise for Thin Clients 64 ---> 3xHP FHD monitos, 1xHP 55" FHD display
---------------------------------------------

For establishing connection we are using mstsc.exe (remote desktop connection).

Any feedback is appreciated

JaimePR,

Hello,

I have different environment RemoteApps that are being published under the RDWeb site. 

I have RDS installed on WindowServer 2012 R2. To make more sense for the End User I think it would better if I publish the RemoteApps under different instance headings.

I want the instance name as a heading instead of separate folders.

Can anyone please advise how to make that happen

thank you

Shekar-Technet

Hey

If I have credentials saved for an RDP connection, it logs me in when I connect. But if the session locks (my servers all timeout after 10-15 minutes and lock), I have to type my password to unlock (or cheat and close/reopen the connection :-)

Is there a way to resend the credentials and unlock an existing open, locked RDP session?

Thanks in advance

Mike

I have a Windows 10 client and a Server 2012R2 server. The client is set to 1920x1080 at 125%. In the past, whenever I connected via RDP, the session automatically went to 125%, regardless of the resolution (I sometimes use 1024x768, or other resolutions), just like it is supposed to. In the last few weeks, it has suddenly stopped doing this. I've tried different accounts, making sure I logged off the Server session (not just disconnected), changing the resolution and magnification on the client, and trying different Server 2012 R2 servers. Nothing works. I really don't want to do some of the manifest solutions that others talk about.

It is almost as if an update to either the server or the client has broken this.

Is there some way of diagnosing this? Is there a log of the connections, that would tell me what the client says it is, so I can see if the client isn't reporting the scale factor, or the server isn't paying attention?

Does anyone else have a suggestion, or is anyone else noticing this issue?

Thank you.

Jeremy Heymann Market Mentor Online

Hi all,

Some of our users are experiencing issues when connecting from a Windows Server 2008R2 terminalserver to our 2012R2 Remote App environment. 

Our setup is as follows:

Windows Server 2012R2

Gateway/connection broker 2012R2

Allow connections only from computers with NLA.

A webfeed url is used to connect: https://***.***.nl/RDWeb/Feed/webfeed.aspx 

Followed by AD domain creds.

We are using Kemp LoadMaster loadbalancers: Vers:7.1.35.4.15528.RELEASE.

The loadbalancers are allowing TLS 1.0, TLS 1.1, TLS 1.2, SSL acceleration is enabled.

We suspect that the issue is caused by a (or multiple) Windows updates on the 2008R2 side.

Does anyone have an idea?

Thank you in advance!

RDS 2012
Remote app server 2012 - approx. 20 clients - get these errors in event viewer repeatedly. Some users report they must restart PC after returning from being away in order for remote app to allow them to reconnect.

How could I get rid of these event viewer errors?

RDS Log File

Log Name:      Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational

Source:        Microsoft-Windows-RemoteDesktopServices-RdpCoreTS

Date:          3/3/2015 7:47:51 PM

Event ID:      97

Task Category: RemoteFX module

Level:         Warning

Keywords:     

User:          NETWORK SERVICE

Computer:      REMOTE1.XXX.local

Description:

The RDP protocol component X.224 detected an error (0) in the protocol stream and the client was disconnected.

System Log Error

Log Name:      System

Source:        Schannel

Date:          3/4/2015 10:42:02 AM

Event ID:      36887

Task Category: None

Level:         Error

Keywords:     

User:          SYSTEM

Computer:      REMOTE1.XXX.Local

Description:

A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 49.

I cannot get my users to connect to their RDS desktop. I have a test network that I'm using for my server certification. I have a server running 2012r2 that is configured as a domain controller. I have another server connected as a member server to the domain. The member server is configured as RDS(terminal Services). This is the scenario: My users login to their Active directory desktop. From there, the users attempt to connect with remote desktop connection to their RDS session host desktop. From what I can see, the user is connecting to the the RDS server itself, just like the normal RDS connection, instead of their session host desktop. When a user connects to their desktop, and opens the start menu, they can see the server manager and everything that's on the RDS server desktop. It's not the the user session host desktop. Can someone help me to fix this configuration. I will send any screenshot or log you may need. Thank you.

We currently manage an 8 node Windows 2008 RDS farm which serves approximately 250 users. We utilise roaming profiles and redirected folders. The majority of our users operate from non-domain joined thin clients. Users connect to a full RDS desktop session rather than using local client desktops and published apps.

We will be replacing the existing thin clients with new domain joined t/clients and domain joined laptops. We are planning to deploy a new Windows 2016 RDS farm. Our initial plan was to stick with RDSH rather than VDI, however, we intend to use published apps with local desktop sessions. are also thinking about utilising both redirected folders and user profile disks.  VDI looks interesting but its unknown territory to us and we're struggling to get to grips with the pros, cons, costs, & licensing implications of RDSH vs VDI. There seems to be a lot of inconsistent and confusing documentation out there!

Anyone been in a similar situation or can point us in the direction of some straight forward documentation?

I am having some difficulties in getting RDS to work in a highly restricted environment in Azure where all network traffic needs to be explicitly allowed in firewall rules.

In the configuration, the RD Brokers and RD Session Hosts are on different subnets. 

I have reviewed documentation such as: 

https://social.technet.microsoft.com/wiki/contents/articles/16164.rds-2012-which-ports-are-used-during-deployment.aspx

https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/RD-Gateway-deployment-in-a-perimeter-network-Firewall-rules/ba-p/246873

I tried allowing outbound TCP 5985 from the RD Session hosts to the RD Brokers. 

That didn't help.

The only thing that works is allowing all outbound traffic between the RD Session Hosts and the RD Broker subnets. 

Azure isn't very user friendly when it comes to trying to figure out exactly what traffic is being blocked by NSGs. 

Can anyone assist with exactly what traffic needs to be allowed outbound from the RD Gateway to the RD Broker?

Thanks.

We just installed two new vmware 2016 standard servers.  One is setup as DC and the other a TS.  There are 30 dell wyse 5070 thinOS thin clients that users are using to connect in to the TS using new 8 Cisco AP (1852) with a new 3504 Cisco WLC.

From day 1 there have been problems with the thin clients dropping their connection to the TS and having to reconnect back in.  The common cause is when using Google maps or anything that uses graphics, which they use quite a bit for dispatching employees.  The screen will freeze up on the RDP session itself, and they will kick back out to the thin client desktop.  At the time of the disconnect we have noticed that the wireless on the thin clients disassociate with the Access point, and then re-associates.  Our first though was that the problem was with the newly installed Cisco AP's, but that was ruled out when we were not able to reproduce the problem from a laptop using wireless.  

I have changed some group policy settings on the terminal server and set RDP compression to "Optimized to use less network bandwidth" and RDP Experience to "Optimized for minimum bandwidth usage".  This has helped somewhat.  We went from users dropping ever 5-10 minutes, to now maybe 4-5 drops total across all users per day.  The problem with these settings is that now users are having a hard time with the graphics performance.  Moving windows around is laggy, maximizing and minimizing windows is slow to refresh, and lots of pixilation.

I currently have a ticket open with Dell to look into these issues as far as the thin clients go, but they are being less then helpful.  

I am trying to set up an application on a Windows 2008 R2 Remote Desktop server. It is a fairly old application, and we are moving it from desktops to a terminal server (.....long story......domains merging.......legacy apps). There is a component of the application which just refuses to play nice. The application is a document management system (TechnologyOne ECM), and when you install it it adds a 'Send To' entry to Explorer. The idea is you right-click a file, select Send To ECM, and ECM opens up with the file ready to be registered.

The 'Send To' entry isn't a normal part of the application install - you need to do a custom install and select it - but on the image we apply to our PCs it wasn't installed, so whenever we re-image a PC we just uninstall this application, reinstall it and the missing Send To target works just fine. But I can't get it to work on a terminal server. I have tried the uninstall/reinstall trick, but this does not help. I have created a brand new VM and installed the application fresh, but this hasn't worked either  I have grabbed a copy of ShellExView and I can see that this component is listed as an installed shell extension. What normally happens on a PC is when a user first logs on, setup for this shell extension is triggered and the appropriate entry is added to the Send To menu. On a terminal server, this first-logon process does not seem to be being triggered for anyone other than the first user to log on.

I logged onto the terminal server as admin, and did a regsvr32 on the dll in question. The next time a user logged on to the terminal server, the first-logon process was triggered and the Send To entry was properly added and configured for that user, and that user was able to right-click a file, select Send To ECM and ECM opened as it should.

However, the first-logon process has not run for ANY subsequent users logging onto the terminal server. I am at my wit's end.....I have spent hours combing through Process Monitor logs......countless uninstall/reinstalls.......countless rebuilding-of-the-terminal-server-and-start-again episodes. Nothing I seem to do will make this shell extension register properly for anyone other than the first user of the terminal server.

If anyone has any ideas I would be most grateful.

hello,

When I deploy a remoteapp server under Windows Server 2012 r2, after the RDS server is deployed, DirectX can be used normally when I login to the server locally, but when using another windows server 2012 with rdp8.1 protocol, I login to the session server remotely, using dxdiag command, and find that only Directx3d is enabled. Directxdraw acceleration and AGP texture acceleration are not available.

Gpedit. MSc > remote session environment: configure remotefx, optimize visual experience when remotefx is used, optimize visual experience for remote desktop service session, use advanced remotefx graphics for remoteapp, configure image quality of remotefx adaptive graphics, configure remotefx adaptive graphics, and use hardware for all remote desktop service sessions Default graphics adapter.

All of these have been set up.

I have deployed another server successfully before, Directx3d function can work, but this one can not work, there are hardware differences between the former using NVIDIA Quadro k4000 graphics card, the latter using NVIDIA geforce GTX 1060 graphics card.


is there any omissions in the deployment process?

thanks.

Hi,

i'm trying to extend a Remote Desktop environment, consisting of an RD Gateway server and 2 Session Hosts. I came across a behavior when establishing the connection to the session hosts that I can't quite explain.
In my understanding, the connection-sequence is as follows: The client establishes a connection to the connection broker. This decides which session host is suitable, and returns the corresponding host, stating the IPv4 address and fqdn. (I use the RDP file generated via RD-Web).
Although I could not find a clear statement, the behavior seems that the client is now trying to establish the session based on the IPv4 address.
With this behavior, I now have 2 use cases that cause problems:
Access to RD-Farm via DirectAccess: After DirectAcces can not directly address IPv4 addresses, the connection will fail. A direct RDP connection to the session hosts specifying the fqdn works fine.
The second case concerns a NAT-linked external network segment. Although the DNS of the foreign network responds with the correct addresses from the transfer network, here too it seems that the client uses the internal addresses reported by the Connection Broker.

I am now at the end of my knowledge, and on the one hand would ask for your opinion on my stated behavior. Of course, I also gladly accept a solution proposal. Maybe there is a way to force the connection to the session host via fqdn. That should actually solve the problems described.

Thank you very much for any help

Hello,

My goal here is to create an Outlook profile for each user who launches a published app from an RDS server by opening Outlook with zero config and then terminating the Outlook app that was spawned from the RDS server. We have GPO in place to enable Outlook zero config and no PST file (online mode only) when Outlook launches from the server. Each day the user profiles on the RDS have to be removed and are recreated when user logs in next day. 

To accomplish this I created a .cmd script file that is launched as a published app:

@echo off
cmd /c Start /min outlook.exe
Start AOSCLUSTER.axc
ping 192.0.2.2 -n 1 -w 30000 > nul
taskkill /f /im Outlook.exe

The Script will start Outlook minimized and will start our ERP program. The script is supposed to wait 30 seconds and then terminate Outlook that was spawned form the server. The Outlook termination command terminates the Outlook session spawned from the server when Outlook isn’t already running locally on the client machine. When Outlook is already running locally on the client machine the taskill command doesn’t kill either Outlook session. Any ideas on how I could get Outlook to terminate when Outlook is already running locally on the client machine?