Archive

Archive for July, 2008

Offline Virtual Machine Servicing Tool – Released

Released from Microsoft today.

The increasing use of virtual machines creates new challenges for IT.
Virtual machines that are left offline for extended periods of time do not automatically receive operating system, anti-virus, or application updates that would keep them compliant with current IT policy. An out-of-date virtual machine poses a risk to the IT environment. If deployed and started, the out-of-date virtual machine may be vulnerable to attack or may be capable of attacking other network resources.

The Offline Virtual Machine Servicing Tool provides a way to automate the process of updating virtual machines with the latest OS patches.

The Offline Virtual Machine Servicing Tool is built on Windows Workflow Foundation and the Windows PowerShellTM interface to manage the workflow of updating large numbers of offline virtual machines according to their individual needs. To do this, the tool works with Microsoft® System Center Virtual Machine Manager 2007 (VMM) and with software update management systems (at present, either Microsoft Windows Server® Update Services 3.0 (WSUS) or Microsoft System Center Configuration Manager 2007).

Download the tool and read more on Technet
http://technet.microsoft.com/en-us/library/cc501231(TechNet.10).aspx

Advertisements
Categories: ConfigMgr

Vista SP1 Installations Deployed Using Operating System Deployment Cannot Hibernate

This article could be interesting for ConfigMgr OSD Admins deploying Windows Vista SP1.
Just spreding the news…

Read more about the issue and the solutions here.
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3606900&SiteID=17

Categories: ConfigMgr

System Center Configuration Manager 2007 R2: New RC Build available

System Center Configuration Manager 2007 R2 Release Candidate (build 6335) has now released on Microsoft Connect.
More about ConfigMgr R2 later.

/Jens Ole

Categories: ConfigMgr

Group Policy Preference Client Side Extensions for Windows XP and Windows Server 2003 Updated

Categories: Group Policy

Migrating and Restructuring Active Directory Domains Using ADMT v3.1

 

Microsoft recently released an updated Active Directory Migration Guide.

This guide explains how to use the Active Directory® Migration Tool version 3.1 (ADMT v3.1) to migrate users, groups, and computers between Active Directory domains in different forests (interforest migration) or between Active Directory domains in the same forest (intraforest migration). It also shows how to use ADMT v3.1 to perform security translation between different Active Directory forests.

Follow the link to download.
http://www.microsoft.com/downloads/details.aspx?FamilyID=6d710919-1ba5-41ca-b2f3-c11bcb4857af&DisplayLang=en

/Jens Ole

Categories: Active Directory

Building your Windows XP Reference Image on VMware ESX – Step by Step

01/07/2008 5 comments

 

When using OS Deployment (OSD) in ConfigMgr to build your Windows XP reference image, you want to have the smallest amount of drivers in your image and inject drivers as part of the deployment. Because of that, building the reference image inside VMware is a good idea and a lot of companies today have a virtualization strategy based on VMware ESX (Hope it must be Hyper-V in the future ;-)).
Besides having a reduced driver set in your image, building your image on VMware results in the “right” HAL type, which most computers uses today. If you have computers with different HAL types, HAL replacement in your Task Sequence (TS) is a possibility, but that is out of scope for this article.

VMware Server or VMware Workstation is also possible to use, to create a slim image, but if you allready have VMware ESX, that’s what you want to use.

Pre-requirements:
Microsoft System Center Configuration Manager 2007 RTM or SP1 (SCCM)
VMware ESX 3.x
VMware Windows Drivers (http://download3.vmware.com/software/vmscsi-1.2.0.4.flp)
AMD PCNet Lance Network Driver (http://www.amd.com/us-en/ConnectivitySolutions/ProductInformation/0,,50_2330_6629_2452%5E2454%5E2486,00.html)

Step 1 – Create your Virtual Machine
Inside VMware console launch the New Virtual Machine Wizard and choose Custom as showed below.

Select Name – Next

Select VMFS – Next

Select Windows XP Professional as Operating System – Next

Select 1 processor – Next

Select 512 MB RAM (Min. for Windows PE 2.x) – Next

Select Network – Next

Important!
Select Storage Adaptor Type = BusLogic – Next

Create new disk – Next

Finished, and the Virtual Machine is ready to build and capture your reference image.

Step 2 – In VMware Console

Now you need to find the VMware Windows drivers.

Attach the vmscsi-1.2.0.4.flp to the ConfigMgr Virtual Machine, if it’s running inside VMware ESX. If not attach vmscsi-1.2.0.4.flp to any Windows Virtual Machine and copy the files to the ConfigMgr server.
The downloaded AMD network driver file must also be extracted and copied to the ConfigMgr server.

Step 3 – In ConfigMgr Console

In this step the correct drivers are imported in ConfigMgr and made available in the Windows PE boot image. At last the Build and Capture Task Sequence is created.

Use the Import Drivers Wizard to import the VMware drivers. (3 drivers, see below)

Add the drivers to a Category ie. VMware.

Add the drivers to a existing Package or create a New Package.

Add the drivers to the boot image

Select Next and then Finish

The following drivers must be in both boot image and in the driver package.

Remember to update your distribution points with the new package and the new boot image.

Create a new task sequence using the New Task Sequence Wizard and select Build and Capture a reference operating system image or modify an existing Build and Capture task sequence.

In the Apply Device Drives section limit the driver search using the newly created category VMware.

In the Apply Driver Package section the VMware mass storage driver is injected to be available at startup.

 

In the Prepare OS section, set Automatically build mass storage driver list, to include other mass storage drivers, than the one used in this image.

Finally
Now remember to Import the Virtual Machine to a collection in ConfigMgr, so it becomes a known client, using the Import Computer Information wizard.

Advertise your Build and Capture task sequence to the collection where to you imported the computer and you are ready to go…

/Jens Ole

Categories: ConfigMgr