anyweb

good point, we will try as much as possible to do this in the future !

you'd have to combine the logic of all three task sequences into one ts, and give the technician some choices in the beginning in order to start the right one, that can be achieved via MDT 2010 Update 1 udi or a front end HTA the task sequence will then have groups inside it to detect what variable you set via the choices in your front end and take appropriate action cheers niall

thanks for sharing

Some of you probably noticed a new download showed up today: The Windows® Automated Installation Kit (AIK) for Windows® 7 SP1 http://www.microsoft.com/downloads/en/details.aspx?FamilyID=696dd665-9f76-4177-a811-39c26d3b3b34 Be sure to read the “readme” that goes along with this at: Windows Automated Installation Kit for Windows 7 Readme http://technet.microsoft.com/en-us/library/dd349350(WS.10).aspx A quick Q&A that I assembled from information in this readme and our own MDT testing: Q: Do I have to use this to deploy Windows 7 SP1 and Windows Server 2008 SP1? This supplement is optional. If you do not need to modify the SP1 boot.wim and winre.wim files, you can continue to use the Windows 7 RTM tools, including WinPE 3.0, without installing this supplement. (So MDT and ConfigMgr can deploy WIndows 7 SP1 just fine using Windows PE 3.0.) Q: How do I install this on a machine currently running the Windows 7 RTM version of Window AIK? There’s no installer provided with this. You need to extract the contents of the download and then XCOPY the files over the top of your existing Windows AIK installation. See the details in the readme. Q: What’s changed in this Windows AIK supplement? * The number in the Version registry value is 3.1 to reflect the new Windows PE version. * The Windows PE 3.1 base image contains Remote Network Driver Interface Specification (RNDIS) binaries. These binaries are also available for Windows PE 3.0 as a hotfix. For more information, see Knowledge Base Article ID: 979265 (http://go.microsoft.com/fwlink/?LinkId=206678). * Windows PE 3.1 includes 802.1x binaries as an optional component. The file name of this package is WinPE-Dot3Svc.cab. This optional component is also available for Windows PE 3.0 as a hotfix. For more information, see Knowledge Base Article ID 972831(http://go.microsoft.com/fwlink/?LinkId=206072). * The Windows PE 3.1 base image contains fixes that are related to 4k/512e drive support. These fixes are also available for Windows PE 3.0 as a hotfix. For more information, see Knowledge Base Article ID: 982018 (http://go.microsoft.com/fwlink/?LinkId=206679). * Windows PE 3.1 includes bug fixes that are related to the Windows PE version that is included with Windows 7 SP1. Q: Does Windows 7 SP1 and Windows PE 3.1 work with MDT 2010 Update 1? Yes, this is fully supported. (There is one small issue involving Windows 7 SP1, Windows PE 3.1, and having Windows RE included in your MDT-generated Lite Touch boot images, but if you don’t mind Windows RE not being there, you don’t need to worry about this.) Q: Does Configuration Manager 2007 SP2 support Windows 7 SP1 and Windows PE 3.1? The Configuration Manager team is still testing Windows 7 SP1 and Windows PE 3.1, so this is unsupported until that testing is completed. Q: Does this supplement include the recently-released USMT 4 update for Office 2010 support? No, you need to download and apply that one (http://blogs.technet.com/b/mniehaus/archive/2011/02/02/usmt-4-0-support-for-office-2010.aspx) separately. via > http://blogs.technet.com/b/mniehaus/archive/2011/02/17/windows-aik-for-windows-7-sp1-released.aspx

I would agree with Peter and Lucid, do Build and Capture from virtual machines, keep the image hardware agnostic, add all your drivers to the deploy task sequence based on wmi queries, much cleaner and less hassle that said, you could try bios updates and/or newer video drivers from the video card manufacturer..

it will get automatically deleted by default in 7 days, you can change that in Site Maintenance, Tasks, Delete Obsolete Client Discovery Data

hi did you create a Computer Association between source and destination pc's before capturing the data ?

