Well momentary pause for head banging here as what did I do now to break the stuff. Time to read and I went searching and finally found a document called Deploying RemoteApp and Desktop connection Step by Step guide from MS. http://www.microsoft.com/downloads/details.aspx?FamilyID=2F5B9705-BC09-466E-882B-7227CBB39183&displaylang=en This helped, you can not install the Remote Desktop Connection broker on the same server as the Remote Desktop Session and Remote Desktop Virtualization Service and Remote Desktop Web.
So I spun up a Virtual Server in our HyperV Environment and installed 2008 R2 RC on it and installed the Broker and Remote Desktop Session Service for Redirection on this server. I uninstalled the Broker from my host machine for the Remote App and Web Access and TS Gateway and the Virtualization service. Followed the document for setting up the broker and away I went the pieces I broke came back online and worked correctly now. Duh…… Takes note to self maybe read next time but then again where is the fun in that.
When I installed the Virtualization service it also will add HyperV but I had already configured and installed HyperV so I was good there and on the server so I installed 2 Windows 7 workstations into the HyperV on the TS Gateway, RemoteApps and Virtualization Server. One was a 32 bit machine and one was a 64 bit machine. I installed Office 2007 and the Live Communicator 2007 R2 onto the machines. These will be going into the Desktop Pool as they call this and the workstations all have to have the same software on them as this basically runs in a Pool as they say you might not login to the same machine each time.
Til Later Just Roger