Eddie Jackson
|Guide to BDD Server Build/Deployment/Applications/Errors |
|Compiled and Updated by Edward Saint Jackson |
| |
| |
|BDD 2007, as you probably already know, is End-to-end guidance, best practices, and tools for planning, building, and deploying Windows and Office. BDD 2007 is developed by a team led by Michael |
|Niehaus (lead developer) and Mike Lewis (Architect). |
|This guide explains the necessary steps to install and configure the core BDD 2007 RC1 components for creating a virtual lab/test environment with BDD 2007 RC1. |
| |
|The Guide Covers The Following: |
|o Creating the BDD 2007 Deployment Server Structure |
|o Add Windows Vista/XP Setup Files |
|o Create a BDD 2007 Build of Windows Vista/XP |
|o Create a Deployment Point |
|o Capture Reference Points |
|o Adding Applications |
|o Injecting Drivers |
|o How to SysPrep |
|o Example BDD Applications With Silent Switches |
|o Detailed Possible Errors and Fixes |
|o Top 10 Common BDD Errors |
|o Create USB Keys |
| |
|* So where do you begin? |
|Build your Server (where BDD will soon reside). |
|Then work on BDD Structure (pg 2-5). |
|Next Capture your OS (pg 27-52) |
|Add Applications, Inject Drivers, and Create Bootable USB Flash Drives/CDs |
| |
|Prerequisites |
|To complete the guide, you need a virtual machine with the following configuration. |
|• OS: Windows Server 2003 SP1 |
|o Server name: SRV001 (Domain Controller for ) |
|o A C: and D: drive (for example 32 GB C: and 96 GB D:) |
|o DNS and DHCP installed and configured |
|o Latest Security patches installed, including Windows Installer 3.1 (KB 893803) |
|On SRV001, download BDD 2007 RC1 to D:\Setup\BDD 2007 |
|o |
|On SRV001, download .NET Framework 2.0 to D:\Setup\Net Framework 2.0 |
|o |
|Download MMC 3.0 to D:\Setup\MMC 3.0 |
|o |
|Download USMT 3.0 to D:\Setup\USMT 3.0 |
|o |
|Download Word Viewer to D:\Setup\WordViewer 2003 |
|o |
|Download WAIK to D:\Setup\WAIK on SRV001 |
|o |
|If needed, download third party device drivers to D:\Setup\Drivers |
|Recommended software (but not required) |
|o GPMC, Windows Server 2003 SP1 Resource Kit and Support Tools |
|Step 1 – Creating The Server Structure |
|In this part you will install BDD 2007 and add the Windows Vista installation files. You will also create the various service accounts used. |
|Install BDD 2007, USMT, WAIK and prerequisites |
|1. On SRV001, using Explorer, navigate to the D:\Setup folder. |
|2. Install .NET Framework 2.0 (netfxx86.exe) with default settings. |
|3. Install MMC 3.0 (WindowsServer2003-KB907265-x86-ENU.exe) with default settings. |
|4. Install MSXML 6.0 (msxml6x86.msi) with default settings. |
|5. Install WAIK (waikx86.msi) with default settings |
|6. Install BDD 2007 (BDD2007_x86.msi), verify that the Distribution Share is installed to the D: drive, otherwise use default settings. |
|7. Copy the USMT 3.0 files (InstallUSMT30_x86*) to D:\Distribution\Tools\x86 |
|8. Due to a bug in the InstallUSMT30_x86_vista.msu package (/quiet switch not working), an USMT30.cab file should be created and copied to the D:\Distribution\Tools\x86 folder. Use the |
|following steps: |
|a. On a Vista machine, install USMT 3.0 (InstallUSMT30_x86_vista.msu) manually to the default location (c:\program files\usmt30) |
|b. Copy c:\program files\BDD 2007\samples\USMT30_x86.ddf from SRV001 to C:\ on the vista machine |
|c. Start a command prompt, change directory to C:\ and run makecab.exe /F USMT30_x86.dff |
|d. Copy the usmt30.cab file to D:\Distribution\Tools\x86 folder on SRV001 |
|9. Due to a bug in Windows PE 2.0 (security.dll is missing), create a folder named D:\ExtraFiles\Windows\System32 and copy Security.dll from the Vista Host PC to it. |
|Create the BDD 2007 service and test accounts |
|1. Using Active Directory User and Computers, create the following OU’s |
|a. Deployment |
|b. Workstations |
|2. Using Active Directory User and Computers, in the Deployment OU, create the following user accounts. Set password to P@ssw0rd. |
|a. BuildAccount |
|b. JoinAccount |
|c. HelpDeskAccount |
|d. EndUserAccount |
| Set permissions on the Workstations OU |
|1. Using Active Directory Users and Computers, allow JoinAccount permissions to manage computer accounts in the Workstations OU. |
|a. In the view menu, select Advanced Features, |
|b. Right-click the Workstations OU, select Properties, and then click the Security Tab. |
|c. Click the Advanced button. |
|d. In the Advanced Security Settings for Workstations window, click Add, type in Join Account and click OK |
|e. In the Permissions List, select the below list of permissions and click OK (Verify that the scope is set to This object and all child objects). |
| |
|Scope: This object and all child objects is selected |
| i. Create Computer objects |
| ii. Delete Computer objects |
|f. In the Advanced Security Settings for Workstations window, click Add, type in Join Account again and click OK |
|g. In the Permissions List, select the below list of permissions and click OK (Verify that the scope is set to Computer objects). |
| |
|Scope: Computer objects |
| i. Read All Properties |
| ii. Write All Properties |
| iii. Read Permissions |
| iv. Modify Permissions |
| v. Change Password |
| vi. Reset Password |
| vii. Validated write to DNS host name |
| viii. Validated write to service principal name |
|h. Click OK once more. |
| * Once Server Structure is complete…page 27-52 has picture illustrations about how to build/capture that first golden image. |
|Step 2 – Add Windows Vista/XP Setup Files |
|Add Windows Vista installation files to the Deployment Workbench |
|1. ON SRV001, capture an iso-file with Windows Vista |
|2. Using the BDD Workbench, expand the Distribution node, right-click on the Operating Systems node, and select New (Or Click New from the Actions pane). Use the following settings for the New |
|Os Wizard. |
|a. Full set of source files |
|b. Source directory: :\ |
|c. Destination directory name: Windows Vista x86 |
|Add applications to the BDD Workbench |
|1. Using the BDD Workbench, expand the Distribution node, right-click on the Applications node, and select New (Or Click New from the Actions pane). Use the following settings for the New |
|Application Wizard. |
|a. Application with source files |
|b. Publisher: Microsoft |
|c. Application name: Word Viewer |
|d. Version: 2003 |
|e. Language: English |
|f. Platform: x86 platform ONLY! |
|g. Source Directory: D:\Setup\WordViewer 2003 |
|h. Specify the name of the directory that should be created: Microsoft Word Viewer 2003 |
|i. Command Line: wdviewer.exe /q /c:”msiexec /I wordview.msi /qn” |
|j. Working directory: .\Applications\Microsoft Word Viewer 2003 |
|Add Out-Of-Box drivers to the Deployment Workbench |
|1. Download drivers to D:\Setup\Drivers for your client hardware |
|2. Using the BDD Workbench,, expand the Distribution node, right-click on the Out-of-Box Drivers node, and select New (Or Click New from the Actions pane). |
|3. Add the drivers in D:\Setup\Drivers to the repository. |
| Step 3 – Create a Build |
|Create a Build |
|1. Using the BDD Workbench,, right-click on the Builds node, and select New (Or Click New from the Actions pane). Use the following settings for the New Build Wizard. |
|a. Build ID: Vista |
|b. Build name: Windows Vista |
|c. Build comment: Company Master Build |
|d. Operating System Image: Windows Vista Ultimate |
|e. ProductKey: |
|f. Organization: EddieJackson |
|g. FullName: EddieJackson |
|h. Internet Explorer home page: |
|i. Administrator Password and confirm Password: P@ssw0rd |
| |
|Step 4 – Create a Deployment Point |
|Create a Deployment Point |
|1. Using the BDD Workbench,, right-click on the Deploy node, and select New (Or Click New from the Actions pane). Use the following settings for the BDD Deployment Wizard. |
|a. Lab or single-server deployment (default) |
|b. Deployment point name: DOMAIN |
|c. Allow user to select additional application on Upgrade (default) |
|d. Ask if an image should be captured (default) |
|e. Do Not Allow the user to set Administrator Password (Default) |
|f. Do Not Allow user for specifying product key (default) |
|g. Share name: Distribution$ (default) |
|h. Allow the user to configure user state options (default) |
|2. Using the BDD Workbench, right-click the DOMAIN Deployment Point and select Properties. |
|3. In the Windows PE Tab |
|a. In the Images to Generate area, make sure that the Generate a Lite Touch bootable RAM disk ISO image checkbox is selected |
|b. In the Extra directory to add, type in D:\ExtraFiles |
|c. Click OK |
|4. Using the BDD Workbench, right-click the DOMAIN Deployment Point and select Update. |
|a. Note: The update process will take 5 - 10 minutes. |
|Set Distribution folder permissions |
|1. Allow BuildAccount modify permissions on the D:\Distribution folder (NTFS permissions) |
| |
| |
|Done! To start deploy Windows Vista, continue with Part2 (Lite Touch Deployment). |
|Step X – Mounting WIM Files (how to) |
| |
|Make sure you update the WIM from Deployment Points in the BDD Interface |
|To be able to mount an image, you have to install the WIM filter first. Start the Windows Explorer with Administrator rights. To do so, you have to right click on its icon. Then, go to C:\Program |
|Files\Windows AIK\tools. There, you can choose the correct folder for your CPU type. To install the WIM filter, right click on wimfltr.inf and then click on “install”. Now, you have to reboot. |
| |
|& |
| |
|Import via a registry file (this will add mount to context menu): |
| |
|Windows Registry Editor Version 5.00 |
| |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format] |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\DefaultIcon] |
|@="C:\\Program Files\\Windows AIK\\Tools\\x86\\imagex.exe" |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\shell] |
|@="Mount" |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\shell\Commit] |
|@="Commit Changes" |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\shell\Commit\command] |
|@="\"C:\\Program Files\\Windows AIK\\Tools\\x86\\imagex.exe\" /unmount /commit c:\\mounted_wim" |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\shell\Dismount] |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\shell\Dismount\command] |
|@="\"C:\\Program Files\\Windows AIK\\Tools\\x86\\imagex.exe\" /unmount c:\\mounted_wim" |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\shell\Mount] |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\shell\Mount\command] |
|@="\"C:\\Program Files\\Windows AIK\\Tools\\x86\\imagex.exe\" /mount \"%1\" 1 c:\\mounted_wim" |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\shell\Mount2] |
|@="Mount Writeable" |
|[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Windows.Image.Format\shell\Mount2\command] |
|@="\"C:\\Program Files\\Windows AIK\\Tools\\x86\\imagex.exe\" /mountrw \"%1\" 1 c:\\mounted_wim" |
|[HKEY_CLASSES_ROOT\.wim] |
|@="Windows.Image.Format" |
| |
| |
| |
|Guide to BDD 2007 – Part 2, Using Lite Touch To Deploy Windows Vista |
|Compiled and Updated by Edward Saint Jackson |
|[pic] |
| |
| |
| |
| |
| |
| |
| |
|BDD 2007, as you probably already know, is End-to-end guidance, best practices, and tools for planning, building, and deploying Windows and Office. BDD 2007 is developed by a team led by Michael |
|Niehaus (lead developer) and Mike Lewis (Architect). |
|This guide explains the necessary steps to use the Lite Touch Component of BDD 2007. It assumes that you have set up the BDD 2007 deployment server as described in “Geeks Guide to BDD 2007 – Part 1,|
|Core Configuration”. |
| |
|To complete the lab, you need the following virtual machines |
|• SRV001 (Domain Controller for ) |
|• PC0001 (Windows XP SP2, 512 MB of RAM) |
| |
|Step 1 – Create and Capture a Vista Reference Machine |
|Create a Vista Reference Machine |
|1. On SRV001, copy the D:\Distribution\Boot\LiteTouchPE_x86.iso file to Z:\Diskimages (C:\Diskimages on the Host PC). |
|2. Create a new Virtual Machine with 512 MB RAM, name it Vista LT Reference and boot from the LiteTouchPE_x86.iso file. |
|3. Complete the BDD Deployment Wizard using the below settings |
|a. Keyboard Layout: United States |
|b. Specify credentials for connecting to network shares: |
| i. User name: BuildAccount |
| ii. Password: P@ssw0rd |
| iii. Domain: DOMAIN |
|c. Computer name: (Default) |
|d. Join a workgroup: Workgroup |
|e. Specify whether to restore user data: Do not restore user data and settings |
|f. Select an operating system image to install: Windows Vista Enterprise. |
|g. Locale Selection: English (United States) |
|h. Time Zone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna |
|i. Select one or more applications to install: Microsoft Word Viewer 2003. |
|j. Specify whether to capture an image: Capture an image of this computer |
| i. Location: \\SRV001\Distribution$\Captures |
| ii. File name: VistaEnterpriseLT.wim |
|k. Review the Details before clicking Begin. |
|4. After installing the base Vista operating system and the Word Viewer application, BDD will automatically run sysprep and capture the computer to an image. |
| |
| |
|Step 2 – Add the previously captured LT image |
|Add Windows Vista installation files to the BDD Workbench |
|1. On SRV001, using the Deployment Workbench,, expand the Distribution node, right-click on the Operating Systems node, and select New (Or Click New from the Actions pane). Use the following |
|settings for the New Os Wizard. |
|a. Custom Image File |
|b. Source file: D:\Distribution\Captures\VistaEnterpriseLT.wim |
| i. Move the files to the distribution share instead of copying them |
|c. Destination directory name: Vista Enterprise LT |
|Add another Build |
|2. Using the Deployment Workbench, right-click on the Builds node, and select New (Or Click New from the Actions pane). Use the following settings for the New Build Wizard. |
|a. Build ID: VistaEnterpriseLT |
|b. Build name: Windows Vista Enterprise LT |
|c. Build comment: Company Standard LT Build |
|d. Operating System Image: CDrive in “VistaEnterpriseLT\VistaEnterpriseLT.wim” |
|e. ProductKey: Do not specify a product key at this time |
|f. Organization: EddieJackson |
|g. FullName: EddieJackson |
|h. Internet Explorer home page: |
|i. Administrator Password and confirm Password: P@ssw0rd |
| |
|Step 3 – Install a new Vista Client using Lite Touch |
|Install a new Windows Vista client using Lite Touch |
|1. Create a new Virtual Machine with 512 MB RAM, name it Vista LT - New Computer and boot from the LiteTouchPE_x86.iso file |
|2. Complete the BDD Deployment Wizard using the below settings |
|a. Keyboard Layout: United States |
|b. Specify credentials for connecting to network shares: |
| i. User name: BuildAccount |
| ii. Password: P@ssw0rd |
| iii. Domain: DOMAIN |
|c. Computer name: (Default) |
|d. Join a Domain: DOMAIN |
| i. User name: JoinAccount |
| ii. Domain: DOMAIN |
| iii. Password: P@ssw0rd |
|e. Specify whether to restore user data: Do not restore user data and settings |
|f. Select an operating system image to install: Windows Vista Enterprise LT |
|g. Locale Selection: English (United States) |
|h. Time Zone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna |
|i. Select one or more applications to install: None (already installed in image) |
|j. Specify the BitLocker configuration: Do not enable BitLocker for this computer. |
|k. Review the Details before clicking Begin. |
|3. BDD 2007 will now Deploy a Windows Vista image including Word Viewer. |
| |
|Step 4 – Refresh a Windows XP SP2 client |
|Refresh a Windows XP SP2 client |
|1. Start the PC0001 Virtual Machine, Add DOMAIN\ HelpDeskAccount to the local administrators group. |
|2. Logon as EndUserAccount, make some customizations like adding favourites to IE, add icons and documents to the desktop, change colours etc. |
|3. Logout and logon as HelpDeskAccount, then start the Lite Touch Deploy Wizard, \\SRV001\Distribution$\Scripts\Litetouch.vbs. Complete the guide using the following settings: |
|a. Choose a migration type: Refresh this Computer |
|b. Computer name: PC0001 (Default) |
|c. Join a domain |
| i. Domain: DOMAIN |
| ii. Credentials |
|1. Username: JoinAccount |
|2. Domain: DOMAIN |
|3. Password: P@ssw0rd |
|d. Specify where to save your data and settings: Automatically determine location |
| i. Allow data and settings to be stored locally when possible |
|e. Specify where to save a complete computer backup: Do not back up the existing computer. |
|f. Select an operating system image to install: Windows Vista Enterprise LT. |
|g. Locale Selection: English (United States) |
|h. Time Zone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna |
|i. Select one or more applications to install: None (already in image) |
|j. Specify credentials for connecting to network shares: |
| i. User name: BuildAccount |
| ii. Domain: DOMAIN |
| iii. Password: P@ssw0rd |
|k. Review the Details before clicking Begin. |
|4. After completion, logon as EndUserAccount and verify that the settings where migrated |
| |
|Guide to BDD 2007 – Part 3, Using Zero Touch To Deploy Windows Vista |
|Compiled and Updated by Edward Saint Jackson |
|[pic] |
| |
|BDD 2007, as you probably already know, is End-to-end guidance, best practices, and tools for planning, building, and deploying Windows and Office. BDD 2007 is developed by a team led by Michael |
|Niehaus (lead developer) and Mike Lewis (Architect). |
|This guide explains the steps necessary to configure BDD 2007 Zero Touch. It assumes that you have set up the BDD 2007 deployment server as described in “Geeks Guide to BDD 2007 – Part 1, Core |
|Configuration”. |
| |
|The guide covers the following steps |
|o Create and Capture a Vista Reference Machine for ZeroTouch |
|o Install and configure OSD FP Update |
|o Capture the Vista Reference Machine |
|o Create the ZTI server structure |
|o Create a ZTI Image Package |
|o Deploy a bare metal computer using ZTI |
|o Refresh a computer using ZTI |
|To complete the lab, you need the following virtual machines |
|• SRV001 (Domain Controller for ) |
|o SQL Server 2000 SP4 |
|o SMS Server 2003 SP2 |
|♣ Installed to D:\SMS |
|♣ SMS Network Access account set to DOMAIN\SMSInstall |
|o Download OSD FP Update to D:\Setup\OSD FP Update |
|♣ |
|• PC0002 (Windows XP SP2, 512 MB of RAM) o SMS 2003 SP2 client installed |
|Step 1 – Create a Vista Reference Machine |
|Add the SMS 2003 Client application to the BDD Workbench |
|1. Using the BDD Workbench,, expand the Distribution node, right-click on the Applications node, and select New (Or Click New from the Actions pane). Use the following settings for the New |
|Application Wizard. |
|a. Application with source files |
|b. Publisher: Microsoft |
|c. Application name: SMS 2003 Advanced Client |
|d. Version: SP2 |
|e. Language: English |
|f. Platform: All Platforms |
|g. Source Directory: D:\SMS\Client\i386 |
|h. Specify the name of the directory that should be created: |
|Microsoft SMS 2003 Advanced Client SP2 |
|i. Command Line: ccmsetup.exe /useronly SMSSITECODE=AUTO |
|j. Working directory: .\Applications\Microsoft SMS 2003 Advanced Client SP2 |
|Create a Vista Reference Machine for ZTI |
|1. Create a new Virtual Machine, 512 MB RAM, named ZTI Vista reference computer. Start the Virtual Machine and boot from the LiteTouchPE_x86.iso file. |
|2. Complete the BDD Deployment Wizard using the below settings |
|a. Keyboard Layout: United States |
|b. Specify credentials for connecting to network shares: |
| i. User name: BuildAccount |
| ii. Password: P@ssw0rd |
| iii. Domain: DOMAIN |
|c. Computer name: (Default) |
|d. Join a workgroup: Workgroup |
|e. Specify whether to restore user data: Do not restore user data and settings |
|f. Select an operating system image to install: Windows Vista Enterprise. |
|g. Locale Selection: English (United States) |
|h. Time Zone: (GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna |
|i. Select one or more applications to install: |
| i. Microsoft SMS 2003 Advanced Client SP2 |
|j. Specify whether to capture an image: Prepare to capture the machine |
|k. Specify the BitLocker configuration: Do not enable BitLocker for this computer. |
|l. Review the Details before clicking Begin.. |
|3. BDD 2007 will now deploy Windows Vista including the SMS 2003 SP2 Advanced Clienmt |
| |
| |
|Step 2 – Install and configure OSD FP Update |
|Install the OSD FP Update |
|1. On SRV001, using Explorer, navigate to D:\Setup |
|2. Install OSD FP Update (OSDeployment_Setup.EXE) with the default settings. |
|Add support files for a generic WinPE 2005 image |
|1. On SRV001, capture an image (iso file) of Windows PE 2005 |
|2. Using the Deployment Workbench, expand the Distribution Share node, right-click on the Operating Systems node, and select New (Or Click New from the Actions pane). Use the following settings|
|for the New Os Wizard. |
|a. Full set of source files |
|b. Source directory: :\ |
|c. Destination directory name: Windows PE 2005 |
|3. Capture an image of Windows Server 2003 SP1. |
|4. Using the Deployment Workbench, expand the Distribution Share node, right-click on the Operating Systems node, and select New (Or Click New from the Actions pane). Use the following settings|
|for the New Os Wizard. |
|a. Full set of source files |
|b. Source directory: :\ |
|5. Destination directory name: Windows Server 2003 SP1 |
| |
|Step 3 – Capture the Vista Reference Machine |
|In this step you will Capture the master Windows Vista image |
|Create an OSD Capture CD |
|1. Using the SMS Admin Console, create a OSD Capture CD |
|Capture the Master Windows Vista Image |
|1. On the ZTI reference computer using the OSD Capture CD, start the OSD Image Capture Wizard (OSDICW.EXE) |
|2. Use the following settings to complete the OSD Image Capture Wizard |
|a. Name the image VistaEnterpriseZTI.wim |
|b. Store the image in the \\SRV001\Distribution$\Captures share |
|c. Connect as DOMAIN\BuildAccount |
|3. Reboot and boot from the OSD Capture CD |
|Add the captured image to Deployment Workbench |
|1. Using the Deployment Workbench, expand the Distribution Share node, right-click on the Operating Systems node, and select New (Or Click New from the Actions pane). Use the following settings|
|for the New Os Wizard. |
|a. Custom image file |
|b. File: D:\ Distribution$\Captures\VistaEnterpriseZTI.wim |
| i. Move the files to the distribution share instead of copying them |
|c. Setup files are not needed |
|d. Destination directory name: Windows Vista Enterprise ZTI x86 |
|Create a Build for ZTI |
|1. Using the Deployment Workbench, right-click on the Builds node, and select New (Or Click New from the Actions pane). Use the following settings for the New Build Wizard. |
|a. Build ID: VistaEnterpriseZTI |
|b. Build name: Windows Vista Enterprise ZTI |
|c. Build comment: Company Master Build ZTI |
|d. Operating System Image: SMS OSDImage in “Windows Vista Enterprise ZTI” |
|e. ProductKey: Do not specify a product key at this time |
|f. Organization: EddieJackson |
|g. FullName: EddieJackson |
|h. Internet Explorer home page: |
|2. Administrator Password and confirm Password: P@ssw0rd |
|Step 4 – Create the ZTI server structure |
|Configure a ZTI Deployment Point |
|1. On SRV001, using BDD Workbench create a ZTI Deployment point using the following settings. |
|a. Build type: SMS 2003 OSD |
|b. Name: DOMAINZTI |
|c. Server name: SRV001 (default) |
|d. Share name: ZTI$ (default) |
|e. Path: D:\ZTI |
|f. Specify user data defaults: Automatically determine the location |
| i. Allow data and settings to be stored locally when possible |
|g. Specify where to obtain SMS 2003 OSD files: D:\SMS\OSD |
|2. Using BDD Workbench, right-click the DOMAINZTI Deployment point and select properties, In the Rules tab, modify the rules to look like below. |
| |
|[Settings] |
|Priority=Default |
| |
|[Default] |
|OSInstall=Y |
|ScanStateArgs=/v:5 /o /c |
|LoadStateArgs=/v:5 /c /lac |
|UserDataLocation=AUTO |
| |
|[SMS] |
|SQLServer=SRV001 |
|Database=SMS_NET |
|Table=v_Program |
|Parameters=PackageID, Programname |
|SQLSHARE=SMSClient |
|3. Edit Bootstrap.ini to look like below |
| |
|[Settings] |
|Priority=Default |
| |
|[Default] |
|OSDINSTALLSILENT=1 |
|OSDINSTALLPACKAGE=NET00001 |
|OSDINSTALLPROGRAM=Install Vista Enterprise |
|4. On the Builds tab, associate the Windows Vista Enterprise ZTI build with the ZTI Deployment Point. Deselect all other Builds. |
| |
|Note: The BuildID of the Build selected will used as subfolder name in the D:\ZTI folder. |
|5. In the WinPE PE 2004/2005 Tab, select the Windows Server 2003 SP1 and Windows PE 2005 operating systems in the list boxes. |
|6. Update the ZTI Deployment Point by right-clicking and select Update (or click update in the Actions Pane) |
| |
|Update OSD FP with the generic WinPE 2005 image |
|1. Copy the D:\ZTi\Boot\Generic_OSD_x86.iso to Z:\diskimages (c:\diskimages on the Host PC) |
|2. Capture the Generic_OSD_x86.iso file |
|3. Using SMS Admin Console, update OSD FP Update with the custom WinPE 2005 image (point to X:\) |
|Create the Packages Share |
|1. Using Explorer, create the D:\Packages folder and share it as Packages |
|2. Allow the Everyone group Change permissions (Sharing Permissions) |
|Create the Logs Share |
|1. Using Explorer, create the D:\Logs folder and share it as Logs |
|2. Allow the Everyone group Change permissions (Sharing Permissions) |
|3. Allow the SMSInstall account Modify permissions (NTFS Permissions) |
| |
|Note: The SMSInstall account is the SMS Network Access Account and will probably need up be updated for your SMS setup. |
|Create the MigData Share |
|1. Using Explorer, create the D:\MigData folder and share it as MigData |
|2. Allow the Everyone group Change permissions (Sharing Permissions) |
|3. Allow the Domain Computers group Create Files/Write Data and Create Folders/Append Data permissions (NTFS Permissions) |
|4. Allow Creator Owner account Full Control (Default, NTFS Permissions) |
| |
| |
|Step 5 – Create a ZTI Image Package |
|Create a OSD Image Package |
|1. Using SMS Admin Console, create an OSD Image package with the previous captured image file. Use the following settings |
|a. Name: Windows Vista Enterprise |
|b. Image file: D:\Distribution\Operating Systems\Windows Vista Enterprise ZTI x86\VistaEnterpriseZTI.wim |
|c. Source: \\SRV001\Packages\Windows Vista Enterprise |
| i. Note: Type in the Source path |
|Create a OSD Image Program |
|1. Use the following settings |
|a. Name: Install Vista Enterprise |
|b. Product Key: Product key not required |
|c. License mode: Per Device or Per User |
|d. Domain: DOMAIN |
|e. Account: DOMAIN\JoinAccount |
| |
|Configure the OSD Image Program for ZTI |
|1. Networks Tab |
|a. OU: Workstations |
|2. Advanced Tab - Validation phase |
|a. Add Custom Action |
| i. Name: ZTI Validation |
| ii. Command: ZeroTouchInstallation.vbs |
| iii. Add all files (*.*) from \\SRV001\ZTI$\VistaEnterpriseZTI |
|1. Note: In order to see all files you need to select All Files *.* from the list box |
|3. Advanced Tab - State Capture phase |
|a. Add Custom Action |
| i. Name: ZTI State Capture |
| ii. Command: ZeroTouchInstallation.vbs |
|4. Advanced Tab - Preinstall phase |
|a. Add Custom Action |
| i. Name: ZTI Preinstall |
| ii. Command: ZeroTouchInstallation.vbs |
|5. Advanced Tab - Postinstall phase |
|a. Add Custom Action |
| i. Name: ZTI Postinstall |
| ii. Command: ZeroTouchInstallation.vbs |
|6. Advanced Tab – State Restore phase |
|a. Add Custom Action |
| i. Name: ZTI StateRestore |
| ii. Command: ZeroTouchInstallation.vbs |
|1.1.1 Add a distribution point |
|1. Add a distribution point to the image package |
| |
| |
| |
|Step 6 – Deploy a New computer using ZTI |
|Create a ZTI Installation CD |
|1. Using SMS Admin console create an OSD installation CD |
|a. Use the following settings |
| i. Automatically choose OS package |
|1. Note: Leave the other default checkboxes selected |
| ii. File name (script): \\SRV001\ZTI$\ZeroTouchInstallation.vbs |
| iii. Arguments: |
| iv. User name: DOMAIN\SMSInstall |
| v. Password: P@ssw0rd |
| vi. Name ZTI Install CD |
| vii. File name (iso): D:\ZTI_Install_CD.iso |
|2. Copy the D:\ZTI_Install_CD.iso to Z:\Diskimages |
|Deploy a bare metal computer |
|1. Create a new Virtual Machine with 512 MB RAM, named ZTI - NewComputer |
|2. Deploy Windows Vista to ZTI - NewComputer Virtual Machine by booting from the ZTI Install CD (ZTI_Install_CD.iso) |
| |
|Step 7 – Refresh a computer using ZTI |
|Prepare a computer for refresh using ZTI |
|1. On PC0002, logon as EndUserAccount and do some customizations |
|Refresh a computer using ZTI |
|1. Verify that the SMS Client is installed on PC0002 |
|2. Create an advertisement of the ZTI Image Program to the Install Vista collection |
|Verify the refresh |
|1. Verify that User State for EndUserAccount is migrated. |
| |
BDD 2007: How to Capture a Reference Computer Image
Published May 20, 2007 Microsoft
Compiled and Updated by Edward Saint Jackson
I’ve been playing HEAPS with the BDD 2007 of late, for personal interest and I’m going to sit the exam. I’ll share quite a few things that I’ve found with you but one thing I found really handy today was how to easily capture a reference computers image to WIM.
With the BDD it will create a bootable ISO image for you to use which will allow you to image your computer with the environments that you’ve specified in the BDD. What it will also allow you to do is capture a reference computers image. To do this, follow these steps;
- Install the reference computer with Vista and any other applications and setting changes you would like to be in your base build
- Sysprep the machine and shutdown/reboot
- Boot up the machine with the ISO image for Lite Touch Deployment
- When at the initial first prompt, choose the option Exit to Command Prompt and choose [Next].
- Map a network drive to your distribution share (net use s: \\servername\distribution$
- Run ImageX from S:\Distribution\tools\x86 with the following command line options: imagex /capture c: s:\wimimagename.wim “Image Capture Name”
Happy Imaging!
Building a Windows XP Image in BDD 2007 Part 1
Compiled and Updated by Edward Saint Jackson
Many people are interested in the utilities and features offered in Windows Vista deployment tools. They are also very interested in the new BDD framework. What many people don't realize is that you can use many of the Vista deployment tools to manage and configure Windows XP images.
The following guide will get you on your way to automated greatness of BDD.
The first thing you need to do is copy the OS files into the BDD infrastructure (like the entire XP CD to c:\temp OR share your CD-ROM and upload from there)
To do this, open the BDD Workbench MMC.
Next, click on [Operating Systems] and click [New] in the Actions Pane.
[pic]
[pic]
In the wizard choose, [Full set of source files] and click [Next].
[pic]
Insert the Windows XP SP2 CD or mount an ISO image on your BDD server. [Browse] to the appropriate drive and select it. Click [Next].
[pic]
Type in the “Destination directory name” you wish to use for the directory and click [Copy].
The operation to copy all the files will take a few minutes you'll see a progress bar similar to the following:
[pic]
This is actually just copying the source files into a directory in your distribution share. You can see the folder if you open your distribution share and browse to the Operating System folder. Note: The distribution share would have been created when you installed BDD. By default it will be on c:\distribution.
[pic]
Now that we have the source files we want to create a build. The build is the part where we specify custom options we want to automate.
• Click on the [Builds] branch in the BDD MMC. In the Actions pane click [New]
• Type in the “Build ID”, “Build Name”, and if needed, “Build comments”. Click [Next]
[pic]
• Select the [Windows XP Professional SP2] source files you wish to use to build your install. Click [Next]:
[pic]
Now you should see your build in the Builds details pane (middle pane). If you double click on the build you will see some options that can be adjusted.
In the General Tab you can adjust the operating system Source, Build names and Version number. You can also adjust comments.
[pic]
The Setting Tab allows you to fix any mistakes or allows for adjustments in the information you entered during the wizard. It also allows you to access the Sysprep.inf and Unattend.txt files.
• Type in your “Volume License Key” from your Microsoft Volume License Agreement. Click [Next].
• In the next screen you need to provide a “Full Name”, “Organization”, and an “IE home page”. Then click [Next] (don't forget to use "http://" when entering in the web URL).
Specify a local Administrator Password and click [Create].
[pic][pic][pic]
Basic Settings for WIM in BDD, properties under Builds
We are still dealing with Windows XP so we still have to sometimes manipulate these files manually. A good example is the case where we need to add SATA drivers to a build. The majority of SATA drivers were released after Windows XP. So even in the SP2 release many new hard disk controllers are not in the Windows XP source files by default. (We deal with this manually by pressing F6 during the text mode setup)
To lay down some context here is the usual startup process for Windows XP install:
Boot Computer ( Start Windows XP install from CD or network ( Start Text Based install ( Load Mass Storage Drivers ( Detect Hard Drives ( Select install Options ( Reboot in the GUI Install Mode.
If there is a problem with the Mass storage Driver you will often get a blue screen when loading the XP GUI installer.
We will cover integrating mass storage drivers into the Sysprep.inf files and Unattend.txt files in a future article.
Finally, there is the -Task Sequence Tab-. The tasks that you find on this tab are all the steps BDD takes to build the image. This is an extremely flexible and easy way to customize your build.
*** 4 items you should disable per Halifax settings: Disable [Tattoo], Disable [Restore User State], Disable [Restore Groups], and Disable [OSD Only].
-- note: you will have to capture the WIM manually now, see below. I disabled the autosysprep/autocapture for a more exact, reliable (though manual) process.
[pic]
Task Sequence in BDD, properties under Builds
[X] – BDD XP Alert: If you are installing/capturing Windows XP
Begin error info -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
This brings us to another issue with Windows XP and BDD 2007. Due to the way BDD 2007 partitions drives it causes that partition to not be compatible with Windows XP. This has been called the BDD Uber bug in some circles. Thanks to the fellows at there is a workaround to patch this bug.
First you need to create a text file with a .reg file extension. next past the following line of text (without the dashed line):
-------------------------------------------------------------------------------------------------------------------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVICES\VDS\ALIGNMENT]
"LessThan4GB"=dword:00000000
"Between4_8GB"=dword:00000000
"Between8_32GB"=dword:00000000
"GreaterThan32GB"=dword:00000000
--------------------------------------------------------------------------------------------------------------------
Save the file to the Distributions\Scripts folder.
Next in the Task Sequence dialog box seen above Click "Preinstall" Then click Add.
You will see a "New task" appear in the list. Use the "UP" Arrow button to move the custom task to the beginning of the list.
Name the task: Fix WinPE 2.0 Bug.
Then enter the following in the command line: reg import %SCRIPTROOT%\YOUR_REG_FILE.reg (Custom_Set_VDS_Alignment.reg)
This fix will make sure that Windows PE uses the correct settings when setting up the Windows XP partition.
End error info -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Finally you're ready to build your deployment point, and kick off your XP install. In the Deploy->Deployment Points branch in the BDD workbench click [New] Choose a lab deployment point. Accept the default options in the Deployment Point wizard. At the the end click [Create]. Once your Lab deployment point has been created, click on it in the Information pane, and then in the actions pane click Update. This will build a new deployment point and create the necessary files you need to boot up Windows PE.
Using the WDS server or the LiteTouchPE_x86.iso file found in [Drive]\Distribution\Boot.
Start WinPE 2.0. (See how to configure WDS for information on booting up over a network)
[X] Possible PE Loading error: ZTI error Unhandled error 0x80070040 TSMBootStrap.exe -2147467259
Begin error info ---------------------------------------------------------------------------------------------------------------------------
Short fix: [Update] your deployment point in BDD, re-burn your CD from the LiteTouchPE_x86.iso AND delete the c:\MININT folder from you target computer.
[pic]
OR
One of the most common issues with MDT 2008 / BDD 2007, LiteTouch and ZeroTouch, is leftover junk from a previous installation preventing a second installation to continue... The solution... Get rid of the junk...
Note: Make sure to do these changes only to the winpe images used for bare metal installations... (wiping the disk in the middle of a refresh installation might lead to , ehh, unexpected, results)
LiteTouch
Create a script that removes the MININT and _SMSTaskSequence folders (if present).
CleanSetupInProgress.cmd
If Exist C:\MININT\nul rd C:\MININT /s /q
If Exist C:\_SMSTaskSequence\nul rd C:\_SMSTaskSequence /s /q
Call the script from unattend.xml (in WInPE 2.1)
Unattend.xml
16
1024
60
768
Lite Touch PE
1
cmd /c CleanSetupInProgress.cmd
Lite Touch PE
2
wscript.exe X:\Deploy\Scripts\LiteTouch.wsf
Restart
ZeroTouch (SMS 2003 OSD FP)
Just add a winbom.ini that will wipe and format the disk... se below example...
winbom.ini
[Factory]
WinBOMType=WinPE
Reseal=No
[WinPE]
Quiet=Yes
Restart=No
[PnPDriverUpdate]
[PnPDrivers]
[NetCards]
[UpdateInis]
[FactoryRunOnce]
[Branding]
[AppPreInstall]
[DiskConfig]
Disk1 = Disk1.Config
[Disk1.Config]
WipeDisk = Yes
Size1 = *
PartitionType1 = Primary
FileSystem1 = NTFS
QuickFormat1 = Yes
SetActive1 = Yes
End error info ---------------------------------------------------------------------------------------------------------------------------
[pic]
Windows PE Mode Booting (from your CD or USB Drive)
Once PE is booted up and initialized, you will be presented with the Windows Deployment Wizard:
[pic] Windows Deployment Wizard from PE Mode
• Choose the correct Keyboard layout for your needs, and click [Next]
• You will be presented with a screen asking for an account with permissions to access the Distribution share you set up on your BDD server.
• Next you will be asked for a computer name.
• Next you will be asked for a domain name. If you want to capture this install to a base WIM Image you must leave the setting to the default "Join A workgroup" Click [Next].
• The following screen prompts you to specify where your user settings are being stored. As are preparing a base image, leave the default setting as is and click "Next".
• Choose the “Windows XP SP2 Build Files” (this is what you just setup in the Deployment Desktop), Click [Next].
• Choose your Time Zone Click [Next].
• Choose any applications you added. (For base images, and first time installs it's fine if you haven't added any applications yet) click [Next].
• Accept the default setting for capturing the image. Rename the image file should you want another name. Click [Next].
• In the final screen you may review details about the install. When you are satisfied with the results click [Begin].
[pic]
Applying Imaging from PE Mode
This Window will pop up and detail the installation progress. If all went well Windows XP should be installed in a fully automated fashion.
! The end product will be a Windows XP WIM image in your Distributions\Capture directory – but that’s in Part 2.
This concludes Part 1. In Part 2, we will pick up where we left off here, and will explain how to use the WIM image to quickly deploy Windows XP desktops.
Let me know what you think of this BDD guidance. If there is a particular element you want to know about in regards to BDD, or any topic for that matter just let me know! I can be reached at Eddie.Jackson@ or MrNetTek2000@
Building a Windows XP Image in BDD 2007 Part 2
Compiled and Updated by Edward Saint Jackson
First make sure that your Windows XP was properly installed, meaning you have your perfect image completed. If for whatever reason you could not get the above to work for you, that’s okay. Look at Page 27.
BDD will bring your through the basic install launched from the GUI.
[pic] Automated Setup Begins
Next you will see the text based installation:
[pic] Automated Console Setup Screen
Finally the GUI setup portion will commence.
[pic] Automated GUI Setup Screen
BDD Light touch wizard will execute the tasks specified in the build Tasks tab.
[pic]
Completing BDD Installation
Sysprep will run on the workstation once all the tasks are completed. This may take a while. Also I have noticed a small bug where you sometimes have to manually set the current window context to the System Management Server dialog box. If you notice it's taking a long really long time (30 minutes +) Just click in the Window.
[pic]
Sysprep is beginning to run
The computer will then reboot into WinPE and capture the image to the capture share on the BDD server.
[X] - Possible PE Loading error: If the computer does NOT restart automatically.
Begin error info -------------------------------------------------------------------------------------------------------------------------------------------------------------
START HERE ONCE YOU HAVE YOUR PERFECT IMAGE
(meaning just build/tweak your current computer image until it’s ready for sysprep):
First download/copy sysprep files to c:\sysprep
1. If it is XP, run sysprep -mini -quiet -reseal
1. If it is Vista, run sysprep /generalize /oobe
2. After shutdown(which may take awhile-up to 30minutes), boot into Windows PE 2.0 from your CD or USB Drive
3. Exit to command Prompt. [Next]
4. Connect to your BDD server "net use F: \\Server\distribution$” Windows PE 2.0 from your CD or USB Drive
5. Navigate to F:\tools\x86
6. If XP, run imagex /capture /compress maximum C:\ F:\Captures\XPImage.wim "XP Image"
6. If Vista, run imagex /capture /compress maximum /flags “Enterprise” C:\ F:\Captures\VistaImage.wim "Vista Image"
[pic]
IMAGEX Capture from PE Mode command console
! If you experience network connection latency/time out issues, try capturing the WIM to a USB Drive, then upload that to the Capture Folder located on the BDD Server.
end error info -------------------------------------------------------------------------------------------------------------------------------------------------------------
[pic]
PE Mode Capturing WIM to Capture folder on BDD Server
If you open the Distribution folder on your BDD server and browse to Captures you can see the newly created WIM Image.
[pic]
The first step to deploying Windows XP with a WIM image is to add it to the operating systems in BDD.
• Click Operating Systems
• In the actions pane click new.
• In the first New OS Wizard panel choose the [Custom Image File] option. and click [Next]
• In the next panel, Click Browse and choose the WIM image found in the Captures folder. If you want to move the image file when you integrate it check the Move Check box. Click [Next]
• Choose [Setup files are not needed]. Click [Next]
• Change the “destination directory” name should it be necessary, then click Copy, or Move if you're moving the file.
You should now see the Windows XP based WIM image in your Operating systems details pane.
[pic]
Now we need to create a new build for the WIM based Windows XP.
• Click [Builds]
• In the actions pane click [New].
• Provide a “Build ID”, “Build Name”, and “Build comments”. Click [Next]
• Enter in the proper product VLK product KEY. Click Next
• Enter the “Full Name”, “Organization” and “IE home page” desired. Click [Next].
• Enter a “local admin password”. Click [Create].
This will create a new Build based on the WIM image. Before moving forward there is one point that should be made. Because the WIM image is an image of a syspreped Windows XP, The first time we boot up a workstation that we applied the image to the workstation will run the Mini Setup mode. This mode is a special GUI only mode of Windows Setup. By using the WIM image we can skip a large portion of the Windows XP install process. The only thing we need to keep in mind is that the setup process that kicks off during the Mini setup is not automated by the unattend.txt file. It is driven by the Sysprep.inf. This is important to note because BDD cannot alter the setup process that takes place in the mini-setup, so your only way to customize that part if the installation is to use the Sysprep.inf file. (Going back to the example we used in the first bdd article you may need to modify this file if your using certain SATA drivers).
Finally because we are deploying Windows XP we need to re-insert the WinPE 2.0 fix we saw in the first article into the task lists. This will again ensure that the partitioning is done correctly.
That's it! We can now deploy Windows XP using the WIM image. Following the same procedure we used in part 1 you can test the installation of the new WIM image.
Once you have successfully captured that first golden image, and you have tested Task Sequence (pg 36), the next two important tasks will be:
1 - Building and adding your applications to the MDT(Applications (pg 54)
2 - Injecting drivers to the MDT(Out-of-box drivers (pg63). ! Remember when you inject drivers you must recreate your USB Keys/Bootable PE CDs (pg38).
Now for those who are still not quite sure what we did here I made a simple flow diagram to illustrate what is going on.
The first part of the exercise, we performed the following steps: (Building a Windows Image in BDD 2007 Part 1)
[pic]
Next we deployed the WIM:
[pic]
As you can see BDD uses the same steps for deploying and capturing images or just deploying images. The recommended approach for building your images is to build them up in an iterative process. When we create the WIM image we are still using the same process to build a Windows XP image, however we jump into the workflow at a much later point in the installation process. (about the half way point of the GUI Based install during a regular installation) This provides a much faster way to build a new base image, or to deploy an already customized image. With Driver Injection you can even use the WIM image for most situations where you would need to create a new image to accomodate new hardware.
[pic]
Let me know what you think of this BDD guidance. If there is a particular element you want to know about in regards to BDD, or any topic for that matter just let me know! I can be reached at Eddie.Jackson@ or MrNetTek2000@
Adding Applications to BDD
Compiled and Updated by Edward Saint Jackson
BDD allows you to automate the installation of base applications as part of the image building or deployment process.
This is really useful if your company can’t afford an application management suite like SMS or Alteris. This functionality is also helpful if you want to automate the way a base application is installed in your image (for instance Microsoft Office).
To add an application into your build/deployment process click the Distribution Share->Applications branch. In the actions pane click “New” This will start the new Applications Wizard.
We will setup Adobe Acrobat Reader 8. This application is pretty common on most corporate installs. For this install we will choose the first installation option “Application with source files”. This will allow us to specify an application that is installed from an installer package. If we wanted to install an application that is launched form a shortcut. (network installed apps) we can use the second option seen in the following image.
[pic]
Next select a folder where the necessary installation source files are stored. Make sure you have all the necessary installation files needed to install the application. in the root of the folder you choose. Some applications will have a more complex folder structure in in their installation media. Make sure the full installation folder structure is in the root of the folder you specify. If the application is in a temporary download folder or other temporary location on your BDD server you can choose to move the installation files to your Distribution share. (C:\Distribution\Applications)
[pic]
Specify a Descriptive folder name for the application. Often if you will be using multiple languages you may want to specify that in this field. Spaces are permitted, and should not cause any issues later on.
[pic]
Finally specify a working directory, and the command line to install the application in and automated and or silent mode. Most applications installs now come with switch options that allow them to be installed in an automated fashion.
If the package is a standard msi you can use “msiexec /quiet /norestart install_package.msi”
Some packages may require an MST of a Microsoft Transform File. A good example of this is Office 2003. In order to make an MST file you usually need a packaging software, or in the case of Office the Office Resource Kit has tools to help with this. We will cover packaging Office for BDD in a future article.
[pic]
Once we have added the package to our BDD workbench we can try it out in our image build/deployment process.
[pic]
During the “Deployment Wizard” any applications we have added will appear in during the wizard interview process. We can pick and choose the applications we want to install. Your menu may many more applications that you have compiled and added to the BDD Application Console, or your menu may have just a few apps.
[pic]
*** you can use BBDAppsSort.exe to sort these names on the menu.
When the deployment process enters the “Install Applications” stage, the applications will be installed you selected.
[pic]
A side note for XP installs:
It is recommended in the BDD documentation to use the applications feature in BDD to install Hotfixes and roll-ups.
Adding Drivers to Out-of-Box Drivers
Compiled and Updated by Edward Saint Jackson
Right click Out-of-Box Drivers and Select [New]
[pic]
Browse to the driver location and then Select [Add]
[pic]
You will see driver being added
[pic]
You have successfully added the driver and must now recreate your USB Keys or Bootable PE CDs.
Top Ten Most Common BDD 2007 Issues
Compiled and Updated by Edward Saint Jackson
Ben Hunter put together these great ten items to watch for if you're using the BDD to image your systems.
Number 1. - Partitioning within the Unattend.xml
BDD likes (no needs) to look after partitioning itself! Do not do this via Unattend.xml. The most common symptom of this is the Task Sequence not restarting after the operating system has been installed.
Number 2. - XP disk partitioning
Affectionately know as the UBERBUG, this little baby causes some machines to blue screen when an XP image is applied to a machine that has been partitioned with Windows PE 2.0. For more information see my previous blog.
Number 3. - Trying to deploy images with WDS
This is a common misunderstanding about the relationship between BDD and WDS. Let me assure the relationship is not a close one, BDD is just using WDS! Simply put uses WDS as a mechanism to boot the Lite Touch WIM which connects to the BDD deployment point. Once this has happened it has nothing more to WDS, nothing! So my advice here is DO NOT try to load an image captured with BDD into WDS.
Number 4. - Failure to join the domain
Oh the joys of documentation, one little error and everyone has strife. The BDD configuration reference states that "MachineObjectOU=NewYork" , it's wrong! Instead it should say something like this "MachineObjectOU=OU=NewYork,DC=DammTypos,DC=com". So if for some reason your machine fails to join the domain then make sure you have specified the correct OU in the correct manner.
Number 5. - Drivers
Where do I start with this one? This could be a number of blogs on its own, maybe I could use this as a teaser to make you keep coming back and finding more useful information on my blog(did I say that out loud?). I will write a blog(s) on drivers soon.
Read on for the last five...
Number 6. - Creating custom WIM image without using /flags
So you already have a Vista machine built up and you have decided that you want to manually image it . So you capture an image and try to import it into BDD but it won't work. Well the real lesson is you should have used BDD to create and capture the image then you wouldn't of had this problem in the first place. But if you really have no choice then remember to specify the correct flags for the Version of Vista you a capturing. Here is and example command line:
imagex /flags “Enterprise” /capture c: d:\image.wim "Custom Image"
And if you want to add a flag to an image you have already capture try this command line:
imagex /flags [flags value] /info mywim.wim [image index] [new name] [new description]
Number 7. - SQL connectivity
Having trouble connecting to your SQL database well take heed of these four simple rules, and your life will be simpler :
1. Make sure your BDD account has access to the database
2. Ensure that the "surface area" of SQL is opened up enough to allow connections
3. Use named pipes - it makes life easier as you cannot use integrated security with TCP/IP sockets
4. If you have an instance then be sure to specify it when connecting to the DB
Number 8. - Memory requirements for Vista PE
Do random things happen when you try to build some machines? Do you have 256Mb of memory? Well the problem you have is that Windows PE 2.0 can boot with only 256MB of memory but it cannot run. This means that when it tries to do stuff it freezes randomly, NICE! So when building machines make sure you have at least 512Mb of memory and everything will be rosy.
Number 9. - Not removing the MININT folder
Are you testing your build and nothing you do seems to have any effect. Usually this is caused by the fact that BDD is storing information from a previous build in the MININT folder. So commit this to command to memory, your gonna need it:
rd c:\minint /q/s
And while your at it you may as well remember this one:
rd c:\_SMSTaskSequence /q /s
Number 10. - Adding Windows PE to console
Are you trying to add your customized version of Windows PE to the console, yeah the one that you spent hours getting just right! Well its not going to work, the Windows PE source files need to be taken straight off the volume source CD. BDD will then combine this with the OS source files and create a version customized just for BDD.
|CREATING BOOTABLE WINPE USB DEVICES |
|Compiled and Updated by Edward Saint Jackson |
|[pic] |
| |
| |
|Community News... |
| |
| |
By: Erik Chapple
Posted On: 5/6/2008
Introduction
This document reviews the processes involved with creating USB devices that boots into a Windows PE 2.0 environment. WinPE 2.0 is a Windows based environment leveraging the core components, that’s offered as part of the Windows Automated Installation Kit (AIK). WinPE 2.0 provides enhanced device driver support, Network support, ADSI, WSH and WMI support which makes it valuable tool for troubleshooting issues when the installed OS is not available. Additionally, Microsoft’s Deployment Toolkit and OSD in SCCM 2007 leverage WinPE 2.0 for OS deployment tasks that prepare the target system for imaging and for applying configuration items prior to starting the new OS.
Creating a Custom WinPE 2.0 CD ISO
From a computer with Windows AIK installed go to the start menu and run "Windows PE Tools Command Prompt" as “Administrator” from in the Windows AIK program folder. The following example commands create a customized PE ISO that can be burned to CD, applied to a bootable USB device or used to boot a virtual machine instance.
1. copype.cmd x86 E:\WinPE
2. imagex /mountrw E:\WinPE\winpe.wim 1 E:\WinPE\mount
3. + Add driver example + peimg /inf="E:\Drivers\NIC\WinXP\b57win32.inf" E:\WinPE\mount\Windows
4. peimg /install=WinPE* E:\WinPE\mount\Windows
5. copy “C:\program files\Windows AIK\Tools\x86\imagex.exe” E:\mount\Windows\Program Files
6. copy “C:\program files\Windows AIK\Tools\Servicing” E: \mount\Windows\Program Files\Servicing
7. peimg /prep E:\WinPE\mount\Windows "yes"
8. imagex /unmount E:\WinPE\mount /commit
9. copy E:\WinPE\winpe.wim E:\WinPE\ISO\sources\boot.wim "All"
10. oscdimg -n -bE:\WinPE\ E:\WinPE\ISO E:\WinPE\PE-VM.iso
Creating a Bootable USB Device.
The target USB 2.0 device should be at least 512mb. If the intention is to leverage the device as a portable deployment solution, potentially including USMT data migration, a larger device should be used.
Formatting
USB device with a single partition
------------------------------------------------
The example formats a device in preparation for WinPE 2.0 and assumes the USB device is detected as disk 1. Using a Windows Vista PC open a command prompt as “Administrator” and run the commands listed below.
1. diskpart
2. select disk 1
3. clean
4. create partition primary
5. select partition 1
6. active
7. format fs=fat
8. assign
9. exit
Formatting USB device with multiple partitions
------------------------------------------------------------------
To provide a portable, full featured deployment solution a USB device with multiple partitions can be leveraged. The first partitions will be dedicated to the boot environment and the other(s) for the deployment/migration data. This example formats a device in preparation for WinPE 2.0 and assumes the USB device is detected as disk 1. Using a Windows Vista PC open a command prompt as “Administrator” and run the commands listed below.
1. diskpart
2. select disk 1
3. clean
4. create partition primary size=512
5. create partition primary
6. select partition 1
7. active
8. format fs=fat32 quick
9. assign
10. select partition 2
11. format fs=ntfs quick
12. assign
13. exit
Applying the boot environment
Booting to Standalone Custom WinPE 2.0
----------------------------------------------------------
This example creates a customized version or WinPE 2.0 and installs it to a bootable USB device. Using a machine with the Windows AIK installed, open "Windows PE Tools Command Prompt" from in the Windows AIK program folder in the Start Menu. The following commands assume the USB device has been formatted with a bootable partition and was assigned the drive letter G:
1. copype.cmd x86 E:\WinPE
2. imagex /mountrw E:\WinPE\winpe.wim 1 E:\WinPE\mount
3. + Add driver example + peimg /inf="E:\Drivers\NIC\WinXP\b57win32.inf" E:\WinPE\mount\Windows
4. peimg /install=WinPE* E:\WinPE\mount\Windows
5. copy “C:\program files\Windows AIK\Tools\x86\imagex.exe” E:\mount\Windows\Program Files
6. copy “C:\program files\Windows AIK\Tools\Servicing” E: \mount\Windows\Program Files\Servicing
7. peimg /prep E:\WinPE\mount\Windows "yes"
8. imagex /unmount E:\WinPE\mount /commit
9. copy E:\WinPE\winpe.wim E:\WinPE\ISO\sources\boot.wim "All"
10. xcopy E:\WinPE\ISO\*.* /s /e /f G:\ (where G:\ is the drive letter assigned to the USB device)
Booting to a BDD 2007 OS Deployment WIM
---------------------------------------------------------------
In this example, BDD 2007 was used to create a custom Lite Touch Installation (LTI) “MEDIA” deployment point. When the deployment point is updated a LiteTouch_x86.wim file is generated containing the deployment, OS, application and driver collateral defined in the BDD Workbench. This WIM file is often larger than a single layer DVD so an external USB hard drive is a good solution. The following section assumes that the USB device is detected as disk 1. Using a Windows Vista PC where the Windows AIK is installed open a command prompt as “Administrator” and run the commands listed below.
1. diskpart
2. select disk 1
3. clean
4. create partition primary size=6656
note: this command creates a 6.5GB primary boot partition.
5. create partition primary
note: this command creates the second partition using the remainder of the drive space, size=n can also be used to define the size of the new partition size in MB
6. select partition 1
7. active
8. format fs=fat32 quick
9. assign
10. select partition 2
11. format fs=ntfs quick
12. assign letter=z
13. exit
Close the command prompt window then open the start menu and run "Windows PE Tools Command Prompt" as Administrator from in the Windows AIK program folder. The following section assumes that M: is the drive that hosts a BDD Media share named “deploy” and that the m:\deploy\LiteTouch_x86.wim is 7GB and the bootable partition created above was assigned drive letter E.
Imagex /apply m:\deploy\LiteTouch_x86.wim 1 e:
Creating Offline SCCM 2007 OS Deployment Media
--------------------------------------------------------------------------
SCCM 2007 can be used to create task sequences and their related files and dependencies to a DVD, CD set or a USB drive. Using external or off-line media will allow you to run the operating system deployment task sequence steps on computers that do not have a network connection or have a slow network.
In the Configuration Manager console, navigate to System Center Configuration Manager/ Site Database / Computer Management / Operating System Deployment / Task Sequences and perform the following steps to create a stand-alone media set.
Start the Task Sequence Media Wizard.
In the Task Sequence Wizard, on the Select Media Type page, select Stand-alone media.
If you selected CD/DVD set on the Media Type page, the files created are a set of .ISO files that need to be burned onto the media set. You can then use another product to burn the installation files onto the CD or DVD set.
Select a USB flash drive on the Media Type page, the files will be created and saved directly to the USB flash drive.
WinPE on a USB Flash Disk
Compiled and Updated by Edward Saint Jackson
The first thing you will need is a USB drive with 512MB or more of storage capacity (WinPE takes about 350MB of space.) The USB drive will be overwritten. You will also need WAIK installed on a Windows Vista client or 2003 server. There are more than a few steps to follow:
1. Format the USB drive. At a command prompt, execute the following commands:
1. diskpart - this will show the known drives on your PC. Make note of the drive number representing your USB drive.
2. select disk where # is the USB drive discovered above.
3. clean
4. create partition primary
5. select partition 1
6. active
7. format fs=fat32 or NTFS (I use NTFS, which has to be done from a Vista box or boot DVD due to diskpart version)
8. assign
9. exit
2. Go to the Start menu. Select "Windows PE Tools Command Prompt" from under the Windows AIK program folder. Run:
copype.cmd x86 c:\
3. Copy versions of ImageX, GHOST, or any tools you want to :\\iso
4. Create and store a wimscript.ini as in Step 4 above.
5. Run the following command to copy WinPE to your bootable USB drive:
xcopy :\\iso\*.* /s /e /f :\
QUICK: I just format my USB from steps 1-9 and then [copy files] over via drag n drop [pic] to [Flash/USB Drive]
You are ready to boot from the key now (make sure you have an updated boot.wim which is in the Sources folder – you update your wim by BDD Console – Deployments - Update)
Let me know what you think of this BDD guidance. If there is a particular element you want to know about in regards to BDD, or any topic for that matter just let me know! I can be reached at Eddie.Jackson@ or MrNetTek2000@
Example BDD Applications With Silent Switches
Compiled and Updated by Edward Saint Jackson
* Very useful to see how app setup works
[pic]
Adobe Acrobat Reader 8.0 x86 AdbeRdr80_en_US.exe /sPB /rs /rps
Adobe Flash Active X 9 x86 msiexec /i install_flash_player_active_x.msi ALLUSERS=1 /quiet
Adobe Shockwave 10 x86 msiexec /i sw_lic_full_installer.msi /passive /norestart
Adobe Standard 8.0 x86 msiexec.exe /i "acrostan.msi" TRANSFORMS="acrostan.mst" /passive
Alfred Bolliger Print Key 2000 5.10 x86 PrintKey2000.exe
BlueCrossBlueShield DDE cscript.exe dde.vbs
Business Objects Crystal Reports XI x86 setup.exe /S ADDLOCAL=ALL CLIENTLANGUAGE=EN PIDKEY=B6W60-01CS200-OOGYX71-OU10 DISABLEWEBUPDATES=1 ProductName=Standard INSTALLDIR="C:\Program Files\Business Objects\Crystal Reports 11" COMMONVERDIR="C:\Program Files\Common Files\Business Objects\3.0" /qb!
Dragon Speech Recognition SP1 x86 msiexec /i "Dragon NaturallySpeaking 9 Service Pack 1.msi" /passive
ePremis Online x86 cscript.exe epremis.vbs
Foward Advantage CDS Fax 36 x86 setup.exe /VERYSILENT SQLSERVER=HSVRLFAX1
Halifax Service Desk Desktop Shortcut cscript.exe servicedesk.vbs
Intel MCA Platform 1.11.2b x86 msiexec /i default.msi /passive /norestart
Intermec EasySet 5.4.4 x86 msiexec /i easyset.msi /passive /norestart
Intermec EasySet Config 1.0 x86 C5ScannerConfig.EXE
Java Runtime Environment 1.5.9 x86 jre-1_5_0_09(NEW).exe /s /v"/qn ADDLOCAL=ALL IEXPLORER=1 REBOOT=Suppress JAVAUPDATE=0
Kronos Workforce Central 5.1 cscript.exe kronos.vbs
Laptop Wireless Configuration HCHS-A 1.0 x86 Configure HCHS-A.EXE
Logitech Mouse Driver 2.22 x86 setup.exe /s
Logitech Mouse Driver-App 2.22 (updated) x86 Logitech_Drivers_App.exe
MedStat QMS Sybase Part 1of2 x86 MEDSTAT_Sybase_12.5.EXE
MedStat QMS Sybase Part 2of2 x86 MedStat_QMS_7518.EXE
Microsoft .Net 3.0 x86 dotnetfx3.exe /q /norestart
Microsoft .Net Framework 1.1 x86 dotnetfx.exe /q:a /c:"install.exe /qb /l"
Microsoft Administration Pack x86 msiexec /i adminpak.msi /passive
Microsoft Group Policy Managment x86 msiexec /i gpmc.msi /passive
Microsoft Internet Explorer 7.0 x86 IE7-WindowsXP-x86-enu.exe /passive /update-no /norestart
Microsoft Managment Counsel 3.0 x86 mmc3.exe /passive
Microsoft Office SP3 x86 MAINSP3.msp /passive /norestart
Microsoft Office Standard 2003 Service Pack 2 x86 SETUPSTD.EXE
Microsoft Power Point Viewer 2003 x86 msiexec /package ppviewer.msi /passive /norestart
Microsoft Visio Viewer 2003 x86 vviewer.exe /Q /C:"setup /q ACCEPTEULA=1 ASSOCIATE=1"
Microsoft Word Viewer 2003 x86 setup.exe
Microsoft Word Viewer 97 x86 setup.exe /QT
Microsoft WSUS Console 3.0 x86 wsus3.exe /q CONSOLE_INSTALL=1
Microsoft XML 6.0 x86 msiexec /package msxml6.msi /passive /norestart
Microsoft XML Parser 4.0 SP2 x86 msiexec /package msxml4.msi /passive /norestart
Motion C5 Knowles Speech Software x86 KnowlesSpeach.EXE
MS Office 2003-2007 Converters 1.0 x86 FileFormatConverters.exe /quiet /passive /norestart
NetLearning Administrator Online x86 cscript.exe netlearnadmin.vbs
Netlearning Citrix Web Client x86 ctxsetup.exe
New Boundary Prism Client 7.0.2 x86 HCHS.exe
Nortel Contivity VPN Client HCHS Staff 6 x86 setup.exe -s
Pacific Edge Project Office Client 4.3 x86 Project_Office.EXE
Philips OB TraceVue Web Access cscript.exe OBTracevue.vbs
Symantec Anti-Virus Endpoint 11 x86 msiexec.exe /i SEM11.msi INSTALLSERVER=0 RUNSCAN=0 RUNLIVEUPDATE=0 ENABLEAUTOPROTECT=1 ADDLOCAL=ALL REBOOT=ReallySuppress /qb!-
Screenshots From BDD Server
Compiled and Updated by Edward Saint Jackson
[pic]
[pic]
Mounting WIM to be able to add/delete from the OS Image
[pic]
Deployment Workbench
[pic]
-----------------------
[pic]
[pic]
[pic]
[pic][pic]
[pic]
-----------------------
3
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- jackson madison county school system jackson tn
- jackson city school jackson ky
- eddie calculator for fdic
- jackson radiology jackson ms
- jackson radiology jackson tn
- eddie cahill
- eddie cahill csi
- eddie cahill cancer
- eddie cahill photos
- erin cahill and eddie cahill
- eddie cahill movies and tv shows
- eddie cahill bio