arwidmark

Well, before spending to much time writing your own script. Try download the free MDT 2012 Update 1 deployment solution from Microsoft. It's a readymade deployment solution containing a HTA wizard that runs in WinPE, that displays the images on the deployment server, and allow you to select computer name, and allow you to select disk configurations (via task sequence selection). / Johan

There used to be a MSE OEM Preinstallation Kit on the Microsoft OEM site (protected), but I haven't tried it... In general I install antivirus apps during deployment, I don't have them in my reference image. / Johan

Don't know about that but you should not use the SaveProfile feature in WinPE 3/4, it's very unreliable. There is a reason why it's removed in WinPE 5.0 (part of the upcoming ADK 8.1) / Johan

If you download the free MDT 2012 from Microsoft , and look at the MDT 2012 boot media you find two vbscripts (litetouch.vbs and litetouch.wsf) that together with a HTA provides a logon screen to both WinPE 3.0 and WinPE 4.0. You can "borrow" these scripts to your own custom WinPE image. MDT 2012 also helps you integrate DaRT into the boot image, so you can remote into it. (like Real VNC, but Microsoft). If you want to password protect the actual PXE boot process you can add an open source menu (part of syslinux) to your WDS server... here is a step-by.step guide on how to do that. http://www.deployvista.com/Blog/JohanArwidmark/tabid/78/EntryID/126/language/sv-SE/Default.aspx / Johan

Depending on what regional setting you want to change there are different properties. The main UI Language (when using multiple language packs) is set via UILanguage. Example: UILanguage=en-US For keyboard it is the KeyboardLocale property Example: KeyboardLocale=en-US / Johan

Just get the tools.cab from DaRT 7, it has the files (but one) you need for the WinPE boot image. If you extract it its organized in the folder structure they need to be in. Then just copy the DartConfig.dat file as well to system32 / Johan

You need to commit the changes to the wim file, using imagex /unmount /commit <mount-folder>. Please note that some wim's, like the Windows 7 boot.wim have multiple indexes, so that you mount the right index. A tip when unmounting and commiting changes is also to close all Explorer windows before doing so. The WIM filter driver in WAIK 2.0 is quite sensible to open file handles. / Johan

A custom boot image will not launch the setup automatically. Add the boot image from your Windows 7 or Windows Server 2008 R2 media, and add your drivers to that image instead. / Johan

Here is an article that explains how copyprofile in Windows 7 really works, unfortunately the Microsoft documentation is incorrect How CopyProfile really works in Windows 7 Deployments http://www.deploymentresearch.com/Blog/tabid/62/EntryId/43/How-CopyProfile-really-works-in-Windows-7-Deployments.aspx / Johan

EFI (or UEFI for new hardware) is a just replacement for the older BIOS firmware. Most new hardware have experimental support for UEFI these days. EFI is used on Itanium based systems (which very few people arfe using). / Johan

Even for x64 you need to use the etfsboot.com bootcode, you can still add secondary boot file iy you need to boot secondary EFI images / Johan

The best way (IMHO) is to use the Microsoft Deployment Toolkit (MDT) to deploy your images. It has ready made functions (sequences) to allow you to do your commands before, and after deployment. In addition it also provides driver injections, admin UI, application installs and update... It's totally free, just download from www.microsoft.com/deployment. Then you can download (or view online) the following free video tutorials on how to set it up. Videos from the MDT 2010 Lite Touch - Unleashed series / Johan

Here is an example of a fully automated bootstrap.ini (skipping the initial welcome page and providing user credentials). Remeber to update the deployment share after updating the bootstrap.ini file (since it lives on the boot image), and then import (or replace) the boot image in WDS. [settings] Priority=Default [Default] DeployRoot=\\MDT01\MDTBuildLab$ SkipBDDWelcome=YES UserDomain=CORP UserID=BuildAccount UserPassword=Password01 / Johan

Sure, Dell has a Tech Center with drivers for all their business models downloadable per model (cab files) http://www.delltechcenter.com/page/Dell+Business+Client+Operating+System+Deployment+-+The+.CAB+Files / Johan

The MSDN article talks about uninstalling the OS preview, not the Assessment and Deployment Kit (ADK). ADK is not publicly available, only for MSDN subscribers (and TAP customers). / Johan

