Hi ...

we have a 2012 TS Fram with 2 SessionHosts/ 1 Broker/ 1 WebAccessGW and application like office/ sapgui/ sap bussines objects etc. ... all applications work fine but with sap gui we have performance probleme ... when the bandwith is not so good the sap gui window is small or we have a half windows and when i click in the window is it normal. when the bandwith is normal sap gui works fine. my question is, we can we fixed configure the rdp connection bandwith?

thanks for help

tmss999

Hello everyone

I'm having a problem with my NLB RDP-Farm setup. It randomly stops working without any error logged. All I can see is that one host only sees itself and the others see all the hosts.

In the NLB Manager one host is green (converged) and the other two are yellow (converging). It worked fine on Friday (all hosts green and converged).

The servers are all Windows Server 2008 R2 SP1 running as a VM on an ESX 4.1. They're currently on the same host, no VMotion took place during the weekend. They have a single network card and use NLB in Multicast mode. I can ping all the Servers without a problem.

I already installed https://support.microsoft.com/kb/978943 but it didn't fix it.

It would be great if someone could help me out here, because I'm starting to run out of ideas.

Thanks in advance.

Cheers

- Darnor

WLBS Output (in German):

--- Host 1 ---

C:\Windows\system32>wlbs query
WLBS Clustersteuerungsprogramm V2.6 (c) 1997-2007 Microsoft Corporation.
Cluster <cluster IP>
Host 1 ist in den zusammenführenden Status 1 mal seit dem Clusterbeitritt
 gewechselt, und die letzte Zusammenführung wurde zum folgenden Zeitpunkt fertig
 gestellt: 11.03.2013 14:33:37
Der Host 1 wurde als STANDARD mit folgenden Hosts als Teil des Clusters
zusammengeführt:
1

--- Host 2 ---

C:\Windows\system32>wlbs query
WLBS Clustersteuerungsprogramm V2.6 (c) 1997-2007 Microsoft Corporation.
Cluster <cluster IP>
Host 2 ist in den zusammenführenden Status 1 mal seit dem Clusterbeitritt
  gewechselt und befindet sich immer noch im Zusammenführungsstatus.
Der Host 2 wird mit folgenden Hosts als Teil des Clusters zusammengeführt:
1, 2, 3

--- Host 3 ---

C:\Windows\system32>wlbs query
WLBS Clustersteuerungsprogramm V2.6 (c) 1997-2007 Microsoft Corporation.
Cluster <cluster IP>
Host 3 ist in den zusammenführenden Status 1 mal seit dem Clusterbeitritt
  gewechselt und befindet sich immer noch im Zusammenführungsstatus.
Der Host 3 wird mit folgenden Hosts als Teil des Clusters zusammengeführt:
1, 2, 3

----------------

WLBS display:

--- Host 1 ---

C:\Windows\system32>wlbs display
WLBS Clustersteuerungsprogramm V2.6 (c) 1997-2007 Microsoft Corporation.
Cluster <cluster IP>

=== Konfiguration: ===

Current time                = 11.03.2013 14:40:10
ParametersVersion           = 6
CurrentVersion              = V2.6
EffectiveVersion            = 00000201
InstallDate                 = 0x513A4BEB
HostPriority                = 1
ClusterName                 = rdp.mycompany.com
ClusterIPAddress            = <cluster IP>
ClusterNetworkMask          = 255.255.254.0
DedicatedIPAddresses/       = <server 1 IP>/255.255.254.0
DedicatedNetworkMasks
McastIPAddress              = 0.0.0.0
ClusterNetworkAddress       = 03-bf-xx-xx-xx-xx
IPToMACEnable               = ENABLED
MulticastSupportEnable      = ENABLED
IGMPSupport                 = DISABLED
MulticastARPEnable          = ENABLED
MaskSourceMAC               = ENABLED
AliveMsgPeriod              = 1000
AliveMsgTolerance           = 5
MaxConnectionDescriptors    = 262144
FilterICMP                  = DISABLED
ClusterModeOnStart          = STARTED
PersistedStates             = NONE
NBTSupportEnable            = ENABLED
UnicastInterHostCommSupport = ENABLED
BDATeaming                  = NO
TeamID                      =
Master                      = NO
ReverseHash                 = NO
IdentityHeartbeatPeriod     = 10000

