This paper provides detailed information focusing on how the migration assistant works and how to install, configure, and use it. The paper also touches on some best practices dealing with server migrations and how best to optimize and streamline the entire process from start to finish.
Author: Shelley Palmer-Fettig
Download the .pdf version of this document here.
Contents
Introduction
To facilitate migration to Dell Server hardware, Dell has joined forces with Altiris as part of a recently announced extended partnership and created the Server to Dell Server Migration Assistant Version 1.0 for Altiris Deployment Solution. This product is designed to work with Altiris Deployment Solution and it snaps predefined jobs into the Deployment Solution Console to assist with the mundane and complex tasks associated with server migrations. This solution enables IT Administrators to fully migrate Server hardware running the Microsoft® Windows Server® operating system to Dell Server hardware while keeping the existing operating system and installed applications intact.
This white paper provides detailed information focusing on how this migration assistant works and how to install, configure, and use it. The paper also touches upon some best practices dealing with server migrations and how best to optimize and streamline the entire process from start to finish.
How to Install
The following steps are provided to install the Server to Dell Server Migration Assistant Version 1.0 jobs into the Altiris Deployment Solution Console.
Assumptions:
- The user has a basic understanding of Altiris Deployment Solution including System Tokens.
- Deployment Solution Version 6.8 is deployed and functioning properly.
- The Altiris Deployment Solution program directory is located at C:\Program Files\Altiris\eXpress\Deployment Server.
Step 1:
Obtain the predefined jobs from the following location and copy to the Altiris Deployment Server:
ftp://DMA:1234Dell@dtxdropbox.dell.com/
Step 2:
Execute the DELL_MIGRATION_ASSISTANT.EXE file from the Altiris Deployment Server. The following informational message will be displayed. Click OK to continue.
Note: The install file is programmed to automatically copy the supporting files to the above mentioned program directory and import the predefined jobs into the Deployment Solution Console.
Step 3:
If the program directory exists, click Unzip to continue; otherwise, change the path to reflect the installed directory. For example, if your program directory was installed to D:\Program Files\Altiris\eXpress\Deployment Server, the entire changed path in the Unzip to folder location would be: D:\Program Files\Altiris\eXpress\Deployment Server\Dell\Sysprep.
Click OK on the following screen:
Note: If the program directory is different from the one listed in Step 2, then the predefined jobs will have
to be manually imported. There are two options available for manually importing:
- Option 1:
- Browse to the Altiris Deployment Solution program directory. For example, D:\Program Files\Altiris\eXpress\Deployment Server.
- From within this directory, browse to the .\Dell\Sysprep directory.
- Edit the INSTALL.BAT file to reflect your Altiris Deployment Solution drive letter and path.
- Execute the INSTALL.BAT file to import the Server to Dell Server Migration Assistant Version 1.0 predefined jobs into the Jobs pane of the Deployment Solution Console.
- Option 2:
- Launch the Deployment Solution Console.
- Right-click in the Jobs pane of the console.
- Click Import.
- Click Browse, and then browse to the DELLMIGRATE.BIN file located in the .\Dell\Sysprep folder of the Altiris Deployment Server program directory.
- Click OK. Note: This action successfully imports the predefined jobs into the Deployment Solution Console.
How Does It Work?
The predefined jobs are based on Microsoft Sysprep methodologies obtained from the updated "Building a Single Image for Dell PowerEdge Servers using Altiris Deployment Solution -- 2nd Edition" white paper, located at http://www.altiris.com/dell. To summarize, the predefined jobs prepare the source server by copying Dell mass storage and Plug-and-Play drivers to a .\Dell directory. In addition, the Microsoft Sysprep utility is also copied to a .\Sysprep directory. The source server then runs the Sysprep utility and prepares itself for imaging. The Source Server image is then captured and deployed to the target Dell server hardware. For more details on how the jobs work, continue to read this section.
When the predefined jobs have been successfully imported, you should see the following jobs in the Jobs pane of the Deployment Solution Console:
Functionality of the Jobs Defined:
Note: The tasks within the predefined Deployment Server jobs (with the exception of the capture and distribute disk image tasks) have been designed to run in the DOS pre-boot environment. The capture and distribute disk image tasks have been designed to use the Deployment Solution default pre-boot environment, whatever that may be. If desired, the image tasks may be edited to work also in the DOS pre-boot environment. As long as the Altiris PXE Server is installed and the PXE Image file for DOS has been configured to use either the default UNDI drivers or the specific NIC drivers for the various network cards in the environment, the predefined jobs should work as designed.
- Capture Source Server Image (For Rollback)
- Captures the Source Server image named using the same name as the Windows NetBIOS, with an "-RB" appended to the image name. The "-RB" signifies that this image is the "Rollback" image and places the image in the .\Program Files\Altiris\eXpress\Deployment Server\Images directory, for example, .\Images\AUSEXCH01-RB.IMG.
Note: It is not required to capture the Source Server image before attempting to migrate to the Dell Server, but is highly recommended. If anything goes wrong with the attempted migration, the Source Server can be restored to its original configuration with its previously captured image.
- Sysprep Source Server
- Copies the supplied mass storage controller and PnP drivers for Dell x3xx through x9xx Servers to a .\Dell directory on the Source Server.
- Copies the supplied Sysprep utility and supporting files to a .\Sysprep directory on the Source Server.
- Copies the DELTREE.EXE file to the C:\Windows\System32 directory on the Source Server.
- Note: Even though the .\Sysprep directory should delete itself automatically after running the Sysprep mini-setup, this directory will sometimes not be deleted, especially if files are executed from this directory during the Sysprep mini-setup process as instructed by the [GuiRunOnce] section of the SYSPREP.INF file. By instructing DELTREE.EXE to execute from the SYSPREP.INF file, it will be certain that the .\Sysprep directory will be completely removed from the target Dell hardware after the image deployment.
- The sample SYSPREP.INF file containing the embedded System Tokens is copied to the Deployment Server's temp directory and named after the Computer ID assigned by Deployment Solution, followed by an .INF extension, for example, 5000058.INF. This file is then tokenized in the DS job 3. Capture Source Server Image, and any instance of a System Token is replaced with respective data from the Altiris eXpress database (if present). The ID.INF file is then copied to the Target Dell Server hardware and renamed back to SYSPREP.INF with the data values from the database. The Sysprep mini-setup process now has the information needed to properly configure the target server.
- The following device path is entered into the HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath registry.
Note: The device path is entered directly into the registry to reduce complications. Also, there is a limit to how many characters you can have in the OemPnPDriversPath= line of the SYSPREP.INF file. By entering the path directly into the registry, you avoid potential pitfalls.
%SystemDrive%\Dell\audio;%SystemDrive%\Dell\cs\1;%SystemDrive%\Dell\cs\2;%SystemDrive%\Dell\cs\3;%SystemDrive%\Dell\cs\4;%SystemDrive%\Dell\cs\5;%SystemDrive%\Dell\cs\6;%SystemDrive%\Dell\cs\7;%SystemDrive%\Dell\cs\8;%SystemDrive%\Dell\m\bc;%SystemDrive%\Dell\m\ch;%SystemDrive%\Dell\m\co;%SystemDrive%\Dell\m\cy;%SystemDrive%\Dell\
mgmt\;%SystemDrive%\Dell\n\bc\1;%SystemDrive%\Dell\n\bc\2;%SystemDrive%\Dell\n\intel\1;%SystemDrive%\Dell\n\intel\2;%SystemDrive%\Dell\non-
raid\bp\1;%SystemDrive%\Dell\non-raid\bp\2;%SystemDrive%\Dell\non-
raid\gem;%SystemDrive%\Dell\storage;%SystemDrive%\Dell\storage\9g\fiber;%SystemDrive%\Dell\storage\9g\perc5;%SystemDrive%\Dell\storage\9g\sas-
nonraid;%SystemDrive%\Dell\storage\9g\scsi-
nonraid;\%SystemDrive%\Dell\v\ati;%SystemDrive%\Dell\v\int;%SystemDrive%\Dell\v\rn5;%SystemDrive%\Dell\v\vol;%SystemDrive%\Dell\misc;%SystemRoot%\inf
Sysprep will execute to prepare the Source Server for migration to the Dell Server hardware. As part of this preparation, all hardware device configurations will be stripped away to provide a higher success rate when migrating the same Windows Server operating system to different Dell hardware. The following command is executed:
%systemdrive%\sysprep\sysprep.exe -reseal -quiet -activated -mini --nosidgen
Note: The -nosidgen switch prevents new SIDs from being generated during the Sysprep mini-setup process. This takes into account any possible domain controllers or role servers that could be affected with a SID change. If a SID change is desired, simply remove the -nosidgen switch from the command line.
If the Source Server is ACPI compliant, it will be shut down automatically through the Sysprep utility when it has finished executing.
Note: The Altiris AClient must be loaded on the Source Server BEFORE the predefined jobs can be used.
Note: It is NOT possible for the DS job's history in this step to be marked with a green checkmark indicating a successful execution because of the way Sysprep functions by removing all hardware device configurations from Windows. When Sysprep executes, it removes the NIC configurations from Windows, and the Altiris AClient loses the connection to the Deployment Server. The Deployment Server is then no longer in communication with the managed system to receive the job status. Removal of the hardware device configurations allows for a higher success rate when mass deploying the image to other vendor hardware. The hardware devices and configurations are re-added during the Sysprep mini-setup process through Plug and Play detection.
For more information on how to overcome this obstacle so that the remaining jobs listed below can be used, refer to the section "Preparations Before Using the Product".
- Capture Source Server Image
After the Source Server has been Sysprepped and shut down, the server is now in its final stages of preparations before being captured to an image file. When the Source Server boots to the pre-boot environment, the SYSPREP.INF file is tokenized in Deployment Solution System Tokens. Tokenization provides greater flexibility, alleviates manual intervention, and reduces human error when deploying and configuring systems. The tokenized SYSPREP.INF file is then copied to the Source Server, which is then captured in the image file using the next sequential DS job. Tokenization ensures that the same NetBIOS name of the Source Server is used for the target Dell Server hardware, allowing server applications dependent on the NetBIOS name to continue functioning when fully migrated.
Note: The migration assistant product has been designed to copy an instance of the SYSPREP.INF file with no Deployment Solution System Tokens as a fallback in case the script to perform the token replacement does not execute for whatever reason. If the migration process gets this far, and the Source Server image is successfully captured and deployed without performing the token replacement, the user can simply enter the requested information when prompted on the Target Dell Server and continue.
- The PAGEFILE.SYS file is deleted to keep the size of the image file deflated by executing the following command:
.\firm -q delete c:\pagefile.sys
Note: When the image has been deployed, the PAGEFILE.SYS file will be regenerated and sized appropriately based on the amount of RAM on the target Dell Server.
- The image will be captured using Deployment Solution's default configured pre-boot environment and named after the NetBIOS name of the Source Server. By default, the image is saved to the .\Images directory of the Altiris Deployment Server, for example, .\Images\AUSEXCH01.IMG.
Note: The successful capture and distribution of the disk image is solely dependent on the proper configuration and optimization of the pre-boot image files. For example, if you are not using UNDI in the DOS pre-boot environment, ensure that the proper NIC drivers are included and configured in the pre-boot image files. If the Altiris Deployment Solution for Dell Servers add-on product is installed in the Deployment Solution Console, the latest NIC drivers for Dell Servers will be installed by default. During installation, if the pre-boot environments have been pre-installed and the PXE Image files have been created, the add-on product will automatically optimize the pre-boot environments for bare metal server provisioning.
Note: Use caution to ensure that the Source Server does NOT boot to Windows Server before the image has been captured; otherwise, all the preparation work you've completed prior to this step will be discarded. The "Create Disk Image" task in the DS job is programmed to instruct the Source Server NOT to boot to Windows before capturing the image to avoid a potential pitfall. However, even though the task has been instructed to not boot the server to Windows before capturing the image, it could still potentially happen.
- *Deploy Source Server Image to Dell Server
-
The previously Sysprepped and captured Source Server image is now deployed to the target Dell Server hardware. The Dell Server has now assumed the role of the retired Source Server.
Note: The asterisk "*" in the job name designates that this job requires manual intervention.
Note: The "Distribute Disk Image" task in this DS job must be edited to point to the previously captured Source Server image file. This file will be named after the computer's NetBIOS name of the Source Server. For more information on how to make this change, refer to the section "Using the Product".
Preparations Before Using the Product
The Server to Dell Server Migration Assistant is based on the Microsoft Sysprep utility. The accompanying SYSPREP.INF file requires specific user data to be entered when the computer is going through its Sysprep mini-setup process. This data includes Product ID, Registered Name and Organization, Computer Name, Time Zone, Licensing Configurations, etc. In order to automate the entire process without requiring user intervention on the computer, this specific user data must be entered in the respective locations of the SYSPREP.INF file. Rather than specifying this information manually, Altiris is able to leverage the use of System Tokens to inject most of this required data (captured by the Altiris AClient) from the Altiris eXpress database directly into the SYSPREP.INF file. For a complete listing of the SYSPREP.INF file and its use of Altiris Deployment Solution System Tokens, refer to "Appendix A -- Sample SYSPREP.INF File with Embedded System Tokens".
Note: It is possible to leave the respective data fields blank when Sysprepping a computer; however, when the image is deployed to the target Dell hardware, the user will be prompted for this information. This is not recommend, but provides flexibility if deploying the Source Server image from CD/DVD independent of the Altiris Deployment Solution. The following section will highlight the areas of the SYSPREP.INF file that must be edited.
Editing the Sample Sysprep.inf File
A copy of the Microsoft Sysprep utility and a sample Sysprep.inf file is integrated into the migration assistant product. The SYSPREP.INF file includes support for Dell xx3x through xx9x Servers, including support for the mass storage controllers found throughout these servers. The SYSPREP.INF file requires some user input before it can be effectively used through an automated process. This section highlights those user input areas of focus.
- Browse to the .\Program Files\Altiris\eXpress\Deployment Server\Dell\Sysprep directory.
- Open the SYSPREP.INF file using a document editor, such as Microsoft Windows® Notepad.
- Find the line labeled ProductKey="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx". Enter the same Product ID or a valid Windows Product ID that was used to deploy the original Source Server.
Note: A valid Windows Product ID used to deploy the Source Server must be entered on the respective line of the SYSPREP.INF file. This ID is used to re-deploy the same image to the target server. If the Product ID is unknown at the time of capturing, or if it needs to be changed, the source image can be edited after being captured using Altiris ImageExplorer. All of the user information specified in this section can be entered using this utility.
- Since Microsoft recommends removing the computer from the domain BEFORE Sysprepping, the Altiris eXpress database no longer contains the domain information that allows the Altiris AClient to re-join the domain as part of the post configuration process.
The migration assistant product is configured to pull the Workgroup name from the Source Server as defined in the Altiris eXpress database and inject that data value into the JoinWorkgroup field of the SYSPREP.INF file. It is then your responsibility to re-join to the domain in one of the following ways:
- Allow the Sysprep mini-setup process to re-join by providing the Domain Credentials and Domain Name in the respective fields of the SYSPREP.INF file.
- Remotely initiate a "Reconfigure" job from within the Deployment Solution Console.
If you choose to remotely initiate a "Reconfigure" job from within the Deployment Solution Console, no further action is necessary. If you want to re-join to the domain using Sysprep, follow these directions:
- Find the line labeled ;DomainAdmin="Username" and remove the semicolon from the beginning of the line. Replace Username with an account that has permission to add a computer to the domain.
- Find the line labeled ;DomainAdminPassword="Password" and remove the semi-colon from the beginning of the line. Replace Password with the password to the computer account above.
Note: It is advised that you create and use a domain account with only permission to join computers to the domain. That way, if the Domain credentials specified in the SYSPREP.INF file are compromised, the user will only have permission to join computers to the domain and not Domain Admin privileges. It is not possible to encrypt the Domain credentials in the SYSPREP.INF file; rather, it is provided in clear text.
- Find the line labeled ;JoinDomain="Domain Name" and remove the semicolon from the beginning of the line. Replace Domain Name with the actual domain name.
- Find the line labeled JoinWorkgroup=%#*"select domain_name from dbo.computer where computer_id=%ID%"% and place a semicolon in front of the line.
- Save all changes made to the SYSPREP.INF file.
Using the Product
Assumptions:
- The user has a basic understanding of Altiris Deployment Solution, including System Tokens.
- Source Server is running Windows Server 2003, and the Windows directory is installed as C:\Windows.
- The Source Server and Target Server must have compatible HAL types.
- By design, the predefined jobs are configured so they do NOT change the Windows SIDs as part of the migration process. This allows for a higher success rate when migrating to the Dell hardware to allow applications and services that depend on this relationship to continue functioning. If the Source Server is joined to a domain, Microsoft recommends removing it from the domain BEFORE running Sysprep and then re-joining as part of the post configuration.
- Refer to the "Resources" section of this document for other "Your Mileage May Vary" scenarios when using this product in conjunction with Microsoft Sysprep.
- The Source Server has Deployment Solution's AClient installed, the service is running, and the computer is fully managed from the Deployment Solution console (allowing jobs to be dragged and dropped to it).
- Load the Altiris AClient on the Source Server.
- If the Source Server is joined to a domain, either manually remove it and place in a Workgroup by reconfiguring from the physical server, or follow the directions below to perform this task remotely from the Deployment Solution Console.
- Right-click the managed system in the Deployment Solution Console, and choose Configure.
- Click the Microsoft Networking icon on the left side of the screen.
- Click the Workgroup radio button.
- Enter the Workgroup name. It is possible to name the Workgroup after the Domain name to keep the Server in the domain master browse list.
- Click OK.
- Remove any hardware vendor management agents or software dependent on the presence of specific physical hardware devices, such as nonDell Hardware agents, NIC Teaming Software and configurations, etc., because they will become obsolete when migrating to the Dell Server hardware. Allow the Source Server to completely reboot after removing each instance so it can cleanse itself from those configurations.
- If the Deployment Server has been configured to use the Altiris PXE Server, make sure that PXE is enabled and is listed in the boot order BEFORE the hard drive. If PXE or DHCP is not used in the environment, then a boot disk must be created from the Altiris Boot Disk Creator to execute the pre-boot jobs. For more information, refer to the Altiris Deployment Solution documentation.
- With the Source Server turned on and the managed system active in the Deployment Solution Console, drag and drop the 1. Capture Source Server Image (For Rollback) job to the Source Server. The Source Server should reboot and either boot to PXE to capture the image or boot from the boot disk created from the Boot Disk Creator. This is a good way to test the image capturing process before attempting to capture the Source Server image after it has been Sysprepped. If the Source Server boots to Windows after it has been Sysprepped and before the image has been successfully captured, the entire Sysprepping process will need to be repeated.
- When the image capture is complete, the Source Server is back in Windows, and the managed system is active in the Deployment Solution Console, drag and drop the 2. Sysprep Source Server job to the Source Server. If successful, the Source Server should power down automatically if it is ACPI compliant.
- From the Deployment Solution Console, delete the previous job's history by clicking on the line item with an hour glass and pressing the Delete key. Click Yes to confirm deletion. You should see similar screens like the ones below:
- Drag and drop the 3. Capture Source Server Image job to the Source Server. The Source Server may indicate that it is managed, when in reality the Server is shut down. This is ok. Drag and drop the job to the Source Server regardless of which state it is in.
- Power-on the Source Server to capture the image using either PXE or a boot disk. Here, you must exercise caution. Watch closely to ensure that the Server attempts to capture the image before booting to Windows. If for any reason you see a message such as "Booting to Production" before the image has been captured, immediately turn the Server off and start to troubleshoot. If you
have performed your testing from Step 5, all should go well when capturing the image the second time around.
- After the Source Server image has been captured, the server will try to boot to Windows and attempt to go through the Sysprep mini-setup process. Ensure that either the Source Server is shut down after the image has been captured, or unplug the network cable from the back of the Server if you are going to allow it to boot back into Windows to watch the Sysprep process. These actions will prevent duplicate NetBIOS names on the network when the image is deployed to the Dell hardware.
- Delete the Source Server from the Computers pane of the Deployment Solution Console by highlighting the managed system and pressing the Delete key. Confirm the deletion. Note: Deleting the managed Source Server from the console allows the Target Dell Server to take the same NetBIOS computer name.
- In the Deployment Solution Console, highlight the 4. *Deploy Source Server Image to Dell Server job located on the left side of the Jobs pane. On the right hand side, double click on the Distribute Disk Image task.
- Click the folder icon and browse to the Source Server image from the .\Images directory, which was Sysprepped in Steps 8 and 9. Click Finish. See screen below.
- From the Target Dell Server, ensure that the hardware has been provisioned and PXE is enabled and set in the boot order BEFORE the hard drive. Note: For bare metal Dell Server provisioning needs, refer to the Altiris Deployment Solution for Dell Servers add-on product for more information. This product allows you to remotely configure the BIOS, DRAC, BMC, and RAID, among other functions.
- Power-on the Dell Server. If Initial Deployment is disabled in the Deployment Solution Console for Servers (default) and the Dell server is able to connect to the Deployment Server successfully, you should see the message The Deployment Server has instructed BootWork to wait. You should also see a new computer listed in the Computers pane of the Deployment Solution console, like the screen below.
- Drag and drop the 4. *Deploy Source Server Image to Dell Server job to the newly managed Dell Target Server.
Note: After several minutes, you should have the Source Server image deployed to the Dell Server hardware followed by the running of the Sysprep mini-setup process. After Windows loads, configures the NICs, and establishes a connection to the Deployment Server, the Dell Server should be named after the Source Server, both in Windows and in the Deployment Server Console.
- When Windows finally loads and the desktop is displayed, you may finish configuring the rest of the Server, such as specifying any static IP address information for the NICs if not using DHCP, re-loading management software, etc.
- If you did not choose to re-join the domain using the Sysprep mini-setup process and want to
perform this function from within the Deployment Solution Console, follow the instructions below:
- Click Tools > Options.
- Click the Domain Accounts tab.
- Click Add.
- Enter the Domain name, User name, Password, and Confirm Password.
- Click OK.
Repeat Steps 18a-e for any remaining Domains that exist in the environment.
- Right-click the managed system in the Deployment Solution Console, and then click Configure.
- Click the Microsoft Networking icon on the left side of the screen.
- Click the Domain radio button.
- Enter the Domain name.
- Click OK.
Note: The Server then adds itself to the domain automatically using the credentials you specified in Steps 18a-e.
Conclusion
This document provides very detailed information on how the Dell Migration Assistant works and how to operate it. The methodologies described and used in this white paper should apply to any Server vendor hardware. Your "mileage may vary" depending on the hardware compatibilities between the Source and
Target Servers.
Keep in mind that the Dell Migration Assistant will quickly become outdated over time as new drivers and hardware are introduced. Refer to the method for updating hardware components in the "Single Image for Dell PowerEdge Servers" White Paper link at http://www.altiris.com/dell. A condensed version of the paper has been published in the February 2007 edition of Dell Power Solutions and can be downloaded at http://www.dell.com/downloads/
global/power/ps1q07-20070193-Altiris.pdf.
The Dell Drivers are current as of the 9/11/2006 release of the Dell Server Assistant (DSA) CD and support all Dell platforms, x3xx through x9xx PowerEdge Servers.
Note: Dell Migration Assistant is provided by Dell as a means to demonstrate Altiris' Rapid Deployment Server's powerful capabilities when dealing with mundane and complex tasks such as Server migrations. It is NOT supported by Dell or Altiris, and the customer uses the Dell Migration Assistant at their own risk.
Resources
Microsoft Summary of Microsoft Sysprep Limitations
http://support.microsoft.com/kb/830958/en-us
Altiris Deployment Solution v6.8 Reference Guide
http://www.altiris.com/upload/deployment_003.pdf
Altiris Deployment Solution for Dell Servers Installation and Configuration Resources
http://www.altiris.com/delldeploy
Appendices
Appendix A -- Sample SYSPREP.INF File with Embedded System Tokens
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath="%systemdrive%\Sysprep\i386"
;Leave following line blank if deleting pagefile.sys from image
KeepPageFile=
;OemPnPDriversPath has been entered directly into registry from DS job
;OemPnPDriversPath=
[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=No
.
OEMSkipRegional=1
OEMDuplicatorstring="Sysprep"
TimeZone=%#*"select time_zone_index from dbo.computer where computer_id=%ID%"%
OemSkipWelcome=1
[GuiRunOnce]
Command0="%systemdrive%\%windir%\system32\deltree /Y %systemdrive%\sysprep"
[Display]
BitsPerPel = 16
XResolution = 1024
YResolution = 768
VRefresh = 60
[UserData]
ProductKey="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"
FullName="%#*"select lic_os_user from dbo.computer where computer_id=%ID%"%"
OrgName="%#*"select lic_os_org from dbo.computer where computer_id=%ID%"%"
ComputerName=%COMPNAME%
[LicenseFilePrintData]
AutoMode=%#*"select os_lic_auto_mode from dbo.computer where computer_id=%ID%"%
AutoUsers=%#*"select os_lic_auto_users from dbo.computer where computer_id=%ID%"%
;[TapiLocation]
;AreaCode=512
[Identification]
;DomainAdmin="Username"
;DomainAdminPassword="Password"
;JoinDomain="Domain Name"
JoinWorkgroup=%#*"select domain_name from dbo.computer where computer_id=%ID%"%
[Networking]
InstallDefaultComponents=Yes
[SysprepMassStorage]
;Adaptec Embedded Serial ATA HostRAID Controllers
PCI\VEN_8086&DEV_24DF="%systemdrive%\dell\storage\aarich.inf","\","Adaptec Embedded Serial ATA HostRAID Controller","Adaptec Embedded Serial ATA HostRAID Driver Ver 6.00 For Windows 2000/XP/2003"
PCI\VEN_8086&DEV_25B0="%systemdrive%\dell\storage\aarich.inf","\","Adaptec Embedded Serial ATA HostRAID Controller","Adaptec Embedded Serial ATA HostRAID Driver Ver 6.00 For Windows 2000/XP/2003"
PCI\VEN_8086&DEV_2652&SUBSYS_01801028="%systemdrive%\dell\storage\aarich.inf","\","Adaptec Embedded Serial ATA HostRAID Controller","Adaptec Embedded Serial ATA HostRAID Driver Ver 6.00 For Windows 2000/XP/2003"
PCI\VEN_8086&DEV_2652&SUBSYS_01851028="%systemdrive%\dell\storage\aarich.inf","\","Adaptec Embedded Serial ATA HostRAID Controller","Adaptec Embedded Serial ATA HostRAID Driver Ver 6.00 For Windows 2000/XP/2003"
;Adaptec Ultra160 SCSI Controllers
PCI\VEN_9005&DEV_00C0="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec SCSI Card 39160 - Ultra160 SCSI","u160dsk1"
PCI\VEN_9005&DEV_00C0&SUBSYS_F6209005="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec SCSI Card 39160/3960D - Ultra160 SCSI","u160dsk1"
PCI\VEN_9005&DEV_00C0&SUBSYS_F6200E11="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec SCSI Card 39160D Ultra160 SCSI","u160dsk1"
PCI\VEN_9005&DEV_0080="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec SCSI Card 29160 - Ultra160 SCSI","u160dsk1"
PCI\VEN_9005&DEV_0080&SUBSYS_E2A09005="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec SCSI Card 29160 Ultra160 SCSI","u160dsk1"
PCI\VEN_9005&DEV_0080&SUBSYS_E2A00E11="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec SCSI Card 39160D Ultra160 SCSI","u160dsk1"
PCI\VEN_9005&DEV_0080&SUBSYS_62A09005="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec SCSI Card 29160N - Ultra160 SCSI","u160dsk1"
PCI\VEN_9005&DEV_0080&SUBSYS_E2209005="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec SCSI Card 29160LP Low Profile Ultra160 SCSI","u160dsk1"
;Adaptec Ultra160 ASIC Controllers
PCI\VEN_9005&DEV_008F="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec AIC-7892 - Ultra160 SCSI","u160dsk1"
.
PCI\VEN_9005&DEV_00CF="%systemdrive%\dell\storage\ADPU160M.INF","\","Adaptec AIC-7899 - Ultra160 SCSI","u160dsk1"
;Adaptec Ultra320 SCSI Controllers
PCI\VEN_9005&DEV_801D="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_801E="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_801F="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_800F="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_800F&SUBSYS_005F9005="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_8000&SUBSYS_00609005="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_8010&SUBSYS_00409005="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_8011&SUBSYS_00419005="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_8012&SUBSYS_00429005="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_8014&SUBSYS_00449005="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_8015&SUBSYS_00409005="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_8016&SUBSYS_00409005="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
PCI\VEN_9005&DEV_8017&SUBSYS_00449005="%systemdrive%\dell\storage\9g\scsi-nonraid\ADPU320.INF","\","Adaptec Ultra320 Family Manager Set - Microsoft Disk","u320dsk1"
;LSI Logic FC9XXX Fibre Channel Adapters
PCI\VEN_1000&DEV_0621="%systemdrive%\dell\storage\symmpi.inf","\","LSI Logic FC909 Fibre Channel Adapter","symmpi.tag"
PCI\VEN_1000&DEV_0622="%systemdrive%\dell\storage\symmpi.inf","\","LSI Logic FC929 Fibre Channel Adapter","symmpi.tag"
PCI\VEN_1000&DEV_0624="%systemdrive%\dell\storage\symmpi.inf","\","LSI Logic FC919 Fibre Channel Adapter","symmpi.tag"
PCI\VEN_1000&DEV_0626="%systemdrive%\dell\storage\symmpi.inf","\","LSI Logic FC929X Fibre Channel Adapter","symmpi.tag"
PCI\VEN_1000&DEV_0628="%systemdrive%\dell\storage\symmpi.inf","\","LSI Logic FC919X Fibre Channel Adapter","symmpi.tag"
PCI\VEN_1000&DEV_0030="%systemdrive%\dell\storage\symmpi.inf","\","LSI Logic 1020/1030 Ultra320 SCSI Adapter","symmpi.tag"
PCI\VEN_1000&DEV_0032="%systemdrive%\dell\storage\symmpi.inf","\","LSI Logic 1035 Ultra320 SCSI Adapter","symmpi.tag"
;DELL CERC SATA 1.5/6ch
PCI\VEN_9005&DEV_0285&SUBSYS_02911028="%systemdrive%\dell\storage\cercsr6.inf","\","DELL CERC SATA 1.5/6ch storage Controller","DISK1"
;DELL 438
PCI\VEN_8086&DEV_1960&SUBSYS_11121111="%systemdrive%\dell\storage\oemsetup.inf","\","Dell PERC 2/SC storage Controller","SOURCE_DISK"
;DELL 466
PCI\VEN_8086&DEV_1960&SUBSYS_11111028="%systemdrive%\dell\storage\oemsetup.inf","\","Dell PERC 2/SC storage Controller","SOURCE_DISK"
PCI\VEN_8086&DEV_1960&SUBSYS_09A0101E="%systemdrive%\dell\storage\oemsetup.inf","\","Dell PERC 2/SC storage Controller","SOURCE_DISK"
PCI\VEN_8086&DEV_1960&SUBSYS_11111111="%systemdrive%\dell\storage\oemsetup.inf","\","Dell PERC 2/SC storage Controller","SOURCE_DISK"
;DELL 467
PCI\VEN_8086&DEV_1960&SUBSYS_04671028="%systemdrive%\dell\storage\oemsetup.inf","\","Dell PERC 2/DC storage Controller","SOURCE_DISK"
;Dell PERC 2, 2/Si, 3/Si, 3/Di Controllers
PCI\VEN_1011&DEV_0046&SUBSYS_13649005="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 2 RAID Controller","DISK1"
.
PCI\VEN_1028&DEV_0001&SUBSYS_00011028="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 2/Si RAID Controller","DISK1"
PCI\VEN_1028&DEV_0003&SUBSYS_00031028="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 3/Si RAID Controller","DISK1"
PCI\VEN_1028&DEV_0002&SUBSYS_00021028="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 3/Di RAID Controller","DISK1"
PCI\VEN_1028&DEV_0002&SUBSYS_00D11028="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 3/Di RAID Controller","DISK1"
PCI\VEN_1028&DEV_0002&SUBSYS_00D91028="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 3/Di RAID Controller","DISK1"
PCI\VEN_1028&DEV_000A&SUBSYS_01061028="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 3/Di RAID Controller","DISK1"
PCI\VEN_1028&DEV_000A&SUBSYS_011B1028="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 3/Di RAID Controller","DISK1"
PCI\VEN_1028&DEV_000A&SUBSYS_01211028="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 3/Di RAID Controller","DISK1"
PCI\VEN_9005&DEV_00C5&SUBSYS_00C51028="%systemdrive%\dell\storage\perc2.inf","\","Dell PERC 3 RAID (SCSI chip)","DISK1"
;PERC 3/QC (DELL)
PCI\VEN_101E&DEV_1960&SUBSYS_04711028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 3/QC storage Controller","SOURCE_DISK"
;PERC 3/DC (DELL)
PCI\VEN_101E&DEV_1960&SUBSYS_04931028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 3/DC & PERC 3/DCL RAID Controller","SOURCE_DISK"
;PERC 3/SC (DELL)
PCI\VEN_101E&DEV_1960&SUBSYS_04751028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 3/SC RAID Controller","SOURCE_DISK"
;PERC 4/Di 0123 (DELL)
PCI\VEN_1028&DEV_000E&SUBSYS_01231028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4/Di RAID Controller","SOURCE_DISK"
;PERC 4/Di 013B (DELL)
PCI\VEN_1028&DEV_000F&SUBSYS_013B1028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4/Di RAID Controller","SOURCE_DISK"
;PERC 4/Di 014A (DELL)
PCI\VEN_1028&DEV_000F&SUBSYS_014A1028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4/Di RAID Controller","SOURCE_DISK"
;PERC 4/Di 014C (DELL)
PCI\VEN_1028&DEV_000F&SUBSYS_014C1028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4/Di RAID Controller","SOURCE_DISK"
;PERC 4/Di 014D (DELL)
PCI\VEN_1028&DEV_000F&SUBSYS_014D1028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4/Di RAID Controller","SOURCE_DISK"
;PERC 4/DC (DELL)
PCI\VEN_1000&DEV_1960&SUBSYS_05181028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4/DC RAID Controller","SOURCE_DISK"
;PERC 4/SC (DELL)
PCI\VEN_1000&DEV_1960&SUBSYS_05201028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4/SC RAID Controller","SOURCE_DISK"
;CERC ATA100/4ch (DELL)
PCI\VEN_101E&DEV_1960&SUBSYS_05111028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL CERC ATA100/4ch RAID Controller","SOURCE_DISK"
;PCI-EXPRESS
;PERC 4e/Si (DELL)
PCI\VEN_1028&DEV_0013&SUBSYS_016C1028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4e/Si RAID Controller","SOURCE_DISK"
;PERC 4e/Di (DELL)
PCI\VEN_1028&DEV_0013&SUBSYS_016D1028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4e/Di RAID Controller","SOURCE_DISK"
;PERC 4e/Di (DELL)
PCI\VEN_1028&DEV_0013&SUBSYS_016E1028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4e/Di RAID Controller","SOURCE_DISK"
;PERC 4e/Di (DELL)
PCI\VEN_1028&DEV_0013&SUBSYS_016F1028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4e/Di RAID Controller","SOURCE_DISK"
;PERC 4e/Di (DELL)
PCI\VEN_1028&DEV_0013&SUBSYS_01701028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4e/Di RAID Controller","SOURCE_DISK"
;PERC 4e/SC (DELL)
PCI\VEN_1000&DEV_0408&SUBSYS_00011028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4e/SC RAID Controller","SOURCE_DISK"
;PERC 4e/DC (DELL)
PCI\VEN_1000&DEV_0408&SUBSYS_00021028="%systemdrive%\dell\storage\oemsetup.inf","\","DELL PERC 4e/DC RAID Controller","SOURCE_DISK"
;PERC5/E Controller Family
PCI\VEN_1028&DEV_0015&SUBSYS_1F011028="%systemdrive%\dell\storage\9g\perc5\oemsetup.inf","\","DELL PERC 5/E Adapter RAID Controller","DISK1"
;PERC5/I Controller Family
PCI\VEN_1028&DEV_0015&SUBSYS_1F021028="%systemdrive%\dell\storage\9g\perc5\oemsetup.inf","\","DELL PERC 5/I Adapter RAID Controller","DISK1"
;PERC5/i Integrated Controller Family
PCI\VEN_1028&DEV_0015&SUBSYS_1F031028="%systemdrive%\dell\storage\9g\perc5\oemsetup.inf","\","DELL PERC 5/i Integrated RAID Controller","DISK1"
;Dell SAS 5x Controllers
PCI\VEN_1000&DEV_0054&SUBSYS_1F041028="%systemdrive%\dell\storage\9g\sas-nonraid\lsi_sas.inf","\","Dell SAS 5x Controller Driver (Windows Server 2003 32-bit)","lsi_sas.tag"
PCI\VEN_1000&DEV_0054&SUBSYS_1F061028="%systemdrive%\dell\storage\9g\sas-nonraid\lsi_sas.inf","\","Dell SAS 5x Controller Driver (Windows Server 2003 32-bit)","lsi_sas.tag"
PCI\VEN_1000&DEV_0054&SUBSYS_1F071028="%systemdrive%\dell\storage\9g\sas-nonraid\lsi_sas.inf","\","Dell SAS 5x Controller Driver (Windows Server 2003 32-bit)","lsi_sas.tag"
PCI\VEN_1000&DEV_0054&SUBSYS_1F081028="%systemdrive%\dell\storage\9g\sas-nonraid\lsi_sas.inf","\","Dell SAS 5x Controller Driver (Windows Server 2003 32-bit)","lsi_sas.tag"
PCI\VEN_1000&DEV_0054&SUBSYS_1F091028="%systemdrive%\dell\storage\9g\sas-nonraid\lsi_sas.inf","\","Dell SAS 5x Controller Driver (Windows Server 2003 32-bit)","lsi_sas.tag"
For in-depth Instructor-Led Training related to this topic, see http://www.akibia.com/altiris