Showing posts with label hyper-v. Show all posts
Showing posts with label hyper-v. Show all posts

Friday, April 5, 2013

What are the practical limits of Windows Multipoint Server?

One of our favorite vendors (hint: starts with an H and ends with a P) recently discontinued a popular line of specifically designed hardware components for Windows MultiPoint server. This included both the Multi-seat server and Zero Client components.

We were very surprised and a bit disappointed!

I called to speak with the HP product champion at our distributor and was told that although the product had been quite popular, the overly optimistic hardware specifications published by Microsoft had caused the unraveling of the product line. Apparently there were too many schools out there attempting to install the maximum allowed zero clients onto an underpowered server at a ratio of 20:1.

And when the system (with 20 students trying to do online gaming) slowed to a crawl, the buyers got upset. Go figure…

As one wise military commander told me many years ago at Officer Training, when asked about the wisdom of doing a particular thing; “You can, but you may not”. This pretty much sums up the wisdom of the aforementioned scenario. Perhaps it is better stated that while you CAN attach 20 Zero Clients onto a modestly provisioned MultiPoint Server, you may in fact not WANT to do so.

For the record, MultiPoint, as of this writing is not going away. Nor has it been an unsuccessful new product, not by a long-shot. It is working very well in the schools we have installed it when a reasonable effort to design the system has been employed.
And not to worry, there are still plenty of vendors supporting the technology and the required Zero Clients that are required to easily roll it out. But you may want to curb your optimism just slightly as you do system design and engineering. A reasonable allocation of server resources, client connections, and bandwidth utilization will help you make MultiPoint the home run in your school.

Here are three specific suggestions that will ensure your project does not get bogged down:
  1. Determine the purpose of the MultiPoint installation
  2. Start with a properly specified server
  3. Calculate the Server/Client Ratio conservatively
Determine the purpose of the MultiPoint Installation
 
There are widely divergent requirements for a MultiPoint installation. Some are managed with the strict control of a well-organized teacher leading a discussion and managing the student sessions. Others are a free-for-all student study hall where anything goes. And on occasion (at least a few times each year) there will be standardized student testing where workstations are configured precisely for a sterile testing environment.
 
As you design you MultiPoint installation, start with the designated purpose. And if you can’t ensure that designated purpose then design conservatively. You will be happier in the long-run (although your financial managers may not share your entusiasm).
 
In our rather unscientific, but thorough testing, we have found that a ratio of 5:1 with a reasonable MultiPoint Server is a very solid place to start. And on the upper end of the scale, we have found that exceeding 10:1 under most conditions is not going to deliver the needed performance for anything more than casual web-browsing.
 
Start with a properly specified server
 
It has been said that “Common sense is not so common”. But it makes sense in this scenario to have a Multi Core processer (more is better), as much RAM as you can afford, and a fast Hard Drive with at least 500GB of space. Additionally, the server needs to have the capability for rendering graphics. This is normally accomplished by installing a graphics card in one of the open slots if it is not built into the mains system board.
 
And while there are many different connection configurations for MultiPoint, we have had the best luck using USB. Accordingly, you will need to have as many USB ports on the server as you plan to have zero-clients. This might require you to purchase a USB card and install it in your server.
 
Some manufacturers design servers specifically for the MultiPoint Server Operating System, but a bare box system is fine. Other than what is mentioned above, there is nothing special about hardware required to run MultiPoint. If it will run Windows7 or Windows Server 2012 standard, it should work fine with MultiPoint Server.
 
Calculate the Client Server Ratio Conservatively
 
The ratio of clients to a single server is the last thing you should determine. We simply call it the client/server ratio. Microsoft advertises a ratio of 10:1 in Windows MultiPoint Standard and 20:1 in Windows MultiPoint Premium. With few exceptions these numbers are (characteristically) hype.
 
For hard core computer lab workstations, keep the ratios low. For occasional browsing of the library collection or standardized testing increase the ratios accordingly.
 
One other aspect of determining ratios is the simple matter of logistics or layout. Depending on how the rows or clusters of workstations are configured in your lab, you may need to adjust your ratios purely based upon space and distance. The USB cables included in the HP Zero Clients were 25’ long. Distances greater than that may not work well. Check with your specific vendor for the lengths of included cabling (if included).
 
Summary
 
Windows MultiPoint Server is a great technology that will dramatically reduce the cost of provisioning a computer lab at your school. Not only do you save tons in buying hardware, but you nearly eliminate one of the more costly components of your technology budget - technical support. And you will see a commensurate reduction in both electrical and heating/cooling costs.
 
