VMworld 2015 Conference Tips

VMworld is only a month away, and as every seasoned conference veteran knows, there are a number of tips that will make the experience better.

I’ve put together my favorite tips for VMworld, and I’ve grouped the tips into categories based on

Social

  • If you haven’t already done so, sign up for Twitter.  The #VMworld hashtag is one of the primary communications channels for conference attendees.  You can also follow sessions by using the session number as a hashtag.
  • Add the “Unofficial VMworld Bloggers List” to your RSS feed. (Note: Link does not work.  Will update when I have an updated  link.)  Bloggers will recap sessions they find interesting or provide analysis of the keynote contents.
  • Be sure to sign up for VMunderground – the best community-led event of the weekend.  This year, it will be at the City View right across from the Moscone Center.
  • Talk to your vendors and tell them you’re going.  Chances are they will have a booth.  They may also have a customer appreciation event that you can score tickets to. 
  • Ask your local VMUG leaders if they know anyone from your area that is going, and find a time to do a local meetup sometime during the conference.

Packing and Travel

  • You’ll be walking around a lot, so clean out your backpack before you leave.  Chances are, you won’t need that Cisco rollover cable or a bitdriver set during the conference.  VMware also provides a notebook, so you can leave yours at home.  If you plan to use the conference backpack, then there is no point in bringing along items that you will have to repack to bring home.
  • The average high temperature for late August is 70 degrees Fahrenheit.  The lows are around 55 degrees.  Pack accordingly, and don’t forget to bring a light coat as it can get a little chilly at night. 
  • Leave a little room in your suitcase to bring stuff back.  The VMworld conference kit usually includes a backpack of some sort, and T-shirts are a popular vendor giveaway.  FedEx and UPS both have retail locations on Kearny Street if you would prefer to ship stuff instead of bringing it on the plane.
  • If you forget anything, there is a Target in the Metreon, which is right across the street from Moscone.

Technology

  • This is another area where travelling light is key as you will have to carry it around for most of the day. 
  • Bring extra batteries or battery packs for your devices.  You will be on your phone, tablet, and laptop all day, and you may not get a chance to recharge them during the day, so it is wise to have a power bank, such as this 13000 mAh battery pack, to keep your mobile devices topped off.
  • Don’t forget to bring your chargers.  There is an Apple store nearby for Apple products, but finding chargers for other laptop brands might be difficult.  Target should have chargers for other mobile devices.

General Conference Info

  • You will be standing and walking a lot.  Comfortable, broken-in shoes are a must.  If you plan to buy new shoes, buy them soon and start breaking them in so you avoid blisters and other foot injuries.
  • It may also be a good idea to start going for a walk a couple of times a week just to prepare.  If you don’t, you may be a little sore after the first day or two. 
  • Drink water frequently.  The VMworld Welcome Kit includes a water bottle, and there are water coolers around Moscone that you can use to fill it.

Sessions

  • Plan your schedule early as popular sessions may fill up quickly.
  • If a session is full, add yourself to the waiting list.
  • If you are interested in two sessions that overlap, book one and add the other to your Interest list.  The schedule changes frequently, and you may get an opportunity to register for both.
  • Every session is recorded, so don’t worry if you miss one.  You can always download and watch the video later.
  • Register for Group Discussions.  They’re a good opportunity to talk to your peers and experts from VMware.  These sessions are small, so register early if you want to guarantee a spot.

Solutions Exchange

  • Block off time in your schedule to peruse the Solutions Exchange.  You want to spend time here talking to vendors.
  • Make it a point to stop by booths for vendors that you already do business with.  This is a good time to ask your vendors’ experts and get your questions answered.

Places to Eat Near Moscone

