Microsoft

Supported command line options for the Microsoft App-V 4.5 Management Server installer

2010-08-19T15:13:00Z

Here is a overview of all the supported command line options in App-V.

The table describes the Microsoft Application Virtualization (also known as App-V), command-line parameters that are available for the Microsoft App-V 4.5 Management Server.

Parameter	Value(s)	Description
OPTIN	True\False	Configures the MU optin.
USERNAME		String value that specifies the user name who is performing the install.
COMPANYNAME		String value that specifies the company name that owns the system.
ADDLOCAL	Release_SoftGrid_Server, Release_AppVirt_Vss_Writer, Release_SoftGrid_Management_Console, Release_SoftGrid_Mgmt_Web_Service	A comma separated list of the App-V Server options that you want to install on the system.
DB_HOST		String value that specifies the hostname of the SQL Server system.
DB_SERVICE		String value that specifies the database on the SQL Server system that is going to be created or used.
DB_PORT	1433	Numeric value that specifies the SQL Server remote connection port number.
SWICERTHASH		String value that specifies the certificate thumbprint for the certificate that is installed on the system.
SWISERVERRTSPPORT	554/322	Numeric value that specifies the RTSP(S) port number on the server.
SWIADMINGROUP		String value that specifies the Admin Group for the server.
SWIUSERGROUP		String value that specifies the User Group for the Default Provider Policy.
SWIDOMAINNAME		String value that specifies the domain name from which the Admin and User groups mentioned above belong to.
SWICONTENTDIR		String value that specifies the content directory for the server.
INSTALLDIR		String value that specifies the installation directory for the server.

As an example, the following sample command line installs the Management Server using all the command line options mentioned above:

msiexec /i "setup.msi" /qn /l*vx %temp%\serverinstall.txt OPTIN="true" USERNAME="UserJim" COMPANYNAME="Contoso" ADDLOCAL="Release_SoftGrid_Server,Release_AppVirt_Vss_Writer,Release_SoftGrid_Management_Console,Release_SoftGrid_Mgmt_Web_Service" DB_HOST="MySQLServer" DB_SERVICE="MySQLDatabase" DB_PORT="1433" SWICERTHASH="1A7E958464C90DABC1232372538A83624600E276" SWISERVERRTSPPORT="322" SWIDOMAINNAME="corp.contoso.com" SWIADMINGROUP="MyAppVAdminGroup" SWIUSERGROUP="MyAppVUserGroup" SWICONTENTDIR="c:\program files\Microsoft System Center App Virt Management Server\App Virt Management Server\content\" INSTALLDIR="C:\Program Files\Microsoft System Center App Virt Management Server\"

Source: kb2384955

Configuration Manager v.Next Beta 1 now on VHD Test Drive Program

2010-08-18T07:42:08Z

Microsoft has now have released a fully configured virtual machine for ConfigMgr v.Next Beta 1. Based on a Windows Server 2008 R2 x64 OS, this is a fully built virtual machine ready to import into your Hyper-V environments.

This is something the ConfigMgr team over at Microsoft has done for a few major releases, starting back at the ConfigMgr 2007 RTM timeframes. Now you to can help and evaluate the latest and greatest ConfigMgr v.Next release. Microsoft is also in the process of uploading the hands on labs for ConfigMgr v.Next.

Here are some resources for you:

VHD Test Drive - System Center Configuration Manager v.Next on Windows Server 2008 R2 – link
VHD Test Drive - System Center Configuration Manager 2007 R2 - link
Configuration Manager vNext Beta 1 evaluation download – link

A sneak peak of Microsoft MED-V 2.0

2010-08-12T19:19:34Z

Microsoft Enterprise Desktop Virtualization (MEDV) provides companies with a way to provide virtual machines to end users that are managed centrally. It helps solve application compatibility problems - you can give users a virtual machine with their legacy apps, and the apps appear to run seamlessly side by side with other apps on their Windows 7 desktop.
The MEDV team is working hard on a new version, here is a sneak preview of the next version of MED-V.

Problems viewing the video? click here

You can find out more about MEDV at http://www.microsoft.com/medv

Microsoft releases RD Gateway Capacity Planning in Windows Server 2008 R2

2010-08-04T10:44:55Z

