Richard Smith : Lite Touch

GUI Interface for USMT

ricsmith — Fri, 11 Jan 2008 16:36:00 GMT

Dan Cunningham has written a GUI wrapper for the User State Migration Tool (USMT) In Dan's interface, USMT provides the logic and mechanisms for the actual capture / restore process, but because USMT is entirely command-line, Dan decided to set about creating a .NET-based wrapper for it to simplify data capture/restore.

Here’s some of the nice features in Workstation Migration Assistant:

Migrate via a pre-defined network storage location, external USB drive, or user-specified location. USB drive detection is automatic
Optional Hard Disk Health Check will run a CHKDSK prior to capture and fix errors if any are found
Optional Encryption using a pre-defined company encryption key, or per-user customised encryption (for highly sensitive data that can’t be stored on a server without being encrypted)
Use different configurations for a multi-OS, XP > XP and Vista > Vista migrations (useful when on XP to force the /TargetXP switch, and if you’re Vista migration can exclude XP-only obsolete files)
Automatically run pre and post capture/restore scripts (very useful to further configure machine settings)
Migrate domain only accounts, or domain and local
Automatically exclude certain domain or local accounts from the migration
Automatically send log files to an e-mail address via SMTP after the migration
On-screen status during every stage of the migration, including ETA
Option to limit migrations to a certain size, i.e. if over 20GB of data to backup, then fail and inform user.
Very configurable through configuration file
Command-line automation

Dan is hoping to release the tool soon - so keep checking http://dcunningham.net/2007/11/22/a-quick-look-at-workstation-migration-assistant/ for updates

powercfg - Useful if you know the GUIDS!

ricsmith — Thu, 29 Nov 2007 21:50:50 GMT

So I have been doing some work with powercfg - and found it a very useful tool for scripting power management options during builds. This command utility is installed with Windows Vista and you can use it to control power settings and configure computers to default to Hibernate or Standby modes.

The following command-line options are available for powercfg.

powercfg [-l ] [-q ] [-x ] [-changename ] [-duplicatescheme ] [-d ] [-deletesetting ] [-setactive ] [-getactivescheme ] [-setacvalueindex ] [-setdcvalueindex ] [-h ] [-a ] [-devicequery ] [-deviceenablewake ] [-devicedisablewake ] [-import ] [-export ] [-lastwake ] [-?] [-aliases ] [-setsecuritydescriptor ] [-getsecuritydescriptor ]

Full details of the switches can be found here

So having delved into this utility a little more - here are my top commands for powercfg ready to use in your scripts:

sets the power configuration to High Performance
powercfg -setactive 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

tweaks the basic power settings
powercfg -change -hibernate-timeout-ac 0
powercfg -change -hibernate-timeout-dc 0

turns hibernation off
powercfg -hibernate OFF

require password when console wakes up (0=false, 1=true)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c fea3413e-7e05-4911-9a71-700331f1c294 0e796bdb-100d-47d6-a2d5-f7d2daa51f51 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c fea3413e-7e05-4911-9a71-700331f1c294 0e796bdb-100d-47d6-a2d5-f7d2daa51f51 0

also needed to show up on Power Menus...
powercfg -setacvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e fea3413e-7e05-4911-9a71-700331f1c294 0e796bdb-100d-47d6-a2d5-f7d2daa51f51 0
powercfg -setdcvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e fea3413e-7e05-4911-9a71-700331f1c294 0e796bdb-100d-47d6-a2d5-f7d2daa51f51 0

power plan type (0=power saver, 1=high performance, 2=balanced)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c fea3413e-7e05-4911-9a71-700331f1c294 245d8541-3943-4422-b025-13a784f679b7 1
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c fea3413e-7e05-4911-9a71-700331f1c294 245d8541-3943-4422-b025-13a784f679b7 1

hard disk timeout
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 0012ee47-9041-4b5d-9b77-535fba8b1442 6738e2c4-e8a5-4a42-b16a-e040e769756e 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 0012ee47-9041-4b5d-9b77-535fba8b1442 6738e2c4-e8a5-4a42-b16a-e040e769756e 0

wireless adapter power (0=max perf, 1=low power saving, 2=med power saving, 3=max power saving)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1 12bbebe6-58d6-4636-95bb-3217ef867c1a 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 19cbb8fa-5279-450e-9fac-8a3d5fedd0c1 12bbebe6-58d6-4636-95bb-3217ef867c1a 0

sleep timeout
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 238c9fa8-0aad-41ed-83f4-97be242c8f20 29f6c1db-86da-48c5-9fdb-f2b67b1f44da 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 238c9fa8-0aad-41ed-83f4-97be242c8f20 29f6c1db-86da-48c5-9fdb-f2b67b1f44da 0

