Tag Info

Hot answers tagged

16

It turns out that much of the configuration data for RDSH is stored in the Win32_TSGeneralSetting class in WMI in the root\cimv2\TerminalServices namespace. The configured certificate for a given connection is referenced by the Thumbprint value of that certificate on a property called SSLCertificateSHA1Hash. In order to get the thumbprint value Open the ...


12

If the files are stored at the filesystem level without user-based encryption and with no ACLs then yes, run away. If ALL data was stored within the database then I would feel slightly less hesitant but even still, any vendor that says it's ok (especially when HIPPA is in the mix) to use shared ID's is suspect in my book. If you join the machine to a ...


8

As Chris S mentioned, there are several things that can contribute to poor remote desktop performance. From my experience, these are the main causes, in order of likelihood. Bandwidth The #1 cause of poor performance with remote desktop is lack of bandwidth. Depending on exactly what is being done, a session can use anywhere from a a few Kbps to a few Mbps ...


8

Try Group Policy Preferences. These provide fairly painless support for the mapping of network drives, and can be set to only apply to particular groups, leaving you to create just one GPP for each group. You could then bundle up any other custom settings for each group into the same Group Policy object while you were at it.


7

Agreed, with profile sharing comes a whole host of issues - not the least of which is the inability to have good accountability (or even ANY accountability) for exactly who did exactly what and exactly when it happened. Find another vendor - one that adheres to basic security principals. Try to find someone with a SAS 70 type II certification if possible. ...


7

Windows XP mode is now free for all versions of Windows 7 Professional and above, is it not? If you're running a domain, you're at least running Windows 7 Pro - why not just use Win XP mode? http://www.microsoft.com/windows/virtual-pc/download.aspx


7

You need to use Loopback Policy processing. Move the RDS server to a new OU. Link your "drive restriction" GPO to this OU. Configure Loopback Policy processing in this GPO to Replace or Merge mode (depending on whether you want to replace the users normal GPO settings with these GPO settings or merge the users normal GPO settings with these settings). I ...


7

I wouldnt be surprised if its caused by the "++" in the name. Try and rename the app?


6