Microsoft today announced the availability of The RD Gateway Capacity Planning in Windows Server 2008 R2.
The document contains scalability results, testing methodologies, analysis, and guidelines for RD Gateway. It describes the most relevant factors that influence the capacity of a given deployment, methodologies to evaluate capacity for specific deployments, and a set of experimental results for different combinations of usage scenarios and hardware configurations.

Click here to download

Linux Integration Services v2.1 for Windows Server 2008 Hyper-V R2 now available for download

2010-07-30T09:42:21Z

When installed in a supported Linux virtual machine running on Hyper-V, the Linux Integration Components provide.

Driver support for synthetic devices: The Linux integration components include support for both the synthetic network controller and synthetic storage controller that have been developed specifically for Hyper-V. These components take advantage of the new high-speed bus, VMBus, which was developed for Hyper-V.

Fastpath Boot Support: Boot devices now take advantage of the storage VSC to provide enhanced performance.
Timesync: The clock inside the virtual machine will remain synchronized with the clock on the host.
Integrated Shutdown: Virtual machines running Linux can be shut down from either Hyper-V Manager or System Center Virtual Machine Manager, using the “Shut Down” command.
Symmetric Multi-Processing (SMP) Support: Supported Linux distributions can use up to 4 virtual processors (VP) per virtual machine.
Heartbeat: Allows the host to detect whether the guest is running and responsive.
Pluggable Time Source: A pluggable clock source module is included to provide a more accurate time source to the guest.

Supported Operating Systems:
Hyper-V Server 2008; Windows Server 2008; Windows Server 2008 R2

Windows Server 2008 with Hyper-V RTM Update (KB950050) applied
Microsoft Hyper-V Server 2008
Windows Server 2008 R2 Hyper-V RTM
Microsoft Hyper-V Server 2008 R2 RTM

Click here to download and learn more

Installing Service Pack 1 on Microsoft Hyper-V Server 2008 R2

2010-07-27T10:41:52Z

With the release of Beta of Service Pack 1 for Windows Server 2008 R2 a number of you have asked about Service Pack 1 for the standalone Microsoft Hyper-V Server 2008 R2, and whether the new capabilities of Dynamic Memory and RemoteFX will be available for it. Absolutely, both Dynamic Memory and RemoteFX have been developed for Microsoft Hyper-V Server 2008 R2 as well.

In order to get these capabilities for the Microsoft Hyper-V Server 2008 R2, you will need to install the Beta of Service Pack 1 on Microsoft Hyper-V Server 2008 R2. Note that the first wave of the Service pack installer is only in 5 languages (English, French, German, Japanese and Spanish), so if you try and apply the package to Microsoft Hyper-V Server 2008 R2 (which has 11 language packs installed by default) you will rightly see the following screen

It’s pretty simple to uninstall these language packs to thereafter install the Service pack. In order to uninstall the language packs, there is nifty utility included (lpksetup.exe). Launch this from an administrator’s command prompt and select “Uninstall display languages”.

Click here to read more

A collection of Microsoft Hyper-V Tools

2010-07-20T19:14:41Z

Here is a list of good Hyper-V Tools. Some of them also gives you the ability to use them with Citrix XenServer, since they are based on the VHD image format.

Wim2VHD

Creates a Windows Server 2008/Vista/Win7 VHD from media in 5 minutes.

VHDtool

Command-line tool for VHD manipulation including instant creation of large fixed-size VHDs

Hyper-V PowerShell library

PowerShell Library for Hyper-V, simplify Hyper-V scripting

CoreConfigurator

Server Core/Hyper-V Server configuration interface

Hvremote

Configures servers and clients for remote management of Hyper-V in both workgroup and domain environments

nvspbind

Tool for modifying network bindings from the command line

nvspscrub

Tool for removing Hyper-V Virtual Networking Configuration from the parent partition

BootfromUSB-HVS

Simplify the creation of bootable Hyper-V Server USB drives

VM Migration Test Wizard

Discovers which hosts need the "Enable Processor compat" option for Live Migration

A guide to App-V publishing and streaming using IIS

2010-06-22T11:04:31Z

From an App-V point of view, this deployment method is not too complicated, but there are some aspects that have the potential to cause confusion in the community and with this I hope to avoid the confusion and hopefully, one can test, play and deploy this method with confidence.

In this article, we will discuss the following:

The configuration of IIS

- The installation of IIS

- The creation of the virtual directory

- The MIME types

The creation and configuration of the Publishing Document

- How HTTP streaming works with App-V and how we use and create the Publishing Document