close action (0=do nothing, 1=sleep, 2=hibernate, 3=shutdown)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 0

also needed to show up on Power Menus...
powercfg -setacvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 0
powercfg -setdcvalueindex 381b4222-f694-41f0-9685-ff5bb260df2e 4f971e89-eebd-4455-a8de-9e59040e7347 5ca83367-6e45-459f-a27b-476b1d01c936 0

processor power cstate (0,1=power saver, 2,3=balanced, 4,5=high perf)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 68f262a7-f621-4069-b9a5-4874169be23c 4
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 68f262a7-f621-4069-b9a5-4874169be23c 4

minimum processor state
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 893dee8e-2bef-41e0-89c6-b55d0929964c 100
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 893dee8e-2bef-41e0-89c6-b55d0929964c 100

processor power perfstate settings
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 bbdc3814-18e9-4463-8a55-d197327c45c0 4
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 54533251-82be-4824-96c1-47b60b740d00 bbdc3814-18e9-4463-8a55-d197327c45c0 4

monitor timeout
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 7516b95f-f776-4464-8c53-06167f40cc99 3c0bc021-c8a8-4e07-a973-6b14cbcb2b7e 0
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 7516b95f-f776-4464-8c53-06167f40cc99 3c0bc021-c8a8-4e07-a973-6b14cbcb2b7e 0

multimedia settings (0=take no action, 1=prevent computer from sleeping, 2=enable away mode)
powercfg -setacvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 9596fb26-9850-41fd-ac3e-f7c3c00afd4b 03680956-93bc-4294-bba6-4e0f09bb717f 2
powercfg -setdcvalueindex 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c 9596fb26-9850-41fd-ac3e-f7c3c00afd4b 03680956-93bc-4294-bba6-4e0f09bb717f 2

set the absentia power scheme (the scheme used when no one is logged in)
powercfg -setabsentia 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c

Enjoy... :-)

Moving from RIS to Windows Deployment Services (WDS)

ricsmith — Fri, 23 Nov 2007 14:44:05 GMT

I wanted to point you in the direction of a document that helps with moving from Remote Installation Services (RIS) to Windows Deployment Services (WDS) on Windows Server 2003.

Many of the clients that I consult for are big RIS users, so this whitepaper has been especially useful in recent months as they have moved to deploying Windows Vista...

You can download it from the link below:

Deploying and Managing the Windows Deployment Services Update on Windows Server 2003

Microsoft Product Evals on Virtual Hard Disk

ricsmith — Mon, 12 Nov 2007 14:00:00 GMT

I am often asked why deployment is such a great place to work as a consultant and I usually answer by saying that deployment (both client and server) touches all aspects of the infrastructure and therefore you need a knowledge across many products. All though I think this is a great thing - it also means that you have to keep up with other technologies - and have them set up in a test environment for your deployment engagements.

I often setup small proof of concept labs for customers - and I make us of a lesser known Microsoft service that provides many products ready configured as time limited Virtual Hard Disks (VHD) ready for download - over the months I have created a library of these that I can set up and leave at customer sites for time limited testing (usually 30 day evaluations). Below are the links to all of the products that we supply as VHD:

BizTalk Server 2006

Exchange Server 2007

Exchange Server 2007 SP1 Beta 2

ISA Server 2006

Microsoft Office 2007 Professional

Office SharePoint Server 2007

SQL Server 2005

SQL Server 2005/Exchange 2007

System Center Configuration Manager 2007

System Center Essentials 2007

System Center Virtual Machine Manager 2007

Visual Studio 2005 Team Suite

Visual Studio 2005 Team System

Windows Server 2008 Beta 3

Windows Server 2003 R2

Windows Vista

Search Server 2008 Express

Hopefully this set of server and client pre-configured virtual machine hard disks will save you endless setup hours and also enable you to start configuring in other services to your deployment engagements.

Microsoft Deployment Released

ricsmith — Mon, 12 Nov 2007 13:47:56 GMT

The first release of Microsoft Deployment is now available. This release marks the first in a series of three Microsoft Deployment releases planned between now and Summer 2008. It focuses on integration with new deployment features in Configuration Manager 2007 as well as features and guidance to support server deployment. Future updates to Microsoft Deployment will add further support for Windows Server 2008, Windows Vista SP1, and System Center Configuration Manager 2007 SP1 releases.

Microsoft Deployment delivers additional value to Configuration Manager 2007 users by adding complete integration into the Configuration Manager 2007 administrator console and task sequencer as a product extension. Microsoft Deployment combined with Configuration Manager 2007allows users to:

