RE: Help with Sysprep Settings in CS.ini...and copying drivers
- From: Troy L. Martin <TroyLMartin@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 3 Oct 2006 12:42:02 -0700
yeah...I think you can use DFS. Never used it in a ZTI scenario, but I still
think it would work.
"Maro" wrote:
One more quick question:OEMPnPDriversPath="DRIVERS\ATIMOBILITY;DRIVERS\IBM\PM;DRIVERS\INTEL;DRIVERS\MATROX;DRIVERS\S50;DRIVERS\T23;DRIVERS\T40;DRIVERS\T42;DRIVERS\T42\PRO2100;DRIVERS\T42\IBM_BG;DRIVERS\T42\PRO1000;DRIVERS\SBLIVE;DRIVERS\RADEON;DRIVERS\RADEON\WDM;DRIVERS\MPC;DRIVERS\MPC\CHIPSET;DRIVERS\MPC\MODEM;DRIVERS\MPC\SOUND;DRIVERS\MPC\VIDEO;DRIVERS\MPC\VIDEO\TVTuner;DRIVERS\E1000CT;DRIVERS\X40;DRIVERS\P5GD1\NET;DRIVERS\P5GD1\CHIPSET;DRIVERS\P5GD1\AUDIO;DRIVERS\P5GD1\ACPI;DRIVERS\BCM57XX;DRIVERS\S51\ACPI;DRIVERS\S51\AUDIO;DRIVERS\S51\CHIPSET;DRIVERS\S51\VIDEO;DRIVERS\A8NSLI\AUDIO;DRIVERS\A8NSLI\NET;DRIVERS\A8NSLI\SATA2;DRIVERS\A8NSLI\SMBUS;DRIVERS\GEFORCE;DRIVERS\SX280\AUDIO;DRIVERS\SX280\CHIPSET;DRIVERS\SX280\VIDEO;DRIVERS\K8WE\AudioDrv;DRIVERS\K8WE\Ethernet;DRIVERS\K8WE\IDE;DRIVERS\K8WE\SMBus;DRIVERS\K8WE\Video;DRIVERS\K8W\AUDIO;DRIVERS\INTEL\1000P;DRIVERS\M52\AUDIO;DRIVERS\M52\CHIPSET;DRIVERS\M52\LAN;DRIVERS\M52\VIDEO;DRIVERS\M52\OTHER;DRIVERS\T43\AUDIO;DRIVERS\T43\BIOMETRIC;DRIVERS\T43\BLUETOOTH;DRIVERS\T43\MODEM;DRIVERS\T43\NET;DRIVERS\T43\VIDEO;DRIVERS\T43\WLANCX2A;DRIVERS\MPC414\VIDEO\nVidia;DRIVERS\MPC414\VIDEO\ATI;DRIVERS\MPC414\NET;DRIVERS\MPC414\CHIPSET;DRIVERS\MPC414\AUDIO;DRIVERS\T60\MODEM;DRIVERS\T60\NETWORK;DRIVERS\T60\VIDEO;DRIVERS\T60\WLANINT;DRIVERS\T60\AUDIO;DRIVERS\T60\TPMATMEL;DRIVERS\SI3114\SATAIDE;DRIVERS\SI3114\SATARAID;DRIVERS\SI3114\SATARAID5;DRIVERS\NFORCE4\NET;DRIVERS\NFORCE4\SATA;DRIVERS\NFORCE4\SATAIDE;DRIVERS\NFORCE4\SMBus;DRIVERS\M2N-E\Audio"
Is it possible to use DFS Roots as the path to anything in ZTI?
--
-Maro
"Troy L. Martin" wrote:
I noticed your OEMPnpDriversPath variable. It looks like you are staging ALL
of your drivers in the WIM image and you are not using dynamic driver
injection. By using dynamic driver injection, you will trim your WIM down by
300 - 800MB (depending on the amount of drivers you are staging).
1. Create a share on a server to store your drivers (e.g.
\\<server>\<share>\<parent folder for all drivers>\<folder for each computer
model your image supports>. Make sure you set the correct share/folder/file
permissions so the ZTI process and read it
2. In each computer model folder, create a folder for each computer
component (e.g. A=audio, V=video, N=nic...etc, etc.) and put each component
driver in it's own seperate folder. For components that have multiple
drivers, I recommend using a numbering system for the folder names (e.g. 1
for 1st driver, 2 for 2nd driver...etc, etc.)
3. In Customsettings.ini do the following:
[Settings]
;;; Add the DRIVERPATH(*) variable to the CustomKeysUserData line. Since
DRIVERPATH is considered an array-variable and can store multiple values, you
have to append the DRIVERPATH variable with (*)
CustomKeysUserData=UDShare,UDDir,UDProfiles,SLShare,OSInstall,DriverPath(*),Packages(*),Administrators(*),Eventshare,BUShare,BUDir,BUACCT,BUPWD,BUFLAG
;;; %MODEL% is the variable for the computer model that was queried and
reported by WMI
[Default]
DriverPath1=\\<server from step #1>\<share from step #1>\%Model%
;;; By adding DriverPath1 variable to the [Default] section, this will only
work if all your installs are done at one location. If your OSD/ZTI process
will be run from multiple geographic locations, you need to use the
[DefaultGateway] section to determine the computer's location, and then
create a unique section name for that particular location and then add then
remove the DriversPath1 variable from [Default] to the new section name you
created for the target location in question. After following step #1 for
your first location, make sure you create the same share/folder/file
structure on each server, at each location. This is the most you have to
keep up with. Then, when you want to support a new computer hardware model,
you just download the drivers from the manufacturer and stage them on each
server...YOUR DONE!!
[Houston]
DriverPath1=\\<server in Houston>\<share from step #1>\%Model%
[Atlanta]
DriverPath1=\\<server in Atlanta>\<share from step #1>\%Model%
.
.
.
.
[New York]
DriverPath1=\\<server in New York>\<share from step #1>\%Model%
When ZTI encounters the DRIVERPATH(x) variable(s), it will auto-magically
connect the the UNC where the driver is stored and copy the drivers (for that
model computer...ONLY) to C:\Drivers on the target computer.
As for the OemPnpDriversPath statement in Sysprep.inf: You no longer have
to worry about keeping up with that. ZTI dynamically parses the driver
share/folder/file structure, searching for the *.inf file for each driver and
will dynamically build the OemPnpDriversPath for Sysprep.inf and the
DevicePath value in the target computer's registry (e.g.
HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath)
If you have futher questions, just reply...I will be glad to assist you!!
"Maro" wrote:
I'm trying to set stuff like the display resolution in my CS.ini file but the
video settings never get set after the image installation. Here is my
CS.ini. The log file identifies Xresolution, YResolution and Vrefresh but
never sets them. Any help would be great.
[Settings]
Priority= MACADDRESS, Default, DefaultGateway
CustomKeysUserData=UDShare, UDDir, UDProfiles, SLShare, OSInstall, DriverPath
CustomKeysSysprep=ComputerName,TimeZone,JoinDomain,MachineObjectOU,BitsPerPel,Xresolution,YResolution,Vrefresh,OEMPnPDriversPath,UpdateInstalledDrivers
OSDVariableKeys=OSDINSTALLSILENT,OSDINSTALLPACKAGE,OSDINSTALLPROGRAM,OSDNEWMACHINENAME
ScanStateArgs=/i:miguser.inf /i:migapp.inf /i:migsys.inf /i:sysfiles.inf
/i:updateuser.inf /v:7 /x /s /f /o /c
LoadStateArgs=/v:7 /c
UserExit=ZTIUserExit.vbs
[Default]
UDShare=\\Deploy-00-AH\MigData
SLShare=\\Deploy-00-AH\Logs
UDProfiles=*\*
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=AH1000A0
OSDINSTALLPROGRAM=ZTI Refresh
BitsPerPel=16
Xresolution=1024
YResolution=768
Vrefresh=75
TimeZone=035
JoinDomain=mathworks
MachineObjectOU= OU=Workstations,OU=AH,DC=ad,DC=mathworks,DC=com
ComputerName=%OSDNEWMACHINENAME%
UDDir=%OSDCOMPUTERNAME%
OSInstall=Y
.UpdateInstalledDrivers=yes
[DefaultGateway]
192.168.100.1=AH1
[AH1]
UDShare=\\smsserver\MigData
SLShare=\\smsserver\Logs
Administrator1=DOMAIN\Domain Admins
[00:16:41:57:D5:6A]
UDShare=\\smsserver\MigData
SLShare=\\smsserver\Logs
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=AH1000A0
OSDINSTALLPROGRAM=ZTI Refresh
OSDNEWMACHINENAME=bmlaptoptest
DriverPath=\\smsserver\Drivers\T60
[00:17:31:D9:AD:48]
UDShare=\\smsserver\MigData
SLShare=\\smsserver\Logs
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=AH1000A0
OSDINSTALLPROGRAM=ZTI Refresh
OSDNEWMACHINENAME=bmx64test
DriverPath=\\smsserver\Drivers\NFORCE4
[00:10:C6:B7:D2:7E]
UDShare=\\smsserver\MigData
SLShare=\\smsserver\Logs
OSDINSTALLSILENT=1
OSDINSTALLPACKAGE=AH1000A0
OSDINSTALLPROGRAM=ZTI Refresh
OSDNEWMACHINENAME=bmcdtest
DriverPath=\\smsserver\Drivers\M52
TimeZone=035
[SysprepInfMapping]
ComputerName=UserData
TimeZone=GuiUnattended
JoinDomain=Identification
MachineObjectOU=Identification
--
-Maro
- Follow-Ups:
- References:
- Help with Sysprep Settings in CS.ini
- From: Maro
- RE: Help with Sysprep Settings in CS.ini...and copying drivers
- From: Troy L. Martin
- RE: Help with Sysprep Settings in CS.ini...and copying drivers
- From: Maro
- Help with Sysprep Settings in CS.ini
- Prev by Date: RE: Help with Sysprep Settings in CS.ini...and copying drivers
- Next by Date: RE: Help with Sysprep Settings in CS.ini...and copying drivers
- Previous by thread: RE: Help with Sysprep Settings in CS.ini...and copying drivers
- Next by thread: RE: Help with Sysprep Settings in CS.ini...and copying drivers
- Index(es):
Relevant Pages
|
