Dario IT Solutions Blog

Cluster Shared Volumes (CSV) is a new feature that was introduced in Windows 2008 R2.

If you want to read more about it, how it works, and how you can enable it. There is a lot of material out there that you can refer to:

• Windows 2008 R2 NLB & Failover Clustering
• http://technet.microsoft.com/en-us/library/dd759255.aspx
• http://technet.microsoft.com/en-us/library/dd630633(WS.10).aspx
• http://blogs.msdn.com/clustering/archive/2009/03/02/9453288.aspx
• http://blogs.msdn.com/clustering/archive/2009/02/19/9433146.aspx

Well, after you’ve setup your cluster, enabled CSV, and added clustered disks to CSV, it is now time to copy your VHD files to those CSV disk. The big question is, which cluster node should you perform this operation on?

We’ll, to make a long story short – Copy it to the node that owns the CSV disk!

The reason this is important is that if you are running the copy on the coordinator node (the node which owns the CSV volume of interest), the writes are all local writes. If you are running the copy on any other node, the writes are actually redirected over the network (because they are extending writes to the file) and not done directly to the volume.

Hope this will save you some much needed time

Hi guys,

I’ll be delivering a session at Intel’s “Life after death using… Intel® vPro™ Technology!” conference held on September 14th 2009 at Air Port City, Israel.

This session will focus on integrating SCCM In-Band management capabilities with vPro Out of Band capabilities.

Out of band management allows an administrator to connect to a computer’s management controller when the computer is turned off, in sleep or hibernate modes, or otherwise unresponsive through the operating system. By way of contrast, in-band management is the classic approach used by Configuration Manager and its predecessors whereby an agent runs in the full operating system on the managed computer and the management controller accomplishes tasks by communicating with the management agent.

Out of band management supplements in-band management. While in-band management supports a wider range of operations because it’s environment is the full operating system, in-band management might not be functional if the operating system is not present or is not operational. In these situations, the supplementary capabilities of out of band management allow administrators to manage these computers without requiring local access to the computer.

Out of band management tasks include the following:

• Powering on one or many computers (for example, for maintenance on computers outside business hours).
• Powering off one or many computers (for example, the operating system stops responding).
• Restarting a nonfunctioning computer or booting from a locally connected device or known good boot image file.
• Re-imaging a computer by booting from a boot image file that is located on the network or by using a PXE server.
• Reconfiguring the BIOS settings on a selected computer (and bypassing the BIOS password if this is supported by the BIOS manufacturer).
• Booting to a command-based operating system to run commands, repair utilities, or diagnostic applications (for example, upgrading the firmware or running a disk repair utility).
• Configuring scheduled software update deployments and advertisements to wake up computers prior to running.

SP2 for SCCM 2007 R2 added some important new features, like:

New Operating System Support
• Windows 7
• Windows Server 2008 R2
• Windows Server 2008 SP2
• Windows Vista Sp2

New Features in Out of Band Management
Configuration Manager 2007 Service Pack 2 improves on the Intel AMT integration provided in Service Pack 1. SP2 adds full feature support for computers that have the Intel vPro chip set and AMT firmware versions 4 & 5. In addition to providing feature parity with SP1 and AMT firmware versions 3.2.1, 4.0 and 5.0, the following new features are supported:

Wireless Management (mobile only)
• Up to eight (8) wireless profiles per out of band service point
• Profiles support SSID, WAP2-Enterprise or WAP-Enterprise security, AES or TKIP encryption, client authentication options of EAP-TLS or EAP-TTLS/MSCHAPv2 or PEAPv0/EAP-MSCHAPv2
• Versions of AMT earlier than 3.2.1 are supported with the Intel translator

Authenticated Wired 802.1x Management
• Single profile
• Profile supports client authentication options of EAP-TLS or EAP-TTLS/MSCHAPv2 or PEAPv0/EAP-MSCHAPv2
• Versions of AMT earlier than 3.2.1 are supported with the Intel translator

