Posted by: Roger Crawford
HP Blades, HyperV, Micosoft Windows Server 2008 R2, Published Apps, Published Virtual Desktops, Remote Desktop Services, TS Gateway, Virtual Desktop Pool, Windows 7
OK got my server up and running and went through the normal drill and got the settings configured on the server for networking and name and domain joined and all of that fun stuff to numerous to mention but I am sure you all know the drill. But I thought ok what am I going to do for sure here you know maybe get a plan of attack or is this just dive in and go. Thought for a moment and just dove in and went and I first decided to add Remote Desktop Services(Terminal Services) they had me for a minute as I was looking for the Terminal Services option then remembered MS had renamed this to Remote Desktop Services.
So I select RDS and oh my more options now what. I had to select from Remote Desktop Session Host, Remote Desktop Virtualization Host, Remote Desktop Licensing, Remote Desktop Connection Broker, Remote Desktop Gateway, Remote Desktop Web Access. So I picked everything except for the Licensing. Bad move but more on that later this was a test so who carried at that point until I fully understood how things works and what I really wanted. The install went pretty quick of the services and the normal rebooting proceeded and when the server came to the desktop I went to configuring the TS Gateway and adding Apps for the Remote Apps everything I have normally done on a regular 2008 server for these functions. Talked to Randy and got a SSL Cert for the Gateway and published it up with ISA and testing proceeded and things worked as expected. So I thought now what is this Virtual stuff so started to read and found I could setup and publish a Virtual workstation. Cool so I followed the documentation on the server to do this and all of a sudden nothing workie anymore and I could only connect by the /admin switch to the server. What the heck did I do now.
Til later just Roger