- Testing the Publishing Document

The configuration of the App-V Client

- The configuration of the HTTP server

- The configuration of the App-V client settings

- More information

For the creation of this document, I have used a Windows Server 2008 R2 machine with Internet Information Services 7.5 and a Windows 7 client with App-V for Windows Desktops 4.6 x64.

The configuration of IIS

The configuration of the IIS server is not that complicated for use with App-V; however, there are some things we should keep in mind.

The installation of IIS

When installing IIS for App-V, we should make sure the following role components are installed:

· Common HTTP Features – ALL except HTTP redirection

· Application Development – ALL

· Health and Diagnostics – HTTP logging and Request Monitor only

· Application Development – ALL

· IIS 6 Management Compatibility – ALL

· Security – ALL authentication options

· Management Tools – ALL

The creation of the virtual directory

A virtual directory in IIS must be created in order to represent the App-V content share that contains all application packages. The virtual directory has to be pointed to the location where the content share is. The content share should be configured as a default file share. For the virtual directory, the default settings can be maintained, but make sure that the virtual directory is located under the default website and that Directory Browsing and Read are checked.

The MIME types

In IIS, we have to configure a couple of MIME types to make sure we can handle the App-V files properly. Below is a summary of these MIME types:

The creation and configuration of the Publishing Document

Whether HTTP Publishing and Streaming works or fails depends mostly on the Publishing Document. The Publishing Document is an .aspx page to which the App-V client connects to send its request for applications (icons, FTA’s etc.). If the Publishing Document is not functioning properly for any reason, the clients will not be able to connect and the App-V applications will not work. There are several methods to create a proper Publishing Document, some of them are easy and some complicated and some of them are suited for quick tests and some not.

We can create a Publishing Document manually, which is a good one for testing purposes. However, when we are looking for a larger deployment, we would not be happy to process each application package manually. This would also be prone to errors and it would require manual modification when a new package is deployed to the environment. Because this is not desired, we can also use more complicated ways to achieve our goal, making our lives much easier in the end by creating your Publishing Document automatically.

How HTTP streaming works with App-V and how we use and create the Publishing Document

When we deploy App-V with Management or Streaming servers, the App-V clients are configured to point to the App-V server, which handles their request. When we only use IIS for the publishing and streaming of App-V applications, we need to have a slightly different approach.

From a client perspective, we do not have to do much, except configuring it to point to a HTTP server and configure some settings. However, from the IIS point of view, we should understand some things before we can implement this properly.

When the App-V client performs a Desktop Configuration Refresh (DC Refresh), it sends a request to the IIS server. With this request, the client is asking what applications are available, and where icons should be placed and whether this application has File Type Associations (FTA’s). The client needs to receive this information in XML format.

Therefore, in order for the client to get all information properly, we have to make sure that this information is accurately available on the IIS server. In order to achieve this, we have to make a Publishing Document. This Publishing Document is an .aspx file that is located in the root of the content directory. The client needs to be pointed to this page in order to work, but this will be discussed later on. This Publishing Document needs to contain information about the Desktop Configuration, which includes (but is not limited to) the Refresh Settings, the Refresh Interval, Reporting Settings and of course, the Applist.

Click here to read the full blog post from Microsoft

Windows 7 Application Virtualization 4.5 SP2 Released

2010-05-31T09:08:20Z

Although customers can already download version 4.6 of Microsoft Application Virtualization, Microsoft is now offering for download the second major upgrade to its predecessor. Application Virtualization (App-V) 4.5 Service Pack 2 (SP2) is now available through the Microsoft Download Center, bringing to the table the latest updates to App-V 4.5. The main changes highlighted by the software giant for the evolution of App-V 4.5 with the release of SP2 involve virtualization support of Office 2010 and of SQL Mirroring.

“This service pack provides the latest updates to Microsoft Application Virtualization 4.5. Because Microsoft Application Virtualization service packs are cumulative, you do not have to install Service Pack 1 before you install Service Pack 2. Service Pack 2 includes all of the fixes that were included in Service Pack 1,” Microsoft revealed.

As was the case with previous App-V releases, Service Pack 2 for v4.5 is available immediately to Microsoft Desktop Optimization Pack (MDOP) customers. App-V 4.5 SP2 can be downloaded through the Microsoft Volume Licensing Site (MVLS), but is also available to MSDN and TechNet subscribers. Of course, customers already running App-V 4.5 can simply deploy SP2 via Microsoft Update.

