Horizon View 6.0 Cloud Pod Architecture FAQ

Version 3

    1. Is Cloud Pod Architecture enabled by default once we install View Connection Server on a Windows 2008 R2 or Windows 2012 R2 machine?

        No, Cloud Pod Architecture is disabled by default. Please refer to the "Administering View Cloud Pod Architecture" guide to enable this feature.

     

    2. How do I check if Cloud Pod Architecture is enabled/disabled in a View environment?

       * Run the vdmadmin command “vdmadmin –X –lpinfo” on a machine where a View Connection Server is installed

       * Run lmvutil command with –-listPods option (Please refer to "Administering View Cloud Pod Architecture" guide)

     

    3. Can I initialize a Pod which has a View 6.0 Connection Server and previous versions of Connection Servers?

        No, all the Connection Servers in a Pod should be of version View 6.0 and above.

     

    4. How do I disconnect/logoff/reset/send message a remote session from the View Administrator UI?

        From View Administrator UI, search for sessions by User, Pod or Brokering Pod (refer to “View Desktop Sessions in a Pod Federation” chapter in "Administering View Cloud Pod Architecture" guide). Select a session and disconnect/logoff/reset/send message either from the toolbar or context menu.

     

    5. How do I find the total number of desktop sessions for a user?

        From View Administrator UI, search for sessions by user (refer “View Desktop Sessions in a Pod Federation” chapter in "Administering View Cloud Pod Architecture" guide). You can see “Total Sessions Found: <number of sessions>” being displayed.

     

    6. How do I find the total number of desktop sessions for a particular Pod?

        From View Administrator UI, search for sessions by Pod (refer “View Desktop Sessions in a Pod Federation” chapter in "Administering View Cloud Pod Architecture" guide). You can see “Total Sessions Found: <number of sessions>” being displayed. This may include both Cloud Pod Architecture sessions and local sessions.

     

    7. How do I find the total number of desktop sessions for a particular Brokering Pod?

        From View Administrator UI, search for sessions by Brokering Pod (refer “View Desktop Sessions in a Pod Federation” chapter in "Administering View Cloud Pod Architecture" guide). You can see “Total Sessions Found: <number of sessions>” being displayed.

     

    8. Will Cloud Pod Architecture work on a View Connection Server that has been restored from backup after failure?

        Yes, Please refer to KB 2080522

     

    9. Can I join Pods from different domains?

        Yes, you can join Pods from different domains. It works if they have two-way trust between them. 1-way trust may not work depending on the direction of trust.

     

    10. If a View Connection Server hosting multiple pools is going to be offline for a maintenance activity, should we do any operation before the maintenance?

         Cloud Pod Architecture will automatically use available floating desktops in pools on other View Connection Servers if configured to do so while a View Connection Server and its pools are offline for maintenance. So, if one View Connection Server in a Pod is offline the other servers will be able to service any desktop requests for that pod.

     

    11. How do I check users getting impacted if a Pod or Site were to become unavailable?

         You can use the “lmvutil –listUserAssignments” command. Please refer to "Administering View Cloud Pod Architecture" guide to get the command details.

     

    12. Can I add Application pools to a global entitlement?

         No, View 6.0 does not support using remote Windows-based applications hosted on a Microsoft RDS host.

     

    13. Why am I not seeing Search Sessions page in View Administrator UI?

         Check if Cloud Pod Architecture is initialized on the Pod. Logoff from View Administrator and Login again.

     

    14. How can I access Global LDAP information with ADSI Edit?

         * It is not recommended to change any values in global LDAP as that may permanently damage your Cloud Pod Architecture configuration.

         * To view the Global LDAP data, start ADSIEdit on a broker

         * Select "Action->Connect to..."

         * In 'Connection point' choose "Select or type a Distinguished Name or Naming Context" and type in "dc=vdiglobal,dc=vmware,dc=int"

         * In 'Computer' choose "Select or type a domain or server" and type in "localhost:22389"

         * Click OK

     

    15. Why is a user not able to launch a desktop although he has a User Home Site defined?

         Please check if the Pod is added to the Site which is Home Site of the user.

     

    16. How do I check the topology of my Cloud Pod Architecture infrastructure?

         * Use the vdmadmin command line tool to issue the command: vdmadmin -X -lpinfo

         * Generate the DCT log bundle. Open file lmvinfo.txt present in the log bundle. You can get the Site, Pod and Pod Endpoint info.

     

    17. How do I troubleshoot desktop launch problems?

         With Cloud Pod Architecture the reasons for desktop launch failing are broadly the same as without Cloud Pod Architecture. The main difference is that the Pod launching the desktop and the Pod hosting the desktop may not be the same. Most problems can be troubleshooted using the error message displayed on the View Client. Most common problems are due to mis-configuration of Global Entitlements. If after addressing configuration problems a desktop still won't launch it may be necessary to look in the debug log of the Pod that is launching the desktop (the Brokering Pod) and search for log lines containing "Breadcrumbs" that indicate how Cloud Pod Architecture tried to handle the desktop request.

     

    18. How do I assign Pods to Sites?

         * Use the lmvutil command line tool with the --assignPodToSite option.

         * Use the lmvutil command line tool with option –-listPods to list the pods in the federation that can be assigned to sites.

     

    19. What happens if I have local entitlements for a Pool and now I create a Global Entitlement and associate the same pools and users to that?

         Cloud Pod Architecture layers onto existing View functionality, so it is possible to entitle users to the same pool both locally and through a Global Entitlement. However, this configuration isn't recommended as it is likely to confuse users. Selecting either of the local or Global Entitlement may result in the same desktop being delivered to the user.

     

    20. There are pools with same name in different pods. Can I add these pools to the same Global Entitlement?

         Yes, pools having same Pool ID in different pods can be added to the same Global Entitlement.

     

    21. Can a user be given multiple sessions?

         Yes, suppose in a classroom students need to login with the same credentials they can do so. You need to create a floating pool with “Allow multiple sessions per user” set to Yes and assign this pool to the Global Entitlement.

     

    22. Will Cloud Pod pools be visible on Horizon Workspace 2.0 Portal?

         Global Entitlements will not be visible in Workspace 2.0 Portal

     

    23. Is it possible to use the lmvutil --unjoin command to remove a pod from the federation if there are still Global Entitlements that make use of pools in the pod? If so, what happens to the entitlement?

         Yes, you can unjoin a Pod from a Pod Federation if there are still pools in that pod that belong to a Global Entitlement. The pools from that pod are automatically removed from the Global Entitlement.

     

    24. I've installed a new replica View Connection Server into my Pod but Cloud Pod Architecture isn't working. What do I do?

         Please refer to KB 2080521 for details on the extra steps that are required to get new replica View Connection Servers to work with Cloud Pod Architecture.

     

    25. Is there any specific header on the log lines of the Cloud Pod Architecture feature?

         * After the timestamp at the beginning of the line, most Cloud Pod log lines will contain "LMV:" near the beginning.

         * Lines that have "[Breadcrumbs] LMV:" indicate communication with a remote pod using VIPA (View Inter-Pod API). The breadcrumbs give an overview of a request, such as a desktop launch, and give an indication of the logic behind the launch by showing where launch has been attempted. They are key to understanding LMV logging, along with all lines that contain "LMV:"

     

    26. How is the communication between different Pods secure?

         Communication between pods happens through VIPA (View Inter-Pod API) using 2-way SSL. Certificates for VIPA are entirely managed by View and are rotated frequently (every 7 days). The lmvutil command line tool provides a mechanism to create and deploy a new certificate should the existing certificate be compromised in the 7 day time window. Options --createPendingCertificate and --activatePendingCertificate) can be used to configure certificates automatically for VIPA. Please refer to the "Administering View Cloud Pod Architecture" guide.

     

    27. Is the firewall in the View Connection Server automatically opened for the required ports when Cloud Pod Architecture is enabled?

         The View Connection Server installer creates the necessary rules at install time. The rules are then automatically enabled and disabled as required when Cloud Pod Architecture is initialized and pods join other pods. View Administrators will also have to open ports on any external firewalls they might have. Please refer to the "Administering View Cloud Pod Architecture" guide for the Cloud Pod Architecture port requirements.

     

    28. What happens if during Pod federation configuration a View Connection Server in a Pod is offline?

         Firstly, attempting any kind of major operation like this while a pod isn't in full health is not recommended. If a View Connection Server is offline then obviously that View Connection Server won't be able to initialize, join, unjoin or uninitialize a pod federation so it is not possible for the configuration to fully succeed for the whole Pod at that point. The lmvutil command line tool will initiate the pod operation and wait up to 30 minutes for that operation to complete. If the broker comes online within 30 minutes the operation should complete successfully and lmvutil will report success, but if it doesn't then lmvutil will report a timeout error. The operation will continue even after the lmvutil timeout.

     

    29. What is the allowed minimum/maximum network latency requirements for inter-pod communication?

         For VMware Horizon View 6.0 release, CPA itself has no particular latency requirements for inter-pod communications, however protocol session latency between pods needs to be considered. If a user in one site gets a desktop from another site, then the latency between the sites needs to support an acceptable remote protocol user experience.

     

    30. If a user is assigned a dedicated desktop from a site and the site goes down, will they get a new desktop?

         Users are not automatically provided with a desktop from another site if the site containing their dedicated desktop has gone down. The desktop request will fail because the dedicated desktop isn't available. The administrator could configure a separate Global Entitlement for the users to provide a floating desktop until such time the original site recovers. That floating entitlement should be arranged to deliver desktops from other sites as required.