Posts

Removing invalid linked clone entries automatically using the ViewDBChk tool

Removing invalid linked clone entries automatically using the ViewDBChk tool in VMware Horizon View 5.3 and later versions (2118050) he ViewDbChk tool allows administrators to scan for and fix provisioning errors that can not be addressed using View Administrator C:\Program Files\VMware\VMware View\Server\tools\bin viewdbchk.cmd --scanMachines --desktopName Intertrust_Global_Desktop_x64 --limit 6 --force To run the View DbChk tool: If required, unzip the tool into a new folder. Click  Start  >  Run , type  cmd , and click  OK . The Command Prompt window opens. Navigate to the ViewDbChk tool: For version Horizon View 6.1,  ViewDbChk  is located under:  C:\Program Files\VMware\VMware View\Server\Tools\bin . For Horizon View 5.3 or 6.0, navigate to the folder created during the unzip process in step 1.   Enter  ViewDbChk  with the required flags as listed below into the command prompt to find and clean your database ...

Ansiple script windows patching

Ansible patching activity document 1.      Server-ansible   – Ansible server. prod1, prod2, sql, Manual 2.       [root@ Server-ansible  analytics]# cat /etc/ansible/hosts – validate the server list. 3.       Edit the if required to remove or add the servers, [Manual] Server1 server2 server3 server4 [sql] Server5 server6 server7 server8 [prod1] Server9 Server10 Server11 Server12 Server13 Server14 Server15 [prod2] Server16 Server17 Server18 Server19 Server20 Server21 Server22 Server23 Server24 Server25 [test] test server- fgtd-nte1-windows_testvm-app001.mhint – this server only for testing don’t use anyware. 4.       Checking the access for list of servers. ansible Manual -m win_ping – This cmd to check the ping communication on the remote servers one by one. Manual is the list of servers already defined ansible prod1 -m win_ping ansible prod2...

VMTool update steps on Horizon VDI Parent VM

VMTool update steps on Horizon VDI Parent VM The order should be as follows: 1 - Turn on the parent VM  and login 2 - Uninstall VMware Horizon Agent and reboot 3 - Uninstall VMware Tools and reboot 4 - Delete the following registry keys and directories if applicable(dependant on Guest OS), then reboot the VM: HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Tools HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM <C:\Program Files\VMware\VMware View\*.*> <C:\Documents and Settings\All Users\Application Data\VMware\VDM\*.*>  <C:\Program Files\VMware\VMware Tools\*.*>  5  - Install VMware Tools, then reboot 6 - Install VMware Horizon Agent and reboot 7 - Log back in and open CMD and type ipconfig /release, then shutdown the VM 8  - Take a snapshot and recompose the pool =================================================================================== https://kb.vmware.com/s/article/2118048 installation order of End User Co...

Update Manager 6.5 issue

Update Manager 6.5 issue ""interface com.vmware.vim.binding.integrity.VcIntegrity is not visible from class loader"" root@homelab71 [ /usr/lib/vmware-updatemgr/bin ]# pwd /usr/lib/vmware-updatemgr/bin root@homelab71 [ /usr/lib/vmware-updatemgr/bin ]# ./updatemgr-util config -g | less <vci_vcIntegrity> <EsxTaskMax>10</EsxTaskMax> <LocalTaskMax>10</LocalTaskMax> <downloadAfterInstallation>true</downloadAfterInstallation> <encryptGuestInfo>true</encryptGuestInfo> <guestRebootTimeout>900</guestRebootTimeout> <guestShutdownTimeoutMinutes>10</guestShutdownTimeoutMinutes> <path>../lib/libvci-vcIntegrity.so</path> <toolsUpgradeTimeoutSec>1800</toolsUpgradeTimeoutSec> <toolsWaitTimeoutSec>600</toolsWaitTimeoutSec> <vimNameSpace>vim.version.version10</vimNameSpace> <vpxdLocation>http://deheremvc30.emea.a...

Migration all the object from VCSA 5.5 to VCSA 6.5 and upgrading ESXi to 6.5

Migration all the object from VCSA 5.5 to VCSA 6.5 and upgrading ESXi to 6.5   Contents Abstract . 2 vCenter Server List: 2 Pre-check before migrate the ESXi host: 2 Implementation Plan: 3 Folder creation: - . 3 Cluster creation: - . 3 Host Migration: - . 3 TFTP Configuration: - . 4 Auto deploy Configuration: 4 ESXi version change: 5 Moving VM: - . 5 Based on the list taken in Check List,  move the VM to respective folders. 5 Management Host upgradation: 5 Post Implementation Check: 6 Roll back Plan: - . 6   Abstract All the core DC vCenter and ESXi host is running in 5.5 version and we are upgrade all ESXi host from 5.5 to 6.5 version and migration all the object from VCSA 5.5 to VCSA 6.5.   Pre-check before migrate the ESXi host: The following item is going to verified by who is going to migrate the vCenter server. Ø   Export the data store and port group list Ø   Export the list of ESXi...