Microsoft Application Virtualization (App-V) with Windows 7, Windows Server, and Office 2010 delivers a seamless user experience, streamlined application deployment and simplified application management. App-V helps transform applications into centrally managed virtual services to reduce the cost of application deployment, eliminate application conflicts and reboots, simplify your base image footprint to expedite PC provisioning, and increase user productivity.

App-V 4.5 Service Pack 2 provides the latest updates to Microsoft Application Virtualization 4.5 code line. This is the first time the team has delivered via Windwows Update App-V 4.5 SP2 introduces:

Enhanced failover protection or disaster recovery of your virtual application infrastructure: App-V data-store failover protection enables administrators to quickly recover from disasters and/or recycle servers for maintenance.
Enable highly available application infrastructure: App-V 4.5 SP2 load balanced management servers can now leverage SQL server mirrored data-store to support high availability scenarios for line of business applications; with automatic failover protection not available with the previous versions of App-V.
Data replication is now possible across geography: this enables organizations to recover from site wide failures faster.
App-V 4.5 SP2 clients can now deploy Office 2010.

To learn more about this release please view the App-V 4.5 SP2 release notes and FAQ.

App-V 4.5 SP2 can be deployed immediately to production and is available via Microsoft Update to MDOP customers and through Microsoft Volume Licensing Site (MVLS). If you want to evaluate MDOP, the MDOP software is available at MSDN and TechNet.

To learn more about App-V you can visit the MDOP homepage and App-V TechCenter.

Microsoft Application Virtualization for Remote Desktop Services 4.6 available for download

2010-04-19T08:48:26Z

Microsoft Application Virtualization (App-V) for RDS helps solve application compatibility on Remote Desktop Session Hosts/Terminal Servers. App-V for RDS 4.6 now supports 64-bit operating systems.

In Remote Desktop Services deployments, application conflicts can lead to silos of remote desktop session host servers. To avoid application conflicts, applications typically must undergo significant testing to determine which applications will collide and, therefore, must be separated and run on different session host silos—a time-consuming and costly process. Separating out multiple remote desktop session hosts to accommodate specific applications routinely results in servers being underutilized because each one is locked into a specific configuration, capable of serving only a limited set of non-conflicting applications. Often, 20 servers are required to support 1,000 users.

Microsoft Application Virtualization for Remote Desktop Services 4.6 helps consolidate remote desktop session host servers by offering the following features and benefits:

Reduce app-to-app and multi-user application conflicts and hence the need for regression testing
Accelerate application deployment by reducing the deployment risk
Simplify profile management
App-V for RDS 4.6 now supports 64-bit operating systems.

Click here to download

Microsoft releases new desktop virtualization MED-V 1.0 SP1 now Available with Windows 7 Support

2010-04-06T07:08:39Z

Last week MED-V 1.0 SP1 was released as part of the Microsoft Desktop Optimization Pack (MDOP) 2010 refresh. This update adds some key new functionality:

Support for Windows 7 hosts – both 32-bit and 64-bit
Support for running the MED-V server on Windows Server 2008 R2
Support for Japanese Windows versions

Note that MED-V 1.0 SP1 still only supports Virtual PC 2007 SP1, so you will be running Virtual PC 2007 SP1 on Windows 7 (not Windows Virtual PC). It also means that Microsoft now can use native VHD booting for a MED-V demo environment.
Existing MDOP customers can download the MDOP 2010 Refresh at the Volume Licensing Service Center (VLSC). For people with MSDN / TechNet subscriptions, the MDOP 2010 Refresh can be downloaded from MSDN and TechNet.

If you do not know what MED-V is or why you should care – if you need to use Virtual PC to solve an application compatibility problem on more than half-a-dozen computers – you need to be looking at MED-V to provide a deployment and management solution for your virtual machines. More details hare here: www.microsoft.com/med-v

Windows 7 XP Mode no longer requires hardware virtualization

2010-03-20T08:37:35Z

Microsoft announced that Windows 7 users who want to run XP Mode on the operating system can now do it with the help of a patch that eliminates the need for hardware virtualization technology.

"Windows XP Mode no longer requires hardware virtualization technology. This change simplifies the experience by making virtualization more accessible to many more PCs for small and midsize businesses wanting to migrate to Windows 7 Professional or higher editions, while still running Windows XP-based productivity applications," wrote Microsoft’s in-house Windows blogger, Brandon LeBlanc, in a Thursday’s post.

