Remote Desktop Services Role on a Virtual Machine (VM) Requirements

Does MS recommend installing RDS Role on Hardware or Virtual Machine? I have a use case where I have about 35 people that will be using the Internet Explorer and possibly run additional piece of software. I'm having trouble determining if the RDS Role on
Virtual Machine will be able to sustain the load of so many users. Should the same performance metric used in hardware selection be appropriate to apply for Virtual Machines. We are using VMware on pretty powerful DELL hardware, which is also hosting
120 existing VMs as of now. So my questions is would VM with 4 CPU's, 8GB of RAM, 80 GB Virtual Disk and 1 GBPs NIC would be handle the job?

Hi,
Thank you for posting in Windows Server Forum.
There is no any particular requirement to run RDS on physical or virtual machine. But if you want to install RD Virtulization role then you need to see that Hyper- V role installed because “when the RD Virtualization Host role service is installed, Server
Manager checks to see if Hyper-V is installed. If Hyper-V is not installed, Server Manager will install it”. And Hyper-V role cannot be installed on virtual machine so for that you need to install on Physical machine. Other all RDS role can be installed
on virtual machine also.
Install the Remote Desktop Virtualization Host Role Service
In addition, please check below articles.
1. Remote Desktop Services: Server and client requirements
2. RDS Hardware Sizing and Capacity Planning Guidance.
Hope it helps!
Thanks,
Dharmesh