You will also have a much, much quieter computer lab (not counting student noise!).
 
But don’t be ridiculous, while you CAN connect 20 clients to a single MultiPoint server, you MAY NOT have a good experience in doing so. Good advice for me back then and for you today…
 
If you need assistance in designing your MultiPoint Server project, give us a call.

Friday, May 25, 2012

Virtualization - Part 3: Solving the Computer Lab Conundrum

In the two previous articles we explored the concept of Shared Resource Computing, termed virtualization, and described a few ways to deploy virtual machines in your school. Let’s get a little more practical and focus on the benefits of using virtualization in your computer lab.
A computer lab is the one common denominator in virtually (there goes another pun) every school we have managed.  Computer labs come in all sizes, shapes, and conditions. Although universal in usage, they vary widely in functionality, ranging from a collection of mostly broken, outdated computers donated to you after the end of their useful life to a collection of brand new ‘out of the box’ desktops.

Regardless of circumstance, there seems to be 5 universal challenges associated with computer labs:
  1. Cost to acquire the hardware, network, and installation
  2. Cost to maintain the high usage in a semi-hostile environment
  3. Noise and heat levels that can distract students
  4. Distractions of an endless variety  (as in the internet) during instruction
  5. Consistent computing environment, especially during testing
Managing your computer lab may in fact be the most time consuming technical support requirement in your school. That tends to be the case in schools with higher grade levels (see my previous article about managing computers in a hostile environment). So in addition to reducing upfront costs, reducing ongoing costs will also be of great benefit.
 
There are many virtualization solutions available that address computer desktops (as opposed to servers), but don’t invest a lot of time exploring them.  In my view there is only one solution that adequately addresses the specific challenges associated with the computer lab in education.
 
That solution is Windows MultiPoint Server 2011, a computer operating system designed specifically for the computer lab at your school. It is the only solution that addresses the above listed challenges completely.
 
Let’s look at each one:
 
  1. The cost savings experienced is directly proportional to the number of multi seat sessions you provision per server. We have tested 5:1 (five computing session to one server), but Microsoft advertises up to 20:1. Even at 10:1 you are only buying a fraction of the computer hardware.
  2. There are no moving parts in the T200 Zero Clients we recommend, no hard drives, cooling fans, disk caddies, etc. Far fewer parts require far fewer repairs. Your administrative costs for the lab will plummet.
  3. Put 25 – 30 computers in an average sized room and you are going to have heating and cooling issues. And the noise level of that environment has never been conducive to instruction and learning.
  4. Having tried to instruct adults in technology training with the internet staring them in the face is a challenge. With kids it is nigh unto impossible. With MultiPoint Manager you control access to the internet, and point all computing sessions at once to where you want the students to go.
  5. Testing preparation becomes a breeze. You simply sign in differently on testing day and the students are presented with a sterile testing environment, with appropriate controls in place to insure testing integrity.
A worldwide study conducted by Forrester Research concluded the following with respect to Microsoft MultiPoint Server technology:
 
  • Teachers and students report that using a Windows MultiPoint Server 2011 station is as good, in terms of speed and performance, as if they were working on a traditional personal computer. 
  • Overall student energy and enthusiasm is boosted when more students have a modern computing station to work on, instead of sharing an older machine and dated operating system amongst their classmates or having no computer access in the classroom at all.
  • Teachers very much appreciate the administration and monitoring capabilities of the new MultiPoint Manager, with which they can direct and control class and individual students' lessons more effectively. The console is reported to be easy to learn, even for non-English speaking and non-technical instructors. 
  • A Windows MultiPoint Server 2011 system is relatively easy to set up and deploy, according to interviewees. This is especially valuable for schools in remote areas where IT skills are scarce.
  • Power cost reductions are important in the many areas of the world where electricity is a large line item in the school's budget — assuming it is available. 
  • The overall cost savings compared to a traditional PC environment is substantial and analyses of these costs comprise the bulk of this study.  All schools reported being able to re-allocate these savings to other assets for enhancing the education of their students.
So there you have it. A three part series about what you need to know regarding Virtualization. For most of you, the sweet spot will be your computer lab(s). Using virtualization will reduce both the initial and ongoing costs of the computer lab, improve the learning environment, and simplify life for your teachers.

And I will virtually guaranteed (my final pun) you will love it. Our early adopters are already coming back for more.