NumberOfRules (1):

      VIP       Start  End  Prot   Mode   Pri Load Affinity
--------------- ----- ----- ---- -------- --- ---- --------
ALL              3389  3389 TCP  Multiple      Eql Single



=== Ereignismeldungen: ===

Das Ereignisprotokoll konnte aufgrund folgender Ursache nicht geöffnet werden:
Der Vorgang wurde erfolgreich beendet.

--- Host 2 ---

C:\Windows\system32>wlbs display
WLBS Clustersteuerungsprogramm V2.6 (c) 1997-2007 Microsoft Corporation.
Cluster <cluster IP>

=== Konfiguration: ===

Current time                = 11.03.2013 14:36:08
ParametersVersion           = 6
CurrentVersion              = V2.6
EffectiveVersion            = 00000201
InstallDate                 = 0x513A0E3D
HostPriority                = 2
ClusterName                 = rdp.mycompany.com
ClusterIPAddress            = <cluster IP>
ClusterNetworkMask          = 255.255.254.0
DedicatedIPAddresses/       = <server 2 IP>/255.255.254.0
DedicatedNetworkMasks
McastIPAddress              = 0.0.0.0
ClusterNetworkAddress       = 03-bf-xx-xx-xx-xx
IPToMACEnable               = ENABLED
MulticastSupportEnable      = ENABLED
IGMPSupport                 = DISABLED
MulticastARPEnable          = ENABLED
MaskSourceMAC               = ENABLED
AliveMsgPeriod              = 1000
AliveMsgTolerance           = 5
MaxConnectionDescriptors    = 262144
FilterICMP                  = DISABLED
ClusterModeOnStart          = STARTED
PersistedStates             = NONE
NBTSupportEnable            = ENABLED
UnicastInterHostCommSupport = ENABLED
BDATeaming                  = NO
TeamID                      =
Master                      = NO
ReverseHash                 = NO
IdentityHeartbeatPeriod     = 10000

NumberOfRules (1):

      VIP       Start  End  Prot   Mode   Pri Load Affinity
--------------- ----- ----- ---- -------- --- ---- --------
ALL              3389  3389 TCP  Multiple      Eql Single



=== Ereignismeldungen: ===

Das Ereignisprotokoll konnte aufgrund folgender Ursache nicht geöffnet werden:
Der Vorgang wurde erfolgreich beendet.

--- Host 3 ---

C:\Windows\system32>wlbs display
WLBS Clustersteuerungsprogramm V2.6 (c) 1997-2007 Microsoft Corporation.
Cluster <cluster IP>

=== Konfiguration: ===

Current time                = 11.03.2013 14:41:22
ParametersVersion           = 6
CurrentVersion              = V2.6
EffectiveVersion            = 00000201
InstallDate                 = 0x513A4C2E
HostPriority                = 3
ClusterName                 = rdp.mycompany.com
ClusterIPAddress            = <cluster IP>
ClusterNetworkMask          = 255.255.254.0
DedicatedIPAddresses/       = <server 3 IP>/255.255.254.0
DedicatedNetworkMasks
McastIPAddress              = 0.0.0.0
ClusterNetworkAddress       = 03-bf-xx-xx-xx-xx
IPToMACEnable               = ENABLED
MulticastSupportEnable      = ENABLED
IGMPSupport                 = DISABLED
MulticastARPEnable          = ENABLED
MaskSourceMAC               = ENABLED
AliveMsgPeriod              = 1000
AliveMsgTolerance           = 5
MaxConnectionDescriptors    = 262144
FilterICMP                  = DISABLED
ClusterModeOnStart          = STARTED
PersistedStates             = NONE
NBTSupportEnable            = ENABLED
UnicastInterHostCommSupport = ENABLED
BDATeaming                  = NO
TeamID                      =
Master                      = NO
ReverseHash                 = NO
IdentityHeartbeatPeriod     = 10000

