AWS Remote Desktop Services Licensing

Greetings! This is my first to post, so please bear with me.
Here is my scenario:
My company has a number of Windows servers (company-owned hardware & OS licenses) in a server farm. My company has purchased User & RDS User CALs for all employees to be able to RDP into each server. Server licenses & CALs are all retail purchases,
no Volume Licensing, no Software Assurance.
The company has also purchased a VL w/SA Microsoft Office w/100 seats. I have installed Office on our servers for our users' use. 
I know this configuration is compliant with Microsoft's License Agreements as we own the hardware and directly purchased the licenses.
However, in addition to the server farm, my company has an account with AWS and wants to create several multi-user (via RDP) servers. Also, my company wants to install Office on the servers for our users.
Here is my problem:
I cannot find clear concise documentation from either Microsoft or AWS confirming the licensing requirements for my AWS scenario.
I've found many blogs saying one could use the regular User/RDS User CALs purchased via VL or Retail.
Alternately, I've found several other blogs talking about User/RDS User SALs (Subscriber Access Licenses) as the requirement since Windows is licensed from Microsoft via AWS through SPLA (Subscriber Provider License Agreement). 
Are SALs included in my monthly payments to AWS? Where do I buy SALs? Does anyone have official documentation from AWS on this topic? The software vendor from which I purchased my company's VL Office has never heard of SALs.
Additionally, I have not been able to find clear documentation regarding the use of Office on an AWS Windows instance. I know AWS supports LM (Licensing Mobility) for users with certain Volume Licensing agreements but LM only applies to Server Applications.
Microsoft Office is a desktop application.
Where can I buy Office for AWS instances? How do I license my users to be able to use Office on an AWS instance?
I've contacted Microsoft and was redirected to AWS. I've contacted AWS but no one seems to know the answers. Is no one else asking these questions? Is no one else using AWS Windows-based servers in a multi-user environment over RDP?
Any input on this topic would be very much appreciated.

I'm doing some licensing audits now and the only thing I've found was a webinar by AWS dated February 27, 2012, so I don't know if it's still the most current information. Due to the fact that the Windows Server license is being offered through Amazon
you would need a SAL in order to legitimately use any Remote Desktop Services, once you buy a SAL any existing user CALs you already have are now valid in AWS. The presenter goes on to say that Amazon would really like to offer SALs, BUT, unfortunately they
do not. This then lead me to alternating paranoid speculation that Microsoft has put Amazons request to sell SALs into the nearest round file so that Azure would be more attractive and a superiority complex rampant with bitter hatred for Amazon's inability
to make money that they would really like to make.
There were a couple of things that seemed kind of odd about this to me. Any existing Server CALs you have are "instantly valid" for use in AWS, but you're RDS CALs are not. It seems to me since the non technical use of those licenses are nearly identical
they should either both be valid or both be invalid for AWS use, so I guess this puts one more point in the hooray Microsoft column.
Apparently I can't post links yet, but there is a page with some references to License Mobility in AWS and a link to the webinar at the bottom in the Licensing & Costs section. The page is aws dot amazon dot com slash Microsoft and the remarks regarding
the RDS licensing are at the 15 minute mark of the webinar. Overall the webinar was generally more useful and less marketing than the page it's on, so if you plan to do anything with SharePoint, SQL Server or any other products it would be worth watching.
Also, Amazon says there is no way to run any version of Microsoft Office in an AWS instance legally, maybe you could get by with Open Office? If you do find a way to run any RDS applications in AWS legally I would be interested to hear about how.

