Gantlett

If anyone could assist me with this I would greatly appreciate it. Thanks in advance.

arr... Can you elaborate? Is my script missing something? Thanks again.

Hi and thanks for your reply. Sorry for the late reply, for some reason I didn't get an email notification even though Im subscribed to this thread… Anyhoo, the article I linked above to certainly instructs to create a custom partitioning script and thats just what Ive done. After some tests, I found that the deployment works if the partition is pre-formatted to NTFS. So the problem is definitely in the partitioning script, I just dont know what it is… Heres the script Im running: SELECT disk 0 SELECT partition 3 FORMAT FS=NTFS LABEL="Bootcamp" QUICK EXIT

Hello, I'm running MDT 2010 and Windows Deployment Services on a Windows Server 2008 SP2 x64. I would like to deploy Windows onto a BootCamp partition using MDT2010 and WDS. Since Macs won’t PXE boot from a Windows server, the way to get the Mac to boot into the WinPE environment is by burning the WinPE ISO to CD and booting the Mac from the bootable ISO. I followed the following guide to build the correct Task Sequence in MDT 2010: http://blog.physh.net/2010/02/deploy-windows-on-macs-using-mdt-2010.html I added BootCamp drivers to the distribution share and created a WinPE ISO using the above instructions. I can boot into WinPE and I have network access, however the LiteTouch process ends at the disk format stage with the following error: ZTI ERROR - Non-zero return code by LiteTouch, rc = -2147467259 0x80004005]LOG]!><time="02:16:14.000+000" date="09-13-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"> I’ve made some research and quickly found that this is a very generic error and basically doesn’t say much. I was able to grab the LiteTouch log files to take a closer look, but there’s no further information available. In WinPE, I manually ran the commands described in the DiskPartMac script and they work fine. Does anyone know why the process is failing? Thanks in advance.

Hello, We have a client in a very small environment consisting of two sites, with two computers in each site. The client needs an IM solution, but the solution must support user restrictions. We must be able to restrict users from logging in using their personal IM accoutns and/or adding their friends. Does anyone know of such a solution? I've googled around but couldn't find anything. Thanks in advance!

On an interesting note, looking at the NIC driver in the “Out-of-Box Drivers” section of the MDT2010 deployment share, it would appear that this driver is unsigned: the “This driver is WHQL signed” checkbox is un-ticked. This is not the case with the MassStorage drivers though - those are signed. So in that case, this means that if I wanted to integrate the NIC driver to the Windows 7 DVD boot.wim using any of the methods described at the first post in this thread, I would have to use the "/forceunsigned" switch, meaning the whole idea of using DISM is doomed for failure anyway... Just a thought.

OK - I found an amazing solution! Did some more research and it turns out that my whole approach is wrong. The way to deploy Windows in our day and age is by using an additional tool together with WDS, and that is Microsoft Deployment Toolkit 2010. The idea is to use MDT2010 to create custom installations with drivers, applications and an install script, and use WDS purely as a PXE boot server to fire-off the custom install. I have to say, MDT2010 is the most amazing tool I have ever seen released by Microsoft! It's dead easy to use and does everything through an easy to use GUI! It just takes care of everything and I'm simply impressed by the incredible job they've done with the whole Windows deployment process (as far as Windows 7 is concerned). Just read through these simple guides to gain an understanding of how the two fit together and how to achieve super-easy deployments: http://edge.technet.com/Media/Deploy-Windows-7-The-Easy-Way-Using-WDS-MDT-and-AIK-Step-By-Step/ http://www.the-d-spot.org/wordpress/2009/11/01/windows-7-lite-touch-installation-with-mdt-2010/ http://www.the-d-spot.org/wordpress/2009/11/16/windows-7-lite-touch-installation-with-mdt-2010-part-2/ I used MDT2010 to create a custom install process which includes the injection of the NIC and SATA drivers required for my new Dell 980's and it worked like a charm! Cheers!

Thanks for the replies guys. The driver I got is definitely from Dell - it's from the 980's driver downloads page. I'll try your suggestions and see if I get lucky!