NumberOfRules (1):

      VIP       Start  End  Prot   Mode   Pri Load Affinity
--------------- ----- ----- ---- -------- --- ---- --------
ALL              3389  3389 TCP  Multiple      Eql Single



=== Ereignismeldungen: ===

Das Ereignisprotokoll konnte aufgrund folgender Ursache nicht geöffnet werden:
Der Vorgang wurde erfolgreich beendet.

Could someone help with the bellow?

We have two servers that we remote into.

Because of this the server that I have set up with remote app I have had to change to port:3392. However remote app no longer works as is is just trying to connect using the server name without the specified port.

Is there a way to specify the port number it should use?

Ali

Hi All,

Ever since I ran the update for 8.1 my Surface is not able to remote desktop to our Terminal Servers using Session Broker. Our RD Infrastructure is setup with 3 x RD Session Hosts and 1 x Sesison Broker. We have a common DNS name for all 3 RD Session Hosts (remote.<contoso>). If I happen to land on the session server with the least amount of users it works but if I happen to need to be redirected to another server I get the generic 'Remote Desktop can't connect to the remote computer' error. Now each Session Host has 2 NICs (an internal private LAN NIC and one with a Public IP Address). Both IP address are set to be sent when doing the relocation and here is where I thing the issue it. I only have this issue when connection from the LAN. When I connect externally the redirection works. It seems to be that the new version of the RDP client (6.3.9600) doesn't handle multiple IP address when redirecting while the older one does and because the public IP address is the smaller number that is the one that gets used first when it attempting the redirection and hence I don't have the issue when connecting externally

I could be wrong with that assumption but that seems to be the only explanation for it that I have seen while investigating it for the last few days.

Has anyone else come across this issue with the Windows 8.1 and 2008 R2 Session Broker?

Windows 2012 R2 Standard Server with Windows 7 Remote Desktop Connection client of version 6.3.9600.

I would like to "lock-down" the configuration dealing with "what" a user who is able to RDP into a server is able to do and or have done. For example both devices (2012 Server and Windows 7 Client) are on the domain, when a person RDP's into a server I do not want their domain drives to map. Also a few other things like printers, etc.

I have modified the registry on the server:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]

However the settings do not apply, as my drives still map when I make my connection.

I then modified keys in this location on the server:
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]

With the same "non-applying" results. Any ideas? Thoughts? Advise?

I've not found a way to enable this for 2012 R2 (or even 2012) yet, only for older versions.

If I'm logged on to a PC that's joined to my Active Directory I'd like my RDWeb site to not prompt me for credentials and just take me to the list of RemoteApp applications. (The applications should then also not prompt for credentials when they're launched)

Thanks.

We have Windows 2008 R2 Remote Desktop farm with deployed RemoteApps.

We use Easyprint by group policy settings. No printer drivers are installed on RD servers.

But every time when client computer with HP LJ P2050 printer make connect to RD farm, driver for HP LJ 2050 be installed on RD server. 

In result some clients print with Easyprint, and other  with HP LJ 2050 driver.

Only HP LJ P2050 printer driver installed to RD server automatically.

How to disable HP LJ 2050 printer driver installation to RD servers ?

Sorry for bad English.

Hi All,