Audit Logging
• Supported on AMT versions 4 and 5
• Select which out of band management features to audit (critical events not supported)
• Enable or disable audit logging per computer after provisioning
• View, clear, and export to file the audit log entries by using the out of band management console

Power State Configuration
• Enable configuration of the power settings to specify whether out of band management activity is supported when the host is on (S0), host is on (S0) or in standby (S3), or always on (S0-S5)

Data Storage
• Save up to 4096 bytes in ASCII characters in the AMT data storage of each computer
• View and save to the data store by using the out of band management console

Lastly, check out this cool integration demo from Intel – a ConfigMgr advertisement is used to remotely and securely wake-up (boot) Intel vPro systems and push an automated BIOS upgrade.

References for additional reading:

vPro ROI Analysis / Benefits of Activating
http://communities.intel.com/docs/DOC-1494/

Case Stories
http://communities.intel.com/docs/DOC-2260

vPro / SCCM Check list, Quick start Guide, & Tips & Tricks
http://communities.intel.com/community/openportit/vproexpert/microsoft-vpro

ConfigMgr Administrators Checklist and Prerequisites

http://technet.microsoft.com/en-us/library/cc161943(TechNet.10).aspx

http://technet.microsoft.com/en-us/library/cc161785(TechNet.10).aspx

Self Pace SCCM SP1 / vPro Activation Training

http://communities.intel.com/community/openportit/vproexpert/microsoft-vpro/blog/2008/10/24/microsoft-sccm-2007-sp1-intel-vpro-training-videos-now-available

Infrastructure Prep Checklist for Microsoft SCCM

http://communities.intel.com/openport/docs/DOC-2300

A new white paper has been published that compares the options to use multiple instances of SQL without Hyper-V with having multiple virtual machines with single instances of SQL Server. Not only it looks at the different pros and cons, but also provides interesting performance information.

Here’s are the topics covered in this 26-page white paper:

• Executive Overview
• Introduction
• Considerations for Consolidation and Virtualization
  • Identification of Underutilized Servers
  • Server temperature
  • Consolidation Approaches
  • Virtualization Platform: WSRM vs. Hyper-V
• Implementation of the SQL Utility
  • Service Offerings
  • Identification of Candidates for Migration
• Attributes of System Quality
  • Availability and Business Continuity
  • Environmental Sustainability
  • Manageability
  • Performance
  • Predictability and Repeatability
  • Reliability
  • Scalability
  • Security
  • Monitoring
  • Supportability
• Conclusion

Download the white paper from http://technet.microsoft.com/en-us/library/dd557540.aspx

Samsung techies linked 24 of the company’s 256GB SSD (Solid State Drives) together in a RAID configuration with the hopes of making the fast SSDs even faster.

The system actually reaches a whooping transfer speeds of 2GBps (!!). Amazing how disks become the real bottlenecks of today’s computers.

Check out this video, you don’t see that kind of speed every day

The IBM Deployment Pack for Microsoft System Center Configuration Manager 2007 is a deployment kit that extends Configuration Manager 2007 by providing IBM utilities, drivers, and custom tasks for creating automated deployment scripts for IBM target servers. The IBM extensions are available as built-in actions within the Configuration Manager menus.

The IBM Deployment Pack includes various IBM and third-party tools that are needed to configure items such as RAID adapters, management cards, BIOS settings, and other vendor specific settings that are required when deploying servers. While it is true these types of activities can be manually added to the operating system deployment (OSD) process, the Deployment Pack is a much simpler solution that puts everything in the right place for the user, so the tools are ready to use in a custom task sequence.

It also includes a custom boot image that is already prepared to work with Configuration Manager OSD. This tool is highly recommended and will save a huge amount of setup and preparation time for the deployment of x86 / x64 servers.

Download from here:

IBM Deployment Pack for Microsoft System Center Configuration Manager 2007

IBM Deployment Pack for Configuration Manager 2007, v1.0 Release Notes

MAP is a scalable and agent-less assessment platform designed to make it easier for you to adopt the latest Microsoft technologies.

