The answer depends on each individual deployment, but no matter the use case, admins will have to work with legacy hardware and consider new devices to support a virtual desktop initiative. From laptops to mobile to thin-client, there are plenty of end user platforms supported by VMware Horizon View.
Desktop as a Service (DaaS), which delivers virtual desktop infrastructure from a cloud provider, allows devices other than PCs to access fully featured desktops that are hosted in the data center. Because servers do all the heavy lifting, these client devices don’t need to be particularly powerful, enabling a new wave of BYOD confusion and excitement, as well as the opportunity for capital expense reduction through less expensive client devices.
There are several options for virtual desktop pools in Horizon View that will change how administrators manage desktops and how users interact with them. There are three main pool types and two assignment types to choose from.
Desktop Pool Types
Unless you’re working with Microsoft Terminal Services machines (in which case you’ll choose Terminal Services pools to allow terminal servers to be treated as Horizon desktops), either migrating or using them alongside Horizon desktops, you’ll select from automatic or manual desktop pools.
There are myriad ways to bill colocation customers, making a comparison between multiple bids an occasionally daunting process. The industry does seem to be shifting towards an accepted standard billing model based on metered electricity use, but older billing methods based on footprint and telecom connections are still in play.
This can make it difficult to compare bids based on different models. What are the distinctions in colocation pricing models and what is the fairest method for customers and providers alike?
Happy Earth Day! As we reflect on environmental impact, let’s take a look at some solid data to see how much energy and carbon dioxide emissions are really saved by data center energy efficiency and renewable energy use. The recent memo from the Greed Grid reintroducing their metrics for data center efficiency provides a great jumping off point to estimate the environmental impact of an average data center.
With recent headlines like Apple’s shift towards renewables and Google’s funding of wind farms, not to mention our own efforts at Green House Data to improve efficiency and overall Power Usage Effectiveness (PUE), many in the data center industry are curious about the actual data at hand. If a company improves 2% of its overall carbon footprint through efficient or renewably powered data centers, what does that actually mean? Is it a large impact or just a PR opportunity?
We took a theoretical 10 MW facility and assumed it was operating at capacity for simplicity of math and comparison. We measured this facility’s emissions at 1.8 and 1.2 PUE to see how improving operations and data center location would each affect emissions.
What is Heartbleed?
This vulnerability takes advantage of a memory configuration within the ever-popular OpenSSL software library. The TLS heartbeat extension (RFC 6520) on an exploited version of OpenSSL allows an attacker to view up to 64k of what is in memory with each “heartbeat.” Thus, a multitude of information can be obtained unnoticed. It is important to note that this exploit is found in OpenSSL's implementation of SSL/TLS, not within the TLS protocol itself.
How does this affect Green House Data's services?
We are actively pursuing efforts to mitigate any presence of vulnerable systems within Green House Data's cloud infrastructure. From what we have seen so far, these efforts are primarily focused on systems using OpenSSL to encrypt TLS connections. Green House Data provides service and customer portals that use SSL and have taken the necessary actions to secure our systems.
What steps can be taken to fix this?