Your setup is suboptimal -- I'd even go so far as to say that the setup you described is actively hostile to VoIP communications. A few key items: 1. You're sending video and audio both ways over the RDP session. 2. You're going over a wireless network. While this often works fine it's generally not a great idea, especially on common WiFi (not dedicated ...


6

I believe you'd still need the terminal server role installed and you'd have to license CAL's for each connection. You can't get access for free like that.


6

You should be able to accomplish this pretty easy. Setup the client to auto start, use one of these methods. Drop an RDP file or shortcut in their startup group or the system startup group. Set a group policy that will automatically start the terminal server client at logon GPO: User Configuration \ Admin Templates \ System \ Logon \ Run these programs ...


6

Gateway wins for me every time. If your clients are running a modern OS (read: XP SP3 or above) with NLA, you can expose dozens or hundreds of terminal servers behind a single interface with a single point of entry. This makes applying NAP much easier, along with controlling who can go where and connect to what. A VPN is more universally accepted (I.e. ...


6

Windows by default allows two RDS RDP* connections out of the box, and they are known as "administrative connections" regardless of if the user account is an administrator or not. If you need more remote connections you need to research RDS which requires it's own set of user connection licenses in addition to CALs. RDS can allow for a number of ...


6

This is a very common issue when RDP is working with insufficient bandwidth or high latency. I'm not sure if it is a protocol bug or an implementation bug (eg. if packets are arriving out of order and not being reassembled correctly, or if they are being misinterpreted altogether), but the solution is either to increase available bandwidth, or adjust the ...


5

You're confusing remote desktop for administration with remote desktop services. Remote desktop for administration is for remotely managing a server via RDP. Remote Desktop Services is for remotely working from a server session as if the remote session were your workstation and running applications within that session via RDP. The conceptual aspects may be ...


5

If you are copying the files via a mapping to \\tsclient\c (or whichever drive on your client you are transferring from) then the copy will terminate because the connection to \\tsclient is lost when you close the RDP client. Instead, create a mapping to \\<computer_name>\<share> and transfer from there. In this case the copy should continue. ...


5

The real answer is to use remote control. A couple of your statements are wrong. You do not need to be an administrator. There is a permission you can grant to non-administrators in order to allow them to request remote control. Go to Remote Desktop Session Host Configuration. Edit the properties of the RDP-Tcp connection. Goto the security tab and click ...


5

You need to enroll for a machine certificate on the workstation. You can setup autoenrollment via group policy or you can navigate to the cert enrollment website on your CA (https://yourCA/certenroll and enroll manually. Autoenrollment is set under Computer Config -> Policies -> Windows Settings -> Security Settings -> Public Key Policies. EDIT After getting ...


5

If you have a user that this happens to often in a day, give them a straight client/server VPN into the RDP server over their internet connection instead of the MPLS, bypassing QoS and the bandwidth congestion of the MPLS circuits themselves. If all is well for a few days, then you can set aside bugs/issues within the client or server and focus on the MPLS ...


5

As I was setting up an environment in a lab to try this (a simple RDS deployment wihtout a domain), I found the answer to your question, though it's not the one you want to hear. RDS in [Server 2012 and 2012 R2] requires all its servers to be added to a domain. That, according to a program manager at Microsoft on the Remote Desktop Virtualization team, who ...


4

No, this is by design. There are some "patches" around which can actually do this, but it's of course totally unsupported, and it also violates the EULA.


4

If you are using, or can use, Server 2008 R2 SP1 and Windows 7 SP1 Clients then you have the capability to use RemoteFX with RDP which adds enhancements to RDP's graphics functions. I've not tried it from remote location but may be worth looking at.


4

Remote Desktop Services is not called Remote Desktop Services in W2K8, it's called Terminal Services. Check for the existence of the Terminal Services service and make sure it's started. User session host mode and management mode both use the same underlying service and protocol; TS service in W2K8 or RDS service in W2K8R2 and the RDP protocol, the ...


4

In Windows Server 2008 (not R2) the service is called Terminal Services, not Remote Desktop Services (that was changed in R2). If that is started, make sure terminal services connections are allowed in system properties, make sure your firewall allows TCP port 3389, and make sure the RDS role is not installed.


4

Why if i deny Users group to remote desktop connection Administrators can't log in also? This is the normal ACL behavior on Windows. DENY takes precedence over allows. If you deny all users, then all users will be denied. If you don't want some users to have access to something you need to remove the ACE that permits that group of users access. ...


4

You'll need to use DNS round robin or NLB to distribute the incoming connections. An incoming connection will be routed to one of the servers (based on whatever mechanism you choose), the server receiving the incoming connection will query the Session Broker server to find out if the user has a disconnected session and will direct the connection to that ...


4

When you run the SCCM installer on your workstation, choose the option to Install Configuration Manager console. Now you can run the console from your own workstation instead of using remote desktop to the server. This screenshot is from Beta 1, but it looks the same.


4

This is very similar to what we do. We have a single TS Gateway that all our clients enter through. This has connection and resource policies that control which user groups can log on to which servers. Each company has their own self-contained terminal server. Most companies can only log on to the one TS, but for one particularly large client, they have ...


4

Using "cloud" infrastructure is a very cost efficient way of deploying virtual desktop infrastructure. To be honest, usually it's in a private "cloud" (i.e. a collection of servers running under vSphere, SCVMM, or some other hypervisor management solution, on the clients site). The biggest issue you will have is latency; and this has very very little to do ...


4

Don't set them up on the same operating system. You don't want anyone to have access to a domain controller other than trusted systems administrators. Ever. If you really must use a single piece of hardware, what you should do is use some virtualization software to separate the roles into two separate server installs that run simultaneously, but are ...



Only top voted, non community-wiki answers of a minimum length are eligible