locked
VDI / RDP / Hyper-V without web portal RRS feed

  • Question

  • Good morning,
    I have a problem with respect to a VDI architecture, I have a scheme running and everything is perfect, one enters the website choose the pool and is redirected to a virtual farm.

    The problem.
    Do not understand how to use that structure to "thin clients" because they do not know where to direct the RDP connection, the RDP gateway, RD Broker, Etc.

    I read somewhere that Microsoft pure VDI can only be used by the web portal, which discourages me much that would mean that I may not use a scale VDI 3000 customers, which is my goal

    Thanks in advance for any response
    • Moved by BrianEhMVP Friday, July 27, 2012 8:48 PM (From:Hyper-V)
    Friday, July 27, 2012 5:22 PM

Answers

  • After much searching, I found a way to do the routing to a virtual pool. only need to have a "Host Session" redirection mode and additionally add some keys to record:

    HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server \ ClusterSettings.

    create a, String value
    Enter a name of "DefaultTsvUrl"

    and the value
    tsv :/ / vmresource.1. <VDI pool ID>

    This tied the server to the specified pool and all connections will be redirected to RDP virtual that are available

    regards,
    • Marked as answer by bioalpha Tuesday, July 31, 2012 9:41 PM
    Tuesday, July 31, 2012 9:41 PM

All replies

  • Hi,

    Thanks for your post.

    As you mentioned, for thin clients with embedded Win7 to access VDI virtual desktop, we can only through Web access. However, for few specific thin clients support PXE boot to access VDI directly. So you may contact the thin client vender for more information about this. Your understanding is appreciated.

    PXE Boot from thin client to Direct VM Pool Machine

    http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2virtualization/thread/b6cc1fe1-cd5a-45d4-965d-4f6fca6197d9

    Best Regards,

    Aiden


    Aiden Cao

    TechNet Community Support

    Tuesday, July 31, 2012 3:17 AM
  • I also discovered this same problem. I'm a little disappointed by the numerous limitations I find with Microsoft's VDI "solution".

    I did find a workaround that if you find and distribute to clients the .rdp file that is published in the web portal then this works BUT it will be hard coded to point at a single pool which is useless if you have multiple pools.

    I also found that RDP works for personal desktops (not pools) if you direct the rdp connection to the session host (redirector).

    Both of these methods are unsupported and may be unstable. This is just what I found during my testing, I don't recommend either.

    Tuesday, July 31, 2012 2:18 PM
  • After much searching, I found a way to do the routing to a virtual pool. only need to have a "Host Session" redirection mode and additionally add some keys to record:

    HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server \ ClusterSettings.

    create a, String value
    Enter a name of "DefaultTsvUrl"

    and the value
    tsv :/ / vmresource.1. <VDI pool ID>

    This tied the server to the specified pool and all connections will be redirected to RDP virtual that are available

    regards,
    • Marked as answer by bioalpha Tuesday, July 31, 2012 9:41 PM
    Tuesday, July 31, 2012 9:41 PM
  • Great, but you are still limited to 1 pool per redirector?

    It's a good idea to have multiple pools so surely this creates just another limitation? Unless you would NLB multiple redirectors.

    Wednesday, August 1, 2012 9:46 AM
  • By doing this you can only use a pool in a redirector.
    to have the balance you can use the RD POOL setting up a farm in the RD Session.

    I do not think this was a limitation because if you look at us to keep our separate entrances for different pools, which takes our dependence on a single point of failure.
    Wednesday, August 1, 2012 5:00 PM