Dynamically install packages
Automatically determine user state store locations
Back up computers and database settings
Install to computers unknown to the Configuration Manager 2007 database
Perform offline patching
Install language packs offline and online
Monitor deployments using an updated Operations Manager 2007 Management Pack

In addition to the new integration with Configuration Manager 2007, Microsoft Deployment also enhances the Lite Touch Installation for deploying desktops and servers. This release allows LTI to:

Deploy pre-release versions of Windows Server 2008, including support for Server Core installation options.
Automate server role definition using Server Manager.
Configure disk and network interface cards (NICs), including static TCP/IP configuration.
Migrate from LTI to Configuration Manager 2007.
Create custom task sequences or modify task sequences based on new templates for:
- Client template: Windows Vista, Windows® XP
- Server template: Windows Server 2003, Windows Server 2008
- Replace scenario template
Invoke Web service calls from rules.
Deploy operating system images using the new multicast feature in Windows Server 2008 Windows Deployment

Microsoft Deployment is available as a free download on the Microsoft Download Center.

The Microsoft TechNet Desktop Deployment Center and the new Server Deployment Center host the Microsoft Deployment process guidance for online reading.

Microsoft Deployment RC1 Released

ricsmith — Thu, 25 Oct 2007 11:06:00 GMT

Business Desktop Deployment (BDD) is now Microsoft Deployment!

The RC1 release and new name for the fourth generation deployment Solution Accelerator, Microsoft Deployment is available from today. Previous Beta releases have been using the code name "Deployment 4" to refer to Microsoft Deployment before the name was finalised.

Microsoft Deployment is the next version of Business Desktop Deployment (BDD) 2007. It unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. Microsoft Deployment adds integration with recently released Microsoft deployment technologies to create a single path for image creation and deployment using:

System Center Configuration Manager 2007 Operating System Deployment
Windows Automated Installation Kit
Windows Deployment Services with new multicast technology
Application Compatibility Toolkit 5.0
User State Migration Tool 3.0.1
2007 Office system
Windows Server 2008 Server Manager for automated server role definition

New Features in Microsoft Deployment

Microsoft System Center Configuration Manager 2007 support, with the following features:

Full support for Windows Vista, Windows XP, and Windows Server 2003 deployments with Microsoft Deployment and Configuration Manager 2007.
Complete integration into the Configuration Manager 2007 admin console and task sequencing capabilities.
- Quick start Configuration Manager 2007 operating system deployments using one wizard to create needed task sequences and packages.
- Extension of the Configuration Manager 2007 task sequencing capabilities with new actions.
Feature parity with BDD 2007 and SMS 2003, including dynamic package installation, automatic determination of state store location, computer backup, and database settings.
Installation support for computers unknown to the Configuration Manager 2007 database
Added support for offline patching
Support for offline and online language pack installation
Deployment monitoring:
- Updated Management Pack for System Center Operations Manager 2007

Lite Touch Installation (LTI) support for Windows Server 2008:

Support for deploying Windows Server 2008 Beta 3 and potentially RC1 (to be verified after RC1 release), including support for Server Core installation options.
Automated server role definition using Server Manager

Lite Touch Installation (LTI) enhancements:

Enhanced disk and network interface cards (NICs) configuration options, including support for static TCP/IP configuration.
Design changes to ease the migration from LTI to Configuration Manager 2007.
Support for multiple task sequence templates. New sample templates include:
- Client template: Windows Vista, Windows XP
- Server template: Windows Server 2003, Windows Server 2008
- Replace scenario template
Ability to invoke web service calls
- Support for web service calls from rules
- Web services can be invoked as part of the rules processing performed by Microsoft Deployment, using new rules that can be defined in CustomSettings.ini.
Support for BDD 2007 upgrade or side-by-side installation with Microsoft Deployment.

Lite Touch Installation (LTI) multicast support:

Deployment Workbench supports multicast transmission of operating system images when performing LTI deployments from Windows Server 2008 servers that are running Windows Deployment Services.

Where to Find Microsoft Deployment

Microsoft Deployment is available as an open beta download.

Join the Microsoft Deployment Connection program on Microsoft Connect.

If you are already registered for the program, click here.

Related Resources

Desktop Deployment Center on Microsoft TechNet

System Center Configuration Manager on Microsoft TechNet

System Center Configuration Manager evaluation software on Microsoft TechNet

Windows Server 2008 on Microsoft TechNet

I will be covering Microsoft Deployment RC1 in more detail over forthcoming blogs

