Topics | How To
| A complete 1-Touch Recovery procedure that incorporates the Broadcomâ NetXtremeâ II™ network interface card (NIC) workaround for a successful Microsoft Windows unattended installation is provided in Perform 1-Touch Recovery with Broadcom's NetXtreme II Driver Workaround. The solution includes creating a custom script for the Windows installation of the NIC along with a list of drivers needed and their usage and placement in the recovery process. |
Custom scripts files are organized according to sections, and each section includes the names of the batch files and dependent files pertinent to the section. Also, each section indicates the phase during the recovery when its associated batch files will run. If a section contains more than one batch file, the file names corresponding to the batch files should be included in the order that the batch files must be executed.
Custom script files can have any name, but they require the .cvinf extension. The files can be placed in any folder that the 1-Touch Server can browse to. See Create and Use a Custom Script for the general steps to create and use custom scripts.
This section identifies the available section titles in the script files and discusses how the files in the scripts are processed:
All the file types listed in this section (.bat, .dll, .exe, etc.) will be copied in the [client file folder]\$OEM$\$1\OneTouchTmp\CustomScripts folder. The OneTouchTmp folder and subfolders will be copied to the system drive during the Windows installation.
All batch (.bat) files listed in this section will be included in the CustomScripts.bat file, and these files will be executed from the [GUIRUNONCE] section of the unattend.txt file, which executes after a Windows installation but before a 1-Touch iDataAgent install and recovery.
The batch files listed in this section will be included in the \POST_CLIENTPREP_TASKS folder, and these files will run immediately after [Finish] or [Apply] is selected in the 1-Touch Client Preparation Wizard. Predefined values are provided for the contents of the batch files to allow you to move files from the CustomScripts folder to another location in the client answer files folder directory structure.
An example of this requirement is provided in the Broadcom solution as presented in Perform 1-Touch Recovery with Broadcom's NetXtreme II Driver Workaround. The Broadcom NIC workaround example requires that the unattend.txt file be placed in the Customscripts folder to be used after the Windows deployment. The unattend.txt file is not created until the Wizard has completed. The CustomScripts.bat batch file will allow you to automate the copy of the unattend.txt file to the Customscripts folder after it is created.
Predefined values:
Custom scripts filename: netxtremeII.cvinf
Sample contents of netxtremeII.cvinf custom script:
[AFTER_OS_INSTALL_BEFORE_NETWORK]
netxtremeII1.bat
netxtremeII2.bat
netset.exe
setup.exe
[POST_CLIENTPREP_TASKS]
copyunattendandsetup.bat
Sample contents of files listed in netxtremeII.cvinf custom script:
Filename: netxtemeII1.bat
Sample contents of netxtemeII1.bat:
c:\pnpdrvrs\net\setup /s /w /v/qn
Filename: netxtremeII2.bat
Sample contents of netxtremeII2.bat:
c:\onetouchtmp\customscripts\netset c:\onetouchtmp\customscripts\unattend.txt
Filename: copyunattendandsetup.bat
Sample contents of copyunattendandsetup.bat:
xcopy %%[CLIENT_FILES_FOLDER]%%\unattend.txt %%[AFTER_OS_INSTALL_BEFORE_NETWORK]%%
xcopy %%[AFTER_OS_INSTALL_BEFORE_NETWORK]%%\setup.exe %%[CLIENT_FILES_FOLDER]%%\$OEM$\$1\PnPDrvrs\Net\
|