Updated 8/1/2012: As of 7/25/2012, new driver CAB's are available for the XPS Ultrabook line AND WinPE. You can find the XPS 13 driver CAB's HERE. As noted below, touchpad still requires application installation for multi-touch gesture functionality.
Edit: I have since discovered a solution for adding a wireless profile as part of the task sequence to resolve this issue. I have updated the instructions to include the new material(In blue text). The task sequence is now completely automated aside from actually launching the deployment. Per best practices, I chose to leave the BDD welcome screen enabled. This gives you one last chance to cancel the deployment before the hard drive is wiped.
Welcome to the wonderful world of ultrabooks, where we don't have NIC's to PXE boot from! If you were wondering how you might go about deploying Windows 7 Enterprise to one of these XPS 13's, here is how I did it.
First off, as there is no way to PXE boot this laptop, I have opted to perform the deployment from a USB Flash Drive. This guide assumes you will deploy entirely from the flash drive and not from a dock with LAN connectivity. My selection profile contains nearly 8GB of data so I went with a 16GB Flash drive to allow for expansion.
Step 1. Preparing the Flash Drive.
See the following link for a detailed explanation on how to properly prep your flash drive to become a boot device: http://www.intowindows.com/bootable-usb/
Step 2. Preparing your deployment share.
Assuming you want the minimal number of OS images, drivers and software installs, you will want to organize your deployment share in such a manner as to allow you to individually select these items.
As you can see in my illustration, I have created nested folders to separate the various software, operating systems, drivers, and task sequences.
This allows me to create a selection profile for the deployment to copy only the software I need for my XPS 13 deployment.
Step 3. Preparing Input Driver Installation.
As noted at the bottom of this page, in order for the multi-touch gestures to function properly, this software must be installed manually.
I used 7-zip to extract the Dell executable to a folder and import the installation folder manually. During the application import process, I use the following command to perform a silent installation of the Touchpad software:
- "setup.exe /exenoui /quiet /norestart"
- Create a selection profile, and select the applications(don't forget your touchpad application), operating system and XPS 13 drivers you want to be included on your Flash media.
- Create a new task sequence specifically for your XPS 13.
- Modify your task sequence to make deployment easier:
- Under the "Preinstall" section, select "Inject Drivers". In the "Selection Profile" drop-down, select your XPS 13 driver selection profile.
- Under "State Restore", add a new "Run Command" after "Gather Local Only".
- As seen in the image below, add the following command:
- netsh wlan add profile filename="%ScriptRoot%\wireless.xml" user=all
- Under "State Restore", add three new "Install Application" tasks
- Input drivers (gives you mouse functionality for adding to wireless)
- Configure the rest of the Task Sequence as you normally would.
- Don't forget to go back and add this task sequence to your Selection Profile
- I recommend capturing a custom WIM of your operating system with all current Microsoft updates. This will greatly decrease your deployment time. If you have done this already, you can disable "Pre-Application" Windows updates as well.
- In the previous step we added a netsh run command to our task sequence which referenced the "wireless.xml" file. Now we will create, configure and copy this file to our "Scripts" folder(%ScriptRoot%) on the deployment share.
- On a computer connected to your corporate wireless network, run the following command:
- netsh wlan export name="NameOfWirelessNetwork" folder=%userprofile%\desktop interface="Name of Wireless Adapter"
- You can find the name of the adapter here: "Control Panel\Network and Internet\Network Connections"(in my case "Wireless Network Connection")
- After executing the command in the previous step, you will have an xml file named after your network and adapter name(ex. Wireless Network Connection-Firm-Corporate.xml)
- Rename this file to wireless.xml for simplicity and to conform to our netsh command in the task sequence. Then edit the file, making the following changes in the <SharedKey> section:
- <protected>true</protected> change to false
- <keymaterial>string of text</keymaterial> delete the string and add the key to your wireless network.
- Now save the XML file and copy it to the Scripts folder in your deployment share.
- Under "Advanced Configuration", right-click Media and select "New Media".
- For "Media Path", I setup a share on my local workstation and specified that UNC path here. ex. \\pc-name\usb_dep
- Click the "Selection Profile" drop-down and select your XPS 13 selection profile.
- Finish the wizard.
The deployment media has properties identical to your deployment share. As such, you will need to configure your "Media Properties" accordingly. Note: We only install 64-bit Windows on our workstations, so this config is geared specifically to 64-bit. Here is an example of my config:
- General Tab
- Verify correct selection profile is selected
- Uncheck "Generate x86 boot image"b
- Uncheck "Generate Lite Touch bootable ISO image"
- Windows PE x64 Components
- Selection Profile: Win PE Drivers(Be sure to download the latest Dell WinPE driver cab(A09) and import to your deployment share. I do not deploy 32-bit W7, so I go back and delete all x86 only drivers.)
- Rules Tab - configure customsettings.ini and bootstrap.ini.
- Below is an example of my customsettings.ini file. For the most part I copied it from my deployment share, but then modified it to perform an automated install. NOTE: Items in red must be in bootstrap.ini for automated deployment.
[Settings]Once you have configured all of your settings, save the changes and exit the properties window.
UserID=UserAccount(user with access to network files)
_SMSTSORGNAME=What you want to appear in the deployment wizard
DomainAdmin=AdminName(admin with permissions to join domain)
TimeZoneName=Central Standard Time
BDEKeyLocation=\\Server\Share (location to store BitLocker key)
;Flash Player ActiveX 32bit
;Oracle JRE 32bit
;Apple iTunes(Don't judge me, our executives/sales LOVE iPads/iPhones)
;Firefox 14 w Flash
;Flash Player ActiveX 64bit
Step 9. Update Deployment Media
- Right click on your newly created Deployment Media and select "Update Media Content". This will copy everything in your selection profile to the UNC path as well as create new Windows PE boot media.
- From the destination directory, copy everything from the "Content" folder to your USB Flash Drive.