Deployment 4 - Using Your BDD 2007 Task Sequences as Templates

ricsmith — Tue, 02 Oct 2007 18:29:40 GMT

So - Deployment 4 Beta 3 - very cool indeed...but I bet your thinking "how can I use the task sequences that I built in BDD 2007 as templates in Deployment 4 Beta 3?" - well that's a good question.

Deployment 4 Beta 3 stores it's task sequence templates in the Program Files\Deployment 4\Templates folder and come with three templates ready configured:

Client.xml
ClientReplace.xml
Server.xml

You can add you own templates to this directory by creating new task sequences in the Deployment 4 Beta 3 Workbench or by copying you task sequences from BDD 2007. In the example below, I have copied two XML files (TS.vista.xml and TS.xp.xml) to the Program Files\Deployment 4\Templates location that I had previously configured in BDD 2007.

We now need to update the headers in our newly copied task sequences to give them a descriptive name. This is because BDD 2007 names all task sequences as SA Task Sequence. Open each task sequence file in your favourite XML editor and change the Name and Description tags to give your files descriptive names (you will see why shortly)

Now that our templates are configured and in the correct location it just a case of creating a new task sequence based on our newly added template files. Open Deployment 4 Beta 3 and right click Task Sequence - choose NEW to start the New Task Sequence Wizard and give your new task sequence an ID, Name and Comments on the General Settings page:

On the Select Template page, the drop down should now show your new templates with the names as edited earlier, which you can now select to create the starting point for your new task sequence.

Once the wizard has completed you will have a new task sequence based on your imported file from BDD 2007 which is now a re-usable template in Deployment 4 Beta 3.