HTAs and Web Services Introducing the windows-noob.com FrontEnd HTA version 1.0 Multipurpose HTA Introducing the BitLocker FrontEnd HTA Multipurpose HTA with BitLocker Support for all three common scenarios, backup, reinstall, new computer [added Jan 2012] HTA frontends for SCCM 2007, HTA Utilities And Frontends What is a HTA ? , where can I get them etc... ? How can I create a boot image with HTA support using MDT Part 1. Create MDT boot image How can I display my HTA Part 2. Displaying the HTA in a Task Sequence How can I Set the Screen Resolution during OSD Using SETRES to set screen resolution Introduction To Web Services What is a Web Service ?, where can I get them etc ? How can I install some Web Services? Installing Web Services Adding values and testing your web service How can I add values and test my web service

If you live in Europe you'll most likely need to deploy some additional languages on top of English Windows 7. To achieve this we can add them at the Build and Capture stage or indeed in our Deploy Windows 7 Enterprise task sequence. All installations of Windows® 7 contain at least one language pack and the language-neutral binaries that make up the core operating system. Licensing requirements state that Windows 7 can include only a single language, with the exception of the Windows 7 Ultimate and the Enterprise editions. These are referred to as single-language editions. However, the Windows 7 Ultimate and Enterprise editions can include multiple language packs. These are referred to as multilingual editions. To see which versions of Windows support Language Packs please review this post on MSDN and scroll down to the Windows 7 editions multilingual support summary. What do I need ? You will need some things in place to add the languages offline, namely MDT 2010 Update 1 integrated into ConfigMgr 2007 SP2 and you'll need to download the Language packs from MSDN. Where can I find Windows 7 Language Packs ? Download the language pack from MSDN which suits your architecture, choose a language other than English (eg: Swedish) then choose the Windows 7 operating system, in the downloads listed you’ll see these:- Windows 7 Language Pack (x64) - DVD (Multiple Languages) 8/6/2009 - 2,200 (MB) Windows 7 Language Pack (x86) - DVD (Multiple Languages) 8/6/2009 - 1,846 (MB) How can I Add Language Packs to ConfigMgr? Language packs are .cab files that you can add to System Center Configuration Manager packages either offline or online. Before adding language packs, however, create a System Center Configuration Manager package that contains one or more language packs. In our example here, we will add language packs using one language per package, so for the Swedish Langauge pack, our SCCM package looks like so:- the Data Source points to the share with our Swedish Language Pack eg:- \\sccm\sources\Windows 7 Language Pack - Swedish and that path contains the following, a sub dr (eg: sv-se) which contains the lp.cab file and nothing more. Note:- All language packs in the same System Center Configuration Manager package are deployed together. If you want to deploy different combinations of language packs, create multiple System Center Configuration Manager packages. Get the Task Sequence Download the following Task Sequence and import it into ConfigMgr. Install Language Pack Offline.XML Let's look closer at this task sequence, First you'll notice that the entire section is separated into a Group, this is to keep things organised and to help you in adding it to your Deploy Task Sequence. Important: This group must be placed in the PostInstall section of your Deploy Task Sequence, and preferably after that Apply Windows Settings and Apply Network Settings Steps, in addition this group must go before the Setup Windows and ConfigMgr steps otherwise the Install Language Pack offline step will fail. Ok let's look at the steps themselves and see what they do. The Swedish sub Group is responsible for installing the Swedish Language pack if a variable called languageValue=Swedish. How you set that variable is up to you, you can set it via a FrontEnd HTA (recommended) or by simply using a Set Task Sequence variable step (before this Group) such as this (not included in the sample task sequence):- Task Sequence Variable: languageValue Value: Swedish If languageValue is determined to = Swedish it then carries out two steps Sets a task sequence variable called OSDUILanguage = sv-SE and then calls the built-in MDT Step, Install Language Packs offline (which references the ZTIpatches.wsf script). This step points to our previously made Swedish Language Package. The actual step takes some minutes as it has to expand lots of files in the cab, and inject them offline (using DISM) into our Windows 7 image. How do we set OSDUILanguage in Windows You'll need to create an Unattend.xml file which specifically mentions the OSDUILanguage variable <UILanguage>%OSDUILanguage%</UILanguage> or use this one which I created earlier. OSD_Variables_added.xml This file must be referenced in the Apply Operating System Image step otherwise the Install Language Pack Offline step will fail as it won't know what variable to set. You can create this unattend.xml file yourself using Windows SIM or use the sample i provide, just remember that the architecture must match the image, and this sample is for 32bit Windows 7 Enterprise (X86). Ok I've done all the steps, now what ? Deploy Windows 7, set the language pack variable either in the Task Sequence or using a HTA, and the end result is that you get your language pack installed as the default language within Windows. The Setup Windows and ConfigMgr step actually inserts our value (sv-SE) in place of our variable in our unattend.xml file so that the following line <UILanguage>%OSDUILanguage%</UILanguage> becomes <UILanguage>sv-SE</UILanguage> which eventually means that your OS is in Swedish. Troubleshooting Notes * use the log files, in particular ztipatches.log which documents what happens when it trys to use DISM to inject the changes * Use at least 1gb ram in your virtual machines otherwise the step will fail to install any language packs (will run out of ram). (1gb for X86 and 1.28 gb for X64) * create the MDT toolkit package the proper way via a Create MDT Task Sequence wizard - why ? see this post After the Install Language Pack Offline step the following will be created in c:\_smstasksequence\ namely:- Packages<dir> ZTIPatches.tmp packageGroups.xml in the Packages directory you’ll have more subdirectories based on how many lp’s you included, one language pack, one dir, 4 language packs in your ConfigMgr Language Package, 4 dirs... you may also see a directory called _smstasksequence\SMSOSD\osdlogs and in there are three files including a log file called BDD_PKGMGR.LOG, analyse it if you are having issues deploying Language packs offline as it will reveal the success or failure of the DISM operations. Unattend.xml changes You can press F8 in WinPE and browse to the locations below and use notepad to examine the changes to the unattend.xml file. Note: The unattend.xml file and/or C:\Windows\Panther\Unattend folder may not appear in your image until directly after the Apply Operating System Image step and the contents of that file depends on whether or not an unattend.xml file was specified in that step. Before the Setup Windows and ConfigMgr step is complete you can monitor c:\windows\panther\unattend\unattend.xml to see what is happening in relation to your modifications taking place or not After the Setup Windows and ConfigMgr step is complete, you’ll see the following has been added to your c:\windows\panther\unattend.xml file. If it is not added or if there are no changes to the %OSD...% variables then something has failed and it's time to troubleshoot. Note: The above locations are during the Windows PE phase. After the Setup Windows and ConfigMgr step is complete it will reboot your computer (unless you have a command prompt open in WinPE), and after that reboot the unattend.xml file will have been removed (by the Setup Windows and ConfigMgr step...). the other values (keyboard layout and so on) are added via separate steps in the Task Sequence which I'll cover in another post. cheers ! niall.