San Francisco has a lot of good cuisine.  They’re especially noted for their Asian cuisine, which is sadly not reflect in the list below. 

  • Oasis Grill – Located across the street from Moscone West.  Servers gyros and Mediterranean
  • Super Duper Burger – Located on the north side of the Yeurba Buena Garden, this place is known for burgers, garlic fries (with fresh garlic), soft-serve ice cream
  • Mel’s Drive In – 50’s style diner near Moscone with excellent breakfast.
  • Thirsty Bear – Located on Howard just east of Third Street.  Known for craft bear and spanish-style cuisine.
  • The Melt – A few blocks away from Moscone at the corner of Minna and New Montgomery, this is a grilled cheese and soup place.
  • Boudin – A local chain with a few locations around Moscone.  Known for their Sourdough bread.
  • Ghirardelli – The famed chocolatier.  The location at Market and Montgomery is also an ice cream shop that is open late.
  • Lori’s Diner – Located at Powell and Sutter, this 50’s style diner is open 24/7 so you can get some post-party breakfast.

And finally – Sushirrito on New Montgomery.  It’s a sushi burrito.  Need I say more??

Other Stuff

  • Go out and enjoy yourself.
  • There is an online registry of events for the week at http://www.vmworld.com/en/gatherings.html.  Go out and socialize with your peers.
  • Even if you don’t know who the bands are, go to the VMworld party.  The last time it was at AT&T Park, it was a blast.
  • If packed events aren’t your thing, go explore the city.  Although a lot of museums close by 6:00 PM, restaurants on Fisherman’s Wharf and Ghirardelli’s are open late. 

Safety

  • San Francisco has a large indigent population.  Be careful when handling money in public or using ATMs.  (Note: This is a general safety tip for any large American city.  You don’t want to make yourself a victim or be “aggressively panhandled.”)
  • San Francisco has some rough areas, and its not hard to get lost and wander into them.  Many of the conference hotels are near Union Square, and it is very easy to take a wrong turn and wander into the Tenderloin District. 

The Approaching Backup (Hyper)Convergence #VFD5

When we talk about convergence in IT, it usually means bringing things together to make them easier to manage and use.  Network convergence, in the data center, is bringing together your storage and IP stacks, while hyperconverged is about bringing together compute and storage together in a platform that can easily scale as new capacity is needed.

One area where we haven’t seen a lot of convergence is the backup industry.  One new startup, fresh out of stealth mode, aims to change that by bringing together backup storage, compute, and virtualization backup software in a scalable and easy to use package.

I had the opportunity to hear from Rubrik, a new player in the backup space, at Virtualization Field Day 5.   My coworker, and fellow VFD5 delegate, Eric Shanks, has also written his thoughts on Rubrik.


Note: All travel and incidental expenses for attending Virtualization Field Day 5 were paid for by Gestalt IT.  This was the only compensation provided, and it did not influence the content of this post.


One of the challenges of architecting backup solutions for IT environments is that you need to bring together a number of disparate pieces, often from different vendors, and try to make them function as one.  Even if multiple components are from the same vendor, they’re often not integrated in a way to make them easy to deploy.

Rubrik’s goal is to be a “Time Machine for private cloud” and to make backup so simple that you can have the appliance racked and starting backups within 15 minutes.  Their product, which hit general availability in May, combines backup software, storage, and hardware in a package that is easy to deploy, use, and scale.

They front this with an HTML5 interface and advanced search capabilities for virtual machines and files within the virtual machine file system.  This works across both locally stored data and data that has been aged out to the cloud due to a local metadata cache.

Because they control the hardware and software for the entire platform, Rubrik is able to engineer everything for the best performance.  They utilize flash in each node to store backup metadata as well as ingest the inbound data streams to deduplicate and compress data.

Rubrik uses SLAs to determine how often virtual machines are protected and how long that data is saved.  Over time, that data can be aged out to Amazon S3.  They do not currently support replication to another Rubrik appliance in another location, but that is on the roadmap.

Although there are a lot of cool features in Rubrik, it is a version 1.0 product.  It is missing some things that more mature products have such as application-level item recovery and role-based access control.  They only support vSphere in this reslease.  However, the vendor has committed to adding many more features, and support for additional hypervisors, in future releases.

You can watch the introduction and technical deep dive for the Rubrik presentation on Youtube.  The links are below.

If you want to see a hands-on review of Rubrik, you can read Brian Suhr’s unboxing post here.

Rubrik has brought an innovative and exciting product to market, and I look forward to seeing more from them in the future.

GPUs Should Be Optional for VDI

Note: I disabled comments on my blog in 2014 because of spammers. Please comment on this discussion on Twitter using the #VDIGPU hashtag.

Brian Madden recently published a blog arguing that GPU should not be considered optional for VDI.  This post stemmed from a conversation that he had with Dane Young about a BriForum 2015 London session on his podcast

Dane’s statement that kicked off this discussion was:
”I’m trying to convince people that GPUs should not be optional for VDI.”

The arguments that were laid out in Brian’s blog post were:

1. You don’t think of buying a desktop without a GPU
2. They’re not as expensive as people think

I think these are poor arguments for adopting a technology.  GPUs are not required for general purpose VDI, and they should only be used when the use case calls for it.  There are a couple of reasons why:

1. It doesn’t solve user experience issues: User experience is a big issue in VDI environments, and many of the complaints from users have to do with their experience.  From what I have seen, a good majority of those issues have resulted from a) IT doing a poor job of setting expectations, b) storage issues, and/or c) network issues.

Installing GPUs in virtual environments will not resolve any of those issues, and the best practices are to turn off or disable graphics intensive options like Aero to reduce the bandwidth used on wide-area network links.

Some modern applications, like Microsoft Office and Internet Explorer, will offload some processing to the GPU.  The software GPU in vSphere can easily handle these requirements with some additional CPU overhead.  CPU overhead, however, is rarely the bottleneck in VDI environments, so you’re not taking a huge performance hit by not having a dedicated hardware GPU.

2. It has serious impacts on consolidation ratios and user densities: There are three ways to do hardware graphics acceleration for virtual machines running on vSphere with discrete GPUs.

(Note: These methods only apply to VMware vSphere. Hyper-V and XenServer have their own methods of sharing GPUs that may be similar to this.)

  • Pass-Thru (vDGA): The physical GPU is passed directly through to the virtual machines on a 1 GPU:1 Virtual Desktop basis.  Density is limited to the number of GPUs installed on the host. The VM cannot be moved to another host unless the GPU is removed. The only video cards currently supported for this method are high-end NVIDIA Quadro and GRID cards.
  • Shared Virtual Graphics (vSGA): VMs share access to GPU resources through a driver that is installed at the host level, and the GPU is abstracted away from the VM. The software GPU driver is used, and the hypervisor-level driver acts as an interface to the physical GPU.  Density depends on configuration…and math is involved (note: PDF link) due to the allocated video memory being split between the host’s and GPU’s RAM. vSGA is the only 3D graphics type that can be vMotioned to another host while the VM is running, even if that host does not have a physical GPU installed. This method supports NVIDIA GRID cards along with select QUADRO, AMD FirePro, and Intel HD graphics cards.
  • vGPU: VMs share access to an NVIDIA GRID card.  A manager application is installed that controls the profiles and schedules access to GPU resources.  Profiles are assigned to virtual desktops that control resource allocation and number of virtual desktops that can utilize the card. A Shared PCI device is added to VMs that need to access the GPU, and VMs may not be live-migrated to a new host while running. VMs may not start up if there are no GPU resources available to use.

Figure 1: NVIDIA GRID Profiles and User Densities
clip_image001[10]

There is a hard limit to the number of users that you can place on a host when you give every desktop access to a GPU, so it would require additional hosts to meet the needs of the VDI environment.  That also means that hardware could be sitting idle and not used to its optimal capacity because the GPU becomes the bottleneck.

The alternative is to try and load up servers with a large number of GPUs, but there are limits to the number of GPUs that a server can hold.  This is usually determined by the number of available PCIe x16 slots and available power, and the standard 2U rackmount server can usually only handle two cards.   This means I would still need to take on additional expenses to give all users a virtual desktop with some GPU support.

Either way, you are taking on unnecessary additional costs.

There are few use cases that currently benefit from 3D acceleration.  Those cases, such as CAD or medical imaging, often have other requirements that make high user consolidation ratios unlikely and are replacing expensive, high-end workstations.

Do I Need GPUs?

So do I need a GPU?  The answer to that question, like any other design question, is “It Depends.”

It greatly depends on your use case, and the decision to deploy GPUs will be determined by the applications in your use case.  Some of the applications where a GPU will be required are:

  • CAD and BIM
  • Medical Imaging
  • 3D Modeling
  • Computer Animation
  • Graphic Design

You’ll notice that these are all higher-end applications where 3D graphics are a core requirement.

But what about Office, Internet Explorer, and other basic apps?  Yes, more applications are offloading some things to the GPU, but these are often minor things to improve UI performance.  They can also be disabled, and the user usually won’t notice any performance difference.

Even if they aren’t disabled, the software GPU can handle these elements.  There would be some additional CPU overhead, but as I said above, VDI environments usually constrained by memory and have enough available CPU capacity to accommodate this.

But My Desktop Has a GPU…

So let’s wrap up by addressing the point that all business computers have GPUs and how that should be a justification for putting GPUs in the servers that host VDI environments.

It is true that all desktops and laptops come with some form of a GPU.  But there is a very good reason for this. Business desktops and laptops are designed to be general purpose computers that can handle a wide-range of use cases and needs.  The GPUs in these computers are usually integrated Intel graphics cards, and they lack the capabilities and horsepower of the professional grade NVIDIA and AMD products used in VDI environments. 

Virtual desktops are not general purpose computers.  They should be tailored to their use case and the applications that will be running in them.  Most users only need a few core applications, and if they do not require that GPU, it should not be there.

It’s also worth noting that adding NVIDIA GRID cards to servers is a non-trivial task.  Servers require special factory configurations to support GPUs that need to be certified by the graphics manufacturer.  There are two reasons for this – GPUs often draw more than the 75W that a PCIe x16 slot can provide and are passively cooled, requiring additional fans.  Aside from one vendor on Amazon, these cards can only be acquired from OEM vendors as part of the server build.

The argument that GPUs should be required for VDI will make much more sense when hypervisors have support for mid-range GPUs from multiple vendors. Until that happens, adding GPUs to your virtual desktops is a decision that needs to be made carefully, and it needs to fit your intended use cases.  While there are many use cases where they are required or would add significant value, there are also many use cases where they would add unneeded constraints and costs to the environment. 

Countdown to Virtualization Field Day 5–#VFD5

In two weeks, I get the pleasure of joining some awesome members of the virtualization community in Boston for Virtualization Field Day 5. 

If you’re not familiar with Virtualization Field Day, it is one of the many Tech Field Day events put on by Stephen Foskett (@sfoskett) and the crew at Gestalt IT.  These events bring together vendors and members from the community to have technical discussions about the vendor’s products and offerings.   These events are streamed live on the Tech Field Day website, and there are many opportunities to interact with the delegates via Twitter by following the #VFD5 hashtag.

The vendors that will be sponsoring and presenting at Virtualization Field Day 5 are:

DataGravity_392x652-wpcf_100x17

 logo1

     logo-large-gray-wpcf_100x48
logo-wpcf_100x21        med-vert-notag-wpcf_93x60 PernixData_Logo_Color
Scale_Logo_High_Res-wpcf_100x38 v2Ravello_Logo_large-wpcf_100x27 VMTurboLogoSm

I will be joining an awesome group of delegates:

This will be my first time attending Virtualization Field Day as a delegate.  I’ve previously watched the events online and interacted with the delegates on Twitter. 

Keep watching this space, and the #VFD5 hashtag on Twitter, as there will be a lot more exciting stuff.

Looking Ahead To the Future

“You might feel that somehow, you’ve lost all your fizz.
Or you’re frazzled like a…um…frazzled thing.  I’m not sure what it is.”
From Happy Hippo, Angry Duck by Sandra Boynton

For the last year and a half, I’ve worked for Faith Technologies, a large electrical contractor with offices in five states, in Menasha, WI.  I have a great manager who has encouraged me to grow and get involved in the greater IT community.  That manager has also lead one of the best teams I’ve worked on to-date.

While I have learned and accomplished a great deal in this role, it is time to move on.  Today is my last day with Faith.

While Faith is a great company, and I have a great manager and work on a great team, I didn’t see a path forward to reach goals that I had set for myself. 

I will be starting a new role next week Tuesday.  My new role is a big change for me as I will be moving from the customer side over to a partner. I’ll be going to work with another awesome team, and I’m looking forward to the challenges that this new role will bring.

What’s New–Horizon 6.1

VMware will be announcing the latest update to the Horizon Suite of End-User Computing products later today, and this edition brings some exciting new features to VMware Horizon.

Some of the new features in this edition are:

  • Support for vSphere 6.0
  • vGPU support for Virtual Desktops and Shared Applications
  • Enhanced Support for VSAN
    • Horizon 6.1 with vSphere 6 will support up to 200 desktops per host, and 4000 desktops and 20 hosts per VSAN cluster.
  • VVOLs support for Virtual Desktops
  • USB Storage Device Redirection for Hosted Desktops and Applications running on Windows Server 2012 and 2012 R2
  • Cloud Pod Architecture can now be managed through the View Administrator Web Console
  • Support for running Windows Server 2012 R2 as a Desktop OS
  • IPv6 support

There will also be two new Tech Previews coming shortly after the Horizon 6.1 launch –

  • Linux Desktops – An upcoming Tech Preview will add support for Linux Desktop VMs to Horizon
  • Chromebook Client – Chromebook users will no longer be restricted to using Horizon Blast to access virtual desktops.  The Chromebook client will be based on the Android App and add Hosted Applications Support to Chromebook.

ControlUp 4.1–The Master Systems Display for your Virtual Environment

One thing I have always liked about the Engineering section from Star Trek: The Next Generation was the Master Systems Display.  This large display, which was found on the ship’s bridge in later series, contained a cutaway of the ship that showed a detailed overview of the operational status of the ship’s various systems.


The Master Systems display from Star Trek Voyager. Linked from Memory Alpha.

Although the Master Systems Display is fictional, the idea of having one place to look to get the current status of all your systems can be very appealing.  This is especially true in a multi-user or multi-tenant environment where you need to quickly identify the systems and/or processes that are not performing optimally.  And this information needs to be displayed in a way that makes it easy to understand while providing administrators with a way to dig deeper if they need to. 

Some tools with these functions already exist in the network space.  They can give a nice graphical layout of the network, and they can show how heavily a link is being utilized by changing the color based on bandwidth utilization.  PHP Weathermap is FOSS example of a product in this space.

ControlUp 4.1 is the latest version of a similar tool in the systems management space.  Although it doesn’t provide a graphical map of where my systems might be residing, it provides a nice, easy to read list of my systems and a grid with their current status, a number of important metrics that are monitored, and the ability to dive down deeper to view child items such as virtual machines in a cluster or running processes on a Windows OS.

image
The ControlUp Management Console showing a host in my home lab with all VMs on that host. The Stress Level column and color-coding of potential problems make it easy to identify trouble spots.  Servers that can’t run the agent won’t pull all stats.

So why make the comparison to the Master Systems Display from Star Trek?  If you look in the screenshot above, not only do I see my ESXi host stats, but I can quickly see that host’s VMs on the same screen.  I can see where my trouble spots are and how it contributes to the overall health of the system it is running on.

What Is ControlUp?

ControlUp is a monitoring and management platform designed primarily for multi-user environments.  It was originally designed to monitor RDSH and XenApp environments, and over the years it has been extended to include generic Windows servers, vSphere, and now Horizon View.

ControlUp is an agent-based monitoring system for Windows, and the agent is an extremely lightweight application that can be installed permanently as a Windows Service or be configured to be uninstalled when an admin user closes the administrative console.  ControlUp also has a watchdog service that can be installed on a server that will collect metrics and handle alerting should all running instances of a console be closed.

One component that you will notice is missing from the ControlUp requirements list is a database of any sort.  ControlUp does not use a database to store historical metrics, nor is this information stored out “in the cloud.” This design decision is a double-edged sword – it makes it very easy to set up a monitoring environment, but viewing historical data and trending based on past usage aren’t integrated into the product in the same way that they are in other monitoring platforms.

That’s not to say that these capabilities don’t exist in the product.  They do – but it is in a completely different manner.  ControlUp does allow for scheduled exports of monitoring data to the file system, and these exported files can be consumed by a trending analysis component.  There are pros and cons to this approach, but I don’t want to spend too much time on this particular design choice as it would detract from the benefits of the program.

What I will say is this, though – ControlUp provides a great immediate view of the status of your systems, and it can supplement any other monitoring system out there.  The other system can handle long-term historical, trending, analysis, etc, and ControlUp can handle the immediate picture.

How It Works

As I mentioned above, ControlUp is an agent-based monitoring package.  That agent can be pushed to the monitored system from the management console or downloaded and installed manually.  I needed to take both approaches at times as a few of my servers would not take a push installation.  That seems to have gotten better with the more recent editions.

The ControlUp Agent polls a number of different metrics from the host or virtual machine – everything from CPU and RAM usage to the per-session details and processes for each logged-in user.  This also includes any service accounts that might be running services on the host. 

If your machines are VMs on vSphere, you can configure ControlUp to connect to vCenter to pull statistics.  It will match up the statistics that are taken from inside the VM with those taken from vCenter and present them side-by-side, so administrators will be able to see the Windows CPU usage stats, the vCenter CPU usage stats, and the CPU Ready stats next to each other when trying to troubleshoot an issue.

image
Grid showing active user and service account, number of computers that they’re logged into, and system resources that the accounts are utilizing.

For VDI and RDSH-based end-user environments, ControlUp will also track session statistics.  This includes everything from how much CPU and RAM the user is consuming in the session to how long it took them to log in and the client they’re connecting from.  In Horizon environments, this will include a breakdown of how long it took each part of the user profile to load. 

image
Grid showing a user session with the load times of the various profile components and other information.

The statistics that are collected are used to calculate a “stress level.”  This shows how hard the system is working, and it will highlight the statistics that should be watched closer or are dangerously high.  Any statistics that are moderately high or in the warning zone will show up in the grid as yellow, and anything that is dangerously high will be colored red.  This combination gives administrators a quick summary of the machine’s health and uses color effectively to call out the statistics that help give it the health warning that the machine has received.

image
Not only can I see that the 1st server may have some performance issues, but the color coding immediately calls out why.  In this case – the server is utilizing over 80% of its available RAM.

Configuration Management

One other nice feature of ControlUp is that it can do some configuration comparison and management.  Say I have a group of eight application servers, and they all run the same application.  If I need to deploy a registry key, or change a service from disabled to automatic, I would normally need to use PowerShell, Group Policy, and/or manually touch all eight servers in order to make the change.

The ControlUp Management Console allows an administrator to compare settings on a group of servers – such as a registry key – and then make that change across the entire group in one batch. 

In my lab, I don’t have much of a use for this feature.  However, I can definitely see the use case for it in large environments where there are multiple servers serving the same role within the environment.  It can also be helpful for administrators who don’t know PowerShell or have to make changes across multiple versions of Windows where PowerShell may not be present.

Conclusion

As I stated in my opening, I liken ControlUp to that master systems display.  I think that this system gives a good picture of the immediate health of an environment, but it also provides enough tools to drill down to identify issues.

Due to how it handles historical data and trending, I think that ControlUp needs to be used in conjunction with another monitoring system.  I don’t think that should dissuade anyone from looking at it, though, as the operational visibility benefits outweigh having to implement a second system.

If you want more information on ControlUp, you can find it on their website at http://www.controlup.com/

End-User Computing PodCast–Market Research

Back in December, I started kicking around the idea of doing a podcast focused on virtual end-user computing topics.  I wanted to do a little market research to gauge community interest in the idea.

I’ve put together a simple survey to gauge interest in the topic, and I would love to get your feedback.

https://docs.google.com/forms/d/12N7cAiGptfQ6E70wSA1jGdfSYLovydjuQAyuwYhD0kg/viewform?usp=send_form

If you have any questions, please feel free to reach out to me using the email link on the top of the page or by sending a message to @seanpmassey on Twitter.

Time to participate in the Project VRC "State of the VDI and SBC union 2015" survey

The independent R&D project ‘Virtual Reality Check’ (VRC) (www.projectvrc.com) was started in early 2009 by Ruben Spruijt (@rspruijt) and Jeroen van de Kamp (@thejeroen) and focuses on research in the desktop and application virtualization market. Several white papers with Login VSI (www.loginvsi.com) test results were published about the performance and best practices of different hypervisors, Microsoft Office versions, application virtualization solutions, Windows Operating Systems in server hosted desktop solutions and the impact of antivirus.

In 2013 and early 2014, Project VRC released the annual ‘State of the VDI and SBC union’ community survey (download for free at www.projectvrc.com/white-papers). Over 1300 people participated. The results of this independent and truly unique survey have provided many new insights into the usage of desktop virtualization around the world.

This year Project VRC would like to repeat this survey to see how our industry has changed and to take a look at the future of Virtual Desktop Infrastructures and Server Based Computing in 2015. To do this they need your help again. Everyone who is involved in building or maintaining VDI or SBC environments is invited to participate in this survey. Also if you participated in the previous two editions.

The questions of this survey are both functional and technical and range from “What are the most important design goals set for this environment”, to “Which storage is used”, to “How are the VM’s configured”. The 2015 VRC survey will only take 10 minutes of your time.

The success of the survey will be determined by the amount of the responses, but also by the quality of these responses. This led Project VRC to the conclusion that they should stay away from giving away iPads or other price draws for survey participants. Instead, they opted for the following strategy: only survey participants will receive the exclusive overview report with all results immediately after the survey closes.

The survey will be closed February 15th this year. I really hope you want to participate and enjoy the official Project VRC “State of the VDI and SBC union 2015” survey!

Visit www.projectvrc.com/blog/23-project-vrc-state-of-the-vdi-and-sbc-union-2015-survey to fill out the Project Virtual Reality Check “State of the VDI and SBC Union 2014” survey.

Writing for Virtualization Review – My 2nd Gig

In my end of the year wrap-up post, I teased that there would be an announcement coming early in January.   Now that it’s early January, I can let the cat out of the bag.

Starting this month, I will writing a twice-per-month column called Sean’s Virtual Desktop in Virtualization Review.  My plan is to write about VDI and to do how-to type articles like the Horizon View series that I’ve done on this blog.

My first article, Pets and Cattle in Virtual End User Computing, should be up sometime in the next day or two.

Edit: The article is now up, and it can be viewed here.

Follow

Get every new post delivered to your Inbox.

Join 108 other followers