You can use this process to add as many templates as you need for your environment - you may want to merge some of the new task sequences from Deployment 4 Beta 3 with your BDD 2007 task sequences to ensure that you are taking advantage of some of the tasks delivered in Deployment 4 Beta 3 such as network card and disk configuration (see Ben's blog for more on this...). You will also need to ensure that any scripts, applications and custom code referenced in your BDD 2007 task sequencer are copied across to the Deployment 4 environment so that the tasks can find them.

For more information, check out Bens article on How to Create a Custom Task Sequence for some other great hints and tips on Deployment 4 Beta 3 task sequences and Michael Niehaus is running a great set of blogs on Deployment 4 Beta 3 New Features.

New Deployment Forum Site...

ricsmith — Tue, 18 Sep 2007 12:44:00 GMT

Deployment Forum is a new community Web site devoted to IT professionals deploying Windows. Myself and fellow MCS blogger Ben Hunter, as well as MCS architect Steve Campbell have taken up residency in the MVP section with a selection of the industry's best deployment specialists and we will all be adding content to the Deployment Forum. The site is run by Jerry Honeycutt, a well respected writer, speaker, and technologist who has written more than 30 technology books and hundreds of technical articles and white papers.

You find Deployment Forum at: http://www.deploymentforum.com

Deployment 4 Beta 3 Released

ricsmith — Mon, 17 Sep 2007 11:39:00 GMT

The BDD team have announced that Deployment 4 (the code name for the next version of Business Desktop Deployment (BDD) 2007) has been released as BETA 3 and unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. Previously referenced as BDD.Next and Windows Server Deployment (WSD), Deployment 4 adds integration with recently released Microsoft deployment technologies to create a single path for image creation and deployment, including:

System Center Configuration Manager 2007 Operating System Deployment
Windows Automated Installation Kit
Windows Deployment Services with new multicast technology
Application Compatibility Toolkit 5.0
User State Migration Tool 3.0.1
Windows Server 2008 Server Manager for automated server role definition (coming soon)

Deployment 4 Beta 3 combines the guidance and toolset from previous releases of Business Desktop Deployment and Beta releases of Windows Server Deployment. This release continues to support Zero Touch Installation (ZTI) of desktop operating systems using Systems Management Server (SMS) 2003 with the Operating System Deployment Feature Pack and adds new deployment and task sequencing capabilities for desktops and servers using System Center Configuration Manager 2007. Deployment 4 also continues to provide Lite Touch Installation (LTI) support without infrastructure requirements and adds capabilities for Windows Server 2003 and pre-release versions of Windows Server 2008.

New features in Deployment 4 Beta 3

Microsoft System Center Configuration Manager 2007 support, with the following features:
- Full support for Windows Vista, Windows XP, and Windows Server 2003 deployments with Deployment 4 and Configuration Manager 2007.
- Complete integration into the Configuration Manager 2007 admin console and task sequencing capabilities.
  - Quick start Configuration Manager 2007 operating system deployments using one wizard to create needed task sequences and packages.
  - Extends the Configuration Manager 2007 task sequencing capabilities with new actions.
- Feature parity with BDD 2007 and SMS 2003, including dynamic package installation, automatic determination of state store location, computer backup, database settings.
Lite Touch Installation (LTI) support for Windows Server 2008:
- Support for deploying Windows Server 2008 Beta 3 and potentially RC0 (to be verified after RC0 release), including support for Server Core installation options. (Windows Server 2008 TAP customers only.)
Lite Touch Installation (LTI) enhancements:
- Enhanced disk and network interface cards (NICs) configuration options, including support for static TCP/IP configuration.
- Design changes to ease the migration from LTI to Configuration Manager 2007.
- Support for multiple task sequence templates. New sample templates include:
  - Client template: Windows Vista, Windows XP
  - Server template: Windows Server 2003, Windows Server 2008
  - Replace scenario template
- Ability to invoke web service calls Support for web service calls from rules
  - Web services can be invoked as part of the rules processing performed by Deployment 4, using new rules that can be defined in CustomSettings.ini.
- Support for side-by-side installation with Deployment 4 and BDD 2007 installed on the same machine.
Lite Touch Installation (LTI) multicast support:
- Deployment Workbench supports multicast transmission of operating system images when performing LTI deployments from Windows Server 2008 servers that are running Windows Deployment Services.

Where to Find Deployment 4 Beta 3

Deployment 4 Beta 3 is available as an open beta download.

To join Deployment 4 beta 3 program, follow these steps:

Visit the Microsoft Connect Web site (http://connect.microsoft.com).
Click Invitations on the Connect menu.
You will need to sign in using a valid Windows Live ID before you can continue to the Invitations page.
Enter your Invitation ID in the box. Your invitation ID is: BDDP-QMYH-VWTH
Click Go.
If you have not previously registered with Microsoft Connect, you might be required to register before you continue with the invitation process.
To download Deployment 4, click Download Now.

Great work from the team getting this release out...

How drivers are added to Windows PE and Windows Vista during an unattended installation

ricsmith — Wed, 15 Aug 2007 15:15:00 GMT

My MCS colleague and top deployment gent - Mark Aslett has put together a handy process list for how device drivers are added to Windows PE and Windows Vista during deployment. The example below assumes than an unattend.xml file is being used to specify the location of drivers in both the windowsPE pass and the offlineServicing pass of the unattend.xml file.

If peimg is used to inject drivers directly into an offline Windows PE image then this fully installs the drivers, i.e. it performs the registry load, hardware ID and service information reflection, etc, and does not significantly delay the Windows PE boot or Vista deployment times.

BDD 2007 gets around most of the issues around deployment time identified above. When BDD creates the Windows PE boot image it will add any drivers that you specify at image creation time, so there is no need to use the windowsPE pass (or peimg to add drivers directly). BDD 2007 uses the offlineServicing pass for driver injection avoiding the bulk of the delays. It also has the added benefit of only copying across the drivers required instead of the entire driver store.

Big thanks to Mark for sharing his findings...

General Purpose CustomSettings.ini

ricsmith — Thu, 02 Aug 2007 16:11:00 GMT

One thing that seems to stump a number of people with BDD 2007 is using the CustomSettings.ini file (accessible via the Rules tab) to automate the deployment wizards. The usual issues are around differing language settings for Windows XP and Windows Vista, as well as turning off and on the relevant wizards.

The customsettings.ini file below is a general purpose one that I tend to use as the starting point for most engagements - it has most of the wizard entries (currently set to NO so that they all show) as well as the UK specific language settings for Windows XP and Windows Vista and UK time zone - for the languge settings, just comment out the ones not used (Windows Vista or Windows XP) and turn off the wizards you dont need - remember that any wizards turned off usually need additional parameters to be entered in customsettings.ini for the options they are requesting...

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y

SkipApplications=NO
SkipAppsOnUpgrade=NO
SkipProductKey=NO
SkipDeploymentType=NO

SkipDomainMembership=YES
JoinWorkgroup=WORKGROUP

SkipAdminPassword=NO
AdminPassword=P@ssw0rd

SkipLocaleSelection=YES

; VISTA LOCALE SETTINGS
KeyboardLocale=en-gb
UserLocale=en-gb
InputLocale=0809:00000809

; XP LOCALE SETTINGS
;InputLocale=0809:00000809
;UserLocale=0809:00000809

SkipTimeZone=YES
TimeZone=85
TimeZoneName=GMT Standard Time

SkipCapture=NO
DoCapture=NO

SkipUserData=NO
UserDataLocation=NONE

Addational information on these settings can be found in the Deployment Configuration Guide located in the documentation directory included with BDD 2007 (usually Program Files\BDD 2007\Documentation)

Multiple Partitions in BDD 2007

ricsmith — Mon, 23 Jul 2007 00:37:00 GMT

Have had a couple of requests to cover creating multiple partitions using BDD 2007. By default BDD 2007 creates a single partition (C:) that then builds out with your required OS and applications via the task sequencer. The partition and format information is not done by the unattend.xml file (WinPE section) as you might expect, but via ZTIDiskpart.wsf. This script uses ZTIDiskpart.txt to describe how the drive should be wiped, re-partitioned and formatted.

The default ZTIDiskpart.txt use DiskPart commands and looks like this:

select disk 0

clean

create partition primary

assign letter=c:

active

exit

In the default settings, the first disk (disk 0) is selected and then cleaned (wiped). A primary partition is then created (using all available space) and assigned drive letter C: The partition is then set as active. ZTIDiskpart.wsf takes care of formatting this single partiton.

To have the ZTIDiskpart.wsf script apply different settings (in this case - create two partitons on the same disk) then we can edit ZTIDiskpart.txt as follows:

select disk 0

clean

create partition primary size=20000

assign letter=c:

active

create partition primary

assign letter=d:

format FS=NTFS QUICK

exit

In this example, the first disk is selected (disk 0) and cleaned as it was in the default script. A primary partition of 20GB is then created (specified in MBs) assigned letter C: and made active. A second partition is then created (by not specifying a size on this second entry, all remaining available space is used) and assigned letter D: This partition is then formatted with NTFS using the QUICK switch (ZTIDiskpart.wsf will take care of formatting the C: drive, however it won't format the second partition, so we include a command for this in ZTIDiskpart.txt)

There is however a gotcha...The allocation of drive letters from within the Windows PE environment doesn't carry over to the installed operating system if you are trying to create partitons on different physical disks. When the operating system has finished installing, the disk letters can be out of sync. To enable the ZTIDiskpart.wsf script to correctly add drive letters and create two partitions on different disks (usefull if using BDD 2007 to create server builds), use the

Select disk 0

Create partition primary

Assign letter=c:

Active

Select disk 1

Create partition primary

Assign

Exit

The key to this working is that no letter is assigned to the second partition (that will be created on the 2nd disk). When the operating system starts you will find that D: will be assigned to the second disk by the OS.

I am greatful (as ever) to Ben Hunter and Michael Niehaus for their input and guidance :-)

Useful Registry Changes During Build Creation/Image Deployment

ricsmith — Tue, 17 Jul 2007 16:30:00 GMT

As I have worked with different customers, a number of common requests often pop up for changes during build creation on deployment. For Windows XP deployment, I built up a library of VB scripts that carried out most of the customisations that I required (and were run either as part of the image creation process - using BDD, or as part of the deployment process - as post deploy actions)

With Windows Vista, I have started to build up the same sort of library and have put together a group of setting changes that can be used in reg files, batch files or VB scripts for making automated changes during image build or image deployment. Some of these entries are from my own deployment projects, whilst others are from Microsoft colleagues like Ben Hunter, Jon Bennett and Michael Murgolo to whom I wish to express my gratitude.

So here is my current list of tweaks...

;Adjust the system tray icons - 0 = Display inactive tray icons
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer]
"EnableAutoTray"=dword:00000000

;Clear Most Frequently Used items
[-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{75048700-EF1F-11D0-9888-006097DEACF9}]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\UserAssist\{75048700-EF1F-11D0-9888-006097DEACF9}]
@=""