The updated version of the software is available on Microsoft’s Web site for Windows 7 32-bit and Windows 7 64-bit. Users who are already running the XP Mode do not require the new update.

However, Microsoft did not mention anything about how the new changes, to run XP mode without hardware virtualization, will affect the performance of the applications.

Changes to make Windows 7 popular
In the past Microsoft has been severely criticized for making things complicated by introducing XP Mode that worked only on PC’s that supported either Intel’s Virtualization Technology or AMD’s AMD-V.

Because of the complications in the adopting the software, customers stayed with Windows XP. Microsoft finally seems to have realized that it needs to uncomplicate the process to popularize Windows 7 adoption.

"This change makes it extremely easy for businesses to use Windows XP Mode to address any application incompatibility roadblocks they might have in migrating to Windows 7. Windows XP Mode will of course continue to use hardware virtualization technology if available," added LeBlanc in his official blog post.

The XP Mode virtualization is available only for Windows 7 Professional, Ultimate, and Enterprise editions.

Microsoft had introduced Windows 7 back in October 2009 and XP Mode is available only on Professional and Ultimate versions of the operating system.

Changes in Microsoft’s virtualization policy
Microsoft also made some changes in its virtualization policy to reduce obstacles in the way of adoption of Window’s 7 furthermore.

From July 1, Windows Client Software Assurance customers will not require a separate license to access Windows in a Virtual Desktop Infrastructure (VDI) environment but will be part of Software Assurance (SA).

Before this SA customers were required to pay additional fee of $23 per device annually by Microsoft for Windows Virtual Enterprise Centralized Desktop (VECD).

According to Dai Vu, director of Virtualization Solutions Marketing at Microsoft, this new development will reduce the confusion and complexity of virtual environment licensing issue where, "Customers feel that because they've already paid for SA, having to pay again [for VECD] doesn't make sense."

Microsoft explains the RemoteFX technology

2010-03-19T09:32:38Z

After yesterdays Desktop Virtualization announcement from Microsoft and Citrix, Max Herrmann, which is a part of the Windows Server Remote Desktop Services marketing team at Microsoft. Explains the RemoteFX technology.

RemoteFX is not a new standalone product from Microsoft. Rather, it describes a set of RDP technologies - most prominently graphics virtualization and the use of advanced codes - that are being added to Windows Server 2008 R2 Service Pack 1; these technologies are based on the IP that Microsoft acquired and continued to develop since acquiring Calista Technologies. So think of Microsoft RemoteFX as the ‘special sauce’ in Remote Desktop Services that users will be able to enjoy when they connect to their virtual and session-based desktops and applications over the network. With Microsoft RemoteFX, users will be able to work remotely in a Windows Aero desktop environment, watch full-motion video, enjoy Silverlight animations, and run 3D applications – all with the fidelity of a local-like performance when connecting over the LAN. Their desktops are actually hosted in the data center as part of a virtual desktop infrastructure (VDI) or a session virtualization environment (formerly known as Terminal Services). With RemoteFX, these users will be able to access their workspace via a standard RDP connection from a broad range of client devices – rich PCs, thin clients and very simple, low-cost devices.

Also today, Microsoft announced a collaboration agreement with Citrix, which will enable Citrix to integrate and use Microsoft RemoteFX within its XenDesktop suite of products and HDX. Microsoft RemoteFX is designed to integrate with partner solutions, and Microsoft expect solutions from Citrix and other partners to enable the fidelity of a RemoteFX-accelerated user experience for a broad range of environments.

Click here to read the Full Article

Microsoft Accelerates Desktop Virtualization

2010-03-18T21:00:10Z

REDMOND, Wash., March 18 - Microsoft Corp. today announced new investments around desktop virtualization technologies and solutions, including virtual desktop infrastructure (VDI), to help organizations of all sizes increase flexibility, employee productivity and IT cost savings. During a webcast at 9 a.m. PDT, the company will detail new technologies, simplified licensing models and an alliance with Citrix Systems Inc., furthering its virtualization strategy from the desktop to the datacenter.

"Employees crave options in where and how they work. And yet, IT still needs to enforce security and compliance of devices. The business is being pulled in two directions," said Brad Anderson, corporate vice president of the Management and Services Division at Microsoft. "Microsoft's desktop virtualization strategy is unique in addressing this balance. It builds on existing investments and comprehensive management to mitigate risks and control costs, while still equipping end users to be more productive from anywhere."

