Virtualization for MOSS (SharePoint 2007): Sort of. Maybe. Some Day
August 12, 2008
Ketaanhs wrote “What Is the Support for Virtualization for MOSS (SharePoint 2007)? You can read the full post on MSDN Web logs here. First, the good news. Mr. Ketaanhs provides links to hard-to-find Microsoft documentation about virtualization; for example, KB897615 which explains a gotcha for everyone but premier support buyers. He has also scoured these fine expository documents for crucial SharePoint virtualization information. So, if you are a lucky MOSS licensee and want to use virtualization to maximize your “scale up and scale out” investments, jump to MSDN and download these files.
Second, the bad news. There is no solid information about support of virtualization in SharePoint 2007. There’s speculation, and Mr. Ketaanhs writes:
So currently as of Aug 08th 2008 we are awaiting an Official statement to come out in few weeks, until then I *assume* Microsoft Support may provide Commercial Reasonable Support.
Virtualization is one of the hot trends in server rooms. With upwards of 65 million SharePoint users, some of those IT managers would like to virtualize, squeeze more mileage from their hardware, and increase the performance of SharePoint when it processes documents, performs queries, and generates those tasty Web 2.0-style interfaces.
In my opinion, Microsoft continues with some of its pre-Ozzie code synchronization policies. Microsoft marketers hype virtualization and cook up zippy new product names like Hyper-V. Licensees, on the other hand, don’t have what they need to do substantive quarterly planning. Not good.
Stephen Arnold, August 12, 2008
Comments
3 Responses to “Virtualization for MOSS (SharePoint 2007): Sort of. Maybe. Some Day”
-
- Subscribe to Beyond Search
Feature archive
News archive
-
One word – vmware
Brain Long,
Brevity is the soul of wit.
Stephen Arnold, August 12, 2008
Just a word of advice – SharePoint 2007 on VMWare in a multi-domain environment has major issues. Authentication from the non-installed domains is lost for no apparent reason, and the only solution is to restore. This is a real nightmare – avoid this installation scenario on VMWare.