## Pages

### Emulex OneCommand Plugin for vCenter

Summary:
This plug in adds an extra tab to vCenter that lets you manage your Emulex HBA/UCNA’s.  From setting drivers parameters to allowing you to apply firmware updates to your HBA/UCNA card.  To do so, you must install the CIM package onto your host and have a server for the Emulex OneCommand Software Plug-in.
PreReqs:
1. Windows Server VM(suggest 2008 x64 R1 or R2)
2. Software Plug-in
3. CIM Provider 3.2.x +
4. vSphere CLI or vMA <— Needed to remotely install CIM provider bundle
5. vCenter 4.1+
Details:
You can install the Emulex Software Plug-in on the vCenter server, but I suggest keeping all modules separate from vCenter if possible.
1. Run the Software Plug-in installation.
2. Install the CIM Provider on all hosts you would like to have onecommand management capabilities.
• Place ESXi server in maintenance mode.
• vCLI command is as follows:
• vihostupdate.pl --server nameofyouresxserver --install --bundle \\path\to\elx-esx4.1.0-emulex-cim-provider-3.2.30.1-offline_bundle-364582.zip
• Enter your root credentials, then reboot when prompted.
Once completed, you should be able to manage your HBA/UCNA devices in vCenter under the new Emulex OneCommand tab.

Side Note:
I went through this whole setup because I wasn’t able to update the firmware on a OCe10102-FX CNA using the standard OneCommand application.  My CNA was running 2.702.200.17 (2.102.200.17) which for some reason caused my vKernel connection to not talk.  Upgrading to 2.703.397.13 (2.103.397.13) fixed this issue.

### Outlook 2011 Reply, New E-mail, etc. not working...

Summary:
Click to create an new e-mail or hitting reply cause nothing to happen.  This seems to occur after updating to Safari 5.0.4.

Workaround:
Uninstall Safari and reinstall it.
1. Download the current Safari version.  Do not install it yet, it will attempt to run.
2. Drag and drop the Safari icon from the applications folder to your trash and empty it.
3. Now go to your downloads folder and find the file named something like "Safari5.0.4".dmg  Double-click it.  Then double click the pkg file that appears in a new window.
4. Follow the wizard, then reboot.

### NFS Mapping to ESX and why you should use PowerCLI, not vCenter.

Summary:

Inserting a new host in an ESX Cluster and mapping an NFS share to it produced an interesting result.  vCenter showed 2 datastores w/ similar names.  1 w/ 48 hosts mapped to it and another w/ my 1 new host mapped to it.  The names were the same albeit one having a "(1)" appended to it.  Attempting to change the new one would result in error stating that a datastore already exists w/ that name.

Details:

Something as minor as an extra '/', servername.local vs. servername, or IP instead of name, makes ESX treat those mapped NFS shares as completely different even if they all point to the same end point.

Example:

Both of these are valid paths to a NFS share in ESX and they both connect to the same resource, but because of one having a FQDN ESX treats them as different shares completely.

netfs://servername.local/share

netfs://servername/share

Resolution:

Use PowerCLI to map NFS shares (or host profiles if you're licensed for them)

   1: #Use an ESX host that has your nfs paths mapped.
   2: $nfsshares = get-vmhost myfirstesxserver | get-datastore | where {$_.type -eq "NFS"} | Get-View
   3: #Now $nfsshares should have all your nfs pathing information.  4:   5: #At this point I'm taking each entry in$nfsshares and
   6: #mapping them to my new esx host
   7: $NewESXHost = Get-VMHost mynewESXServer  8: Foreach ($nfsshare in $nfsshares)  9: {$NewESXHost | New-Datastore -nfs -name $nfsshare.info.nas.name -nfshost$nfsshare.info.nas.remotehost -path $nfsshare.info.nas.remotepath} Trick: In the script above, if you want to see the nfs share information before you apply it do this after running the lines 1 - 3:  1: Foreach($nfsshare in $nfsshares) {$nfsshare.info.nas}

Summary:

When attempting to connect to a VMWare View 4.5 environment via a Security server the following error is generated:

VMWare View for iPad is technically made for View 4.6, however, it will work w/ a 4.5 environment, just not connecting through a 4.5 security server.  So it’s a half-truth.

WorkAround:

• You can configure VPN via the Enterprise Tool provided by Apple free of charge.
2. Connect to a 4.5 Connection Server (not a 4.5 security server)
• This can normally be achieved through step 1 or via your internal wireless network.

Resolution:

1. Easy if you are running Windows 2008 R2.
1. Why 2008 R2?  This is the only to get PCoIP support through the security server.
2. A bit more complicated if you find yourself needing to upgrade the OS on all your connection/security servers from Windows 2003.

Summary:

Was looking for the method to do this, it’s pretty simple, but everyone had very detailed posts of other things they were doing (checks and balances).  Here is the key snippet to do it:

   1: #This simply gets you the object to work with.  You can replace
   2: #'nameofcomputer' with a variable to target more systems.
   3: $admin = [adsi]("WinNT://" + nameofcomputer + "/administrator, user")  4:   5: #This invokes the set password method and changed the administrator password  6: #to Whatever1  7:$admin.psbase.invoke("SetPassword", "Whatever1")

If you want more robust script that records data of it’s changes see here.

### Windows 2008 customization specification does not join VM to domain.

Summary:

Ran into this problem.  Logs weren’t obvious in demonstrating problem.  Resolution is located in VMWare KB.  I used my PowerCLI script to fix the issue on all my Windows 2008 Cust.Specs.

Resolution:

Username of account that joins system to domain must be formatted as <username>@yourdomain.com.

VMWare KB:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012314

### View 4.5 New VM's not being composed.

Summary:
VM's stopped composing and the following messages appears in View logs:

VC_DISABLED:VC:cn=04683182-25c0-40f7-b9a1-1963167d877a,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int;REASON:VM operation failed: com.vmware.vdi.svisupport.SVIException: View Composer Fault: VMware.Sim.Fault.VcDatastoreInaccessibleFault;

Desktop Composer Error:VMware.Sim.Fault.VcDatastoreInaccessibleFault; Error Type:com.vmware.SviService.VcDatastoreInaccessibleFault;Error FaultActor:null; Error code:{http://schemas.xmlsoap.org/soap/envelope/}Client; Error details:[Lorg.w3c.dom.Element;@b729f8

This seems to occur if an ESX host is added to the View Cluster that has not been mapped to the View shared disks.  Placing the host in maintenance or disconnecting doesn't seem to help.

Workarounds:

• Remove the ESX host until all shared disks have been mapped.
• Move ESX host to temporary folder/cluster/node until host is configured properly.