We assume that you have a server running Window Server 2012 (Windows Server 8 Beta) that is part of a Active Directory Domain. Open up the Server Manager Console and choose option 2, “Add roles and features”:
Choose next to start the deployment
Select the “Remote Desktop Services scenario-based installation”
As we want all the roles to be running on the same server, we choose the Quick Start option.
As we are going to be deploying sessions, not Virtual Desktops, we choose Session Virtualization.
We select the server where we want to install the roles
We confirm that we allow the deployment to reboot the server (needed for the RDSH role)
That's it! The Scenario Based Deployment will now install the RD Session Host, RD Connection Broker and RD WebAccess role, create a first Session Collection and add computers to the Active Directory Groups as needed.
To make the lab even more complete, several applications are already added to the Remote App sections and published on RD WebAccess to give you an environment that can be used for demo’s instantly!
Carsten Siemens edited Revision 3. Comment: Fixed misspelling and added tag: has comment
Freek Berson edited Revision 1. Comment: Added a explicit remark that's thw wiki is about Sessions not VDI
Freek Berson edited Original. Comment: Added a source
Hi Freek,
Aside of the Web Access to the deployed apps, is there another client for the workstations ? or is that the best suggested way to access the published applications ?
Coming from a Citrix XenApp environment, I wanted to know how easy it is to convert the clients...
Thanks in advance for your comments,
Beat BUCHER
Senior System Admin
@BiggJake, yes it can be deployed on a Win 2012 VM running op a Win2012 Hyper-V host.
Kind regards,
Freek Berson
Can this be deployed on a Windows 2012 Std server that is a HyperV machine guest of a Host Windows 2012 Std HyperV machine?
Your first comment says it all "We assume that you have a server running Window Server 2012 (Windows Server 8 Beta) that is part of a Active Directory Domain." You know what assuming does. Where is the information for if the server is not in a AD domain but stand alone. From this it seems you can not run a Remote Desktop Server ie "Terminal Server" unless there is a domain available? Am I correct in this? The overview in Server Manager for RDServices on a workgroup server says "You are currently logged on as a local administrator on the computer. You must be logged on as a domain user to manage servers and collections." Did you forget about Workgroup instances? How do we use it if there is no domain available as in a virtual server install at a datacenter? Regards, Dale