One final note; in order to use MultiPoint Server 2011, you will need to address your Microsoft software licensing. See my earlier article about this subject.  After all, you don’t expect Microsoft to allow creation of all those virtual computers without licensing them!

Friday, May 18, 2012

Virtualization - Part 2: Which Virtualization Solution Should I Use

Wading through the vast array of virtualization solutions is a challenge and frankly it will mostly be a waste of your time, until you focus on a specific solution needed for your school. I emphasize “specific”, because sometimes the process associated with the high tech virtualization strategy is a very low-tech and practical need to just get something done without an army of Network Engineers and a couple of hours on the phone with technical support.
You can virtualize servers, if you have a need to either consolidate physical hardware or add another server for a specific application. You can virtualize desktops and launch them in thin client sessions to create a sterile computer lab environment (such as required for testing). Or, you might want to use virtualization as part of your backup strategy for mission critical applications, such as computers running your financial software.
Whatever your circumstances, be sure you have a solid business case for implementing a virtualization strategy. Don’t get sucked into the IT department’s love affair with virtualization without a compelling solution attached to it. The one certainty about virtualization is that it will virtually guarantee (another intended pun), that your IT team will be on the payroll for as long as you keep that virtualized environment in place. This is a pretty complex solution, even for those of us in the business.
Here are three very specific examples of where we have used virtualization to the benefit of our school partner:
VoIP Management Server: Due to growing pains, one of our schools needed to setup a remote administration office to accommodate temporary office space during new facility construction. They did not want to spend on infrastructure that would be replaced within a year, and space was very limited.
The VoIP system they setup for the temporary offices required a server for the call manager (PBX functionality).
Using Microsoft Hyper-V technology, we created a VM (Virtual Machine) which had the sole purpose of running the call manager software. There were specific system requirements that differed from the configuration of the host server, otherwise we would not have needed a VM in the first place.
It ran flawlessly for the period of about 24 months (ever heard of construction delays) and then we decommissioned that VM and moved to the new facilities. Mission accomplished.
The business case for this virtualization was temporary computing requirements with the least amount spent on hardware, software, and electricity.
Server Migration: A rather old and inefficient server at partner school needed replacing. Simple enough, right? Well yes, except the school financial system was installed on this server and the orders were to not to interrupt it. It also did after hours synchronizing with a district system, which required point in time coordination.
Quick is not something that can be guaranteed with a single network engineer managing an entire school on one day per week (our model). So we employed a virtualization strategy.
The solution was to configure a VM and work through all of the network connection issues, configuration, and testing. Then at a pre-appointed time we quickly took a snap-shot (image) of the operating server and virtualized it. This VM then ran for a period of several weeks giving us plenty of time to install and configure the new physical server, without pressue on our part or interruption on theirs.
Why did we not simply keep running the financial system as a virtual machine? Good question, although it could have in theory been easily done. There were ownership (as in the district’s property) and licensing issues that drove the decision.
The business case for this virtualization was a time critical server migration. Not just the length of time it took, but the point(s) in time requirement as well.
Computer Lab:  A thoroughly trashed computer lab at one of our partner schools needed replacing, but budgets were very tight. We needed to find a way to refurbish/replace the computer lab for well under $10, 000 with the specific requirement to make them easy to use for state mandated testing.
If you read between the lines, what the administrator was trying to avoid was that very stressful “day of testing” computer problem nightmare you have all experienced.
Our virtualization solution in this situation was Windows MultiPoint server connected by HP Zero Clients. Using MultiPoint server, we were able to reduce the cost of the lab by 75% (we set up in a conservative 5 – 1 ratio) and provide a sterile computing environment on testing day.
The setup was easy, because MultiPoint Server 2011 is designed specifically to recognize and configure the HP Zero Clients. And after downloading the states thin client setup utility, we were able to quickly boot into a “Sterile” testing environment. That is where all computer sessions are identical, locked down, ready for testing, and capable of being administered by a proctor.
The business case for this virtualization was not only cost, but in delivering a sterile computing environment, (as we defined above).
Summary
Virtualization is a mature and well adopted technology used worldwide in a variety of circumstances. It may indeed be appropriate for you to consider. Before doing so, identify a specific computing problem and desired outcomes and a budget before calling your IT provider.
Hopefully your IT provider is wise enough to guide you in selecting your virtualization strategy, software provider, and configuration to accommodate your business case. And if you have a requirements for a temporary, time critical, or specific computing environment; then virtualization is likely a good choice.
And that’s virtually all I have to say about it… until next week. We’ll look a little deeper at virtualizing your computer lab.