Installing Hyper-V Part 2
Okay it took a bit longer then desired, however here is the first actual part concerning installation of Hyper-V.
So what is actually the most important component when designing a Hyper-V environment? Just like VMware it is actually the storage. Of course you could start out with local storage but quite frankly; that is not anything near a modern infrastructure anymore. One could argue that for a test/home environment local storage is sufficient but I don't quite agree with that: Most challenges in a server virtualization implementation are actually storage and backup based. Although it pretty much extends the scope of my inital blog series plan I find it important enough to discuss it so here it goes!
Central vs Local storage
Local storage of course limits you in flexibility and expandability. However on my demo laptop I am forced to use local storage while keeping my VM's synchronized between my Laptop and my regular environment. How I will synchronize this I will get back to while blogging about replication and site recovery.
Apart from a portable demo environment there is no justification to implement server virtualization with Hyper-V on local storage.
Central Storage Iscsi or Fiber?
It will be obvious that a fiber based storage solution is a bit above my budget for home usage thus that answers that question quite easily. However what about production environments?
Fiber is the way to go
When taking variables as price, performance and proven technology into account a fiber based SAN is the way to go. Fiber will obviously give you a maximum throughput of 4 Gb/s whilst Iscsi is limited to 1 Gb. Indeed, 10 Gb ethernet is available yet not quite stable in relation with Iscsi yet. The storage market is rapidly moving (like the virtualization market) however and I do expect that 2009 or 2010 will be the definite breakthrough of stable ISCSI based storage networks. If I would be an IT manager and I would have to make the decision now, I would simply play safe and choose fiber.
For test and small production environments ISCSI is however an excellent low cost choice.
Hardware or software based storage solution?
Basically this is a no brainer; production and business environments will use something like HP EVA, DELL Equallogic or Netapp based hardware. In principle all fine solutions that differentiate on matters way beyond the scope of this Blog and storage expertProxy-Connection: keep-alive
Cache-Control: max-age=0
will be way more valuable to consult concerning this. What I want to talk about are the software based solutions on the market available today since that will be the material I'll be working with. There are a couple of options:
Lets thinapp IE7 and IE8 together
Its, Monday morning so time for some fun!
A customer asked me if it was possible to install Internet explorer 8 beta, and still be able to use Internet explorer 7 for old applications (in their test environment). Of course I answered and immediately started testing. As you all know Microsoft app-v does not support sequencing internet explorer so the best thing to do was use VMware’s Thinapp. My base image is an Windows XP SP3 machine, SP3 does not install IE7 or IE7 updates unless you already installed IE7 before upgrading to SP3 (see Microsoft KB) To successfully sequence IE7 to work together with IE8 download the following files:
• WindowsXP-KB957095-x86-ENU
• WindowsXP-KB958644-x86-ENU
• Nlsdl.exe (microsoft)
• idndl.exe (microsoft)
• IE7-WindowsXP-x86-enu.exe
These downloads will definitely save you some time finding out exactly witch updates you need, after this the Thinapp part is pretty straight forward.
• Install updates
• Start capture
• Install IE7
• Stop capture
• Revert machine
• Install IE8
• Start the tests
Because this is a fast proof of concept test, I challenge you to drop some improvements in the comments to make it even better.
MDT 2008: Updating deployment point using Powershell
Everybody who has been playing around with MDT faces this issue. For some changes you make you need to update your deployment point.
I got tired of clicking through the GUI to update my deployment point, so that's why I started hacking around in Powershell to automate this process
Here's the powershell script for updating the deployment point, it takes 2 parameters:
name of deployment point and the updatetype (Full or FilesOnly)
#'***********************************************************************
#'* File: UpdateDeploymentPoint.ps1
#'* Creation Date: 2008/12/07
#'* Author: Henk Hofs (Login Consultants)
#'* Purpose: Updates MDT Deployment Point
#'* Usage: ./UpdateDeploymentPoint.ps1 [Deployment Point Name] [UpdateType]
#'* Reference:
#'*
#'* Revisions: 0.1 HHO Initial Version
#'***********************************************************************
# Initialization
# Get command-line parameters for Deployment Point name and UpdateType
Param
(
[string]$DeployName =$(throw "You must specify the name of the deployment point"),
[string]$UpdateType = $(throw "You must specify the update type, choose between: Full and FilesOnly")
)
#Set Upd Variable (boolean) according to input from parameter
Switch ($UpdateType)
{
"Full" {[Boolean]$Upd = 0}
"FilesOnly" {[Boolean]$Upd = 1}
}
#Create temp directory for log file if it does not exist
if ((Test-Path -Path C:\temp) -eq $false)
{
New-Item -ItemType directory c:\temp
}
#Load MDT Assembly
$MdtInstallDir = (gp "HKLM:\software\microsoft\deployment 4").Install_Dir
[Reflection.Assembly]::LoadFile( "$MdtInstallDir" + "Bin\Microsoft.BDD.ConfigManager.dll")
$manager = [Microsoft.BDD.ConfigManager.Manager]
#Load DeployManager class
$deployManager = $manager::DeployManager
#Load list of deployment points
$deployList = $deployManager.GetDataTable()
# Loop through the list
foreach ($item in $deployList)
{
#Look for the name that was entered as a paramater
if ($item["Name"] -eq $DeployName)
{
#Set $deployGUID variable and use it to update the deployment point
$deployGUID = $item["guid"]
Write-Host "Updating deployment point" $DeployName "with guid" $item["guid"] "using updatetype" $UpdateType
Write-Host "Please be patient..."
$deployPoint = $DeployManager[$deployGUID]
$deployPoint.Generate("x86", "C:\temp\DeployUpdate.log", $Upd)
}
}
Well, after you updated your deployment point, you have to replace your image in WDS. So I got something for that as well... a nice oneliner in CMD
wdsutil /replace-image /image:"Lite Touch Windows PE (x86)" /ImageType:Boot /Architecture:x86 /ReplacementImage /ImageFile:"D:\Distribution\Boot\LiteTouchPE_x86.wim"
You might want to replace "D:\Distribution\Boot\LiteTouchPE_x86.wim" with the path to you imagefile
-Henk
Vista and 2008 SP2 BETA
I was just browsing the web and stumbled accross this. Whoohoo, Vista and 2008 SP2 Customer Preview Program!.
Wait... what?! Vista and 2008 SP2 BETA?
That's right! A single service pack that covers both Client and Server!
This is actually pretty nice! This reduces the management of service packs for both server and client. Just service packs ![]()
So what's actually in there?
Well... seeing as after you installed a fresh Vista SP1 machine you almost get crushed by updates. Here's a list of hotfixes included in service pack.
Other then that there are a few new features:
- Support for new types of Hardware and emerging standards, including Bluetooth 2.1, the ability to natively record data on Blu-Ray media, support for ICCD/CCID smart cards, and support for the new VIA 64-bit CPU
- Wi-Fi setup and maintenance is simplified with the addition of Windows Connect Now (WCN)
- The ex-FAT file system is enabled, supporting UTC timestamps to ensure correct file synchronization across time zones
- Windows Search 4.0 is included, which provides users faster and more relevant results. Windows Search 4.0 also allows Group Policy integration, which provides administrative control over search parameters
- End users should also experience improvements in resume performance when a Wi-Fi connection is no longer available
Get your copy here!
EDIT:
You can also get the SP2 update through Windows Update. Use the script below to enable the update:
reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\VistaSP2 /f reg delete HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\WindowsUpdate\VistaSP2 /f reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\VistaSP2 /v Beta1 /t REG_SZ /d 93F7D954-DF91-22E6-99AB-4D8AF54E813A /f
MDT 2010
I just read this article, which announces the beta of MDT 2010 coming out soon
According to the article it will have:
- Support for Windows 7 and Windows Server 2008 R2.
Well, that was to be expected. I already installed Windows 7 on a VPC, but the installation process looked the same as Vista/2008. So there's probably some extra features/roles/components you can select in the task sequences, but I don't think this will be too exciting
- Deployment Workbench and script architecture improvements.
I'm very curious about the script architecture improvements!! Will they have changed to Powershell instead of VBScript? I do hope so, because i'm still looking for a reason to start learning Powershell!
- Documentation improvement
Right, nothing to add to that
I signed up for the beta, and will get a download link as soon as it's available!
I will be writing an article about MDT 2010 as soon as I get to take it for a spin.