About Me

My photo
This blog has been created to share technical information, interesting innovations that I notice on daily basis and Architectural/Consulting overview of various technologies. My areas of interest, on which I would be blogging, are VMware, Microsoft and Citrix Technologies. I hope you will enjoy this blog and share your experience with me.

Horizon View 6.2 Secondary Credentials for One-way trust

Horizon View 6.2 introduced a new feature for the Active Directory One-way trust. If you have installed and configured Connection Server (CS) and at the time of performing entitlements under ‘Users & Groups’ or browsing the ‘AD Container’ under the (Guest Customization) during the pool creation you will encounter the following error message in View Administrator console:

Query Error

Follow these steps in order to fix the issue by adding the Secondary Credentials on the CS using vdmadmin command.

  1. Go to the CS server and open the Command prompt using the Admin privileges
  2. Change the directory path to C:\Program Files\VMware\VMware View\Server\tools\bin>
  3. Command to Add the Secondary Credentials:
    vdmadmin -T -domainauth -add -owner domain\viewadminUIuser -user domain\trustdomainuser -password trustdomainpassword
  4. Command to Remove the Secondary Credentials:
    vdmadmin -T -domainauth –remove-owner domain\viewadminUIuser -user domain\trustdomainuser
  5. Command to View all the Secondary Credentials for specified accounts
    vdmadmin -T -domainauth –list -owner domain\viewadminUIuser
  6. Repeat Step 3 multiple times, if you have more than One View Administrator that needs the capability to entitle Users & Groups or Creation of Desktop pools

Usage Notes:
Next to the -owner switch you need to add the user account use to logging into View Administrator Console
Next to the –user switch enter the credentials or service account of the trust domain where the User, Groups, OU Structure etc. reside

After you have added the secondary credentials, you will be able to perform ‘User & Group’ entitlements along with the ability to browse the ‘AD Container’ during the desktop pool creation in View Administrator console.

More details about the Secondary Credentials can also be found in the View Administrator Guide (Page No. 237)

Thanks,
Aresh

Collect Horizon View Connection Server Logs in vRealize Log Insight

If you are using the VMware Horizon View Content Pack for Log Insight it will capture the Connection Server logs (Log-Date.txt and Debug-Date.txt etc.). However, it doesn’t work out of the box by deploying the Content Pack alone. You will have to enable the View GPO (vdm_common.adm) onto the Connection Servers in order to get the logs captured by Log Insight. In our scenario without the GPO it was only able to capture the Windows Events Application, System and Security only.

You need to perform the following steps:

  1. Download the Horizon 6 View GPO Bundle (VMware-Horizon-View-Extras-Bundle-3.5.0-2999900.zip) from https://my.vmware.com Downloads section. The Build number will depend on your version of Horizon View
  2. Extract the View Common Configuration Template (vdm_common.adm) from the zip bundle and copy it over to the domain controller
  3. Create a new OU and name it E.g. ViewServers and move all the Connection Server machine accounts into that OU
  4. Open gpmc.msc on the domain controller go to the newly created OU – ViewServers and “Create a new GPO and link it here” give a name to the GPO as ViewLoginsight and then click on Edit
  5. Go to Computer Configuration –> Policies –> Administrative Templates right click open “Add/Remove Templates” to import the vdm_common.adm file.
  6. Go to Computer Configuration –> Policies –> Administrative Templates –> Classic Administrative Templates (ADM) –> VMware View Common Configuration –> Log Configuration
  7. Select “Send Logs to Syslog server” choose Enabled under the Send logs to Syslog Server type – Debug|LogInsightIPAddress (E.g. Debug|10.10.10.1, Info|10.10.10.1, Trace|10.10.10.1)
  8. On the Connection Server VM make sure you have the following entry added. Navigate to %ProgramData%\VMware\Log Insight Agent\
  9. Open the liagent.ini file in any text Editor (Notepad, Notepad ++ etc.)
  10. Add the following configuration parameters to the file
    [filelog|ViewMain]
    directory="C:\ProgramData\VMware\VDM\logs"
    include=log-*.txt;debug-*.txt
    exclude=wsnm_starts.txt
    Note: We are only capturing the logs from Connection Server and not from the View Agent (deployed on the desktops). We have removed the pcoip_server and pcoip_agent from the default string as mentioned under Tech Specs in Solution Exchange portal page.

  11. Save and Restart the VMware Log Insight Agent service.

You will be able to see the Horizon View Connection Server logs getting captured to the Log Insight Manager: (Example below)

CSLoginsight


There is also a detailed blog post on this topic by one of my colleague Sivaprasad click on this link - http://incloudnet.com/2015/01/08/view-loginsight-support/

Thanks,
Aresh

Collect Horizon View Composer Logs in vRealize Log Insight

If you are using the VMware Horizon View Content Pack for Log Insight it doesn’t capture the View Composer logs. As you are using the Log Insight instance to centralized all your logs, you may want to capture the Horizon View Composer logs please follow these steps:

  1. Install the log Insight Agent on the Horizon View Composer server VM within your environment
  2. Navigate to %ProgramData%\VMware\Log Insight Agent\
  3. Open the liagent.ini file in any text Editor (Notepad, Notepad ++ etc.)
  4. Add the following configuration parameters to the file

    [filelog|ViewComposer]
    directory=”C:\ProgramData\VMware\View Composer\Logs”
    include=vmware*.log
    exclude=vmware-viewcomposer-audit.log;vmware-sviconfig.log

  5. Save and Restart the VMware Log Insight Agent service.

You will be able to see the Horizon View Composer logs getting captured to the Log Insight Manager: (Example below)


LogInsight


Thanks,
Aresh

My Blog List