Similar Messages

  • Server 2012 R2 Remote Desktop Services Licensing

    I currently have a single Remote App server running on server 2012 (not R2). Let's call it Remote1 for simplicity.  I want to add a second individual server (Remote2) running it's own connection broker, gateway and session host on one machine. 
    Is it possible to do this while having Remote1 acting as the license server or would I have to add Remote2 to the server pool acting as a session host only?  Would purchasing Remote2's own set of CAL's make this work?

    Is the license server and the session host in the same domain? You don't have to put Remote2 into pool where you have Remote1.
    They both can act as seperate entity as you said. But if the only need is to have remote1 as a license server for remote2 then you can use the following method to specify the license mode and license server on remote2
    Configure the Remote Desktop Session Host role with to use the localRemote Desktop Licensing server. Follow these steps:
    Open an elevated Windows PowerShell prompt
    Type the following command on the PS prompt and press Enter:
    $obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
    Run the following command to set the licensing mode:
    Note: Value = 2 for Per device, Value = 4 for Per User
    $obj.ChangeMode(value)
    Run the following command to replace the machine name with License Server:
    $obj.SetSpecifiedLicenseServerList("LicServer")
    Run the following command to verify the settings that are configured using above mentioned steps:
    $obj.GetSpecifiedLicenseServerList()
    You should see the server name in the output.
    Hari Kumar --- Disclaimer: This posting is provided AS-IS with no warranties or guarantees and confers no rights

  • Remote desktop service license pool

    Hi,
    Like we create disk pool, is there a way to create RD license pool? I mean can we create per user or per device CAL pool ?
    Thanks,
    Umesh.S.K

    Hi Umesh,
    Thanks for your confirmation.
    Regards.
    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

  • 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

  • License questions on Remote Desktop Services

    Hi all,
    I have 3 Win2012 Servers installed with Remote Desktop Service enabled and running, and we haven't deployed the Remote Desktop Server Role. As 2 of them are at the remote locations, we will use remote desktop connection to connect
    from the server at our office to others for administration and problem solving.
    We would like to know under this situation (connect one server at each time), any license is needed to purchase?
    Thanks!
    BRgds/Edward

    this article explains the usage for the /admin parameter:
    http://blogs.msdn.com/b/rds/archive/2007/12/17/changes-to-remote-administration-in-windows-server-2008.aspx
    I'm not sure if this has changed in WS2012 (I suspect not), but I've not personally spent any time with WS2012 RDS yet.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • 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

  • 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

  • Cannot run more than one instance of a remote app in remote desktop services Server 2012

    All,
    I installed "Remote Desktop Services (RDS) Quick Start Deployment for RemoteApp, Windows Server 2012 Style" using the instructions here http://blogs.technet.com/b/yungchou/archive/2013/02/07/remote-desktop-services-rds-quick-start-deployment-for-remoteapp-windows-server-2012-style.aspx
    I need to set up an image viewing program (Olyvia) to allow students using Macs and iPads access to this windows only application in order for them to get their work done.  We may have 12 or more students accessing and trying to run the Olyvia application
    at any one time.
    All works good, except that I cannot run the Olyvia application (setup as a remoteapp program) more than one instance at a time.  That is, when I start up "olyvia" on a Mac, it works great.  If I leave it up and running, and then try
    and start up "olyvia" on an iPad (using different accounts), I get the following error message:
    "Cannot run more than one instance of this program simultaneously.  Either the program is already running, or it has not been terminated completely."
    I need to understand the root issue.
    1.  Is this a licensing issue?  So, I need to add some CALs to the RDS server?
    2.  Is this a application issue with "olyvia"?  So, no matter what I do, it is not going to be able to be used by more than one person at a time when configured as a remoteapp?
    3.  Did I not "publish" the application correctly?
    4.  Is this happening because I followed the "quick start" guide?
    Appreciate any help I can get on this.  We have no problem getting CALs, I just need some help with the root issue.
    Thanks,
    Geoff Weatherford
    CVMBS, CSU

    Hi Geoff,
    Each application uses different techniques for determining if multiple instances are running.  If you can determine what method it is using then perhaps you could use App-V or other virtualization software.
    In the best case you really should direct your question to the maker of Olyvia.  The reason I said that is they specifically designed their software to prevent multiple instances, so the first question is, why?  Is it related to Licensing? 
    Compatibility?  If you knew the specific reason(s) why they are doing it and the technique used then at the point using a virtualization technique may be the best option.
    -TP

  • 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

  • Error when uninstalling App-V RDS client: Product: Microsoft Application Virtualization (App-V) Client for Remote Desktop Services 5.0 Service Pack 2 x64 -- Error 1324. The folder path 'C:' contains an invalid character

    Issue:  experienced when attempting to uninstall the App-V 5.0 SP2 RDS client. 
    Event Log:  Product: Microsoft Application Virtualization (App-V) Client for Remote Desktop Services 5.0 Service Pack 2 x64 -- Error 1324. The folder
    path 'C:' contains an invalid character
    Symptoms (when in this current state): 
    Unable to uninstall the SP2 client
    You can upgrade the client (via hotfix) and uninstall the hotfix, but you will not be able to remove the SP2 client
    AppvVfs filter driver will not create an instance, therefore applications will not be able to read into existing streamed VFS content, or trigger sparse files to stream content.  (you can still stream the content via other means, like the UI or powershell)
    Because of the AppvVfs filter driver not instantiating, applications that depend on licences that exist in VFS will not be able to be read causing certain applications to react as if the license does not exist or is an incorrect format

    Resolution:
    Check for the existence of a hidden folder named %appdata% in the C:\Program Files\Microsoft Application Virtualization\Client folder.  (You will need to un-check the folder options box in windows explorer for "Hide
    protected operating system files" to see it)
    If the hidden %appdata% folder exists, delete it.
    Proceed to uninstall the App-V client
    After a clean uninstall and removal of remnants of the client, reinstall the client again and apply the latest hotfix available (Hotfix 2 for SP2 at a minimum).

  • 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

  • Terminal Services (TS) or Remote Desktop Services (RDS) scenario clarifications

    Dear Support,
    Question:
    Do I still need to purchase RDS CALS license? or can use MSDN CALs in the Terminal Server?
    Due to MSDN subscribers are End users, do not use Production Data and have to demo their developed applications to other End users group.
    Scenario:
    1. Use only Remote Desktop Session.
    2. End users are MSDN Subscribers.  (Although stated by Microsoft End users are non MSDN subscribers)
    3. End users demo applications to End users.
    4. End users develop their applications and have to demo to other End users group.
    From MSDN link:
    Client Access Licenses for Terminal Services
    With an MSDN subscription, you are allowed to provide end users access to Internet demonstrations of your programs via Terminal Services (Windows Server 2003 or Windows Server 2008) or Remote Desktop Services (Windows Server 2008 R2). Up to 200 anonymous
    users can simultaneously access your demonstration this way. Your demonstration must not use production data. MSDN subscribers are licensed to demonstrate their applications to end users,
    but Terminal Services (TS) or Remote Desktop Services (RDS) is the only scenario where end users without an MSDN subscription can interact with the demonstration application while the software is licensed through MSDN subscriptions.
    Accessing CALs            
    MSDN subscribers can access CALs for demonstration purposes through the
    Product keys page of MSDN Subscriber Downloads. Please access the documentation resources online for assistance with the
    Terminal Server activation process. If you have any questions, please visit the Microsoft
    Terminal Services forum.
    Mary Lee

    Hi
    Please call the licensing to be sure. In the USA (866) 230-0560 or
    [email protected]
    Regards, Philippe
    Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
    Answer an interesting question ? Create a
    wiki article about it!

  • [Forum FAQ] Available updates for Terminal Services/Remote Desktop Services

    The table summarizes the available hotfixes and updates for issues that can occur in Terminal Services/Remote Desktop Services.
    Terminal Services (Remote Desktop   Services) in Windows Server 2008
    KB
    2312539
    Remote Desktop Services (Terminal   Services) on Windows Server 2008 R2 SP1
    KB 2601888
    Remote Desktop Services in Windows Server   2012
    KB 2821526
    Remote Desktop Services in Windows Server   2012 R2
    KB 2933664
    Thanks for the suggestion of
    armin19.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    I'm interested in that issue as well as a lot of our Clients would like to deploy Adobe Creative Cloud apps in their Enterprise. As I'm a Citrix virtualization engineer I'd like to have an official Statement from Adobe whether or not their products can be licensed and installed on either Citrix XenDesktop (formerly XenApp) Servers and/or virtual Desktops (VDI Environment). This questions Needs answering from both a licensing as well as technical Point of view. So please Adobe, share your knowledge with us.
    Alex

Maybe you are looking for