Friday, 7 December 2018

Enabling ThinPrint logging in Horizon View 7.x

Enabling ThinPrint logging helps you to troubleshoot issues with ThinPrint. ThinPrint logging can be enabled on VDI Desktop as well as on Horizon View client system. However, implement this procedure if ThinPrint is being used in environment.

Enabling TPAutoConnect and ThinPrint logging on the VMware View Desktop machine:
  • Start regedit.exe from command prompt or Windows Run.
  • Navigate to the HKLM\SOFTWARE\ThinPrint\TPAutoConnect key.

  • Create a new String value and name it DebugFile.


  • Modify DebugFile and set its Value data to C:\\tpautoconnect.log
    • Note: Ensure that you include the two backslashes so that the log file is created at the root of the C:\ drive.


  • Create a new DWORD value and name it DebugLevel.
  • Modify DebugLevel and set its Value data to 000000ff.
  • Navigate to the HKLM\SOFTWARE\ThinPrint\TPVMMon key.
  • Create a new String value and name it DebugFile. Modify DebugFile and set its Value data to C:\\thinprint.log.  
  • Create a new DWORD value and name it DebugLevel. Modify DebugLevel and set its Value data to 000000ff.
  • Create a new DWORD value and name it DebugMode. Modify DebugMode and set its Value data to 00000003.

  • Restart the TP AutoConnection Service for the changes to take effect.

  • Verify that log is being created.


Similar to above steps, ThinPrint logging can be enabled on Horizon View client machine as well. Follow below instructions to do the same.
  • Navigate to the HKLM\SOFTWARE\ThinPrint\Client key in Windows registry editor.
  • Create a new String value and name it DebugFile.
  • Modify DebugFile and set its Value data to C:\\thinprintclient.log.
  • Create a new DWORD value and name it DebugLevel.
  • Modify DebugLevel and set its Value data to 000000ff.
  • Create a new DWORD value and name it DebugMode.
  • Modify DebugMode and set its Value data to 00000003.
  • Navigate to the HKLM\SOFTWARE\ThinPrint\TPViewture key.
  • Create a new String value and name it DebugFile.
  • Modify DebugFile and set its Value data to C:\\tpviewture.log.
  • Create a new DWORD value and name it DebugLevel.
  • Modify DebugLevel and set its Value data to 000000ff.
  • Reboot the View Client system for the changes to take effect.

Wednesday, 5 December 2018

How to connect AD LDS database instance on View Connection Server

Below steps can be used to connect AD LDS database instance on Horizon view connection server.

  • Launch ADSIEdit tool.



  • In ADSIEdit console, right click ADSIEdit and click Connect to



  • Enter the details as shown below without any changes and click OK. NOTE:- Do not change any values e.g.  domain name. You do not need to type your active directory domain details here.



  • Now you should have your AD LDS database details as shown below.



Data recovery password in Horizon view 7.x

Data recovery password is configured during the initial setup of horizon view connection server as shown in below image. Data recovery password is required during the restore operations of AD LDS instance using vdmimport command. 

It is good idea to set data recovery password along with password reminder as it can be used to recover password in case you loose/forget the password. 


Data recovery password can be changed as required at later time also from View global settings page or Backup tab in Connection server properties as shown below.





AD LDS backup automatically runs everyday midnight as default schedule. We can change the periodicity of the backup, retention, offset and default path. 


One thing to be noticed here, there is no option to set clock time for backup schedule. We can only mention periodicity like every hour or every 6 hour and so on as shown below.


Manual backup option is also available in the View administration portal, hence can be executed as required from admin portal >View Configuration > Servers > Backup now button as shown below.



When backup is executed, it backs up AD LDS instance as well as the composer database in default path on connection server.



AD LDS Backup file (*.LDF) is by default encrypted. Hence, cannot be used directly while performing restore operations. One needs to decrypt the backup file first and then decrypted file is used to perform the restore operation. 


In order to generate decrypted LDF instance, vdmimport command is used with below syntax.

vdmimport -p "Your data recovery password" -f "Backup file path" > "new file name".ldf

In case you do not remember the data recovery password and try wrong password, error will be generated upon executing command as shown below.


Assuming that we do not know password for recovery, simply run vdmimport command without -p parameter. Once command is executed, it will prompt you for the data recovery password, however, if you had configured the reminder option, it will show you reminder string above password prompt as shown in image.


Enter the Password to proceed with decrypt operation. Once you have the decrypted LDF file. Use it to perform restore of AD LDS instance.



Cheers!!!! Hope this helps.

Popular Posts This Week