;Show/Hide desktop icons
; Internet Explorer = {871C5380-42A0-1069-A2EA-08002B30309D}
; User's Files = {450D8FBA-AD25-11D0-98A8-0800361B1103}
; Computer = {20D04FE0-3AEA-1069-A2D8-08002B30309D}
; Network = {208D2C60-3AEA-1069-A2D7-08002B30309D}

; 0 = Display
; 1 = Hide

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\HideDesktopIcons]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\HideDesktopIcons\NewStartPanel]
"{871C5380-42A0-1069-A2EA-08002B30309D}"=dword:00000001
"{450D8FBA-AD25-11D0-98A8-0800361B1103}"=dword:00000000
"{20D04FE0-3AEA-1069-A2D8-08002B30309D}"=dword:00000000
"{208D2C60-3AEA-1069-A2D7-08002B30309D}"=dword:00000000

;Add "Explore From Here" to the context menu
[HKEY_CLASSES_ROOT\Folder\shell\fromhere]
@="Explore from &Here"
[HKEY_CLASSES_ROOT\Folder\shell\fromhere\command]
@="explorer.exe /e,/root,/idlist,%I"

;Add a Search Provider to the START MENU (example)
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes\Google]
"DisplayName"="Google"
"URL"="http://www.google.com/search?q={searchTerms}&rls=com.microsoft:{language}&ie={inputEncoding}&oe={outputEncoding}&startIndex={startIndex?}&startPage={startPage}"