In this version, MAP has expanded its assessment capabilities to include SQL Server 2008, Forefront/NAP, and Microsoft Online Services migration, as well as providing a Power Savings assessment to help you "go green."

In summary, MAP 3.2 assessment areas now include:

• SQL Server 2008 Migration Proposals and Reports (NEW!)
• Forefront/NAP Readiness Proposals (NEW!)
• Microsoft Online Services Migration Surveys, Proposals, and Reports (NEW!)
• Power Savings Proposals (NEW!)
• Server Migration Reports and Proposals (Windows Server 2008 and "virtualized guests by hosts" reporting) (NEW!)
• Server Consolidation Reports and Proposals (Virtual Server 2005 R2 and Hyper-V)
• Desktop Security Assessment to determine if desktops have anti-virus and anti-malware programs installed and up-to-date, or if the Windows Firewall is turned on
• Windows Vista and Microsoft Office 2007 Hardware Assessment Reports and Proposals

Based on hypervisor technology, the Hyper-V™ virtualization feature in the Windows Server® 2008 operating system is a thin layer of software between the hardware and the operating system that allows multiple operating systems to run, unmodified, on a host computer at the same time. Hyper-V is a powerful virtualization technology that can be used by corporate IT to consolidate under-utilized servers, lowering total cost of ownership (TCO) and maintaining or improving quality of service (QoS). Hyper-V opens more potential development and test environment types that otherwise might be constrained by hardware availability.

It is challenging enough in general to right-size the hardware to consolidate current workloads and provide headroom for growth. Adding virtualization to the mix increases the potential capacity planning challenges. The goal of this document is to help address these by focusing on two key areas of running Microsoft® SQL Server® in a Hyper-V environment:

• System resource overhead imposed by running SQL Server in a Hyper-V environment

• How well Hyper-V scales running SQL Server 2008

This white paper describes a series of test configurations we ran, which represented a variety of possible scenarios involving SQL Server running in Hyper-V. The paper discusses our results and observations, and it also presents our recommendations. Our test results showed that SQL Server 2008 on Hyper-V provides stable performance and scalability. We believe Windows Server 2008 Hyper-V is a solid platform for SQL Server 2008 for the appropriate workload. It is practical to run production workloads under a Hyper-V environment, as long as the workload is within the capacity of your Hyper-V guest virtual machine.

For more information, please refer to the whitepaper Running SQL Server 2008 in a Hyper-V Environment – Best Practices and Performance Recommendations.

The BiztTalk team has published great content on TechNet that could be leveraged to implement and measure performance of SharePoint Server or Project Server virtualization on Hyper-V:

• Measuring Performance on Hyper-V
  • Measuring Disk I/O Performance
  • Measuring Memory Performance
  • Measuring Network Performance
  • Measuring Processor Performance

• Tools for Measuring Performance
• Optimizing Performance on Hyper-V
  • Allocate 110%�125% of the Hardware Resources to the Hyper-V Virtual Machines
  • Optimize Hyper-V Performance
  • Optimize Performance of Disk, Memory, Network, and Processor in a Hyper-V Environment
  • Optimize BizTalk Server Solution

Even if you are not interested in BizTalk, this is a good guide performance wise!

Microsoft has published an interesting article about their official support for installing Exchange on Hyper-V\Virtual Server 2005 virtual machines.

To make a long story short, here are the support policies for both Exchange 2007 and Exchange 2003:

Support Policy and Recommendations for Exchange Server 2007

Microsoft supports Exchange Server 2007 in production on hardware virtualization software only when all the following conditions are true:

• The hardware virtualization software is Windows Server 2008 with Hyper-V technology, Microsoft Hyper-V Server, or any third-party hypervisor that has been validated under the Windows Server Virtualization Validation Program.
• The Exchange Server guest virtual machine:
  • Is running Microsoft Exchange Server 2007 with Service Pack 1 (SP1) or later.
  • Is deployed on the Windows Server 2008 operating system.
  • Does not have the Unified Messaging server role installed. All Exchange 2007 server roles, except for the Unified Messaging role, are supported in a virtualization environment.
