Plain Virtualization

It has been some time since my last post.  Have been really busy however I always make a point to at least do a meaningful post a month.  Since VMworld is also round the corner, there will be many updates from all other bloggers around the world. Recently was doing a Proof of Concept (POC) for Horizon Mirage and was questioned on the time to centralize an end device was too long. Here's what happen: A simple centralize of endpoint took as long as 140mins in one setup and 52mins in another which could not have been shorter since the endpoint is plain OS image about 40GB in size. Setup 1 First setup that took 140mins where the Horizon Mirage Server is a VM on a standalone ESXi server with local disk with two 500GB 7.2RPM SATA disks extended into one datastore. Setup 2 The Horizon Mirage server was installed on a physical server with 500GB 7.2RPM SATA Disks on Raid 1.  This took 52mins. Separately, my colleague did a test as well in our office network which...

Recently did a presentation on VMware Mirage to one of my customer who have attended the vForum 2012 and like to explore.  Some questions were posted and like to share some of the ways you can compliment or work with your existing patch management which you might currently have in your environment. You can find out more on VMware Mirage here . Download a free trial here . Question 1: SCCM in place for patching endpoints.  Mirage can help in two use cases: Use Mirage to build the reference machine for base layer and deploy to all end points.  SCCM to push all other apps and patches. Use Mirage to build reference machine for base layer and deploy to all end points as standard.  Use SCCM to only patch the reference machine.  Use Mirage to create different layers for different layers required. Now which to choose?  I would recommend option 2.  Here is why.  Using SCCM to patch the reference image and using Mirage to capture helps manag...