Hi all -
I was wondering if anyone else was having the same horrible experience I was having with RemoteApp. Now, I know that it shouldn't be deployed on a Domain Controller, but I have a small environment and the application I need to serve lives on our DC. I set
up the deployment as such: On the DC, I have Hyper-V enabled and within that, I set up a server providing ALL RD roles accept RD Session Host - the DC's only role is RD Session Host, serving the program Pilot ERP to my users.
I was told that Microsoft doesn't support having the DC as having ANY roles in such a deployment. (maybe someone could tell me why?), but our IT budget just won't allow for another server, so I have to make due with what I have.
The problem is that while I got the contraption to work, I came in the following day to find that I was unable to manage the deployment in any way. It still works, but I cannot add apps, disconnect users, or make changes in ANY way whatsoever. The RD section
in Server Manager is reporting that the server farm cannot be found and that it can't connect to the servers within it.
This is what I saw the following morning after I left the office the night before and EVERYTHING was working fine. The ONLY thing that happened since I last logged in was the nightly backup.
What I don't understand is how MS could publish a solution that is so horribly fragile. The current deployment is the THIRD incarnation of it. I had to tear the entire deployment down three times and start over. Is this REALLY that stable on a server that doesn't
function as a DC? I can't imagine installing RemoteApp in a larger environment. I have only about a dozen users including myself.
It was my original intention to deploy Citrix XenApp - but that got crushed because I couldn't get it to work using Hyper-V. When I informed my boss that we needed to purchase a new server to deploy XenServer, I was summarily shot down.
Any thoughts would be helpful.
thanks
-Rik