I could uninstall ADK fine on one of my test macines, but yes I'm using VM's for test Thanks for the heads up though, I haven't done any extensive search for installation leftovers. / Johan

I think you guys will like this blog post... Windows 8 Preview - Howto - Creating a WinPE boot image with .NET Framework and PowerShell http://www.deploymentresearch.com/Blog/tabid/62/EntryId/41/Windows-8-Preview-Howto-Creating-a-WinPE-boot-image-with-NET-Framework-and-PowerShell.aspx / Johan

The Dart component outputs a xml file with the connection info (ticket number, port etc), it's the inv32.xml file and is stored in X:\Windows\System32. You can (quite easily), create a vbscript that parses that file and stores a shortcut on the server. The dart connection viewer accepts commandline input of ticknumber etc. Sidenote: In MDT 2012 Beta 2 (out in october) Microsoft added a connect button in the server side UI, so you can see all running/deploying clients, and directly connect to them. Very nice / Johan

Not terminal services, but remote connection (sort of the same), with the new remote recovery in the Dart 7.0 tools. I use them for my MDT 2010/2012 and ConfigMgr 2007/2012 deployments, but they work in any WinPE - Without disabling the firewall like VNC requires... Here is an article on how to add remote connection to WinPE. Remote Connection to WinPE during MDT/SCCM deployments http://www.deploymentresearch.com/Blog/tabid/62/EntryId/36/Software-Assurance-Pays-Off-Remote-Connection-to-WinPE-during-MDT-SCCM-deployments.aspx / Johan

You can capture to a share on a client as well, there is no server or domain requirement (even though its recomenned) You can also specify a local drive, problem is that you may not know what driveletter the USB disk gets. If you want to a manual capture using Imagex it needs to be done after sysprep is being run, and when booted into WinPE / Johan

Check if MDT adds the nvrd.sys info to unattend.txt (MassStorageDrivers and OEMBootFiles) before the first reboot (still in post-install phase)... Second, I do think you are breaking the OEM EULA be deploying XP that way, normally the OEM licensing is quite specfic on how to use the recovery media from the OEM. Check out the XP re-imaging rights, which can allow you to use a VL media instead. / Johan

Cluberti is spot on, MDT has password protection by default of the boot image. As for limiting deployments per vendor, very easy, this is also built in... use the following rules (customsettings.ini)... You can also do it per model, if you only want to allow installation on specific dell models [settings] Priority=Make, Default [Default] OSInstall=NO [Dell Computer Corporation] OSInstall=YES [Dell Inc.] OSInstall=YES [Dell Computer Corp.] OSInstall=YES If you want to use wildcards (sort of) you can use this user exit http://blogs.technet.com/b/deploymentguys/archive/2009/09/10/using-and-extending-model-aliases-for-hardware-specific-application-installation.aspx / Johan

The easiest way is to configure multiple task sequences in MDT, with different disk configurations. When editing the task sequence there is a nice UI for configuring multiple disks/partitions etc. You can customize the MDT wizard (more advanced = requires custom scripting) to prompt you for partitioning layout. You can also create multiple partiioning steps in the task sequence, and add condition to them,,, conditions like, if the harddrive is larger than 300 GB, create two partitions... / Johan

The optimal scenario to create ref-images for MDT is to use the build and capture scenario with MDT to create the image (possibly with the LTISuspend option if you need to do something manually) and always in a virtual machine to get the best image, and to able to use snapshots. Build and Capture is the most reliable way. Howvere, since you already have an image you are happy with, you can create a Capture Only Task Seqeunce in MDT. When running the task sequence (by starting the litetouch.vbs script from your running image), it will run sysprep with the correct switches, stage winpe on the drive, reboot, and capture it to your deployment server. Please note that the capture only task sequence is a little bit buggy in some scenarios... the build and capture is more mature and well tested. Also please note that the machine you are using is considered "used" after you run a capture only task sequence.. That's why my initial recommendation on using vms and snapshots. / Johana

You need to create an x64 winpe image to run the x64 setup.exe So instead of running "copype x86 c:\whateverfolder" you need to run "copype amd64 c:\whateverfolder" / Johan