2012 remote desktop service and users temp folders

Hello guys,
in windows server 2012 R2 How I can set TEMP folder configuration (clean at logoff) ? in 2008 R2 it is set on terminal host configuration.
I would like that users when logoff nee dto clean temp folders.
thanks
Andrea

Hi Andrea,
Thank you for posting in Windows Server Forum.
We can configure the temporary folders on RDSH server by GPO setting. We can configure the option “Do not delete temp folder upon exit" and the "Do not use temporary folders per session” on below mention
path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Temporary folders
Hope it helps!
Thanks.
Dharmesh Solanki

Similar Messages

  • 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

  • 2008 and 2012 Remote Desktop Service

    I have a Windows 2012 R2 with License Manager and RD Session configured but the RD Licensing Diagnoser says that the Licensing mode is not configured and RD Session Host Server is within its grace period.

    Hi Joseph,
    Thank you for posting in Windows Server Forum.
    Please clarify the question of TP’s first. In addition, I would like you to recheck the configuration related to RD Licensing on server 2012.
    RD Licensing Configuration on Windows Server 2012
    http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Setting Up Remote Desktop Services Windows 2012 DMZ

    Hi
    I'm new to the Windows 2012 RDS. I am trying to figure out some things.
    I have an application that I would like to publish to the outside world to our customers.
    Im thinking of using Windows 2012 remote desktop services and publish the app via web browser. So users go to the URL and see the application.
    Do I need a client brooker and gateway server for this setup? or can i simply deploy a web access server on the dmz which then connects to my remote session host server inside?

    Hi,
    To allow outside access into your RDS environment you would need to use the RD Gateway role. This can be configured on the same box as your RD Web Access role if resources are limited.
    The RD Gateway role uses ether TCP 443 or UDP 3391 depending on what you have chosen to configure. You need to create a port forwarding rule from and to the gateway box using 443.
    Have a look at the following articles:
    http://ryanmangansitblog.com/2013/03/27/deploying-remote-desktop-gateway-rds-2012/
    http://ryanmangansitblog.com/2013/03/10/configuring-rds-2012-certificates-and-sso/
    This should assit with the configuration.
    Best regards,
    Ryan Mangan | Ryanmangansitblog.com | Help keep the forums tidy, if this has helped please mark it as an answer

  • 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!

  • Server 2012: Remote desktop licence manager not issuing licences

    Hi,
    I am battling with an problem which i cannot seem to resolve and no other forums actually come to a conclusion on how to resolve this problem!
    I have a windows server 2012 server which is NOT part of a domain.
    I have installed Remote Desktop Services and also installed the Remote Desktop License manager and i just cannot get the license manager to issue cals when users connect remotely via RDP
    I have installed an extra two CAL's and tried using them as both a "Per User" and also "Per Device" but still does not work.
    I have now run out of my grace period and cannot connect to the server at all
    I have also tried changing some gpo's with no luck, 
    Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
    "Use the specified RD license servers" = myservername
    "Set the Remote Desktop licensing mode" = Per User
    How can i fix this?
    Thanks

    Hi,
    Thank you for posting in Windows Server Forum.
    Have you seen that you have activated RDS License server before installing CAL?
    Please check that the License Server should be part of ‘Terminal Server License’ group in Active Directory Domain Services. You can also configure RD License server manually by powershell commmand. Please check below article for information.
    RD Licensing Configuration on Windows Server 2012
    http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
    In addition, please install below Hotfix and verify the result.
    No RDS license when you connect to an RDS farm in Windows Server 2012
    http://support.microsoft.com/kb/2916846
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Allow log on through Remote Desktop Services Group Policy for Domain Controllers

    Hello,
    We want to allow our Helpdesk Operators to be able to connect to Domain Controllers with the Remote Desktop Services. This is by default not allowed but according to many sites, it should be able to configure by using a Group Policy.
    We made a new Group Policy with the setting 'Allow log on through Remote Desktop Services' and 'Allow log on locally' (as an extra for testing) and applied Security Filtering to only use it for a specific Security Group. Our test user is a member of this
    security group and should be able to access the Domain Controllers now. However this isn't working.
    The error message we receive upon trying to connect:
    The connection was denied because the user account is not authorized for remote login.
    For troubleshooting, we also applied the Security Group for that setting in the Default Domain Controllers Policy but that doesn't seem to work either. We want to avoid customization on our Default Domain Controllers Policy but this was just a test case
    for solving our problem.
    What should we do to solve our problem?
    I hope to hear from you soon.
    Thanks in advance.

    Hi, I just found out what the problem was. This site helped me alot:
    http://blogs.technet.com/b/askperf/archive/2011/09/09/allow-logon-through-terminal-services-group-policy-and-remote-desktop-users-group.aspx
    In my case, I had the group added to the Allow Logon Through Remote Desktop Services but was not added to the Builtin\Remote Desktop Users group. After knowing this I made some changes to our situation and are now using the builtin\Remote Desktop Users group
    rather than a new self made Security Group. I also added the Remote Desktop Users to the Allow Logon Through Remote Desktop Service in the Default Domain Controllers Policy as this is not done by default. By default only the Domain Administrators are able
    to logon through remote desktop services.
    You do not need the 'Log on Locally' permission within the Group Policies.
    In short:
    Add the desired users/groups to the 'Builtin\Remote Desktop Users' security group.
    Add the 'Builtin\Remote Desktop Users' security group to the 'Allow Logon Through Remote Desktop Services' within the 'Default Domain Controllers Policy'.
    Thank you anyway for the fast reply.
    Have a nice day!

  • 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

  • REMOTE DESKTOP SERVICES CLIENT ACCESS LICENSES FOR MICROSOFT WINDOWS SERVER 2012 STANDARD AND DATACENTER

    I am using a window 7 professional  service pack 1 and I purchase REMOTE DESKTOP SERVICES CLIENT ACCESS LICENSES FOR MICROSOFT WINDOWS SERVER 2012 STANDARD AND DATACENTER. but  the seller did not send me any installation CD or instruction
    on how to use it.
     Please how can I use it on my window 7 professional  service pack 1.
    Thank you.

    Though Bill is absolutely correct for most CALs, Remote Desktop Services does have its own special licensing server.  I haven't installed one on 2012, yet, but here is a step-by-step guide for 2008. 
    http://technet.microsoft.com/en-us/library/dd983943(v=ws.10).aspx
    Here is a lab guide for 2012 -
    http://technet.microsoft.com/en-us/library/jj134160.aspx
    But, the explanation of your environment begs the question - what are you trying to do?  You say you have a desktop OS and you are talking about Windows Server products.  In that light, your question does not make a lot of sense.
    . : | : . : | : . tim

  • Users not showing in Terminal Server Under Remote desktop services manager and Task Manager

    Hi All,
    I have a problem here in Terminal Server. I can not see the users logged in to Server but i know users are accessing the files and currently working.
    1. From the Task Manager-- Show processes from all users displayed all the processes accessing by users.
    2. From the Task Manager-- From Users Tab--No users list at all
    3. From the Command Prompt- Query users-- No information
    4. From the Remote desktop services Manager-- used with IP/Host name-- Still can not see the users list and processes. So i can not kill the session if needed.
    Enviroment:
    TS CALS 20 currently accessing 15 users
    VM-WARE GUEST: 2008 RS Terminal Services/Remote Desktop services installed
    Windows up to date-- Just updated last month
    Problem is here for long time. Just couldn't find the time to trouble shoot.
    UMESH DEUJA MCP,MCTS,MCSA,CCNA

    Hi,
    Thank you for posting in Windows Server Forum.
    As you have tried many steps, I suggest you to try below command line and power shell command if successful in your case. Please try below command with Admin access:
    qwinsta /server:<servername>
    To kill a session use rwinsta to delete the session specifying the ID number:
    rwinsta /server:computer01 3
    Here's the list of command line tools for Remote Desktop Or, you can use PowerShell:
    Get-RDUserSession and Disconnect-RDUser
    Please check the list of Power Shell command from
    this link.
    Hope it helps!
    Thanks,
    Dharmesh

  • 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

  • Remote Desktop Service Manager - configure permissions for Remote Desktop Users to Send Message, Disconnect, Logoff

    Hello, dear colleagues.
    We are using Windows Server 2012 R2 as Remote Desktop Server. Also use Windows Server 2008 R2 with Remote Desktop Service Manager to control RDS user sessions (Send Message, Disconnect, Logoff, Query Info). 
    Send Message, Disconnect, Logoff options works only for users in Administrators group.
    I can't to configure permissions for Remote Desktop Users, specific user or AD group. 
    To set permissions I'm running RDS Host Configuration on Windows Server 2008 R2 and connect to Windows Server 2012 R2. Then double-click
    RDP-Tcp, Security tab, add specific user account , AD group or configure
    advanced permissions
    for Remote Desktop Users.  
    But, as I sad above, these options works only for users in Administrators group. How to make it work for Remote Desktop Users or specific user, AD group?
    Thanks.
    P.S. If move specific user from Remote Desktop Users group to Administrators group on
    Windows Server 2012 R2 - it works. 

    Hi,
    You can prevent administrators from changing the permissions for a connection by applying the
    Do not allow local administrators to customize permissions Group Policy setting. 
    This Group Policy setting is located in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security
    Apart there is one command with which you can set the permission for that check the related
    article. Additionally checkthis
    thread for more detail.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • 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'. 

  • 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

  • How to license remote desktop services in 2012 without a deployment?!?!

    Am I crazy or is there no way to license a 2012 RDS server? I don't want to deploy a gateway or a connection broker. My servers are on a domain and I just want to point it to a license server for the CALs (per user).
    Why can't I seem to do this and 2012 REQUIRES the use of some scaled out deployment?
    what am I missing?

    Hi,
    You can Specify the name of the RD Licensing server and set the licensing mode using group policy.  For example, you could use gpedit.msc on the server and modify the setting under the following path:
    Computer Configuration\ Administrative Templates\ Windows Components\ Remote Desktop Services\ Remote Desktop Session Host\ Licensing
    -TP

Maybe you are looking for