I have a Server 2012 RDS farm with a handful of RemoteApps published.  I have about 150 users running these applications.  We are having issues with computers running Windows 8/8.1 that have multiple monitors.  We can run the RemoteApps fine but when we minimize the app and then try to restore it, we get a black window.  The only way to fix it is to right click the app in the taskbar, choose close window, and reopen the app.  This only seems to happen on Windows 8/8.1 machines with multiple monitors.  If I disconnect the second monitor then the app can be minimized and restored without issue.  The monitors in use do have different screen resolutions but this shouldn't matter as RDS is supposed to support this.  I have not seen this issue on any of my Windows 7 computers.  Is there any settings that I should be looking?  I don't think this is an app issue as I can recreate the problem using MS Word as a RemoteApp.  In most cases, additional monitors are connected via USB using DisplayLink devices.

Thanks for your help!

Scott

We have had RDS 2012 in production for about a month or two. Every once in a while i am getting a user with a empty UnifiedSessionID. Any thoughts on what is causing this? 

Get-RDUserSession | Where-Object {$_.UnifiedSessionID -eq $null} | fl

When this happens the user seems to be hung. Cant login to the environment. I cant kick them out with the  

Get-RDUserSession | Where-Object {$_.UnifiedSessionID -eq $null} | Invoke-RDUserLogoff -Force

as it says access denied.

I am not even really sure how i am fixing them... after some tinkering they are fixed. This morning i rebooted the VDI management box and it cleared it up.

Just trying to get a definitive answer to the age old question of can we remove the initial user logon requirements when accessing the RD Web Access server in a 2012 R2 RDS deployment?

I was under the impression that the Single Sign-On only removes the logon prompts when users try to access a RemoteApp or Session Host once they've logged on to the Web Access server?