Similar Messages

  • Windows 2012 R2 Active Directory Domain Services and Remote Desktop services Role on the same server.

    Findings: 
    Currently, Windows 2012 R2   AD DS role and RDS With Broker services can only seem to coexist properly in a new domain not an existing domain. Any attempt to add to an existing domain causes internal database user access denied issues and any attempt to
    adjust rights and circumvent is dubious at best.
    The escalation technician said it best. Out of 50 clients that want to do this, they end up not being able to help 5 right off the bat for whatever reason. As for the other 40 they might be able to help by running reports, adjusting rights and trying to add
    the roles until it works.  This can end up being a 20 day process. Basically they are playing whack-a-mole with user rights and permissions until something sticks.
    We tried creating an OU where any other domain policies would not be inherited to see if that was the issue, a fresh install with different sequence of adding the Roles, no effect.
    Given the errors I witnessed when running procmon and then trying to add the roles, the NT System and the Windows Internal database user had access denied issues on 100+ registry keys when trying to add the roles. After that the system is not behaving normally.
    The errors displayed almost mirror the errors that would occur on Windows 2012 when those two roles would be added which of course is officially NOT supported on that system.
    This blog needs serious revision:
    http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
    This is the excerpt from that blog: Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller.  In addition, we published
    guidelines for how RD Session Host could be used without the RD Connection Broker.
    Microsoft Support was curteous and helpful and they were the ones who advised cutting our losses, which mirrored my hunch after seeing what was transpiring in the system.  They refunded my money for the support call. 
    For me, it was an opportunity to find out if there was any way to configure Windows 2012 R2 in the Same manner that it was setup as Windows 2008 R2 and lay that to rest. The coexistence is poorly implemented. It is as if there was a reaction from all the deprecation
    of bread and butter features such as shadowing in TS and the coexistence of AD DS and RDS to where those features were re-added haphazardly. (I have no complaints on shadowing on Windows 2012 R2 it works, just do not like having to go to server manager to
    use it).
    I opted for virtualizing the Domain controller to eliminate the incompatibility issues and that is what I will be doing from now on. I found free solutions for backing up and reporting for virtual machines as well as the suggested procedures for configruing
    a Domain controller as a virtual machine on a Hyper-V environment and I will be sticking to those. Thus far the setup has been operational.
    I am not allergic to virtualization, but for really small setups it adds additional time and considerations but if that is how it has to be done, so be it. Windows 2008 R2 days are numbered and since we can usually squeeze 5-7 years on quality server equipment,
    buying a Windows 2008 R2 setup now is a borderline disservice in my opinion.
    Hopefully someone finds this useful and saves some time.

    Hi,
    Thank you for posting in Windows Server Forum.
    Do you need any other assistance?
    Based on your description, you are describing your story of successfully implementing RDS server with AD role and more regarding all RDS related scenario. For shadowing feature, you can use with command also. Below is the syntax to shadow a session.
    mstsc /v:<ServerName> /shadow:<SessionID>
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • How to install the Remote Desktop Services role on a Windows 2012 R2 Server

    Hello,
    I am a bit confused on how to install the RDP role on a 2012 R2 server. I have a two server domain and would like to make the second member server an RDP server to host applications (Word, Excel, a medical software, etc.) where users from their windows
    7 desktop will use the Remote Desktop Connection to connect to the server, create a session and do their work. When installing the role, I am prompted with two options:
    1- Role-based or feature based installation
    2- Remote Desktop services installation
    I see the RDP install option in both cases.
    1- Which one do I use?
    2- What role services do I install? (Connection broker, Gateway, Licensing, Session Host, Virtualization host and Web access). I think I need the first four only.
    3- When installing software after RDP, I use the Change user /install and Change user /execute commands. What happens to the software that is already installed? Can remote
    users use those?
    Any help will be very much appreciated.
    Thank You,
    Victor.

    TP,
    Thank you for your response. I added the RD Licensing thru the Role-based option.
    Also opened the local group policy thru gpedit.msc and added the server name and the licensing mode type to Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session
    Host -> Licensing
    Use the specified RD license servers = NameOfMyServer
    Set the Remote Desktop licensing mode = TypeOfMyLicense (Per User in my case)
    Thank you again,
    Victor

  • Windows 2008 R2 Remote Desktop Service Role pickup 2012 RDS License Server.

    I am installing Citrix onto a Windows 2008 R2 server as part of this I need to setup the RDS Role on the same box and then point it to the Windows RDS License server.
    Our plan is to have a Windows 2012 License server for RDS Licenses i.e. install 2012 RDS Licenses.
    I was wondering if it was possible for a 2008 R2 RDS role to pick up 2012 RDS Licneses from a Windows 2012 RDS Server?
    Many thanks,
    Steve

    Hi Steve,
    Thank you for posting in Windows Server Forum.
    Yes, agree with TP’s comment. You can also check below interoperability matrix link for details.
    RDS and TS CAL Interoperability Matrix
    http://social.technet.microsoft.com/wiki/contents/articles/14988.rds-and-ts-cal-interoperability-matrix.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Remote Desktop Services Failover

    Hi All
    I am using RDS1 and gateway.
    i want to Build redundancy for rapps for wordpad and calc between rds1 rds2.
    if RDS1 failed how to recover rapps ...................................?
    please reply ASAP
    Baljit 

    Hi Baljit,
    Thanks for your posting in Windows Server Forum.
    Here agree with words of armin, there is no redundancy only HA. So as suggested by armin you need to configure HS for your RDS Server. For HA deployment providing you article for more information.  
    Configuring Remote Desktop Services roles for high availability
    Hope it helps!
    Thanks,
    Dharmesh

  • How do I remote control a user in remote desktop services in Windows Server 2012?

    Hello,
    we currently operate in a 2008 R2 environment with the majority of clients connecting to our terminal servers.  We use the remote control feature in terminal services manager to connect to a users session when a user phones our helpdesk with
    a question / issue.
    Just today I've installed 2012 server on a hyper-v virtual machine to have a play with it.  I've installed the Remote Desktop Services and noticed this remote control feature is gone.  I can still log off or send a message to a user, but I can
    no longer remote control their session.
    I've seen one or two other posts stating this feature has been removed completely.
    So, a couple of questions:
    1. How on earth do I "shadow" or connect to a users session now?
    2. If I have to go third party to get this functionality back, what's the best software on the market for this and does it support remote connecting of users who have their RDP session span multiple monitors? (2008 R2 doesn't)
    3. Will Microsoft ever bring this feature back? as at this stage I doubt we would move to 2012.  This is the one feature that is crucial to the day-to-day running of our helpdesk.
    Cheers.

    A large percentage of our IT support business is through remote management. Most of our large enterprise customers are Terminal Server environment (now called Remote Desktop - why does Microsoft have to change EVERYTHING - how would they feel if I changed
    the colour of the sky from blue to red just because I could?).
    Last week, after much expense to the customer (and realising that there WOULD be some cosmetic headaches to contend with Server Management) we installed a new "Remote Desktop Server" for them and shifting them from 2003 - a big leap so we discovered.
    During deployment it came as a HORRIFIC surprise that we could not remote control user's sessions!
    Yes, we ARE to blame for not fully realising the cock-up Microsoft has made for us. We should have fully researched every detail of what changes they made and what they have robbed us of.
    Firstly, the removal of the ability to fully manage user's sessions came as a HUGE blow!
    The remaining multiple issues that followed (including the hugely cumbersome and SLOW way of accessing user's sessions and the false information that the console was reporting users logged in when they had already logged out) suddenly resulted in us decommissioning
    the new 2012 installation in favour of a 2008 R2 installation.
    Some may ask; Why not use "Third Party" apps to counteract the issue? Firstly; why spend MORE and why use a third party app that "is as" cumbersome to use just because of a freaking feature that Microsoft deemed a "security risk" - for G.D sake!
    We have now been directed by management to convince customers that a move to 2012 is NOT recommended - good choice boss, I love you!
    The question is; will Microsoft re-implement this feature and fix Server Management performance/accessibility in a future release before 2008 R2 is no longer available? Probably not - it looks like their stubbornness to forge ahead with their craze mind-set
    of transforming their products into something that is now annoying millions (including their bloody push towards everything-cloud which NONE of our customers want anything to do with).
    Microsoft! Get us back on to your side and take a step back, take a deep breath and listen to consumers!

  • Using unattend install files to automate the creation of Win7 pooled VDIs in 2012 remote desktop services

    Hi All,
    I have a problem that I have been working on for the past week and hoping someone can provide the missing link for me.
    Background
    We currently have a 2008 "VDI" environment with both personal and pooled Windows 7 desktops deployed to thin clients. We have just set up our first 2012 Hyper-V server and plan to deploy pooled and personal VDIs under 2012. I have been working
    on the process and successfully created both pooled and personal Windows 7 desktops using the Remote Desktop Services and creating the collections.
    I created the golden image and sysprep'd it (/Generalize /OOBE /Shutdown). During the creation of the Pool collection I manually inputted the Virtual settings (i.e. the OU, etc). I notice there is an option to supply an unattend.xml file with the answers.
    We are deploying the pool into a computer lab in the school for the students to use. I want the pool to revert to the pristine state after the student logs off.
    Problem
    When the user logs into the pooled desktop I notice that the activation for the Windows license has not been run. I am trying to use the unattend file to activate the license before the first log-in. Using the Windows System Image Maker I've install our
    volume license key, but it does not activate. The only option I have to activate it is to run a synchronous command during first login. This can only be inserted in the OOBE phase. When the user logs in the license activates, but when they log out,
    the machine reverts to the pristine state.
    I confess I'm  newbie to unattend installs but I've been reading the docs on line trying to figure out how to change this behavior. I'm also assuming this won't be a problem with the personal desktops pools.
    Any help is greatly appreciated.

    Hi,
    Please make sure to following guide like this link to deploy the virtual desktops
    Windows 8 / Windows Server 2012: Pooled Virtual Desktop Infrastructure
    http://blogs.technet.com/b/askperf/archive/2012/10/31/windows-8-windows-server-2012-pooled-virtual-desktop-infrastructure.aspx
    Regarding to activation, see introduction in this link:
    http://technet.microsoft.com/en-us/library/dn645522.aspx
    Which did you use? for KMS as an example, you have to activate the master\template VM with the Windows version specific KMS Key and make sure that your KMS Server is auto discoverable.
    The snapshot on the automatically created pooled collection VM is taken before KMS activation is initiated from the guest OS. So the KMS activation would take place only after user logs on. once the rollback is enabled, the pooled VM will
    rollback to clean state and may perform the windows activation again when any user logs on to the VM again.
    And you mentioned that you're using WSIM and installed Volume License Key, (I suppose you mean that you've typed the key in the "Product Key Selection" in WSIM), but as I know, we should leave the product key blank if you are using KMS host
    for activation.  
    Yolanda Zhu
    TechNet Community Support

  • Install Remote Desktop Services Failed on Windows 2012 Server

    I understand RDS is not recommended on DC due to security consideration.  However since I want to play it at home, it is not much a concern.  Such scenario works fine on Windows 2008 R2.  But on Windows 2012, the RDS (session-based, have not
    tried VDI, but expect same result) installation always fails and is incomplete on DC. 
    In \Administrative Tools\Terminal Services, I only have RD Licensing Diagnoser and RD licensing manager.  The remote desktop service management service cannot be started (Error code: 0x88250001).  Is there any extra configuration needed for RDS
    working on Server 2012 DC or before the installation?  Thanks.
    Update: this issue has been solved in Windows 2012 R2 Server.  According to
    http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
    "Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller.  In addition, we published
    guidelines for how RD Session Host could be used without the RD Connection Broker."
    The guidelines (http://support.microsoft.com/kb/2833839/en-us) primarily apply to Windows 2012 Server.

    Asinine.  Simply Asinine.  Microsoft took it out because of $GREED$.  
    RemoteDesktop has become so popular, they had to break it to make more money.  Thats why they discontinued SmallBusinessServer.   If this practice is so tabooo... Why did MS go the opposite direction with SBS 2011 Premium Cal's?  SBS2011
    had DC, Exchange, RDS and Sharepoint,SQL, RemoteWebWorkplace, OWA all working in perfect harmony.  It is an untrue statement then, that it was "allowed but not recommended"
    Now you by Server2012 (core + two virtual) and its not enough for all this. 
    You need at least another $700 for another sever licence to have it all
    and who knows if SQL will run on a DC, or Exchange, or R-DERP server.  Another reacherous bridge to cross.
    By far, the absloute worse release since Millennium.  The product is not ready for production, we broke our rule of waiting until the first SP1 upgrade for this and Exchange 2013.  Problems with USB drivers and networking running extreamly slow. 
    Our 2003 SBS server was at least three times as fast, and this server has SAS and SSD drives running.  It can't get out of its own way, and IE10 is the most unstable piece of crap to come out of Redmond.  Open wide and swallow - Mother Microsoft
    knows whats best for you.  YOU WILL EAT OUR SLOP AND LEARN TO LIKE IT.   Server2012 AKA  "METRO-SERVER"
    Now here I sit after 50 Hours back to back setting up a new R-DERP server 2012, AD, Have my RDP licences in my hand at $100 each, and WTH does Microsoft care if I install it on my DC.  ITS MY DC.  And the cost savings versus the "risk" was
    previously MY decision. 
    Sure, I can install a couple of Virtual HyperV sessions but they are so tempremental to a power-outage in a small business its not worth it.  I have to double up my server hard drive resources, buy a $800 battery backup unit and make sure to attach
    the cable, and even then, if that Bi**H does not shut down properly, one bit goes awry in a VHD or VHDX file and you are screwed.  Restore from lastnights backup and forget about todays work.  Not to mention it will probably take a half day to try
    to fix it, then recover it then tell the 30 users they lost a days worth of work. 
    HYPER-V is for test servers and has no place in a small (micro) business environment. 5-30 users. 
    Microsoft's solution, buy another server.  Need Exchange?  Buy another server or take the risky cheapskate route and spin up some VHD's.  Might as well put a gun to your head and play russian roulette, at least you know you have a one in six
    chance of failure.  With MS, its a 100% failure for a dirty shutdown power loss, motherboard blows, memory goes corrupt in a few years, your conventional method of recovery is gone, and you have some upchucked VHD file to try to recover some of TODAYS
    data from. 
    Screw server 2012 forever. 
    I will sell 2008 and SBS2011 Premium unitl it rots in hell like XP (of which there is NOTHING wrong with for the average, WORD, EXCEL, OUTLOOK and QUICKBOOKS that all SMB's use.  Its MS $GREED$  Grab the world by the B**ls and squeeze with all
    your might to squeeze every dime you can out of *SMB* because big business is going to run thier 2003 Exchange and 2008 servers into ground before they switch to this garbage. 
    YOU CANNOT INSTALL EXCHANGE 2013 on DC , OR on R-DERP server. 
    Go buy another server license and server or MOVE TO THE CLOUD and get fleeced every month. 
    I have 30 DC/R-DERP/Exchange and SBS2011 Premium servers all running for years in perfect harmony, locked down with security so the users can't even WIGGLE with something they are not supposed to work with.  They get their apps, cannot install anything
    and all these servers are running just fine behind the firewall and perfectly save.  The track record of this combination is 100% stable and is up 24/7/365 with no problems.  Do yourself a favor and throw this 2012 into the river, you don't need
    any weights because it is LEAD and will sink to the bottom by itself.
    Why, you ask?  Official is "Its for your protection"  The real reason?  To sell you more $700 server licences.
    Maybe for SMB, we start selling Linux NAS Servers, host the Exchange in the cloud and be hearded like cattle to the Microsoft slaughterhouse.  One way or another, you are going to bleed.    A little each month to move to the cloud, or
    a small fortune if you want to have it in house.  Microsoft wants it to be more expensive to have in house.  No more buying a server and running it for six years before you upgrade.  They can't have in house servers competing with their cloud,
    and small businesses are the low hanging fruit  ripe for the pickin'. 

  • To install Remote Desktop Services User CAL on Windows Server 2008 R2 Enterprise Edition with SP1

    Dear Sir,
    Presently we have installed Windows Server 2008 R2 Enterprise Edition with SP 1. And now i would like to install Remote Desktop Services User CAL on this server. I have 25 digit product key of Windows Server
    2008 R2 Remote Desktop Services User CAL (20). Downloaded this product key from our MSDN Subscriptions.
    Kindly suggest me how to install (CAL server with product key that i have) and configure remote desktop services on my above existing server also how to point other server with my CAL server.
    Thanks

    Hi,
    1. Install Remote Desktop Session Host and Remote Desktop Licensing Role Services using Server Manager.
    2. Open RD Licensing Manager (licmgr.exe), Activate your server, then install your license
    3. In RD Session Host Configuration (tsconfig.msc), set the Licensing mode to Per User and Specify your RD Licensing server name (itself).  If you want you may configure these two settings via group policy setting instead.  The path of the
    group policy settings is Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing
    4. You may point other RDSH servers to your RD Licensing server using RD Session Host Configuration or via group policy as mentioned above.
    5. Optionally you may consider installing other Remote Desktop Role Services such as RD Gateway, RD Web Access, RD Connection Broker, etc.
    -TP

  • Questions in regards to server 2012R2 Remote desktop Service deployment and GPO

    Hi Everyone
    We have a business requirement moving to 2012R2 RDSH server. I have installed a 2012R2 member servers and enabled Remote desktop licensing role. I have activated the licenses. the servers is in operational
    I have deployed 3 windows 2012R2 member server "RDS1" , "RDS2" and "RDS3".
    on RDS1 I ran Add roles and Feature Wizard > Remote Desktop Services installation > Quick Start >Session based desktop deployment to complete the installation.
    On RDS1 Server Manage Dashboard Page Select Remote Desktop Services > Overview. Under RD Licensing I added my 2012R2 license server "2012r2-tslic". Go to task. Edit deployment properties RD license mode to per device and click OK.
    Reboot RDS1
    Check RD Licensing Diagnoser everything is clear
    On RDS2 I did the exact same thing ran Add roles and Feature Wizard > Remote Desktop Services installation > Quick Start >Session based desktop deployment to complete the installation. 
    But With RDS2 I move this server to an OU that link to a GPO with RD licensing details. after reboot the servers check RD Licensing Diagnoser I can see 2012r2-tslic specified as the license servers.  
    Based on this document
    http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx  Are you suppose to configure RD license server via Remote desktop Service deployment ? Not GPO ?
    Here are my questions
    We currently have ten 2008r2 terminal servers in a NLB cluster. each RDSH server have in house application installed on each one of them. User connect to the 2008R2 RDSH servers via RDP connection. we have a restricted GPO apply to those
    RDSH servers. user cannot do anything on RDSH servers apart from running the application and use excel.  On the remote desktop session host configuration we have enable settings like end a disconnected session , Active session limit  ,
    remote control users session , LPT port redirection.
    We push out RD license server detail via GPO to the terminal servers
    Can I use our existing GPO apply the licensing server settings , desktop restriction setting to the 2012R2 RDHS servers or we should be using Remote desktop Service deployment to do the job ? If that is the case how would you transfer the
    current 2008r2 environment to 2012 using Remote desktop Service deployment. is that mean I have to manually configure 1 by 1.
    Please help
    Many thanks

    Hi,
    Please see my response to you in the other thread.  Please contact me via email and I will go over the basic planning and deployment steps with you which will help clear things up and get you started off on the right foot.
    You should only run through the wizard and create a RDS deployment once.  Then you add the various servers (RDSH, RD Licensing, RD Gateway, etc), set Deployment properties, etc.
    Thanks.
    -TP

  • Windows Components/remote desktop services/remote desktop session host/profile doesn't appear to be working on 2008R2 boxes

    I have two domains.   One is an account domain with a one way trust with the resource domain.   Resource domain trusts the account domain and has a number of 2008R2 servers running within.  I am experiencing severe logon delays
    due to these servers being unable to access the server that hosts the user home folder specified directly on the user account profile tab from the account domain.   When using my workstation in the actual account domain (corporate) I have no
    problems.
    Because of these network restrictions,  I need to override the 2008R2's desire to access that user home folder location in the account domain.
    So far the best thing I have found to try is Windows Components/remote desktop services/remote desktop session host/profile/Set Remote Desktop User Home Directory
    The problem is that so far I have tried to configure this to point to both a local folder as well as a network path and it doesn't appear to be doing anything.   Not seeing any errors in the app or system log either.
    It is still trying to map the path in the account domain.
    Any ideas?
    Is there a better way to accomplish my goal?   The servers in the resource domain will be Citrix servers and there will be a lot of users connecting from the account domain.
    I tried this setting too,  but it only seems to work on the 2012 machines in my Resource domain.
    With the introduction of Windows 8 and Windows Server 2012 there is now a new group policy setting called “Set user home folder” and is found under Computer Configuration > Policies > Administrative Templates > System > User Profiles
    Help!

    Hi,
    This might be due to permission problems. Please check whether the user accounts for whose home folder to be redirected have permissions in the shared folder specified in the server. 
    Checkout the below link on Best Practice for creating Roaming Profile and Folder Redirection
    http://www.grouppolicy.biz/2010/08/best-practice-roaming-profiles-and-folder-redirection-a-k-a-user-virtualization/
    Regards,
    Gopi
    JiJi
    Technologies

  • Remote Desktop Services that require Native SQL Server Client in Windows Server 2012?

    I have somehow gotten really confused on this.. Is the Remote Desktop Connection Broker the only Remote Desktop Service that requires the SQL Native Client to be installed in Windows Server 2012 (r2) ?

    Hi,
    If you plan on configuring RDCB in HA mode then the SQL native client is required.  The other RDS role services do not require it.
    -TP
    Is High Availability Mode enabled by Default?

  • 2008 R2 Remote Desktop Services Problems With Older RDP Clients

    I recently deployed a new 2008 R2 server to serve as a Terminal Server (Remote Desktop Services) for about 30 people. The new server is replacing a 2003 server. I expected the new machine to be a considerable upgrade and was looking forward to happy people
    and less problems. Reality is I am finding several unexpected headaches - discouraging considering the amount of money we have spent on the new machine.
    Most of the users connect via HP thin clients, they are the T5510, T5520 and T5530 thin clients. What I have found is performance issues when connecting via these thin clients. I believe the RDP client on these thin clients is RDP 5.5 or earlier. And I do
    not believe it is possible to upgrade the RDP client version on the thin clients - I guess they are to be seen as "disposable".
    The performance issues are: black blocks appearing when connected - and I have deselected bitmap caching - makes no difference. When typing in certain places the display of the typed characters could not keep up with the user. And lastly I have a weird thing
    that just popped up today; where if the user goes to Google it freezes up their entire environment - I cannot even remote control the user/session - why this came up today and was not a problem before I am not sure.
    With all of the above issues I have found that the problem goes away or does not exist if I connect to the server using an RDP client on an XP or 7 computer. So I have to conclude the RDP client is the problem.
    Does anyone have information on this? Is there anything I can do as far as configuration on the server to allow me to use these older RDP clients? Do I have any alternative other than buying new thin clients?
    thanks!

    From your description, I also agree that the problem may be in the top RDP client.
    1.      
    HP Compaq t5510 Thin Client:
    Operating System: Microsoft Windows CE.NET
    RDP Client: Remote Desktop 5.1 Add-On
    2.      
    HP Compaq t5520 Thin Client:
    Operating System: Microsoft Windows CE 5.0
    RDP Client: Remote Desktop 5.5 Add-On
    3.      
    HP Compaq t5530 Thin Client
    Operating System: Microsoft Windows CE 5.0\6.0
    RDP Client: Remote Desktop 5.5 Add-On
    We can try to optimize two ways.
    1.      
    Upgrading Driver – Network for Thin Client
    (1) HP Compaq t5510 Thin Client:
    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=420576&prodTypeId=12454&prodSeriesId=420575&swLang=13&taskId=135&swEnvOID=1054
    (2) HP Compaq t5520 Thin Client:
    http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=500833&prodTypeId=12454&prodSeriesId=500832&swLang=13&taskId=135&swEnvOID=2051
    (3) HP Compaq t5530 Thin Client
    http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c01087297&prodTypeId=12454&prodSeriesId=3341951
    Upgrading RDP to the latest version of HP Web site.
    Let thin clients use to connect to the Remote desktop server with low load.
    (1) Open the Remote desktop client in customer’s Thin Client
    (2) Click Advanced option. In choose your connection speed to optimize performance area, you can select the low load option. For example, modem(56kbps).
    I noticed that you have deselected bitmap caching in Remote Desktop Client options, but makes no difference. You can try again. Then please remember disconnect idle sessions and rational allocation of resources in Terminal Server.
    Technology changes life……

  • Need help setting up Remote Desktop Services

    This is my first server and I can't get Remote Desktop Services to work. I need to access my Server 2012 machine from my Windows 7 computer. I realize this is probably a trivial task for a server admin of any experience level, but I am utterly confused.
    When I try to access https://servername.domainname.local/RdWeb, the webpage is unavailable. When I replace .local with .com, same result. Only when I use https:192.168.1.***/RdWeb it connects.
    I log in and click an application. An rdp file is downloaded. I double-click the file. A warning message appears listing the URL of the remote computer (servername.domainname.local) and the gateway server (servername.domainname.com). When I log in from there,
    I get the following message:
    "Your computer can't connect to the remote computer because the Remote Desktop Gateway server address in unreachable or incorrect. Type a valid Remote Desktop Gateway server address."
    Any help is greatly appreciated.

    Hi,
    The ideal method for managing a server from a client computer is achieved by installing the RSAT tools (remote server administration tools).
    http://www.microsoft.com/en-us/download/details.aspx?id=39296
    What these tools do is to actually install Server Manager on your client computer. However, you will need a Windows 8.1 computer to install the tools in the link above. They won't install on Windows 7. Note: The RSAT tools are available for Windows 7 but
    you can only manage 2008 R2 and earlier with that version of RSAT. The RSAT tools are sync'd with the release of client and server versions.
    RSAT does need a direct connection between the client and the server (as far as I know), so you can't manage your intranet server from the public Internet this way unless the server has a public IP address or - more ideally you have a VPN server set up to
    access your internal network.
    As Tim mentions, you can configure routers with 'port forwarding' to connect via RDP from outside your private network to the inside. If you log into the router you should see this option but it does require some understanding of what you are doing.
    In this case, you would need to connect to the router's external (public) IP address. You should be careful however enabling access into your private LAN from the outside as this does open you up to some security risks.
    Another option for you is to use a 3rd party solution such as logmein or teamviewer although in my opinion these are less than ideal methods.
    -Greg

  • User profile vs Remote Desktop Services Profile

    On a Windows 2008 R2 Domain Controller, if you open properties of an user account, you'd see
    a Profile Tab as well as Remote Desktop Services Profile Tab.
    I found this very confusing, can any one tell be the key difference between those 2?
    If I don't specify Remote Desktop Services Profile path, when I logon to Remote Desktop Server, it seems take user's
    romaing profile.
    Anyway, please advice.
    Thank you.

    Hi,
    Thank you for posting in Windows Server Forum.
    The profile tab of the user properties window allows you to configure user profile, logon scripts and home folder details for the user object. It is very useful when you have to allow your user access the same environment and data irrespective of the machine
    he logs in from.
    Active Directory User properties – Profile tab
    Remote Desktop Services User Properties
    You can specify a Remote Desktop Services-specific profile path and home folder for a user connecting to an RD Session Host server. This profile and home folder will only be used for Remote Desktop Services sessions. You should assign a separate profile for
    Remote Desktop Services sessions because many of the common options that are stored in profiles, such as screen savers and animated menu affects, are not desirable when using Remote Desktop Services.
    Manage User Profiles for Remote Desktop Services
    http://technet.microsoft.com/en-us/library/cc742820.aspx
    User Profiles on Windows Server 2008 R2 Remote Desktop Services
    http://blogs.msdn.com/b/rds/archive/2009/06/02/user-profiles-on-windows-server-2008-r2-remote-desktop-services.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki

Maybe you are looking for