hi all, I've added a new section in Deploying Operating Systems called FrontEnds and Web Services along with some new content to help you in creating your very own FrontEnd. enjoy cheers niall

Step 10. Configure Application Settings Next we need to configure the application settings (Step by Step Guide) , failure to do so will mean the webservice cannot do anything. Open IIS Manager, expand the Webserver Node, expand the Sites Node, expand your Default Web Site, click on the Deployment Webservice Folder/Application (NewWebService) and then double click on the Application Settings Icon on the right side. And enter the appropriate details… The following are configurable:- By default, the webservice will use the configured application pool user for authentication. It requires only a couple of Application Settings to be set: RootServer - The SCCM Root Server SLPServer - One SCCM Server with the SLP Role RootSiteCode - The Root site code For Access to the MDT Database you need to configure at least MDTDBServer - The MDT Database server (with Instance if necessary) MDTDBName - The MDT Database name MDTDBIntegratedSecurity - Set to "True" if you want to use the application pool account for authentication. If set to "False" you need to supply the following two settings MDTDBUser - Username to access the MDT Database MDTDBPassword - Password to access the MDT Database For Active Directory access, you can optionally configure the following Application Settings. This is only necessary, if the application pool user account does not have enough permissions to do execute the required functions, and/or if you need to access a different domain as the application pool User is member of: ADDomain - Domain to query (use either "domain.com" or "DC=Domain,DC=COM" format) ADUsername - Username for authentication ADPassword - Password for authentication You will note i didn't configure any of the MDTDB settings as I'm not using them currently in my environment. Step 11. Test the New Web Service You should now be able to use the Webservice. To test the functionality just open your favourite Browser and point it to http://sccm/NewWebService/ad.asmx- For Active Directory related functions http://sccm/NewWebService/mdt.asmx- For MDT related functions http://sccm/NewWebService/sccm.asmx- for SCCM related functions. Troubleshooting To troubleshoot when things are not working, browse to the LOGS folder of where you installed the Web Service, and you should see Trace, Debug and Info logs, open them in CMTrace to review.

