Remote Desktop Services - VDI / Hardware and Software requiremnts

I am going to plan to do POC for 50 user on customer end for Microsoft VDI installation. For this i required hardware and software requirement.

Hi Pratik,
Thank you for posting in Windows Server Forum.
It all depends on how you want to configure your VDI environment. In Server 2012\R2 there are 2 flavors: Pooled & Personal and further can deploy both that as Managed\UnManaged deployment. You can check following article for further details.
RDS Hardware Sizing and Capacity Planning Guidance
http://blogs.technet.com/b/iftekhar/archive/2010/02/10/rds-hardware-sizing-and-capacity-planning-guidance.aspx
Choose a VDI Deployment Scenario
http://technet.microsoft.com/en-us/library/dn645525.aspx
Deploying VDI for RDS 2012 / 2012R2 – Part I
http://thewolfblog.com/2014/03/26/deploying-vdi-for-rds-2012-2012r2-part-i/
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Similar Messages

Anywhere Access: There is an error in your Remote Desktop Services Settings.

On my server2012 Essentials machine Anywhere Access is giving me this error:
"There is an error in your Remote Desktop Services Settings." and tells me it cannot be automatically repaired and to contact support.
Here's where I made my mistake: I went into IIS and changed the bindings for the Default Website to another port than 443, but then changed it back again.
Is this a cerificate Issue? Or any other cause? Could anyone help me to solve this problem?

Hi ErikLely,
Before going further, would you please let me know if the error message you described was complete? If not, please post the complete error message or provide a screenshot.
It will help us to narrow down this issue. Besides, can you remember which operation you do before this issue occurred or just sudden?
In addition, please check the Event Viewer. In Event Viewer, please follow the path:
Applications and Services Logs-> Microsoft->
Windows-> TerminalServices-LocalSessionManager and
TerminalServices-RemoteConnectionManager. If any errors you can find, please don’t hesitate to post it here and let me know.
By the way, please refer to the following article and check if configure Access Anywhere correctly.
Manage Anywhere Access in Windows Server Essentials
http://technet.microsoft.com/en-us/library/jj730374.aspx
Please also refer to the following articles and do some general troubleshooting, then check if can narrow down this issue.
Troubleshoot Anywhere Access in Windows Server 2012 Essentials
http://technet.microsoft.com/en-us/library/jj673001.aspx
Remote Desktop Services: Troubleshooting
http://technet.microsoft.com/en-us/library/ff404143(v=WS.10).aspx
Hope this helps.
Best regards,
Justin Gu

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

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

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

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

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

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

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

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.

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

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!

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

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!

Remote Desktop Services - VDI / Hardware and Software requiremnts

Similar Messages

Maybe you are looking for