;Resort the Start Menu
[-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder]

;Disable Menu Delay
[HKEY_CURRENT_USER\Control Panel\Desktop]
"MenuShowDelay"="0"

;Add the Registry Editor to the context menu
[HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\regedit]
@="Re&gistry Editor"
[HKEY_CLASSES_ROOT\CLSID\{20D04FE0-3AEA-1069-A2D8-08002B30309D}\shell\regedit\command]
@="regedit.exe"

;Customise Windows Vista Shutdown Speed
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control]
"WaitToKillServiceTimeout"=20000

;Increase NTFS System Peformance by disabling NTFS Last Access Update and 8.3 Creation
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"NTFSDisableLastAccessUpdate"=1
"NTFSDisable8Dot3NameCreation"=1

;Turn Off System Beeps
[HKEY_CURRENT_USER\Control Panel\Sound]
"Beep"=No

;Disable Welcome logon screen & require CTRL+ALT+DEL
reg add "hklm\Software\Microsoft\Windows NT\CurrentVersion\Winlogon" /v LogonType /t REG_DWORD /d 0 /f
reg add "hklm\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v DisableCAD /t REG_DWORD /d 0 /f

;Interactive logon: Do not display last user name
reg add "hklm\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" /v dontdisplaylastusername /t REG_DWORD /d 1 /f

;Enable Remote Desktop
reg add "hklm\system\currentcontrolset\control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f

;Allow connections from computers running any version of Remote Desktop (less secure)
reg add "hklm\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v UserAuthentication /t REG_DWORD /d 0 /f

;Use simple file sharing - 0 = unchecked, 1 - checked
reg add "hklm\SYSTEM\CurrentControlSet\Control\Lsa" /v ForceGuest /t REG_DWORD /d 0 /f

;Disable Automatic Updates
reg add "HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU" /v NoAutoUpdate /t REG_DWORD /d 1 /f

;Set the Screen Saver Settings
reg add "hku\.DEFAULT\Control Panel\Desktop" /v ScreenSaveActive /t REG_SZ /d 1 /f
reg add "hku\.DEFAULT\Control Panel\Desktop" /v ScreenSaverIsSecure /t REG_SZ /d 1 /f
reg add "hku\.DEFAULT\Control Panel\Desktop" /v ScreenSaveTimeOut /t REG_SZ /d 900 /f
reg add "hku\.DEFAULT\Control Panel\Desktop" /v SCRNSAVE.EXE /t REG_SZ /d "%SystemRoot%\System32\YOUR_FILE.scr" /f

;Set the Desktop Wallpaper
reg add "hku\.DEFAULT\Control Panel\Desktop" /v Wallpaper /t REG_SZ /d "%SystemRoot%\Web\Wallpaper\YOUR_FILE.bmp" /f
reg add "hku\.DEFAULT\Control Panel\Desktop" /v WallpaperStyle /t REG_SZ /d "2" /f
reg add "hku\.DEFAULT\Control Panel\Desktop" /v TileWallpaper /t REG_SZ /d "0" /f

BDD Lite Touch and Zero Touch Lab Recommendations

ricsmith — Tue, 26 Jun 2007 19:46:00 GMT

So - I get asked a lot about how to set up a test lab or Proof of Concept environment for Lite Touch and Zero Touch. Working with my colleages in the MCS UK desktop team, specifically Mark Aslett and Adam Shepherd, we have developed a rough guide to a lab design that works for us that I thought I would share for discussion...The lab environment looks like this -

Infrastructure Server

Requirement	Why?
Windows Server 2003 R2	To fully support Windows Vista, in particular some group policy functionality and to test the DFS-R replication of images, domain controllers should be Windows Server 2003 R2.
Active Directory	Required to authenticate users accessing the Windows DS, RIS, SMS and BDD 2007 servers. Additionally Windows DS servers must be a member of an Active Directory domain.
DNS	DNS name resolution must be possible in the lab environment for Active Directory to function and for clients to locate network resources.
DHCP	During the development process clients will boot to the network to load Windows PE, this will not work without DHCP.