Hello everyone, I'm running Windows Deployment Services on a Windows Server 2008 R2 x64 system. Currently, we have two boot.wim images on the server which are working fine. These boot.wim files were taken "as is" from Windows 7 ISO's. We have a 32-bit one and a 64-bit one. The problem is that we bought a shiny new Dell workstation (OptiPlex 980), and when I PXE-boot this baby into WDS, WinPE starts to boot, starts loading the GUI with the blue Windows 7 background and then says that network drivers cannot be found. This brings us to my problem: I tried integrating the correct NIC driver into the boot.wim image, but I'm experiencing some issues. Here are the two methods I've tried integrating the drivers and their respective results: Method 1: 1. I installed WAIK for Windows 7 on a Windows 7 workstation. 2. Copied the original Windows 7 ISO boot.wim file to a local folder. 3. Ran the "Deployment Tools Command Prompt" (DISM) as Administrator 4. Fired off the following commands in the following order: a. DISM /Cleanup-Wim b. Dism /Mount-Wim /WimFile:C:\winpe_dell\boot.wim /index:1 /MountDir:C:\winpe_dell\mount c. Dism /image:C:\WinPE_dell\mount /add-driver /driver:"C:\Users\erez\Desktop\Optiplex 980 Drivers" /recurse /forceunsigned b. Dism /Unmount-Wim /MountDir:C:\winpe_dell\mount /Commit The result: Immediately after selecting the boot image in the PXE menu, a black screen appears complaining about a recent hardware change and saying Windows cannot start. Method 2: 1. Using the same WAIK for Windows 7 on the same Windows 7 workstation. 2. Fired off the following commands in the following order: a. DISM /Cleanup-Wim b. copype.cmd amd64 c:\WinPE_dell c. copy "c:\program files\Windows AIK\Tools\amd64\imagex.exe" c:\WinPE_dell\iso d. Dism /Mount-Wim /WimFile:C:\winpe_dell\winpe.wim /index:1 /MountDir:C:\winpe_dell\mount e. dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-setup.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-setup_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-scripting.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-scripting_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-setup-client.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-setup-client_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-setup-server.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-setup-server_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-wds-tools.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-wds-tools_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-wmi.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-wmi_en-us.cab" f. dism /image:C:\WinPE_dell\mount /add-driver /driver:"C:\Users\erez\Desktop\Optiplex 980 Drivers" /recurse /forceunsigned g. Dism /Unmount-Wim /MountDir:C:\winpe_dell\mount /Commit The result: WinPE starts to boot, starts loading the GUI with the blue Windows 7 background and then says that the setup language cannot be determined. Can anyone please point me to what I'm doing wrong here? Thanks in advance!

Hi and sorry for the delayed response. Your suggestion did the trick! Thank you so much for your kind help!

Thanks, I'll give that a shot!

Hi and thanks for your reply I've edited the original post to include correct attachments. I tried attaching it to the server, and when that failed, I tried attaching it to the image.

Hello, I am trying to set up an unattended deployment system for Windows 7. I installed WDS on Windows Server 2008 64-bit Enterprise Edition SP2. I compiled an answer file and applied it to the Server Properties\Client tab. However, the WDS client completely ignores the answer file. I tried removing the answer file from the Server Properties\Client tab and applying it to the install image, but the client still ignores the answer file. I was able to grab the log file from the client, and it looks like the answer file arrives OK. I have attached the WinPE client's X:\Windows\panther directory below, as well as the XML answer file: panther.zip WDSUnattend.xml What am I doing wrong? Thanks in advance!

Hello I have a Server 2008 R2 x64 Windows Deployment Server running and I'd like to deploy XP and 7 through it. I would like to integrate mass storage and NIC drivers to the winpe.wim image. There are two ways of doing this: 1. Using DSIM to integrate the drivers to an offline WinPE image 2. Using Windows System Image Manager to create a distribution share with drivers, point an answer file to the driver path, and have WinPE query that path for drivers when WinPE boots up. I would like to use method 2, as it is more modular and easier to maintain - if a driver is causing problems, or if you need to add a driver, simply add or remove .inf files from the distribution share (I can't believe I'm saying this, but very cleverly done by Microsoft). No need to modify the boot.wim image. According to the Windows System Image Manager help, and according to Microsoft's TechNet AIK 2.0 guide, to add a driver path to an answer file, one must add to the answer file a component called Microsoft-Windows-PnpCustomizationsNonWinPE. This is where my problem is: I can't find such a component in the WinPE.wim image! It simply isn't there! My WinPE.wim file was created using copype.cmd x86 c:\WinPE_x86, so it's a clean file. I tried adding all the available packages, but that hasn't added any new components. I've googled and couldn't find anyone experiencing this problem at all. What am I doing wrong? Thanks very much.

I need to be able to deploy an OEM version of WinXP Pro through WDS 2008. The problem is that when booted into WinPE to capture the sysprepped system, the drop down menu is empty when I try to capture an OEM system. This problem does not occur when I try to capture a VLK system. I found this MS article which states that MS don't support sysprepping an OEM system. How can I get around this problem and deploy an OEM XP image through WDS 2008? This is so annoying...