Seems like my error (the issue due to Windows Media Player sharing being enabled) and many other known issues are discussed in this article.

http://technet.microsoft.com/en-us/library/dd349350(WS.10).aspx

hope it helps you out…

We will configure WDS to use PXE boot, use SQL Server to retrieve the computer name and have some beer afterwards.

PXE Boot

First configure a DHCP scope to serve the clients with an IP address. Then install the Windows Deployment Service (WDS) role on your MDT box, and configure WDS. I like to have a PXE delay of 3 seconds and I’m running DHCP on the same server as WDS. So I need to check ‘Do not listen on port 67’ and ‘Configure DHCP option 60 to indicate that this server is also a PXE server’.

Now we have to import the WinPE boot images, previous generated by MDT, into WDS:

Browse to the Boot-folder in the Deployment Share, and select the LiteTouch-wim-file(s) (I’m importing the x64 version only, as I don’t use Windows 7 x86 for now):

Boot your client machine and hit F12 to boot into PXE, or choose boot from network card in the BIOS.

We still have to choose a computer name during deployment:

Using MS SQL Server (Express) you can fully automate this!

Preparing SQL Server

In my test lab I will use SQL Express 2008 SP1. Open SQL Server Configuration manager, set SQL Server Browser to automatic and start the service:

Enable Named Pipes in SQL Server Configuration Manager:

Restart the SQL Server service:

Start SQL Management Studio and create a Security Login (I’ll use my MDT domain-join-user):

Add the db_datareader and db_datawriter permissions for the domain\svc-join user to the MDT database:

Create a database

Open the Deployment Workbench and Create a new database:

We have finished creating the MDT database.

Now we have to configure CustomSettings.ini before we can use the database:

By clicking Configure Database Rules, you actually adding extra lines to CustomSettings.ini in order to make a connection to the database. Select what you need:

Take a look at your CustomSettings.ini file (by right-clicking the DeploymentShare > Properties > Rules tab):

You can modify CustomSettings.ini further. To join a domain for example:

SkipDomainMembership=YES
JoinDomain=thedspot.local
DomainAdmin=svc-join
DomainAdminDomain=thedspot.local
DomainAdminPassword=*
MachineObjectOU=OU=Computers,OU=Unmanaged,DC=thedspot,DC=local

Obtaining Computer names from the SQL database

Hit Computers > New to add a MAC address and corresponding computername (OSDComputerName):

Our LiteTouch deployment succeeded:

The computer name was retrieved from the database and domain join was successful.

Please find other parts here:

Windows 7 Lite Touch installation with MDT 2010 – Part 1

Windows 7 Lite Touch installation with MDT 2010 – Part 2

Windows 7 Lite Touch installation with MDT 2010 – Part 4

The Microsoft Application Compatibility Toolkit (ACT) version 5.5 contains the necessary tools and documentation to evaluate and mitigate application compatibility issues before deploying Windows 7, Windows Vista®, a Windows Update, or a new version of Windows® Internet Explorer® in your environment.

1. Prerequisites

Before installing the ACT you need to have an SQL server installed. These are the SQL server versions you can use:

• SQL Server 2005
• SQL Server 2005 Express
• SQL Server 2008
• SQL Server 2008 Express

The client OS you can install the ACT on are all the client OS between Windows XP SP2 and Windows 7. The server OS needs to be at least Windows Server 2003 SP2.

Last but not least you also need the .NET Framework 2.0 or newer.

2. Installation of the ACT 5.5

When launching the installer of the ACT (Application Compatibility Toolkit.msi) a wizard starts and you need to go through the 6 steps. The wizard will ask you some questions about the SQL server database, log files, etc.

3. Different topologies

4. The Application Compatibility Manager (ACM)

This is the main tool you use to manage the DCP’s (Data Collector Package) and all the retriever information from all the machines you ran the ACT on. The ACT is dependent from an agent (called a DCP) which you create in the ACM. In the following screenshots you can see how to create such a Data Collector Package.

Once you saved the msi-file you can start to distribute the package among all the computers you want the ACT to retrieve the information from. There are several ways to do this:

• Put the file on the network share
• Put the file on the local drive of the computer
• Put the file in a GPO
• Put the file in a startup/logon script.

If the file has been run on a computer you’ll receive the information in the ACM. In the following set of screenshots the DCP will be run on a local machine and outputting the data to the same machine.

When the output is available in the ACM we can analyze all the information:

• Which programs are installed on the machine(s)?
• Which computers have been scanned?
• Which devices are discovered during the process?

Be aware:

The “ACT Log Processing Service” needs to be started otherwise there will be no output shown in the ACM.

The two configuration files we need to modify are CustomSettings.ini and Bootstrap.ini.  Use this method to view and modify them; In DeploymentWorkBench right-click your Deployment Share and choose Properties and hit the Rules tab. This is the CustomSettings.ini file. To view and modify Bootstrap.ini hit the Edit Bootstrap.ini-button at the bottom.

CustomSettings.ini file we will be using:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipPackageDisplay=NO
SkipApplications=NO
SkipAppsOnUpgrade=YES
SkipCapture=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBDDWelcome=YES
SkipAdminPassword=YES
AdminPassword=Pa$$w0rd
SkipDeploymentType=YES
DeploymentType=NEWCOMPUTER
SkipUserData=YES
SkipDomainMembership=YES
SkipComputerName=NO
ComputerName=PC-xxxx
SkipTimeZone=YES
KeyboardLocale=0813:00000813
UserLocale=nl-be
TimeZone=105
TimeZoneName=Romance Standard Time
_SMSTSOrgName=The D Spot
SkipBitLocker=YES
SkipSummary=NO

You can adapt these settings to your needs. For example join a domain, skip the summary and so one.

Our Bootstrap.ini file:

[Settings]
Priority=Default

[Default]
SkipBDDWelcome=YES
DeployRoot=\\Servername\DeploymentShare$
UserDomain=DOMAINNAME
UserID=SERVICEACCOUNTNAME
UserPassword=PASSWORD
KeyboardLocalePE=0813:00000813

This file will be injected in the WinPE ISO file, to connect to the Deployment Share. After a modification to this file you need to perform a Deployment Share Update. To regenerate the LiteTouchPE_x64.iso & LiteTouchPE_x86.iso files.

With these configuration files in place, our LTI will ask for a Task Sequence and Computername only.

If your environment has computer names based on MAC Addresses you can get the computer name out of a SQL Database. But in most companies a technician will choose the computer name based on the label attached on the computer case, I choose this just to have an example.

Next time we will go further with user data migration.

Please find other parts here:

Windows 7 Lite Touch installation with MDT 2010 – Part 1

Windows 7 Lite Touch installation with MDT 2010 – Part 3

Windows 7 Lite Touch installation with MDT 2010 – Part 4

Microsoft Deployment Toolkit (MDT) is a Solution Accelerator for operating system and application deployment. MDT 2010 supports deployment of Windows 7 and Windows Server 2008 R2 in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP.

We will start our MDT 2010 series with a basic Windows 7 Lite Touch installation (LTI). In this first article we will setup an easy to understand deployment of Windows 7. In future articles we will customize our LTI deployment to understand all possible options available in MDT 2010.

Prerequisites:

You must be a member of a domain and have a DHCP server in place to feed our client machines with IP addresses. Prerequisites tools are MDT 2010 and Windows Automated Installation Kit (AIK) for Windows 7, available at Microsoft for free. After installing both tools on our client computer we are ready to begin.

Start the Deployment Workbench.

You can find it under All Programs –> Microsoft Deployment Toolkit –> Deployment Workbench.

First we need to create a Deployment Share:

Right-click on Deployment Shares and choose New Deployment Share.

Choose a path where all data will be stored. This folder must be on a NTFS partition. I choose X:\DeploymentShare.

Next, specify a sharename and description for the store:

DeploymentShare$ is the sharename and MDT Deployment Share is the description. I leave both default settings.

Next step we need to choose whether we want to be able to capture an image after deploying it to a computer. We leave this option enabled, so we can capture an reference image later.

We leave options Allow Admin Password and Allow Product Key disabled. Last screen is the summary, click next to start creating of the Deployment Share. Close the wizard to return the our Deployment Workbench.

Installation complete, we’re ready to configure our newly create deployment share.

First add Windows 7 setup files to the deployment share by right-click Operating Systems and choose Import Operating System.

Choose Full set of source files, specify the Windows 7 DVD so all files can be copied to the deployment share:

Choose a directory name, where to store this operating system in the deployment share:

At the Summary screen we get an overview of what we have created, give it a quick look and click Next to begin the import process.

We’re done importing the Windows 7 DVD.  We can add applications and drivers as we like, but in this basic article I will leave it for future posts.

Now we need to create a Task Sequence (TS). Task sequences provide the mechanism for performing multiple steps or tasks on a client computer at the command-line level without requiring user intervention. We need to create a TS for deploying our Windows 7 to a virtual bare-metal computer. Right-click Task Sequences and choose New Task Sequence.

Choose an ID, and a Name for the Task Sequence.

Select Standard Client Task Sequence and select the operating system to deploy (we have only one OS imported yet).

Select Do not specify a product key, and fill in the OS Settings.

Last step is to specify a local admin password for the client computer. Next, Finish to create the Task Sequence.

After creating our TS we need to update the deployment share by right-click our deployment share and choose Update Deployment Share.

The update process does several things. Like the creation of the WinPE iso files, needed to boot our client to start deployment. These iso files are stored in the \Boot directory of the deployment share.

Now we are ready to perform the operating system installation. I’m using a Hyper-V virtual machine as a target machine. But you can burn the ISO to CD or copy it to a bootable USB drive to install a physical machine as well.

I create a new virtual machine in Hyper-V. And choose to install an OS from image and specify the file LiteTouchPE_x86.iso created earlier with MDT (in the Update process). So it will boot from the ISO file.

Fire up the virtual machine:

As you can see the default keyboard layout is set to United States, and we need to specify credentials to the deployment share. These and many more can be preconfigured in configuration files. Think about the winnt.sif file used in Windows XP unattended setups. It’s not like it, but it will come close.

To proceed the installation choose a Task Sequence. As we have only one, we can’t miss. Choose a computername and click Next.

You can join the domain or choose to join a workgroup and restore files using USMT.

All these settings need to be modified. I made screencaps of the default settings, so you can see what we can preconfigure with the configuration files. In order make an installation with only the minimal user interaction.

The installation has started.

Installation complete.

In the next article we will modify the MDT configuration files, to make this deployment less interactive and more unattended.

Please find other parts here:

Windows 7 Lite Touch installation with MDT 2010 – Part 2

Windows 7 Lite Touch installation with MDT 2010 – Part 3

Windows 7 Lite Touch installation with MDT 2010 – Part 4

Earlier this week, Microsoft released a hotfix rollup that will solve these problems for good.

to remediate these problems, you have to install the hotfix on all site servers in your environment.

If your environment is not yet in native mode, the clients will also need to have the hotfix applied.

I guess you would all use SCCM to have that fix distributed, don’t you?

More Info on http://support.microsoft.com/Default.aspx?kbid=974236

We will explain a bare metal Windows 7 deploy, as well as an upgrade path from Windows XP.