Hi

Hopefully this is the right place to ask, I am more after feedback and ideas around a project I’m working on. I am connecting a remote site in a different part of the country to our head office, there will be a dedicated 10M fibre VPN pipe between the two sites. 

The remote site will connect to a RD session host server running Windows 2012 with thin clients, the rest will use PC’s and I’ll pace those PC’s on our domain, the RD session host server will also hold all the data for their site. I was going to place a DC or RODC at the remote site so authentication traffic etc. doesn’t travel up the pipe, using 2008R2 or 2012. There will be 20 users connecting.

I am worried about the remote users opening, saving etc. across the pipe. Other traffic across the pipe will be Emails, Internet, Terminal Services, Data access.

Does the above sound correct, or are there better ideas to get around data access.

Feedback would be great.
Thank you

Работал сервер терминалов на Windows Server Std 2012 в течение нескольких месяцев. Случилось ему перезагрузиться, и после загрузки пользователи не смогли зайти на удаленные рабочие столы. Не работает так же и админская удаленная консоль. Пишет, не удалось проверить лицензию этого сервера терминалов и т.п. Однако сервер должным образом был активирован ранее.
Далее обнаружил, что при запуске непосредственно на сервере оснастки Лицензирование сервера терминалов выдает ошибку - отсутствует mstlsapi.dll
Данная библиотека была найдена где-то глубоко внутри в подпапках ОС (типа C:\Windows\xxxxx\7fdkrkufg4453\, точный путь не запомнил, скопировал ее в C:\Windows\system32, теперь при запуске оснастки пишет: licmgr.exe -"Ошибка при запуске приложения (0xc000007b). Нажмите ОК для продолжения"

Через удаление компонентов снёс лицензирование, перезагрузился, поставил вновь, перезагрузился, не помогло.

Can't solve this one.  8 User accounts on Server 2008 64 bit TS, using RDC protocol. Loaded Windows Live, Mail component only. Set up email accounts for all users except one.  On that account trying to open Live Mail yields:

"Windows Live Mail could not be started.  It may not be installed correctly. Make sure your disk is not full or that you are not out of memory. 0x80041161."

All clients are thin clients, no local HD. How can this occur for only one client? How to delete all traces of email account for this user and retry? The other 7 User accounts have active mail.  One possible cause would be my use of a Registry cleaner (maybe not a good idea as it was not needed for a specific reason).  Otherwise, nothing unusual, all other terminal services and programs work.  Can't find a link to how to clear our whatever is giving only this User account the error message for Live Mail.  Tried removing Windows Live and reinstalling, no go.  All Users have standard access, elevating this User to admin did not change error.  Appreciate any insights.

Hi,

We recently enabled Session Directory for our TS setup, in which we have a two servers farm, to which we might add more servers in the future, however while we want to distribute most of the users' sessions among the servers in the farm, we also have the need to map a few users' session to one particular server in that farm, since that particular server has an application that is not available on others, and we are facing a licensing cost if we were to deploy it to other servers in the farm.

Typing the server's IP/DNS name and not the farm's DNS name has no effect, still the user is redirected by the Session Directory service.

I've been googling around for an answer but I failed to find any, and I was hoping for your help.

Regards

Hi All,

I'm attempting to publish the RDWeb page through TMG, but am encountering the problem with the XSL style sheet (Site.xsl; also discussed here: http://social.technet.microsoft.com/Forums/en-US/winserverTS/thread/09fd46ae-783d-4880-a405-3f98c45b652d)

When switching IE 10 into compatibility mode or anything below IE8 mode the error message changes to an "access denied".
There are no denied connections in TMG.

I traced the communication with Fiddler and the response code on the Site.xsl file is 304, which seems to indicate some kind of caching issue (??).

I need to add that the internal DNS name of the RDWeb site is different than the external one. I've seen some posts that indicate making these the same alleviates this problem, but for various reasons I need to keep it this way - after all, that's what a reverse proxy is there for, isn't it?

Has anyone found a workaround or fix for this?

Thx in advance - M.

Hallo!

I have set up a Remote Dexktop Service using the "Quick" deployment method in Server Manager and everything is working greate internally, but I cannot start an app published in Remote Web Access from outside our network.

The problem is that it wants to start the using the internal URL, for example, server.domain.local, instead of the external one, for example remote.server.com.

I therefore want to know how I can change the default URL for the Remote Web Access server and all the Remote Web Apps in Windows Server 2012?

I have allready looked in Server Manager and I can change some of the deployment settings in server manager, but there is no way to alter the URL of the Remote Web Access server. See below images:

Pressing the internal URL only results in opening the internal URL.

This was very simple to do in Windows Server 2008 R2 using the tsconfig tool, but it does not seam to be any way of solving this in server manager.

A possible sollution would be to alter the registry someware in HKLM->Software->Microsoft->Windows NT->Terminal Services. But this can easaly lead to problems due to wrong format, etc. and is probably not supported.

Is there a simpler and supported way?

Hi,

Running Windows 2012 Standard Edition, trying to steer the RDP-Tcp (protocol) to only listen to one specific adapter instead of the default "all network adapters" using a script. The problem is that I cannot get the code to become instantly updated, rather I need to reboot to make it work which is not my cup of tea. Once I reboot everything is working, but I dont wanna boot.... code example follows below; (written in PowerShell)

#Connect to the WMI TS repository:

$objWmiTerminalServices = (Get-WmiObject -Namespace "root\Cimv2\TerminalServices" -query "SELECT * FROM Win32_TSNetworkAdapterSetting"  | Where {$_.TerminalName -eq 'RDP-Tcp'})

$result = $objWmiTerminalServices.SelectNetworkAdapterIP("10.63.240.24") #<-- The IP / Adapter I want RDP to listen to....

$result.ReturnValue #<-- Returns 0, meaning IP was valid according to MSDN documentation....

#Reconnect to object to verify that config was accepted...

$objWmiTerminalServices = (Get-WmiObject -Namespace "root\Cimv2\TerminalServices" -query "SELECT * FROM Win32_TSNetworkAdapterSetting"  | Where {$_.TerminalName -eq 'RDP-Tcp'})

$objWmiTerminalServices.NetworkAdapterName #<-- First time, going from the default configuration of all network adapters, this works, but not back and forth...

#Lets revert back to all network adapters beeing bound to RDP

$objWmiTerminalServices.SelectAllNetworkAdapters()

As soon as I reboot, connect to the WMI TS repository again, the configuration has been updated. Tried only restarting the service but with no success... any clues? Also tried making the configuration stick using the following code once I have changed the RDP to be bound a specific adapter, see below;

$objWmiTerminalServices = (Get-WmiObject -Namespace "root\Cimv2\TerminalServices" -query "SELECT * FROM Win32_TSNetworkAdapterSetting"  | Where {$_.TerminalName -eq 'RDP-Tcp'})

$objWmiTerminalServices.SelectNetworkAdapterIP("10.63.240.24")

$objWmiTerminalServices.psbase.put()

Any clues on how to make the configuration sticky directly without reboot, and how to broadcast the change to all parts of the OS directly? Take care dudes...

br4tt3

Our accountant has all of a sudden not been able to log on to our Windows Server 2003 R2 Standard Edition via Remote Desktop Connection. Other remote users can still log on, and her logon on the host computer works, but her remote login (from several different computers, both PC and Mac) does not work.  We are a very small company and the guy my boss calls for IT is unavailable, so I am attempting to troubleshoot and fix this problem.  If you attempt to log in remotely, you put in her username and password, the login rectangle just freezes, the username and password are greyed out and the cursor drags a black pixelated line.  Earlier today, the login rectangle (not the whole screen, just the login area) would turn black. Now it just sort of freezes, and all you can do is drag the cursor around and make big black pixelated lines. (Update - it's turning black again)

She said it happened after she had a crash with Excel.  Her login works fine on the host computer, but remotely the login does not work from anywhere.  Everyone else's remote login works fine.  If anyone out there has some idea of what's happening and thoughts on how it could be fixed, I would very much appreciate it, as we need our accountant!  Thanks in advance.

We currently run three Windows Server 2003 R2 64-bit terminal servers for all of our employees to work on.  We have done so for a number of years.  Since 2011 we have been running them in a virtual environment (VMware ESXi 4.1, migrating to 5.1 soon).  All in all, they have worked great for us and have been a great work environment for our employees.  Out of nowhere, however, we started having issues.

On May 20th of this year, we suddenly had one of our terminal servers seize up on us.  All employees working on this server suddenly saw their sessions stop responding entirely.  No new logins to the server could be made--even at the console.  Attempts to remotely connect via Event Viewer or Performance Monitor were no go.  Interestingly, remotely browsing the file system works fine, as well as connecting to see the services (though starting and stopping the services won't work).  The bottom line is that the server becomes completely unresponsive and all I am able to do is do a hard shutdown of the server and boot it back up.

Following is a list of bullet point notes of observations regarding this issues:

* This has happened since the given date to all 3 of our terminal servers and multiple times.  Sometimes it may go a couple days before it happens, sometimes it may go a couple weeks (we actually just went two weeks without any of this and then it happened again yesterday).

* Event Viewer looks clean when I get the server back up.  It indicates no issues logged, so whatever is causing this doesn't leave anything in the Event Viewer log.

* I have scoured the logs of our VMware ESXi server and things look mostly normal there.  No indications of abnormal events.

* I have moved the virtual machines to an entirely different VMware ESXi host and the issue still happens, so this helped rule out hardware issues on the ESXi host.

* No new updates have been made to the ESXi host servers--they have been running the same software and update revisions for quite some time now.

* I removed the most recent windows updates we had done before the first May 20th event (as best I could find for what had recently been installed), but that was to no avail--the issue still popped up

* The terminal server doesn't all seize up at once.  I'll find a few users will first report that they are seized up and usually by this time I am not able to log in at all to the console (or make any new remote desktop connection, either).  However, some users may still be able to work for a couple more minutes.  This all to say that it's not a sudden seize up for everyone on there at once.  It takes maybe 3-5 minutes from the first report before every last person is fully seized up.

* We have the latest service pack and windows updates (minus ones I removed which I had recently installed prior to the first event).

* We run the latest uphclean software (version 2.0.49 beta -- the most current that works on 64-bit terminal servers).  Unfortunately, the most recent non-beta version doesn't work on 64-bit Windows.

* The issue can happen no matter the load on the terminal server.  One of our terminal servers has half the number of people on it as the other two and roughly half the load.  The CPU usage and memory can be quite a bit lower than the maximum allocated for the machine and the issue will still happen.

* The issue doesn't seem to be tied to the length of terminal server uptime.  The first incident happened within 24 hours of a terminal server reboot.  This last stint has been two weeks of no seizing up (though right now we reboot our terminal servers weekly in off hours through a scheduled task).

* This KB article best describes the issue, except it's from 2003 and pre SP1 I think.  All current files I have are newer and I couldn't install this hotfix if I wanted to (I think it's rolled into current SPs / updates): http://support.microsoft.com/kb/832971?wa=wsignin1.0

* Another note on hardware activity.  Eventually once everyone has seized up and nobody is working anymore, the hardware monitor inside of the ESX host server shows most all hardware usage for the virtual machine going to little usage, except the CPU usage never flatlines.  There's still an accumulated usage of a couple Ghz of processor between 4 cores which indicates there's still something running on the terminal server and using CPU cycles.  It isn't anywhere near pegged, but there is still constant CPU activity after everything has stopped functioning.  I've noticed this every time one of our terminal servers has locked up.  There's a constant and steady indication of CPU usage that's roughly the same on any one of the terminal servers after it seizes up.

I'm sure there are more details and notes I don't have readily available of observations I have made of this issue.  I am fully and completely stumped and have no idea what more to do.  There are no leading indicators it's going to happen--it's just sudden and out of the blue.  I've been searching high and low for a pattern.  I've scoured through all software to see if a particular piece of software or an update to software might be causing it, but I'm finding nothing thus far.  I spent a couple hours last night after the lockup we had yesterday trying to get into the server to see what was going on (I moved all employees on this particular server off to a standby server to work while I tried to figure out the issue).  I can't get anywhere to see what might be the culprit.

For anyone who might be able to provide any insight or help into this problem, I would be truly grateful.  I am going to continue looking into other pieces of 3rd party software... and maybe printers as well (though nothing has been updated there in quite some time either).  I'm grabbing at straws to find what suddenly brought this on.

Thanks.

We are looking to transition from XenDesktop 5.6 to Server 2012 RDS.. just curious if others have done so and what your experience was? Thanks!

I have terminal servers farm with 2 RDSH Servers 2012 and User Profile Disk. I have Desktop Experience Feature installed on both servers. I add picture to account from Personalize/account Picture, and when user log off picture is missing. Looks like server didn’t save this to user profile disk.

Did I miss something or this feature is not enabled for remote desktop server role.

Thanks

Hi there !

I am working on setting up an entire 2012 RDS system, with TMG Server as reverse proxy in back Firewall mode, 2 RDG, 2 Brokers HA attached to a 2012 SQL server holding the DB, and of course, collections with multiple RDSH servers. After some headaches, everything is working ok and I am about to be done.

I just have a little (last) issue with certificates. I have been able to handle most of them with the 2012 RDS cert manager through topologie builder but the problem is on the end of the chain, on the RDSH.

We bought a public domain wildcard cert *.externaldomain.com and applied it to RDGs and Brokers. Then I also applied it on RDSH servers, and I am having "Code: 0x607" issues from RDC8/Windows8 or simply still a mismatch prompt from older RDC, telling that I am trying to access RDS1.internaldomain.lan and the cert applied to the RDP-TCP connector (using powershell or WMI commands just fine) is *.externaldomain.com and of course, doesn't match.

I am 99% sure that changing the FQDN collection to farm1.externaldomain.com would fix the problem. On 2008 R2 it is something you can do pretty easy from the RDS properties of each RDSH servers, but not on 2012 anymore.

Is there a way to change the FQDN of a collection to be used by remoteApps? Do you think it is something 2012 R2 will bring ?
If no, is the only way to proceed is to buy a *.internaldomain.lan wildcard cert?

Note that when using a Full desktop connection with RDC (through the Gateway), with farm1.externaldomain.com as host, it works just fine and the certificate is approved. (I also managed externaldomain.com domain on my internal DNS serveur to resolv internal IPs)

I would really appreciate your advises on that one !

Thanks !

David

I have a VM as broker/web access/licensing server. I have two physical hosts as session hosts.

When I try to add the physical hosts as session hosts, I get an error that the collection completed with errors - I have no idea where the log files are to decipher what these errors are. 

On the session hosts, I can connect to them but get an error that they do not see the licensing server even though it is configured in the collection properties.

Also, if I enable user profile disks, I get an error that a temporary profile is created and the vhd is named TEMP.

Any ideas? I'm two days into this.

We're running RemoteApps on WS2012. Hundreds of .rdp RemoteApps were published using PowerShell.

When I want to add additional groups through User Assigment in the GUI I get: "Cannot bind argument to paramter 'VirtualPath' because it is an empty string".

How would I do this in PowerShell, if I use the below command it doesn't add the UserGroups, it replaces the group:

Set-RDRemoteApp -Alias "rdp1" -DisplayName "rdp1" -collectionname remoteapps -connectionbroker rds.domain.local -UserGroups ADGroup1

Here's my situation.  I'm fairly new to this type of work but have been tasked with doing some research and hope someone here can help clear this up as there is WAY too much available information to process at times. 

We're getting rid of an existing domain (A) which still has the resident Terminal Server on it.  I have already migrated the users and desktops to the new domain (B).  There are several people who are strictly thin client/TS users and others who are desktop users who also use the Terminal Server for financial applications.  Some of the users are also setup with POP Outlook accounts on the Terminal Server, though their .pst files reside on their Home folders on another server.

If I just migrate the server do the user profiles remain intact or do I need to perform some work or make some type of provision for that before we migrate the server?  is there any specific version of the ADMT that I need to use for this?  We setup a temporary VM specifically to run this when moving the users and PCs over but that guy may not exist any longer due to drive space restrictions.  It can always be redone though.

What's the best way to handle this?  should I just jump in and move this thing over one night or is it not as simple as that?  There are about 25 users to consider.

Thanks,

Mike

Hi Everyone,

I have managed to install and configure WS2012 with Hyper V and a virtualized TS Server. In fact the inputs and problems/solutions available in this forum have helped me.

I have following problem :

I have created a virtual which is a RDS Server It has RDCB/RDSH/RDWEB /RDGateway roles installed on it. The Remote DEsktop Licensing shows no errors or issues. If I login through IE, I am able to login and see the published the applications on this server. Both my ADDS server and TS Server as well as Thin Clients are in the same subnet on local LAN within the premises.

I have a few Thin Clients in my local LAN network with WIN7 embedded. These are not able to log in through RD Gateway.

1. If I give IP address of the RDS server & tick automatically detect RD Gateway settings, the RDP Client connects as a Remote Console Admin. Initially it says the server is an untrusted server, but if I say connect anyway, it connects.

2. If I provide IP address in General Tab ( remote computer ) and  RDGateway server IP Address in Advanced Settings ' use following Gateway Server' it returns an error stating ' the subject in the certificate and server name does not match ' and does not connect.

3. INstead of IP Address, if I provide FQDN for TS Server ( TS-Server.mydomain.local ) ,as well at 'use this RDGateway server , it says the RD gateway server is temporarily unavailable, please try later.

This is holding up my go-live date for the server,. Any help will be highly appreciated.

Added On 14-06-2013

 I have tried to do a Remote DEsktop connection from TS Server to itself, even there it says ' The RD gateway server is temporarily unavailable, please try later. '

I have checked logs but there in nothing in them.

From :

shekhar-nsk