vSphere 5.5 Update 1 is out with vSAN support!

What’s new

vCenter server 5.5 Update1

  • vCenter Server is now supported on Windows Server 2012 R2
  • vCloud® Hybrid Service™ vSphere® Client Plug-in, is now available in vSphere Web Client.

 

vSphere ESXi 5.5 Update1

  • VMware Virtual SAN  Virtual SAN 5.5 is a new hypervisor-converged storage tier that extends the vSphere Hypervisor to pool server-side magnetic disks (HDDs) and solid-state drives (SSDs). By clustering server-side HDDs and SSDs, Virtual SAN creates a distributed shared datastore designed and optimized for virtual environments. Virtual SAN is a standalone product that is sold separate from vSphere and requires its own license key

 

vSphere replication 5.5 Update1

  • VMware Virtual SAN is a fully supported feature of vSphere 5.5u1. You can use Virtual SAN in production environments with vSphere Replication 5.5.1 and vSphere 5.5u1.
  • Configure vSphere Replication on virtual machines that reside on VMware vSphere Flash Read Cache storage. vSphere Flash Read Cache is disabled on virtual machines after recovery.

 

vCenter Orchestrator 5.5 Update1

  • Workflow tagging
  • Plug-ins improvements
  • Version control system support
  • Dynamic Types (Beta)

Horizon View 5.3.1 is out and supports vSAN!

Today, VMware announced the General Availability (GA) of VMware Virtual SAN 5.5 and I’d like to take a moment to also introduce Horizon View 5.3.1. With this release, we are continuing the tradition of rapidly introducing innovations to market. And, now, the details:

  • Horizon View 5.3.1 supports VMware Virtual SAN 5.5. VMware Virtual SAN 5.5 is a component of VMware vSphere 5.5U1.
  • Horizon View 5.3.1 when used with VMware Virtual SAN 5.5 has been shown to reduce the total CAPEX cost of storage by up to 50%.
  • Horizon View 5.3.1 GA is intended for use with Virtual SAN 5.5 datastores only. There are no other new features in Horizon View 5.3.1 besides support for Virtual SAN 5.5.
  • Customers can purchase a Virtual SAN 5.5 license to deploy Horizon View 5.3.1.

How to distribute Mirage Client with logon script

One of the things that Horizon Mirage doesn’t give you out of the box is the ability to deliver the Mirage client to clients in a centralized manned, which is kinda awkward for a solution that tries to centralize everything.

I solved this problem with a logon script i use for client deployments; you can use and tweak my script as you want but don’t blame me if it doesn’t work for you 🙂

Here’s the thing:

@echo off

rem echo Detecting OS processor type

if "%PROCESSOR_ARCHITECTURE%"=="AMD64" goto 64BIT

:32BIT
rem echo 32-bit OS
msiexec /norestart /quiet /l* "\\path_to_log\%COMPUTERNAME%-MirageClient.log" /i "\\path_to_setup\MirageClient.x86.15875.msi" serverip=<your_mirage_server> usessltransport=false
goto END

:64BIT
rem echo 64-bit OS
msiexec /norestart /quiet /l* "\\path_to_log\%COMPUTERNAME%-MirageClient.log" /i "\\path_to_setup\MirageClient.x64.15875.msi" serverip=<your_mirage_server> usessltransport=false
:END

Notice that the setup files have to be on a network share as well as the location of the log files where everyone have write access.

New job, new challenges, new opportunity to learn

If you have been following my blog so far you might have noticed that I’ve kept a long radio silence recently.

The reason for this is that I am leaving the company I am working for to join a Citrix Partner, Sinthera.

I will be part of the Citrix Group there and still be involved in VMware projects, so it seems I will be able to know both sides of the EUC river.

A lot to learn, a lot of new stuff… many new challenges.

I’ll do my best to keep writing in this blog and you might expect I will open a Citrix section as well 🙂

I would like to thank you all the people at Gruppo Sinapsi who helped me develop as a professional in all those years.

Wish me luck!

%d bloggers like this: