I thought I would share this script, its been circulating a bit but I feel it is a nice one to have in your toolkit.

Have you ever had to remove a LUN from a cluster and thought “Do I really need to detach all the LUN’s, before un-mapping from my SAN?”

1. Unmount Datastore
2. Detach LUN
3. Un-map from SAN
4. Rescan Cluster

Well here is a handy script with output. All you need to do is unmount your datastore(s), and then enter in your naaid of your LUN’s and the cluster you want to remove it from, save it an execute. All the LUN’s will be detached without having to manually …

Today vSphere 6.0 U1 is released. This is normally the update everyone waits for before upgrading their production environments to the latest version. I think the first time in awhile, a lot of people will wait.

You see, VMware has had a bug KB2124669 since ESXi 6.0 that can cause an ESXi host to randomly lose connection, freeze and overall act really terrible. With the release of 6.0U1 it still exists.

So I have had some time to play around with the new Linux Horizon View Agent and using Ubuntu as a VDI guest and it works pretty well. However as most of us have seen, when a user is logged onto the guest the screen is shown in the console. In some organizations this may pose a privacy or security risk.

Right now there is no true workaround as that is how the view session is handled, however there is a workaround to disable console access.

So Horizon View 6.1.1 was released recently with added support for published applications to finally be accessible via the HTML client. The process is pretty straightforward, however I came across one hiccup I wanted to share.

I am assuming you have already upgraded your View Composer, Connection and Security Servers and are now focused on getting the agents up to date.

1. Install/Update Agents on virtual desktops to 6.1.1 (The HTML Access 3.4 client will not work with previous agent versions)
2. Install/Update Agents on RDS servers to 6.1.1
3. Install the HTML Access 3.4 to all your connection …

Here is a bit of my experience with the VCP6-DCV Delta beta exam.

Initial Thoughts

Today I sat and took the VCP6-DCV Delta Exam beta. I have never taken a VMware beta exam so I wasn’t quite sure what to expect, from what I have been told, I expected lots of questions with bad grammar and horrible spelling. However today I got something a bit different. Ill explain it best without violating any NDA.

So one thing I have come across with a few VCSA6 installs was the inability to use login with current credentials via the Web client or vSphere client.

Working with VMware support we were finally able to get it working with a few tweaks and there is a current pending KB that has not been published yet. (KB2113038) I have been told this affects both an embedded deployment (VCSA and PSC together) and external deployment (VCSA and PSC seperate.)

So as always things change across multiple Window’s operating systems and VMware revisions. I had a need to extend the drives on about 50 VMs today and really didn’t want to do all that clicking. I remember awhile back it was easy to do this with a Basic Set-Harddisk and use the -ResizeGuestPartition but alas that has been removed from the current functionality. So I took my search to google and found a couple scripts that worked ok, but nothing that was a seamless experience.

VMware has announced https://mylearn.vmware.com/mgrReg/plan.cfm?plan=64178&ui=www_cert the availability of the VCP6-DCV beta exams. The beta exam includes 3 seperate exams. If you are currently an active VCP you can either take the VCP6-DCV or VCP6-DCV Delta exam, and if you are currently not certified you are required to take the vSphere 6 Foundations and VCP6-DCV to obtain the certification.

vSphere 6 Foundations : Exam code: 2V0-620

VCP6-DCV : Exam Code: 2V0-621

I was trying to remove SRM 5.1 from our environment and kept getting an error that UAC must be disabled. Even though UAC was set to “Never Notify” SRM didnt like this.

To fully disable UAC run the following command from an elevated command prompt and then reboot the system.

1REG ADD “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System” /v EnableLUA /t REG_DWORD /d 0 /f

Note:

You can also avoid this by doing the uninstall as the builtin local administrator account

I was in the process of getting vRealize for Horizon configured, and as I was going through the broker agent configuration for the life of me I couldn’t get the eventdb portion to work. Everytime i entered in the user name and password, I would receive the following error. FAILED (Format of the initialization string does not conform to specification starting at index 88.)

I knew it wasn’t a password issue as I was able to logon to SQL Manager with no issue, and the Horizon View EventsDB was working fine, so I went on a google search to try to hunt through logs. SQL Server was …