Hi All,
I have Dual booted my existing Dell E7440 and installed Server 10 TP Build 9841.
This then has Hyper-V, RDSH, RDVH and RDS Licensing installed, initially I was concerned that I was not seeing any GPU/vGPU come through to the Hyper-V
Settings and thought this GPU was somehow not powerful enough, but it was a simple case of forgetting to install the native Intel HD4600 Drivers - once that was installed this popped thru fine.
I have then built a Template VDI instance based on Client 10 TP and run this up and have now been focusing on getting a full RemoteFX session running
- my particular interest is in being able to run my laptop as a live demo when needed to showcase the new OpenGL capabilities of the latest version of RemoteFX.
Anyway, this is where I seem to be running into Issues, I have tried setting most of the GPO settings via Local GP (gpedit.msc) as there is no domain
in this solution yet, I thought I'd get the basic fundamentals working first before I complicated things further ;-)
Essentially under previous versions of RemoteFX we noticed that one guaranteed way of ensuring that you *really* were on a RemoteFX session was to
run QUSER in CMD prompt and if you saw it as TCP#0 this proved you were at the console session, anything else was essentially an RDP session - now I'm not sure if this behaviour has changed (don't think so) - but it looks very much like I've still been completely
unsuccessful about managing to initiate a true RemoteFX session.
I have noticed in the Event Viewer that I am not seeing any RemoteFX licensing entries - and yet I have RDS Licensing installed and activated. It
also appears that an Event ID of 258 indicates a failed connection, and I did have a few of those until about 3 days ago, and yet I still can't get a RemoteFX connection?
If anyone has any bright ideas about what else to check, or even a check list of some sort to run thru that would be very much appreciated. As it
stands now when you try searching for answers on this the results are invariably related to either 2008 R2 or 2012 R2 and it's quite obvious that the settings in gpedit.msc have changed subtly enough to make this a bit more difficult to navigate?
Thanks in advance, Dave Caddick