Customers are also looking at desktop virtualization as a means to reduce costs and accelerate delivery of new applications. A new Microsoft total cost of ownership study on the use of application virtualization technology showed that customers using a Microsoft virtualization technology called Microsoft App-V achieved a 27 percent labor savings, and equivalent cost savings of $82 per PC per year, in application life-cycle management compared with those not using application virtualization. The study also demonstrated how Microsoft App-V helps IT professionals deliver applications more quickly and efficiently.

"We have a strong philosophy that IT is an enabler for the business, and we are always looking for the best IT solutions to meet the needs of our employees and customers," said Chaz Spahn, senior systems engineer for Expedia Inc. "We're working with Microsoft on our desktop virtualization projects. We're using App-V in production and looking to virtualize about 90 percent of our applications. In addition, we have two use cases where we are exploring hosted desktops and foresee about 30 percent of our users could move to this platform. Microsoft was our choice since they have the right solutions to increase our speed of application and desktop provisioning, improve security and compliance, and provide integrated management across our physical and virtual environments."

Microsoft outlined improvements that make it easier to access desktop virtualization. More information on today's announcement and Microsoft's virtualization strategy is available here.

New VDI promotions available for qualified customers to choose from today. Microsoft and Citrix Systems are offering the "Rescue for VMware VDI" promotion, which allows VMware View customers to trade in up to 500 licenses at no additional cost, and the "VDI Kick Start" promotion, which offers new customers a more than 50 percent discount off the estimated retail price. Eligibility and other details on the two promotions can be found at http://www.citrixandmicrosoft.com.
Improved licensing model for virtual Windows desktop. Beginning July 1, 2010, Windows Client Software Assurance customers will no longer have to buy a separate license to access their Windows operating system in a VDI environment, as virtual desktop access rights now will be a Software Assurance benefit.
New roaming use rights improve flexibility. Beginning July 1, 2010, Windows Client Software Assurance and new Virtual Desktop Access license customers will have the right to access their virtual Windows desktop and their Microsoft Office applications hosted on VDI technology on secondary, non-corporate network devices, such as home PCs and kiosks.
Windows XP Mode no longer requires hardware virtualization technology. This change simplifies the experience by making virtualization more accessible to many more PCs for small and midsize businesses wanting to migrate to Windows 7 Professional or higher editions, while still running Windows XP-based productivity applications.
Two new features coming in Windows Server 2008 R2 service pack 1. Microsoft Dynamic Memory will allow customers to adjust memory of a guest virtual machine on demand to maximize server hardware use. Microsoft RemoteFX will enable users of virtual desktops and applications to receive a rich 3-D, multimedia experience while accessing information remotely.
New technology agreement with Citrix Systems. The companies will work together to enable the high-definition HDX technology in Citrix XenDesktop to enhance and extend the capabilities of the Microsoft RemoteFX platform.

"By joining forces in desktop virtualization, Citrix and Microsoft can provide customers of all sizes with groundbreaking solutions that are profoundly simpler, richer and more cost-effective," said Gordon Payne, senior vice president and general manager, Desktop Division, at Citrix Systems. "Today's announcements mark a historic milestone in our 20-year relationship that will dramatically simplify desktop computing for years to come."

In today's webcast, Microsoft and Citrix executives, analysts, and customers will discuss today's news and Microsoft's desktop-to-datacenter virtualization strategy. Today's webcast also marks the beginning of a 100-city, worldwide series of events to educate customers on the comprehensive portfolio of desktop and datacenter virtualization solutions provided by Microsoft and its partners, including Citrix. To join the dialogue, Twitter users can tweet their comments and questions to #MSVirt.

Founded in 1975, Microsoft (Nasdaq: MSFT) is the worldwide leader in software, services and solutions that help people and businesses realize their full potential.

SOURCE Microsoft Corp.

NetApp Storage Best Practices for Microsoft Virtualization

2010-03-15T13:38:42Z

This technical report (TR) provides guidelines and best practices for integrated architectures and implementations of Microsoft® Hyper-V with NetApp® storage solutions. The NetApp technologies discussed in this technical report are important to achieving an integrated storage solution that is cost effective, operationally efficient, flexible, and environment friendly.

Click here to download the whitepaper