Is there a way to use the current users credentials (they're all connecting from domain joined windows 7 or 8 machines) to logon to the RD Web Access site?

Cheers for now

Russell

We have a single server on our clients domain, running WS 2012 Standard.  Remote Desktop CALs were also purchased for each of their 7 users.

Server roles include both remote desktop (licensing server as well as various remote desktop roles) and AD DS.

The server is a new Single server install for a Small Business.  In the past, this type of client would usually have used SBS and be able to perform all of the roles needed for a business with one server.  Now it seems that Microsoft is forcing the issue and making small businesses purchase several servers to accomplish the same tasks that SBS 2011 would handle easily.  Or they need to setup a virtual environment with multiple servers and server licensing.

I have preformed two re-installations of the OS and when the AD DS and Remote Desktop services are installed the Remote Desktop management service fails to run. 

The first install was the OS, AD DS and Remote Desktop Services, Updates and I also configured the Licensing Manager, Activated and installed RD CAL licenses.  I can get users to connect remotely, but I cannot start the RDMS and get any management of the connections to work.

The second install I left the server as standalone (WORKGROUP) and installed the Remote Desktop Services role, performed all 79 Updates.  Remote desktop worked at that point, but still could not run the Management tools, because it required a Domain User login NOT a local login.  At this point all of the Services for remote desktop in AdministratorTools|Services would run.  The last step I did was add the AD DS role and then the RDMS service would no longer start.

The Overview for Remote Desktop Services role reports"

"The server pool does not match the RD Connection Brokers that are in it. Errors:

1. Cannot connect to any of the specified RD Connection Broker Servers. Ensure that at least one server is available and that the Remote Desktop Management (rdms), RD Connection Broker (tssdis), or RemoteApp and Desktop Connection (tspubrpc) services are running.

Also, I found on this Forum:

"This issue is addressed for WS 2012 in Article ID: 2799605, with a servicing stack update available in Article ID: 2871777.",

However even after installing that update the RDMService still fails to start.

hello

have a program that will start on the RDSH host server and run successfully but program will not run through RomoteApps publish.

target :C:\dlc101b\bin\prowin32.exe -pf login.pf -T "%TEMP%"

start in :C:\NxT\code

how do I configure remoteapp programs parameters  to make this program work

Thanks

Hi,

so I was just wondering before I purchase any rdscal license for server 2008r2, is the rdsession host accessable via internet(mainly a remote office) when there are no licenses installed other than the 120 day trial.

I have a Server 2012 level domain with a Server 2012 RDS server running all the roles on one machine with a default collection.  Everything works just fine.  As a part of the RDWeb App page you have the "Connect to a remote PC" link at the top.  This works beautifully for administrators.  However, most all domain users are by default standard users and this link fails for them with the above error.  I've added/enabled all the recommended GPOs to allow connection through Remote Desktop that I've been able to find through searches but still this problem persists.  If I change the user to be a local administrator on their workstation (not desirable) it works just fine.  What am I missing or failing to consider?

I tried adding the group \Domain Users to the Remote Desktop Users security group and that didn't work either so I removed it as they don't need access to the DC.  I see many other discussions around this error but I haven't found the answer I need.

Hello Everyone,

In a Server 2012 environment with RD Gateway and RD Web Access, how can I restrict access to specific published apps externally but still permit access internally?  Using the ACL on the published app doesn't work because then the app is not available internally.  The only options I see in RD Gateway are for access to "Network Resources" (computers).  So this doesn't work either.  Since we can't deploy apps using a MSI anymore, the web feed is the only option.  This means I can't use the option to not display the app in RD Web Access or it won't be distributed for internal use.  Where is the filter that says User A can run RemoteApp A internally using the shortcut in the Start Menu but not externally using RD Web Access but still allow them to run RemoteApp B both internally and externally?

Thanks,

Scott

Hi,

I am trying to figure out how to configure Windows 2012 R2 RDCB for HA. I know that the new RDCB role is mandatory in 2012 and there is a native HA but the setup is for a small customer with only 25 clients and the native way of doing HA means another host and SQL license. This adds complexity and another point of failure. I was hoping that I can use NLB to load balance the RDCB role. My problem is that right now I have two VMs running RDSH and RDWA. One of the VMs is also running the RDCB role. If the VM with the RDCB is down users are unable to access the second RDSH. Here’s the setup:

Two physical host running ESXi 5.1.

VM1 on ESXi1  - RDCB, RDSH, RDWA

VM2 on ESXi2 - RDSH, RDWA

I found many posts about load balancing using NLB for all of the roles but not the Connection Broker.

Regards,

Ivailo

Windows Server 2008 R2

I have multiple consultants doing RDP to a server. Problem with this is each of their AD accounts gets a different, separate login profile on the server. They wish to have a common profile so that any changes done by one will be seen by other consultants as well as having a common Desktop where they keep notes and stuffs.

Is it possible to have multiple RDP users login to the same profile in the server?

Hi,<o:p></o:p>

I have managed to configure and install RDS Windows 2008 R2 Farm with 3 Remote session hosts and one connection broker .One of the session host servers is also the connection broker. All connected to my domain and so on.<o:p></o:p>

It seems to work fine until all of a sudden, with no alerting, the server become inaccessible and would not accept any connections. When I log on to the server using KVM (Physical access with monitor and keyboard) , it seems that the serer function extremely slow ! <o:p></o:p>

Moreover, when I try to ping another server in the same domain a get "destination unreachable".
When I look at the services status, I notice that remote desktop management service is down. When I try to start the service I get the error: "Windows could not start the RemoteApp and desktop connection management service on local computer.<o:p></o:p>

Error 0x800706fd: the trusted relationship between the workstation and the domain failed."<o:p></o:p>

Only after brutal shutdown of the whole server it becomes stable again and accepts connection and function properly untill next time.

I have already tried to replace the cable connected to the switch ,the port and the network card but no luck. ( all other servers are onnected to the same switch so I assume there is no problem with the switch )

The server can function properly for 2 days and suddenly ( apparently something happens )
and then it became slow and lose the connection to the domain and/or network.<o:p></o:p>

Please advise ASAP this is my connection broker server of my RDS Farm.<o:p></o:p>

Thanks in advance.