Build Server

Requirement	Why?
Windows Server 2003 R2	Recommended to host the other server applications, specifically Windows DS and RIS.
RIS	Prerequisite to installing Windows DS and used for legacy testing and OSD boot image delivery.
Windows Deployment Services	Should be installed in mixed mode to support legacy images such as the SMS OSD boot CDs as well a Windows PE 2.0 boot images used by BDD 2007 and Windows Vista deployments.
Windows Automated Installation Kit	Provides a number of tools required by BDD 2007 including System Image Manager, ImageX and Package Manager.
BDD 2007	Used as a repository for all build components, the generation of the reference build and the configuration of the ZTI scripts.
SQL 2005 Express	Used to test role based deployments and configurations that are moved to the deployment server

Deployment Server

Requirement	Why?
Windows Server 2003 R2	Recommended to host the other server applications.
SQL Server 2005 SP1	SQL is required by SMS 2003 and role based deployments using the BDD 2007 database. Can also be used for ACT database support. SQL 2005 SP1 should be the minimum service pack used.
SMS 2003 SP3	SMS is required to support OSD captures and deployments; it is also used as the mechanism for managing the replication of images and applications. Service Pack 3 is the update for SMS that supports Windows Vista and the latest OSD Feature Pack Update.
SMS OSD Feature Pack Update	Required to allow for operating system images to be captured and deployed via the SMS infrastructure.

The three server installation can be consolidated to two servers if Zero Touch is not required, but we find that this design works well when developing build and deployment designs in many customer environments.

User Account Control - What you need to know from a deployment perspective

ricsmith — Tue, 26 Jun 2007 19:24:00 GMT

I've had a couple of emails from people attempting to use their own admin accounts to carry out the build process and hitting User Account Control (UAC) issues. User Account Control is a core security feature of Windows Vista that fundamentally changes the way users will use the operating system. By default UAC helps protect against malware by running all users as Standard Users (including Administrators). When an application or user requires elevated privileges to complete a task, a consent prompt is presented to the user. The user can then subsequently (given the proper rights) elevate permissions in order for the application to complete the task. Enhancements in Windows Vista and UAC now allow Standard Users to perform more common tasks then before, opening up the possibility of removing administrative privileges from end users. The table below identifies some of the new stadard user tasks and the tasks that require admin elevation.

Standard User Tasks

Requires Administrator Elevation

Windows Vista

Ø Establish a Local Area Network connection

Ø Establish and configure a wireless connection

Ø Modify Display Settings

Ø Users cannot defragment the hard drive, but a service does this on their behalf

Ø Play CD/DVD media (configurable with Group Policy)

Ø Burn CD/DVD media (configurable with Group Policy)

Ø Change the desktop background for the current user

Ø Open the Date and Time Control Panel and change the time zone

Ø Use Remote Desktop to connect to another computer

Ø Change user's own account password

Ø Configure battery power options

Ø Configure Accessibility options

Ø Restore user's backed-up files

Ø Set-up computer synchronization with a mobile device (smart phone, laptop, or PDA)

Ø Connect and configure a Bluetooth device

Ø Install and uninstall applications

Ø Install a driver for a device (E.G. a digital camera driver)

Ø Install Windows updates

Ø Configure Parental Controls

Ø Install an ActiveX control

Ø Open the Windows Firewall Control Panel

Ø Change a user's account type

Ø Modify UAC settings in the Security Policy Editor snap-in (secpol.msc)

Ø Configure Remote Desktop access

Ø Add or remove a user account

Ø Copy or move files into the Program Files or Windows directory

Ø Schedule Automated Tasks

Ø Restore system backed-up files

Ø Configure Automatic Updates

Ø Browse to another user's directory

The BDD 2007 process uses the in-built administrator account that is re-enabled by the build unattend file (shown below) that BDD 2007 generates when you set up a new build. This account is used to carry out the required tasks when Windows Vista has finished it's initial installation. This account is exempt from UAC.

            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Description>EnableAdmin</Description>
                    <Order>1</Order>
                    <Path>cmd /c net user Administrator /active:yes</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>EnableAdmin_ploc</Description>
                    <Order>2</Order>
                    <Path>cmd /c net user Administrator_ploc /active:yes</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>UnfilterAdministratorToken</Description>
                    <Order>3</Order>
                    <Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>

Issues arrise if you try to use your own Administrator account generated as part of the Windows Vista install process - these accounts, even though part of the local Administrators group are not exempted from UAC, so running particular tasks and scripts will cause the UAC dialogues to appear and interupt any automated process you wish to run. Always try to use the built in Administrator account for all build functions