Hi guys,
We are exploring the possibility of deploying a remote desktop services solution across two physical sites. I did not manage to find any design guide and information on the bandwidth requirements. Has anyone deployed such solutions and what will be the consideration factors in the design?
Thanks guys,
Thank you for your reply to my original question. I want to know if you can put the fldrredir on the primary domain controller.
A yes or no would be ok, but if no please give me a reason, and again thank you.
Bill Miracle
Hi everybody,
I'm using Ulteo OVD. With this RDP virtualization software, sometimes when you use an application and try to open/save a file, when the Common File Dialog is opened and you choose "my computer", you can't see the folders that are redirected from your PC. But if you look for \\tsclient you can view and use them.
The server is a Windows Server 2008 R2.
What can be causing this? How could I fix this?
Thank you very much!
Thanks in advance for any help.
I currently have Windows 2012 R2 Remote Desktop services configured with RDWEB. From the
Internet, the user can open https://mypublicdomain.com/rdweb, login, and click the icon for my RDS Session host farm to initiate a Remote Desktop services session to one of my hosts. This works great,
the connection opens to my RD Connection Broker and a session on an RD host automatically opens (SSO works fine, no extra credential prompt)
However, when I click the "Connect to a remote PC" link on RDWEB and then enter the name of an internal PC, I get:
1. A login prompt (unexpected since I get SSO when connecting to the TS farm as mentioned above
2. When I enter my credentials, I get an error that it can't connect to the machine.
I've confirmed that
1. All users (domain) users have permission in the connection authorization policy
2. Resource access policy is set to allow connections to "all machines"
3. I've set the DefaultTSGateway property in IIS to the public FQDN for my RD farm.
4. The internal machines I'm trying to connect to are up and running and remote desktop connections directly to them from another internal machine work fine.
Here's what my environment looks like:
Thanks!
Hello,
we have a TerminalServer Farm of five Servers.
Connecting to the Servers with only one Monitor works fine. Connecting to the Servers with multimonitor support (2 Monitors or three Monitors) shows only a black screen on all monitor with the taskbar.
But its curios, I have this problem only on 2 of the 5 servers. All 5 Servers are absolutely identically (fresh) installed with a software dist. Really NO differences.
We've tried this with different clients. Win7, WinXP, Win7 Embedded (HP Thin Client T510), WinXP Embedded (HP TC 510). Same problem on all clients.
Any Ideas ?
Thanks a lot.
Regards...
Hi all,
I am new into Remote Desktop through Web Access and I would like to ask you if it's possible to copy a file from the computer accessed with the RD Web Access to my computer?
Thanks and Regards
Hello,
First sorry for my bad english :)
I have a problem with my server 2012 when publishing remoteapp program. This error shows with every program i want to publish? Can you please help me.
Error when trying to publish remote app: Failed: Coul not create a published application instance on the server: ......
error in event viewer under Microsoft\windows\RDMS-UI\ Admin log
Event ID 16393
Publishing Failed for RDSH Collection - RemoteApp name: Excel 2013 Collection name: ........ Failure: Could not create a published application instance on the server .......
Please i googled it and didnot find any solutions can someone help me?
Hello Guys,
In order to solve another problem I'm having, I wish to add a RemoteApp using Powershell. I have created a remote desktop session Deployment using the Server Manager, and adding RemoteApps there works perfectly. However, when I want to use Powershell to add a RemoteApp, it gives me the following error message:
New-RemoteApp : A Remote Desktop Services deployment does not exist on sv-xxx-rds03.xxxx.infra. This operation can be performed after creating a deployment. For information about creating a deployment, run "Get-Help Set-VDIDeployment" o r "Get-Help Set-RDSHDeployment". At line:1 char:1+ New-RemoteApp+ ~~~~~~~~~~~~~+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-RemoteApp
When I want to create a new SessionDeployment I get the following:
New-SessionDeployment : A session-based desktop deployment is already present. At line:1 char:1+ New-SessionDeployment+ ~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-SessionDeployment
Anyone any idea how I can make my server recognize the fact that he already has a deployment and that he's a member of that deployment?
Hello
I am currently working in an environment where we use a bespoke application install on two APP servers which have RDS installed and are load balanced with high availability. This works great however i have been asked if we can limit the amount of sessions per user to 2 sessions as there are people opening 3 and 4 sessions of the same application which is slowing down the server. Is this a possibility with just Windows Server 2012 R2 or RDS or will i need some 3rd party software/scripts?
Thanks in advance
Lewis
I'm needing Windows Server 2008 r2 with 10 server CALS and 10 RDS CALS. When I search for a source online I see 10 RDS CALS selling as low as 220.00 and as high as 500.00.
My question is: How do I know the lower priced item is the same as the higher prices item?
Hi All,
I support a small business and they are currently looking to upgrade their Windows Server 2008 server to Windows Server 2012 R2 (When it gets release). The current set-up is 1 Server which has the following Roles installed:
- Active Directory Domain Services
- DHCP Server
- DNS Server
- Remote Desktop Services
I realise that it's not recommended to have Active Directory and Remote Desktop Services on the same server but due to the client only having 5 users it's been working very well for them and it's very easy to support.
I'm currently using the Windows Server 2012 R2 Preview version to make sure that everything's going to work and there's a smooth transition to the new version of windows. What I'm starting to notice is that I am no longer able to install both Active Directory Domain Services and Remote Desktop Services on the same server. I have seen a few articles saying that there where ways to get around this but nothing has worked.
I don't want to have two servers in the office for 5 users as the business will see no point upgrading as pricing will be to high, also having VM's I believe will cause a major bottle neck on the server.
Has anyone got a work around for this problem??
Thanks in advanced.
Mike
I have discovered that while working on my desktop, while having a connection open to my server 2012, I keep dropping the connection. What I've discovered is that as long as i work on the primary monitor on my desktop, and then open the remote connection to work on the server, the connection stays alive. When I work on the secondary monitor, for as little as a few minutes, and go back to the primary monitor and expand the server window, the connection has timed out and it reconnects on 1 of 20 try's.
I am wired into the modem/router, and this does not drop the connection with my other office's connection to the server 2012, but they do not use multiple monitors on their desktop.
Any suggestions?
About 8 of them when anyone logs into server 2012 r2 RDS server. This was a server 2k3 domain and there were definitely some hickups with terminal server licensing not be delegated Access to TS licensing user properties in AD and issue with 2003 default DC policies preventing windows internal database from working correctly. This one I'm clueless about. There is nothing that isn't working, there are no application or system errors occurring along with the audit failure. Hoping someone super smart would know..
Thanks,
Klaus
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 10/10/2014 3:13:10 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: TERMSERV.PACE.local
Description:
An account failed to log on.
Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: TERMSERV
Account Domain: PACE
Failure Information:
Failure Reason: The user has not been granted the requested logon type at this machine.
Status: 0xC000015B
Sub Status: 0x0
Process Information:
Caller Process ID: 0x0
Caller Process Name: -
Network Information:
Workstation Name: TERMSERV
Source Network Address: fe80::2051:ba32:44bf:c24
Source Port: 64432
Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2014-10-10T20:13:10.838588600Z" />
<EventRecordID>70558</EventRecordID>
<Correlation />
<Execution ProcessID="604" ThreadID="7156" />
<Channel>Security</Channel>
<Computer>TERMSERV.PACE.local</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">TERMSERV</Data>
<Data Name="TargetDomainName">PACE</Data>
<Data Name="Status">0xc000015b</Data>
<Data Name="FailureReason">%%2308</Data>
<Data Name="SubStatus">0x0</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">NtLmSsp </Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">TERMSERV</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">fe80::2051:ba32:44bf:c24</Data>
<Data Name="IpPort">64432</Data>
</EventData>
</Event>
Hi All,
Let me first explain what I have and what I'm trying to achieve.
I have 1x Microsoft RD Connection Broker Server
I also have 2x Microsoft Remote Desktop Session Host servers (one primary and one secondary)
I then have a Kemp hardware loadbalancer which contains the IPs of the Session Host servers
I have configured an RD Connection broker farm that includes the two aforementioned Session Host servers.
The plan is for clients to connect into the Session Host servers via the Kemp loadbalancer's virtual IP. As the Session Host servers are part of the RD Connection Broker Farm on the RD Connection broker sever I want there to be continuity for user sessions in the event of a primary Session Host server failure. The problem is that this is not happening!
To test I am logging into a user session on Session Host Server1 (I get server1 as I have weighted the real server IP on the Kemp device so it will always connect here unless it is down). I then simulate a Server1 failure (pulling power). The session crashes and I start a new session. The Kemp device does its job and directs me to Server2. All good so far. However once I put in the users login details I get the 'Server cannot be found' error. So the connection broker is kicking in as its trying to connect me to the existing session but on the wrong server! It is trying to reconnect me to the failed server. Does anyone have any ideas why this would be happening?
Any help appreciated!
I renamed my cluster shared volume from Volume1 to the same name as my SAN LUN to keep things straight. The name has a dash in it and looks something like this: LUN 3 - HyperV Virtual Desktop Storage 2 I am trying to deploy a new desktop collection with the virtual desktop location set to C:\ClusterStorage\LUN 3 - HyperV Virtual Desktop Storage 2\Virtual Desktops but every time I enter that path in the desktop creation wizard Server Manager locks up.
Anyone seen this?
I have created a rds deployment as follows
3x Server 2012r2
RDSH01 (RemoteApp Host)
RDSGW01 (is actually running web access)
RDSBR01 (Broker)
I created it using the add role wizard and everything is currently working as expected.
When I run get-RDremoteapp I get the following message
Get-RDRemoteApp : A Remote Desktop Services deployment does not exist on RDSH01.domain.com. This operation can be performed after creating a deployment. For information about creating a deployment, run "Get-Help New-RDVirtualDesktopDeployment" or "Get-Help New-RDSessionDeployment".+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDRemoteApp
I have tried running this remotely and directly on each of the 3 machines above, however I get the same error message.
Any suggestions?
We're deploying an application via RemoteApp to our employees. Everything Works well, untill some users start having issues connecting and get the error message saying:
"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"
Clients connecting are Windows 7 and Windows 8 computers and both have had the same issue at some point.
The server task manager shows disconnected sessions without displaying the name, and allways with the same processes there (4):
- Windows Logon User Interface Host
- Desktop Window manager
- Client Server Runtime process
- Windows Logon Application
using the query sesión command I see disconnected sessions with no name as well and and if I try to reset sessions that don´t show name and are disocnnected they never do and looks like the command never ends. Allways running cmd with higher privileges.
the only solution happens to be rebooting the sesión host server... I would like to go to production having resolved this issue.
Any ideas?
does anybody know how to resolve this?