• The storage used by the Exchange Server guest machine can be virtual storage of a fixed size (for example, fixed virtual hard drives (VHDs) in a Hyper-V environment), SCSI pass-through storage, or Internet SCSI (iSCSI) storage. Pass-through storage is storage that is configured at the host level and dedicated to one guest machine.

  Note:

  In a Hyper-V environment, each fixed VHD must be less than 2,040 gigabytes (GB). For supported third-party hypervisors, check with the manufacturer to see if any disk size limitations exist.

  • Virtual disks that dynamically expand are not supported by Exchange.
  • Virtual disks that use differencing or delta mechanisms (such as Hyper-V’s differencing VHDs or snapshots) are not supported.
• No other server-based applications, other than management software (for example, antivirus software, backup software, virtual machine management software, etc.) can be deployed on the physical root machine. The root machine should be dedicated to running guest virtual machines.
• Microsoft does not support combining Exchange clustering solutions (namely, cluster continuous replication (CCR) and single copy clusters (SCC)) with hypervisor-based availability or migration solutions (for example, Hyper-V’s quick migration). Both CCR and SCC are supported in hardware virtualization environments provided that the virtualization environment does not employ clustered virtualization servers.
• Some hypervisors include features for taking snapshots of virtual machines. Virtual machine snapshots capture the state of a virtual machine while it is running. This feature enables you to take multiple snapshots of a virtual machine and then revert the virtual machine to any of the previous states by applying a snapshot to the virtual machine. However, virtual machine snapshots are not application-aware, and using them can have unintended and unexpected consequences for a server application that maintains state data, such as Exchange Server. As a result, making virtual machine snapshots of an Exchange guest virtual machine is not supported.
• Many hardware virtualization products allow you to specify the number of virtual processors that should be allocated to each guest virtual machine. The virtual processors located in the guest virtual machine share a fixed number of logical processors in the physical system. Exchange supports a virtual processor-to-logical processor ratio no greater than 2:1. For example, a dual processor system using quad core processors contains a total of 8 logical processors in the host system. On a system with this configuration, do not allocate more than a total of 16 virtual processors to all guest virtual machines combined.

Support Policy and Recommendations for Exchange Server 2003

Microsoft supports Exchange Server 2003 in production on hardware virtualization software (virtual machines) only when all the following conditions are true:

• The hardware virtualization software is Microsoft Virtual Server 2005 R2 or any later version of Microsoft Virtual Server.
• The version of Exchange Server that is running on the virtual machine is Microsoft Exchange Server 2003 with Service Pack 2 (SP2) or later.
• The Microsoft Virtual Server 2005 R2 Virtual Machine Additions are installed on the guest operating system.
• Exchange Server 2003 is configured as a stand-alone server and not as part of a Windows failover cluster.
• The SCSI driver that is installed on the guest operating system is the Microsoft Virtual Machine PCI SCSI Controller driver.
• The virtual hard disk Undo feature is not enabled for the Exchange virtual machine.

  Note:

  When a Microsoft Virtual Server SCSI adaptor is added to a virtual machine after the Virtual Machine Additions have been installed, the guest operating system detects and installs a generic Adaptec SCSI driver. In this case, the Virtual Machine Additions must be removed and then reinstalled for the correct SCSI driver to be installed on the guest operating system.

Rest of the recommendations are at source.

Asset Intelligence enhances the inventory capabilities of Configuration Manager by extending hardware and software inventory. Many inventory classes improve the breadth of information gathered about hardware and software assets.

Download this update to correct a few Asset Intelligence license reports that are not displaying the correct product codes.

This update is only applicable to the Configuration Manager 2007 SP1 Asset Intelligence knowledge base. It is not intended for SMS 2003 SP3 release or Configuration Manager RTM release. An update for SMS2003 and Configuration Manager 2007 RTM will be provided at a later date.