Step 6. Refresh Default Web Site Right click on Default Web Site, click Refresh (if you don’t do this the New web Service will still appear as a folder in IIS instead of as an Application. Step 7. Add Application Pool In IIS Manager, locate Application Pools, right click and choose Add Application Pool, give it a name such as New Web Service and click ok Step 8. Configure Application Pool Now you can configure this Application Pool to use a Different User Account for running your Webservice. To do this Open IIS Manager, expand your Webserver Node and click on Application Pools. Right click your Application Pool on the right side and choose Advanced Settings... In the Process Model area click in the Identity field and then click on the ... Button Choose Custom account and click on Set... Step 9. Configure the Webservice to use the application Pool Open IIS Manager, expand your Webserver node and Sites node, expand your Default Web Site node, Right click on the NewWebService folder and choose Manage Application - Advanced Settings... In the General area click into the Application Pool field and then click on the ... Button choose the appropiate Application Pool (called New Web Service) click OK, OK

In this example we will install Maik Kosters excellent web services (7.2) on our SCCM server (which is already running IIS). Installing the Web Service Step 1. Download the files from this codeplex site Step 2. Extract the content of the zip file into a folder on your Webserver Step 3. Copy the contents to your webserver root, rename the folder to something like NEWWebservice Step 4. Add the folder as a new Application to IIS (Step by Step Guide IIS 6 | Step by Step Guide IIS 7), Start IIS manager, expand Sites, right click on Default Web Site and choose Add Application. Step 5. Specify an "Alias" (the name you would like to use to access the Webservice, lets call it NewWebService) and the physical path to the extracted content of the webservice eg: c:\inetpub\wwwroot\NEWWebService At this point the webservice is accesible (in internet explorer http://sccm/newwebservice/sccm.asmx ) but you cannot do anything with it (as it doesn’t know how to communicate with your SCCM site…) until you’ve done some final configuration…

Adding paramters to a webservice. Ok now that the webservice is working, lets add two parameters (name and age) that we can pass to our webservice, go back and edit the code in Visual Studio. Change this using System; using System.Collections.Generic; using System.Web; using System.Web.Services; namespace windows_noob_webservice { /// <summary> /// Summary description for Service1 /// </summary> [WebService(Namespace = "http://windows-noob.com/")] [WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)] [system.ComponentModel.ToolboxItem(false)] public class Service1 : System.Web.Services.WebService { [WebMethod] public string HelloWorld() { return "Hello World"; } } } To this using System; using System.Collections.Generic; using System.Web; using System.Web.Services; namespace windows_noob_webservice { /// <summary> /// Summary description for Service1 /// </summary> [WebService(Namespace = "http://windows-noob.com/")] [WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)] [system.ComponentModel.ToolboxItem(false)] public class Service1 : System.Web.Services.WebService { [WebMethod] public string HelloWorld() { return "Hello World"; } [WebMethod] public string HelloWorld2(string name) { return "Hi " + name; } [WebMethod] public string HelloWorld3(string name, string age) { return "Hi " + name + " your age is " + age; } } } Build the code (compile it) and you can simply copy the DLL found in bin to your webserver to test the new functions. Copy the dll to the BIN folder of your current webservice on your server… Copy the new web service operation to your CustomSettings.ini file and update your MDT Files package once done. Once done, test the web service, Click on HelloWorld3 Input some values into the fields:- And click on Invoke, the result is ouput Testing webservices from WinPE We will now Create a WSF script file called helloworld.wsf, containing the following lines <job id="MDTMenu_helloworld"> <script language="VBScript" src="..\ZTIUtility.vbs"/> <script language="VBScript" src="..\ZTIDataAccess.vbs"/> <script language="VBScript"> Dim oService Dim oXML oEnvironment.Item("testing") = Wscript.Arguments.Named.Item("helloworld") Set oService = New WebService oService.IniFile = "CustomSettings.ini" oService.SectionName = "helloworld" Set oXML = oService.Query If oXML Is Nothing Then oLogging.CreateEntry "Unable to call HelloWorld web service.", LogTypeWarning WScript.Echo "Not Found" & vbcrlf Else oXML.setProperty "SelectionNamespaces", "xmlns:wn='http://windows-noob.com/'" WScript.Echo oXML.SelectSingleNode("wn:string").Text End If </script> </job> Save it in the wnb subfolder of your MDT Files scripts directory. (eg: scripts\wnb) Next create a new file called name_age.wsf, Paste in the following:- <job id="MDTMenu_name"> <script language="VBScript" src="..\ZTIUtility.vbs"/> <script language="VBScript" src="..\ZTIDataAccess.vbs"/> <script language="VBScript"> Dim oService Dim oXML oEnvironment.Item("name") = Wscript.Arguments.Named.Item("name") oEnvironment.Item("age") = Wscript.Arguments.Named.Item("age") Set oService = New WebService oService.IniFile = "CustomSettings.ini" oService.SectionName = "helloworld3" Set oXML = oService.Query If oXML Is Nothing Then oLogging.CreateEntry "Unable to call UserGetName web service.", LogTypeWarning WScript.Echo "Not Found" & vbcrlf Else oXML.setProperty "SelectionNamespaces", "xmlns:wn='http://windows-noob.com/'" WScript.Echo oXML.SelectSingleNode("wn:string").Text End If </script> </job> Save the file and update your MDT files package on the distribution points. Edit your CustomSettings.ini file, Add the following lines:- PXE boot into WinPE, at your FrontEndHTA screen, press F8 to bring up a command prompt, cd to the following address C:\_SMSTaskSequence\WDPackage\Scripts\wnb And execute this:- Cscript.exe /nologo helloworld.wsf The following is output In the screenshot above, UserDomain and UserID are actually the Network Access Account retrieved from SCCM. (SCCMnaa) as defined in Computer Client Agent Properties. Now lets test passing values to our Hello World3 operation in our webservice, Open a command prompt in WinPE and type this:- C: Cd _SMSTaskSequence\WDPackage\Scripts\wnb Then to execute the webservice try Cscript.exe /nologo name_age.wsf /name:niall /age:44 We pass two properties to the web service, name and age, and the output is seen above.

What is a Web Service ? A webservice provides an ability to set/change/list information using functions that reside on a web server running IIS. The webservices can be targetted to different operating systems using different versions of the .net framework, if you want access to all versions of the .net framework then develop your webservices using Visual Studio 2010. Where can I get them ? You can make your own (using Visual Studio 2008 or 2010), or download some that others have made (highly recommended), such as Maik Kosters webservices from here - http://mdtcustomizations.codeplex.com/releases/view/26318 Or Michael Niehaus - http://blogs.technet.com/b/mniehaus/archive/2009/12/06/ris-style-naming-with-mdt-2010-use-a-web-service.aspx Maik Kosters Web Services MDT Webservice http://mdtcustomizations.codeplex.com/wikipage?title=Webservice%20-%20MDT&referringTitle=Documentation SCCM Webservice http://mdtcustomizations.codeplex.com/wikipage?title=Webservice%20-%20SCCM&referringTitle=Documentation Active Directory Webservice http://mdtcustomizations.codeplex.com/wikipage?title=Webservice%20-%20Active%20Directory&referringTitle=Documentation Making your own Webservice To make your own webservice, you should install Microsoft Visual Studio, I’d recommend using Microsoft Visual Studio 2010 to access all the different versions of .net. Start Visual Studio 2010 and you’ll see this window (Choose your default environment settings) the first time you run it, choose General Development Settings. Click on New Project A window will appear, here you can choose the template, so if you want to code in visual basic choose that, in our example however we will use C#. Select Visual C# and click on Web, in the .NET drop down menu, select .NET Framework 2.0 and choose ASP.NET Web Service Application. The default Hello World webservice code appears. Change the webservice’s namespace to http://windows-noob.com/ Right click on your webservice listed in the Solution Explorer pane (to the right hand side) and choose Build Once your code is compiled, to test it click on Debug, this will launch your webbrowser, and you can then click on the web service itself to see the web service, in this example click on Service1.asmx . Our simple webservice appears Click on the HelloWorld link to see what happens Click on the Invoke button If you already have a webservice running, you can copy just two files from your project folder to the ‘live’ webservice you have running on your server to test otherwise you’ll have to setup the webservice on your chosen server using the How Can I install a Web Service. Copying files from the project (local) To your webserver (remote)

by default when you execute some action (like displaying a HTA or a script or whatever) during a Task Sequence in Configmgr, the Installation Progress window will be present Infront of your work of art, to avoid this, you can use a backend javascript .js file (such as the deployment.js included in the Windows-noob.com Multipurpose FrontEnd HTA), include the following lines to hide the progress bar while the HTA is being displayed var oTSProgressUI = new ActiveXObject("Microsoft.SMS.TSProgressUI"); oTSProgressUI.CloseProgressDialog(); your backend Javascript file is in turn referenced by the FrontEnd HTA using the src command eg: <script type="text/javascript" src="DeployMenu.js"></script>

You can use your FrontEnd HTA to set values (variables) which in turn can be used (or checked for) in your Task Sequence. The FrontEnd can display options to your users like drop down menus or Radio Buttons, which have corresponding backend scripts which set values. In addition, values can be gathered using the MDT ztigather.wsf script, this queries wmi and pulls a whole load of values which in turn are processed by ZTIUtility.vbs, For example, the UUID value of a client is gathered (read) by ZTIgather.wsf, and ZTIutility.vbs sets this value oEnvironment.Item("UUID"). We can create a function in our HTA FrontEnd backend javascript script, to show the value of UUID. function showUUID() { var oEnvironment = new ActiveXObject("Microsoft.SMS.TSEnvironment"); alert(oEnvironment("UUID")); } The script above will only work if a Gather step has taken place beforehand. When ZtiGather.wsf runs, it produces a log file (ztigather.log) and in that log file you can see what it has detected, anything that is marked as Property can be ‘used’ or displayed in our HTA, Javascript (*.js) backend sample The below script will set a variable called DEPLOYMENTTYPE. It sets it to a value which in turn we'll check for in our task sequence. var oEnvironment = new ActiveXObject("Microsoft.SMS.TSEnvironment"); oEnvironment("DEPLOYMENTTYPE") = "NEWCOMPUTER"; The task sequence has a Group which checks for the value of that variable and if=NEWCOMPUTER It does some actions. windows Scripting File (*.wsf) backend sample The below sample code sets a variable called ALLOWOSDBUILD, which is checked for in the task sequence, if the value=NO then the task sequence shutsdown the computer. <job id="PromptForPassword"> <script language="VBScript" > Dim env,oTSProgressUI,MyPass Set env = CreateObject("Microsoft.SMS.TSEnvironment") set oTSProgressUI = CreateObject("Microsoft.SMS.TSProgressUI") oTSProgressUI.CloseProgressDialog() env("ALLOWOSDBUILD") = "NO" MyPass=Inputbox("Please enter the Password to start the OS Deployment") If MyPass = "password" then env("ALLOWOSDBUILD") = "YES" End If </script> </job> and below is a VBS example set env = CreateObject ("Microsoft.SMS.TSEnvironment") strTask = env("_SMSTSPackageName") ' log file to be used strFile = "\\server\log$\" & strTask & ".txt" the above writes out the Task Sequence name as the 'name' of the log file.

To add your HTA to your task sequence, you'll first need a boot image with HTA support. Once you have that the rest is easy. At the beginning of your task sequence create a Run command Line step with the following in it mshta.exe "%scriptroot%\wnb\Deploymenu.hta" let me explain what is happening in this step... The mshta.exe file is like a web browser and displays our HTA (hypertext application). you'll notice i'm using a path to our HTA which is "%scriptroot%\wnb\Deploymenu.hta" that is because I place the HTA files in a sub directory of my MDT toolkit scripts directory (MDT Toolkit scripts directory=%scriptroot%). This is not possible without a Use Toolkit Package step shortly before this step otherwise the %scriptroot% variable won't be set, so prior to this in my Task Sequence I have a Use Toolkit Package step. To copy your HTA file(s) to a sub directory in your MDT Toolkit package, locate the package source in ConfigMgr, find the scripts directory and create a new sub directory called My_Custom_Scripts (or whatever you want) which contains your scripts. In my example the sub directory is called wnb and I place my HTA file and all supporting scripts in there. Don't forget to Update your distribution points for your MDT Toolkit package after copying the new scripts/files.

here are some sample task sequences for just that purpose http://blogs.technet.com/b/mniehaus/archive/2010/07/20/mdt-2010-update-1-fixes-to-configmgr-state-migration-point-scenarios.aspx or if you want to get very cool you could try the windows-noob.com MultiPurpose HTA which does side-by-side and other scenarios all in one task sequence

here's how http://blogs.technet.com/b/mniehaus/archive/2010/07/20/mdt-2010-update-1-fixes-to-configmgr-state-migration-point-scenarios.aspx

After an already long development path, Microsoft has just released the release candidate for Internet Explorer 9, their attempt at turning the tide. They've looked at an impressive 17000 pieces of feedback for the release candidate, and they made lots of changes. There are a lot of changes under the hood. The release candidate adds support for CSS3 2D Transforms, HTML5 Geolocation, a set of HTML5 semantic elements, and the HTML5 canvas global­Composite­Operation property. They also improved the performance of CanvasPixelArray. "The IE9 RC is faster with real world sites. In addition to making the script engine faster, we've improved and tuned the rest of the browser as well. You'll find that Gmail, Office Web Applications, and many other sites are faster as a result of scenario tuning, network cache tuning, and new compiler optimizations," details Dean Hachamovitch, Microsoft's corporate vice president for Internet Explorer, "You'll also find that the RC of IE9 often uses megabytes less memory than the beta because of changes like delayed image decoding. We've also improved the performance of things many people do every day, like find on page, and made improvements which extend battery life." Interface-wise, the biggest change is the addition of an option to display the tab bar on an additional row. Sadly, you can't place these tabs atop the address bar where it belongs according to the Gospel Of Chrome (the One True browser interface). Another issue is the font rendering, which is still fuzzy due to the DirectWrite support. Why IE9 can't just use my global font settings is beyond me. It might sound petty to some, but it's frickin' 2011 and I demand consistent font rendering. Whether it's the fuzzy but shape-accurate Mac OS X variant, or the sharp but shape-inaccurate variant in Windows - they're both fine as long as it's an either-or thing! You can download the release candidate today. via > http://www.osnews.com/story/24398/Internet_Explorer_9_Release_Candidate_Released

Yesterday, Microsoft officially handed off the final release (RTM) of Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) to their OEM partners. On February 16th Windows 7 and Windows Server 2008 R2 SP1 will be available for MSDN and TechNet Subscribers as well as Volume License customers. On February 22nd, Windows 7 and Windows Server 2008 R2 SP1 will become generally available for folks to download via the Microsoft Download Center and available on Windows Update. For Windows 7, SP1 will help keep your PCs well supported by delivering ongoing updates, many of which have been made previously available through Windows Update. It also includes client-side support for RemoteFX and Dynamic Memory which are two new virtualization features enabled in Windows Server 2008 R2 SP1. Read more about those updates here from the Windows Server Team. via > http://windowsteamblog.com/windows/b/bloggingwindows/archive/2011/02/09/announcing-availability-of-windows-7-and-windows-server-2008-r2-sp1.aspx

are you doing a build and capture of windows 7, or are you deploying a previously captured image ? if it was previously captured how was it created ? what steps do you have in your current task sequence (a screenshot of it is enough)

i think Tim explains it brilliantly here http://deployment.xtremeconsulting.com/2009/11/20/understanding-usmt-with-mdt-2010/

are you installing 64bit windows 7 or 32 bit, the unatten.xmlfile must match the architecture