John Wray's Blog - VMware

VMware Change Power Policy to High Performance - powerCLI

john@johnwray.com — Fri, 10 Mar 2017 02:50:00 -0500

I wanted to change the power setting of all my hosts to high performance and not do it one at a time manually.

This is an easy to accomplish this with powerCLI.

====================================================================

Add-PSSnapin VMWare.VimAutomation.Core

connect-VIServer -server <vcenter.your.domain> -User <DOMAIN\User> -Password <password>

$vmHosts = Get-VMHost
foreach ($vmHost in $vmHosts)
{
$view = (Get-VMHost $vmHost | Get-View)
(Get-View $view.ConfigManager.PowerSystem).ConfigurePowerPolicy(1)
}

====================================================================

This sets the Power Policy to High Performance (1)

1=HighPerformance

2=Balanced

3=LowPower

Removing stuck or missing desktops from VMware Horizon View

john@johnwray.com — Sat, 20 Sep 2014 02:56:00 -0500

Every once in a while you will get View Desktops stuck in View Administrator that won’t delete or were deleted and are showing as missing. You will need to manually clean them from the ADAM database. First connect to the ADAM database from one of the connection servers. Normally DOMAIN-VDCS1

Windows Server 2008

To connect to the View ADAM database:

Log in to one of the View Connection Servers.
Click Start > Administrative Tools > ADSI Edit.
In the console window, right-click ADSI Edit and click Connect to.
In the Name field type: View ADAM Database
Select Select or type a Distinguished Name or Naming Context.
In the field below, type dc=vdi,dc=vmware,dc=int
Select Select or type a domain or server.
In the field below, type localhost
Click OK.
Click View ADAM Database [localhost] to expand.
Click DC=vdi,dc=vmware,dc=int to expand.

Next, locate the GUID of the stuck/orphaned VM you would like to disappear.

Removing the virtual machine from the ADAM database

Note: Before removing entries from the ADAM database, note the virtual machine name of the desktops that are being removed for reference when editing the Composer Database.

Connect to the View ADAM Database. For more information, see Connecting to the View ADAM Database (2012377).
Locate the GUID of the virtual machine

Right-click the Connection View ADAM Database [localhost:389], and click New > Query.

Under Root of Search, click Browse.. and select the Servers organizational unit.
Click OK.
In the Query String, paste this search string:

(&(objectClass=pae-VM)(pae-displayname=VirtualMachineName))

Where VirtualMachineName is the name of the virtual machine for which you are trying to locate the GUID. You may use * or ? as wildcards to match multiple desktops.
Click OK to create the query.
Click the query in the left pane. The virtual machines that match the search are displayed in the right pane.

Once you clean out all of the GUIDs, refresh the query to make sure you got all of the VMs.
Check the View Administrator before you go any further, you may have unstuck enough to where the rest of the process completed.

Notes:

Check if there are entries under OU=Desktops and OU=Applications in the ADAM database.
A broken pool that does not contain any desktops can be removed from View Manager by removing the pool entry from both the Server Groups and Applications organizational units. However, removing one entry and not the other from the ADAM database results in the java.lang.nullpointerexception error when attempting to view the pools or desktops inventory in View Manager.

Removing the linked clone references from the View Composer database

After cleaning out the VMs from the ADAM database you may get an error about a VM with the specifications already exists.

To remove the linked clone references from the View Composer database:

sviconfig -operation=removesviclone -vmname=<name of vm> -adminuser=username -adminpassword=password -ServerUrl=https://localhost:18443/SviService/v3_0

SviConfig is located on vCenter Server hosting View Composer (or standalone Composer server) at:

32-bit servers: Install_drive\Program Files\VMware\VMware View Composer

64-bit servers: Install_drive\Program Files (x86)\VMware\VMware View Composer

VAAI Manual Install

john@johnwray.com — Fri, 19 Sep 2014 06:53:00 -0500

If you check the storage you will see that Hardware Acceleration is not supported. This doc assumes you have uploaded the NetAppNasPlugin.zip file to a mounted datastore. I usually use the nonreplicated datastore and create a Patches folder. The zip can be downloaded directly from NetApp. Turn on SSH and login to your host. cd to the patches directory. cd /vmfs/volumes/nonreplicated/Patches

do an ls –l and you should see the zip file you uploaded.

Enter the below command, changing the path after the –d to your path. Each server will be different.

esxcli software vib install -n NetAppNasPlugin -d /vmfs/volumes/e8638f00-81facdd9/Patches/NetAppNasPlugin.v20.zip

Once the command finishes you should see the message below telling you the update completed successfully. Put the server into maintenance mode and reboot.

When the server comes back up you should see that Hardware Acceleration is now supported.

Install ESXi 5 from a USB Flash Drive.

john@johnwray.com — Fri, 19 Sep 2014 06:52:00 -0500

Install ESXi 5.x from a USB Flash Drive.

1. Download an older version of SYSLINUX because the newer version won’t work in this case. (http://www.kernel.org/pub/linux/utils/boot/syslinux/3.xx/syslinux-3.75.zip)

2. Extract the zip somewhere on your computer.

3. Download the current iso for ESXi 5.x install.

4. Extract the ESXi 5 installable ISO to a folder.

5. Format your flash drive with FAT32.

6. Open a command prompt (Open as admin if you are a ‘tard and haven’t shut off UAC)

7. Navigate to where you extracted the SYSLINUX zip file from step one.

8. Navigate to the win32 subfolder (Syslinux\syslinux-3.75\win32)

9. Execute this command syslinux –mfa F: (F: is the drive letter assigned to your flash drive, could be anything.)

10. Copy the contents of the folder for the ESXi 5 install you expanded from the iso.

11. Rename two files:

a. ISOLINUX.CFG gets renamed to SYSLINUX.CFG

b. ISOLINUX.BIN gets renamed to SYSLINUX.BIN

12. Boot from USB and install ESXi 5 much quicker. J