So I seem to be stumped. We have some old Citrix Presentation Manager servers running on Win 2003 that my boss would like to retire, and replace with Remote Desktop Services under Server 2012. The catch is that these servers would VMs, running under VMware ESXi 5.0 build 821926 (we're not quite yet ready to go to ESXi 5.1 yet). I have installed Server 2012 Standard as a VM, and that all worked fine. (vCenter is running 5.0 build 804277, BTW)
But I can't seem to install RDS. (Remote Desktop Services - the last time I used even Terminal Services was on Win 2003, over 5 years back). Following this blog post
<http://technet.microsoft.com/en-us/magazine/jj554307.aspx>
I am trying to install RDS. But it keeps failing on installing the RD Virtualization Host step - all it says is that it failed. The other 2 steps (Connection Broker and Web Services) installed fine. I have 2 vNICs (E1000e, since the blog posts say that you need a 2nd NIC for Hyper-V to create a virtual switch)
I don't see anything in the Event log that is telling me WHY it failed. I am seeing Event 9645 from source MSSQL$MICROSOFT##WID.
Message is "An error occurred in the service broker manager, Error 3602, State: 145".
And I can't seem to track down what this means. The online Event log help is no help (it never seems to be, for me). I haven't found it in
eventid.net, and Google isn't showing me anything close to my situation. And I haven't seen anything similar in searches here.
So let's start at the beginning:
1. Is this even possible - can you install/run RDS on Server 2012 as a VM under ESXi 5.0 build 821926? I've seen posts that seem to indicate people have done it with Win 2008 R2, but nothing for Win 2012.
(eventually we want to publish an application or two, not a lot, and no need of a full desktop, as I understand it). I know MS says you shouldn't (or can't) run Hyper-V inside of Hyper-V, but it doesn't seem to say anything about Hyper-V inside any other virtualization - ESXi, XenApp, etc.
2. If it is possible, what am I missing? The article didn't mention any pre-requisites I don't have. I have Server 2012 as a domain member
in my Win 2008 R2 AD domain.
So far, I am not liking Server 2012. :-)