none
Microsoft Desktop virtualization with XenDesktop - Components, high availability

    Frage

  • Hi,

    Need following information on Desktop virtualization combining Microsoft and Citrix VDI components. Desktops run in VDI will be around 1500.

    1. What the various components required for Desktop virtualization delivered through combining Microsotf and Citrix as solution ?

    2. What are the high availability options for virtualized desktops running on Microsoft + Citrix? What are the components that can be either clsutered or load balanced for HA?

    3.  What are the hardware recommendations for VDI components. Around 1500 desktops.

    4. Is there any maximum limit on no. of VMs running on Hyper-v?

    5. Is there any capacity and sizing document\tool available?

    Thanks in advance.

    Thanks & Regards,

    MS Expert

    Samstag, 3. März 2012 16:09

Antworten

  • The requirements of any VDI solution is relatively the same across vendors.

    You need a hypervisor, a management stack, a broker, a client.  Then you need capacity and a VDI model (dedicated desktops, pooled desktops, or sessions (not really VDI)).

    In the MSFT + Citrix solution - citrix is the broker, the client, the protocol.  MSFT is the management stack and the hypervisor.

    So, the HA is the Hyper-V HA.  The management stack is SCVMM.

    The Citrix broker (Desktop Delivery Controller) is the point where VMs are provisioned, and controlled and allocated to customers.

    Hyper-V 2008 R2 has a limit os 1000 VMs per cluster.  So, if you want all the VMs to be HA, then you need two clusters.  You still only need one SCVMM.  If you do not cluster your Hyper-V servers SCVMM will not allow your VMs to be HA, but you can get up to 384 VMs per host.  The capacity of your hardware usually limits the number of VMs (per host or per cluster) before the software does.

    The capacity and sizing can be found at both the Citrix and MSFT sites.  Mind you, your configuraiton options are highly flexable, so there is no canned answer as to how to configure.  Always plan to spread your VMs across multple LUNs / CSVs.

    With XenDesktop you can use Machine Creation Services or Provisioning Server to manage desktop updates.


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Montag, 5. März 2012 16:11
    Moderator

Alle Antworten

  • Hi,

    There are very helpful videos available on Technet Edge website : http://technet.microsoft.com/en-us/edge/default for Microsoft and Citrix V-Alliance.This will really help you in getting most of your questions answered

    One you can refer is : http://technet.microsoft.com/en-us/edge/ff832960?Category=Citrix

    See if this helps or we can discuss more on this.

    Other Threads : http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/98b0475a-5cc1-46a5-bc3b-1fc1408cb75f

    Sanket J

    Montag, 5. März 2012 06:01
  • The requirements of any VDI solution is relatively the same across vendors.

    You need a hypervisor, a management stack, a broker, a client.  Then you need capacity and a VDI model (dedicated desktops, pooled desktops, or sessions (not really VDI)).

    In the MSFT + Citrix solution - citrix is the broker, the client, the protocol.  MSFT is the management stack and the hypervisor.

    So, the HA is the Hyper-V HA.  The management stack is SCVMM.

    The Citrix broker (Desktop Delivery Controller) is the point where VMs are provisioned, and controlled and allocated to customers.

    Hyper-V 2008 R2 has a limit os 1000 VMs per cluster.  So, if you want all the VMs to be HA, then you need two clusters.  You still only need one SCVMM.  If you do not cluster your Hyper-V servers SCVMM will not allow your VMs to be HA, but you can get up to 384 VMs per host.  The capacity of your hardware usually limits the number of VMs (per host or per cluster) before the software does.

    The capacity and sizing can be found at both the Citrix and MSFT sites.  Mind you, your configuraiton options are highly flexable, so there is no canned answer as to how to configure.  Always plan to spread your VMs across multple LUNs / CSVs.

    With XenDesktop you can use Machine Creation Services or Provisioning Server to manage desktop updates.


    Brian Ehlert (hopefully you have found this useful) http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Montag, 5. März 2012 16:11
    Moderator
  • Hi Brian, Sanket. Thanks alot for all the inputs. Probably, i missed a very important component of VDI, i.e. Application rendering\virtual applications.

    Since its a statagic alliance between Microsoft + Citrix, what would be the recommended application virtualization solution for MS+Citrix VDI? Is it Microsoft App-v or XenApp? Pls. suggest from performance, scalability, HA point of view.

    Thanks


    Montag, 12. März 2012 16:17
  • I do not work for any marketing division but i can tell you that for application delivery there is App-V, XenApp, and XenApp Streaming.  Or a combination of, depending on the requirements of the customer and their applications. 

    What is used depends on the needs and desires of any customer.  Not all applications play well with Termianl Services, nor App-V, VDI is a good fit for applications like this.  None of these alone is a best solution.

    App-V packages can be targeted to XenApp as easily as well as a VDI desktop.  So thre are multiple ways and combinations that can be used to roll the solution and make it the best for customer.

    The overall solution is all about flexability.


    Brian Ehlert (hopefully you have found this useful)
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

    Montag, 12. März 2012 18:25
    Moderator