Search the VMware Knowledge Base (KB)
View by Article ID

Troubleshooting issues with image publishing or gold pattern reseal in Horizon Cloud with Hosted Infrastructure (2143985)

  • 0 Ratings

Symptoms

  • Cannot publish or reseal gold pattern/image.
  • Publishing or resealing gold pattern/image task fails.

Cause

This issue occurs:
  • If a DaaS agent is not configured properly
  • Due to sysprep issues

Resolution

To troubleshoot the issue:
  • Verify if the certificate file from Administrator portal’s patterns screen is placed under the appropriate folder that is DaaS agent installed location. 

    For example: C:\Program Files (x86)\VMware\VMware DaaS Agent\Cert\cacert.pem

  • Verify if TA IPs are configured properly in monitoragent.ini file and registry (Check note below to configure this step).
  • Verify that the DaaS icon is showing up in the task bar.

    Right click the icon > About > Advanced to verify Collector Address is correctly displaying the Tenant Appliance IP.

  • Check if Antivirus is preventing the sysprep operation by disabling the Antivirus or adding required files to the exception.
  • Check for applications that may disrupt sysprep such as MS Security Essentials.

    For more information on MS Security Essentials, see Gold pattern seal fails - local admin account and the DaaS Agent service are being set to disabled (2100336).

  • Verify if the image has rearm counts left by running this  slmgr -dlv command.
  • Verify if the user account used for reseal/publish operation is member of local administrator account and is enabled.
  • Verify if there are any scripts in the image that customizes user accounts.
  • Refer DaaS Agent log under installed location and troubleshoot based on the error messages. Log file is located at  C:\Program Files (x86)\VMware\VMware DaaS Agent\service\logs (or under the custom install location).
  • For any other issues with Sysprep, start by looking at two sysprep files:

    • setupact.log
    • setuperr.log

    Check these locations for Windows Vista, Windows 7/8, Windows Server 2008/2008 R2/2012:

    C:\Windows\Panther
    C:\Windows\Panther\UnattendGC
    C:\Windows\System32\sysprep\Panther


    For more information, see Locations of sysprep log files (2001932).


  1. Hardcode TA IPs:

    Inside the GP VM OS, locate the MonitorAgent.ini file.

    File Locaion for 64 Bit OS: C:\Program Files (x86)\VMware\VMware DaaS Agent\service
    File Locaion for 32 Bit OS: C:\Program Files\VMware\VMware DaaS Agent\service

  2. Manually add the IPs of Tenant appliances in the  MonitorAgent.ini file:

    1. Stop the DaaS Agent service.
    2. Navigate to the MonitorAgent.ini file (file location mentioned above for 64bit and 32bit OS)
    3. Open the MonitorAgent.ini file using text editor. Locate entries smiliar to:

      ;standby_address=uncomment_and_add_comma_separated_standby_address_list
      collector_path=dt-collector-ws/services/CollectorWebService
      auto_discover=1


    4. Remove ; to uncomment the line.
    5. Add the IPs of your Tenant appliances.

      For example:

      standby_address=192.168.100.2,192.168.100.3
      collector_path=dt-collector-ws/services/CollectorWebService


      Note: Do not place the VIP/Floating IP of the Tenant in this file.

    6. Change the auto_discover from 1 to 0.

      auto_discover=0

    7. Start the DaaS Agent Service.

  3. Update the registry entry:

    Registry Paths:

    64bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware DaaS Agent
    32bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware DaaS Agent

    For example:

    1. In HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware DaaS Agent, set these values:

      "ConfiguredHostname"=dword:00000001
      "vmid"="6e8606d6-7b6c-4b4d-926b-cc8cc75c5ae2"


      Create these values in String value type:

      "AgentInstallPath"="C:\Program Files (x86)\VMware\VMware DaaS Agent" 
       "DesktopMgrAddresses"="Update TA DT/SVC network range IP addresses (Eg: x.x.x.2, x.x.x.3)"


      Note: Do not use TA VIP IP (x.x.x.4)

    2. Reboot the GP VM after registry update.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: