lawson23

unattended.xml help!

35 posts in this topic

Are you saying the Drivers do not work?

If not you may need to add this

    <settings pass="generalize">
<component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
</component>
</settings>

and then do not add any more reference to Driverpaths. Remove from your <settings pass="offlineServicing">

To instruct Windows Setup to maintain the driver settings, prepare the computer for image capture by generalizing the computer with an answer file that includes the Microsoft-Windows-PnpSysPrep\PersistAllDeviceInstalls setting.
0

Share this post


Link to post
Share on other sites

ok first maybe I should explain the setup.

I'm trying to duplicate the $OEM$ driver install like I could do with XP sif file. Just as in the article you created describe using:

$1 <<- Drive Root

$1\Drivers <<- where some OEM place driver files

but I use:

$1 <<- Drive Root

$1\DRV <<- where some OEM place driver files

I'm not using a dvd I'm using a deployment solution (altiris) to push this stuff out. They capture the sources folder only so not sure if I can add $winpedriver$ folder as you describe. I'm really courious if I can duplicate what I used to do above. Is this possible or not? Also Altiris has a driver setup routine that is putting in the offline service area. I'm not sure I want to pull this out. I would think I could use multiple methods if the xml allows it.

I'm thinking of doing a registry modification after deployment to update the driver location key and then forcing a pnp check since nothing appears to be working out with the xml.

0

Share this post


Link to post
Share on other sites

I have not done a Win7/WinSrv8 Install as-of-yet.

I can say this about $OEM$ folder and transfer to HDD during install (at least for 2k/XP/2k3) -

When the install is from CD/DVD, the $OEM$ folder is on the CD/DVD ROOT, and contents within will copy to the HDD.

When the install is from HDD, the $OEM$ folder is placed within the HDD "I386" Folder, and contents within will copy to the HDD.

This is according to the $OEM$ naming structure as indicated (what copies to where), e.g. $1 transfers to HDD ROOT etc.

It appears you're "rolling out" remotely from HDD, so... (I386=SOURCES? :unsure: )

HTH (and you'll get more specific or I will be corrected from someone who has used this method)...

Edited by submix8c
0

Share this post


Link to post
Share on other sites

I have not done a Win7/WinSrv8 Install as-of-yet.

With Win 7/8 you place the $OEM$ within the sources folder and they are copied to respective locations.

lawson23

Glad you finally told me what you are using. When I searched the @ProcessArchitecture it was returning sym,antec links and I wondered why

Symantec Puts Altiris Unit on the Block

You could use $1\DRV or even $1\$WinPEDriver$

but any boot critical will not be available till the driver setup routine you talk of has run

Edited by maxXPsoft
0

Share this post


Link to post
Share on other sites

MaxXPSoft,

So my question is there anyway to kick that driver routine off with the way I'm putting the drivers on the system from the xml? To duplicate what I did with XP? We have so few systems it is just easier to manage drviers this way than injecting and all that stuff.

If I renamed my folder from drv to $winpedriver$ would it then possibly work? I'm just trying to learn and understand this. Will say they went from like a few options to way to many.

Also I never got an answer regarding how the drivers have to be put in the xml. If I have multiple folders do I have to put multiple entries or just the one root entry.

For example currently I only place on driver in my driver folder but it is located:

sources\$OEM$\$1\DRV\Systems\e6410\NIC

From what I read you can now just define the root location but this was not true with the sif oem method.

0

Share this post


Link to post
Share on other sites

From what I read you can now just define the root location but this was not true with the sif oem method.

lots of things changed with Vista and later

Using $OEM$ and <Path>%systemdrive%\DRV</Path> so you would place the whatever name you use like this $OEM$\$1\DRV

Windows 7 recurses the specified folder so you only need the root folder

Only .inf drivers can be added to a Windows image by using this procedure. in other words extracted just like XP was

0

Share this post


Link to post
Share on other sites

Ok so in the xml file I would put: $OEM$\$1\DRV

as I have been putting: c:\DRV


<settings pass="windowsPE" wasPassProcessed="true">
<component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:action="add" wcm:keyValue="201">
<Path>$OEM$\$1\DRV</Path>
</PathAndCredentials>
</DriverPaths>
</component>

0

Share this post


Link to post
Share on other sites

Ummm... one might ask what you would have done in XP. I would imagine the Pathname would be the same (e.g. %SystemDrive%)... After all, the $OEM$ folder contents copies the same way? :unsure:

0

Share this post


Link to post
Share on other sites

Ok so in the xml file I would put: $OEM$\$1\DRV

No :no: , just like I said <Path>%systemdrive%\DRV</Path>

I do not know if that altiris will use the $OEM$ same way as intended

0

Share this post


Link to post
Share on other sites

Ok so in the xml file I would put: $OEM$\$1\DRV

No :no: , just like I said <Path>%systemdrive%\DRV</Path>

I do not know if that altiris will use the $OEM$ same way as intended

Well I started a test late Friday and had to leave and so far it appears that this did work:

<Path>$OEM$\$1\DRV</Path>   

Going to run another test to be sure.

2nd test also worked great. So far it looks like this solves my problems regarding drivers. Any comments regarding it?

Edited by lawson23
0

Share this post


Link to post
Share on other sites

2nd test also worked great. So far it looks like this solves my problems regarding drivers. Any comments regarding it?

Sure, attach the setupact.log from Windows\$Panther folder on installed system. I gotta see this.

0

Share this post


Link to post
Share on other sites

I could not attach the log file because of the size so I have pasted what I think is the important pieces.

2013-01-21 16:58:48, Info                  IBS    InstallWindows:Successfully loaded resource language [en-US]
2013-01-21 16:58:48, Info [0x0601c1] IBS InstallWindows:Install Path = \\BER-AP21.motorwheelcvs.com\deployment\Task Handler\SOI\63b172c3-308d-4929-a8f5-8d8148ac7be3\sources
2013-01-21 16:58:48, Info [0x0601c2] IBS InstallWindows:Setup Phase = 2
2013-01-21 16:58:48, Info [0x0601e9] IBS CheckWinPEVersion:Compatible WinPE Version 6.0.6001 sp 1.0
2013-01-21 16:58:48, Info [0x0601c9] IBS InstallWindows:Starting a new install from WinPE
2013-01-21 16:58:48, Info IBS InstallWindows: Setup working directory = X:\Windows\panther
2013-01-21 16:58:48, Info [0x0601ce] IBS Setup has started phase 2 at 2013-01-21 16:58:48
2013-01-21 16:58:48, Info [0x0601cf] IBS Install source is \\BER-AP21.motorwheelcvs.com\deployment\Task Handler\SOI\63b172c3-308d-4929-a8f5-8d8148ac7be3\sources
2013-01-21 16:58:48, Info [0x0601d0] IBS Build version is 6.1.7601.17514 (win7sp1_rtm.101119-1850)
2013-01-21 16:58:48, Info [0x06403f] IBSLIB CreateSetupBlackboard:Creating a new persistent blackboard. Path is [X:\Windows\panther\SetupInfo] Setup phase is [2]
2013-01-21 16:58:48, Info [0x090008] PANTHR CBlackboard::Open: X:\Windows\panther\SetupInfo succeeded.
2013-01-21 16:58:48, Info [0x064043] IBSLIB CreateSetupBlackboard:Successfully created/opened Setup black board path is [X:\Windows\panther\SetupInfo]
2013-01-21 16:58:48, Info IBS InstallWindows:No UI language from a previous boot was found on the blackboard. Using selected language [en-US].
2013-01-21 16:58:48, Info IBS InstallWindows:Setup architecture is [x64]
2013-01-21 16:58:48, Info [0x0601d5] IBS InstallWindows:Starting with Empty Queue. Setup Phase = 2

2013-01-21 16:58:56, Info IBS No <Path> was specified in an <InstallFrom> element for <OSImage>; will assume default one
2013-01-21 16:58:56, Info IBS No credentials specified on <InstallFrom> element
2013-01-21 16:58:56, Info IBS Callback_SetWinPEAndOSImageInfoOnBB: Cannot set image info as source path is not yet set.
2013-01-21 16:58:56, Info PnPIBS: Entering PnP callback to install drivers on WinPE ...
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver paths ...
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory C:\$WinPEDriver$.
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory D:\$WinPEDriver$.
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory X:\$WinPEDriver$.
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory Z:\$WinPEDriver$.
2013-01-21 16:58:56, Info PnPIBS: Finished checking for pre-configured driver paths.
2013-01-21 16:58:56, Info PnPIBS: Reading driver paths from unattend.xml ...
2013-01-21 16:58:56, Info PnPIBS: $OEM$\$1\DRV is listed as a driver path in unattend.xml ...
2013-01-21 16:58:56, Info PnPIBS: Finished reading driver paths from unattend.xml.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV ...
2013-01-21 16:58:56, Info PnPIBS: Found the directory Audio.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Audio ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Audio.
2013-01-21 16:58:56, Info PnPIBS: Found the directory chipset.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\chipset ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\chipset.
2013-01-21 16:58:56, Info PnPIBS: Found the directory misc.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\misc ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\misc.
2013-01-21 16:58:56, Info PnPIBS: Found the directory modem.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\modem ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\modem.
2013-01-21 16:58:56, Info PnPIBS: Found the directory nic.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\nic ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\nic.
2013-01-21 16:58:56, Info PnPIBS: Found the directory SATA_SCSI.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\SATA_SCSI ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\SATA_SCSI.
2013-01-21 16:58:56, Info PnPIBS: Found the directory Systems.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems ...
2013-01-21 16:58:56, Info PnPIBS: Found the directory e6410.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6410 ...
2013-01-21 16:58:56, Info PnPIBS: Found the directory NIC.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6410\NIC ...
2013-01-21 16:58:56, Info PnPIBS: Found the file E1K62x64.cat
2013-01-21 16:58:56, Info PnPIBS: Skipping the file E1K62x64.cat because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file e1k62x64.din
2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1k62x64.din because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file E1K62x64.INF
2013-01-21 16:58:56, Info PnPIBS: Added driver $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF to the list of drivers.
2013-01-21 16:58:56, Info PnPIBS: Found the file e1k62x64.sys
2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1k62x64.sys because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file e1kmsg.dll
2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1kmsg.dll because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file NicCo36.dll
2013-01-21 16:58:56, Info PnPIBS: Skipping the file NicCo36.dll because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file NicInstK.dll
2013-01-21 16:58:56, Info PnPIBS: Skipping the file NicInstK.dll because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file PROUnstl.exe
2013-01-21 16:58:56, Info PnPIBS: Skipping the file PROUnstl.exe because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file Version.txt
2013-01-21 16:58:56, Info PnPIBS: Skipping the file Version.txt because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6410\NIC.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6410.
2013-01-21 16:58:56, Info PnPIBS: Found the directory e6420.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6420 ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6420.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems.
2013-01-21 16:58:56, Info PnPIBS: Found the directory Video.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video ...
2013-01-21 16:58:56, Info PnPIBS: Found the directory ATI.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\ATI ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\ATI.
2013-01-21 16:58:56, Info PnPIBS: Found the directory Intel.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\Intel ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\Intel.
2013-01-21 16:58:56, Info PnPIBS: Found the directory nvidia.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\nvidia ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\nvidia.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV.
2013-01-21 16:58:56, Info PnPIBS: The class GUID for INF $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF is 4d36e972-e325-11ce-bfc1-08002be10318
2013-01-21 16:58:56, Info PnPIBS: The class GUID 4d36e972-e325-11ce-bfc1-08002be10318 is not boot-critical.
2013-01-21 16:58:56, Info PnPIBS: The driver $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF is not boot-critical and hence it will not be installed.
2013-01-21 16:58:56, Info PnPIBS: Exiting PnP callback to install drivers on WinPE ...
2013-01-21 16:58:56, Info PnPIBS: Entering PnP callback to add drivers to the offline image ...
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver paths ...
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory C:\$WinPEDriver$.
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory D:\$WinPEDriver$.
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory X:\$WinPEDriver$.
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory Z:\$WinPEDriver$.
2013-01-21 16:58:56, Info PnPIBS: Finished checking for pre-configured driver paths.
2013-01-21 16:58:56, Info PnPIBS: Reading driver paths from unattend.xml ...
2013-01-21 16:58:56, Info PnPIBS: $OEM$\$1\DRV is listed as a driver path in unattend.xml ...
2013-01-21 16:58:56, Info PnPIBS: Finished reading driver paths from unattend.xml.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV ...
2013-01-21 16:58:56, Info PnPIBS: Found the directory Audio.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Audio ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Audio.
2013-01-21 16:58:56, Info PnPIBS: Found the directory chipset.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\chipset ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\chipset.
2013-01-21 16:58:56, Info PnPIBS: Found the directory misc.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\misc ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\misc.
2013-01-21 16:58:56, Info PnPIBS: Found the directory modem.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\modem ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\modem.
2013-01-21 16:58:56, Info PnPIBS: Found the directory nic.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\nic ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\nic.
2013-01-21 16:58:56, Info PnPIBS: Found the directory SATA_SCSI.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\SATA_SCSI ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\SATA_SCSI.
2013-01-21 16:58:56, Info PnPIBS: Found the directory Systems.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems ...
2013-01-21 16:58:56, Info PnPIBS: Found the directory e6410.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6410 ...
2013-01-21 16:58:56, Info PnPIBS: Found the directory NIC.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6410\NIC ...
2013-01-21 16:58:56, Info PnPIBS: Found the file E1K62x64.cat
2013-01-21 16:58:56, Info PnPIBS: Skipping the file E1K62x64.cat because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file e1k62x64.din
2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1k62x64.din because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file E1K62x64.INF
2013-01-21 16:58:56, Info PnPIBS: Added driver $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF to the list of drivers.
2013-01-21 16:58:56, Info PnPIBS: Found the file e1k62x64.sys
2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1k62x64.sys because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file e1kmsg.dll
2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1kmsg.dll because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file NicCo36.dll
2013-01-21 16:58:56, Info PnPIBS: Skipping the file NicCo36.dll because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file NicInstK.dll
2013-01-21 16:58:56, Info PnPIBS: Skipping the file NicInstK.dll because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file PROUnstl.exe
2013-01-21 16:58:56, Info PnPIBS: Skipping the file PROUnstl.exe because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Found the file Version.txt
2013-01-21 16:58:56, Info PnPIBS: Skipping the file Version.txt because it is not an INF file.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6410\NIC.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6410.
2013-01-21 16:58:56, Info PnPIBS: Found the directory e6420.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6420 ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6420.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems.
2013-01-21 16:58:56, Info PnPIBS: Found the directory Video.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video ...
2013-01-21 16:58:56, Info PnPIBS: Found the directory ATI.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\ATI ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\ATI.
2013-01-21 16:58:56, Info PnPIBS: Found the directory Intel.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\Intel ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\Intel.
2013-01-21 16:58:56, Info PnPIBS: Found the directory nvidia.
2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\nvidia ...
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\nvidia.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video.
2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV.
2013-01-21 16:58:56, Info PnPIBS: Driver $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF is being queued up for addition to the offline image.
2013-01-21 16:58:56, Info IBS Callback_Compliance_GatherDeviceIDs:Driver package is [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF]
2013-01-21 16:58:56, Info IBS GatherDeviceIDsInDriverPackage:Driver package path is [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF]
2013-01-21 16:58:56, Info IBS GatherDeviceIDsInDriverPackage:Successfully gathered device ID's from [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF]
2013-01-21 16:58:56, Info PnPIBS: Successfully gathered device ID's from [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF]
2013-01-21 16:58:56, Info Callback_GatherDiskInfo: Entry: flags = [0x1]; major = [DriveInformation] / minor = [0x90001]
2013-01-21 16:58:56, Info RefreshDiskInfo: Using VDS
2013-01-21 16:58:56, Info RefreshDiskInfo: Found flag DISKINFO_REENUMERATE_DISKS



2013-01-21 17:15:05, Info [0x0602a4] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package path is [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF]
2013-01-21 17:15:05, Info [0x0602b2] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package is [NOT critical]
2013-01-21 17:15:05, Info IBS AddDriverPackageIntoDriverStore:Driver package path is [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF]
2013-01-21 17:15:05, Info IBS AddDriverPackageIntoDriverStore:Image architecture is [0x9]
2013-01-21 17:15:05, Info IBS AddDriverPackageIntoDriverStore:System root is [C:\Windows]
2013-01-21 17:15:05, Info IBS AddDriverPackageIntoDriverStore:System drive is [C:\]
2013-01-21 17:15:08, Info [0x0602b0] IBS AddDriverPackageIntoDriverStore:Successfully added the driver package [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF] into driver store. Destination driver package path is [C:\Windows\System32\DriverStore\FileRepository\e1k62x64.inf_amd64_neutral_bfac63e16fb1c2b4\E1K62x64.INF]
2013-01-21 17:15:08, Info [0x0602a8] IBS CallBack_AddDriverPackageIntoDriverStore:Successfully installed the driver package [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF]. Driver store path is [C:\Windows\System32\DriverStore\FileRepository\e1k62x64.inf_amd64_neutral_bfac63e16fb1c2b4\E1K62x64.INF]
2013-01-21 17:15:08, Info IBS Callback_AddDriverPackageIntoDriverStore: Checking for iSCSI deployment scenario

0

Share this post


Link to post
Share on other sites

I could not attach the log file because of the size so I have pasted what I think is the important pieces.

You can see it searches for the $WinPEDriver$

PnPIBS: Checking for pre-configured driver paths ...
2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory C:\$WinPEDriver$.

Was the folders on the target drive just like that? $OEM$\$1\DRV

Reason I ask is I wanted to know if that altiris copied the folders to the drive same way Windows installer does, apparently not cause Windows would have just placed the DRV folder on root

0

Share this post


Link to post
Share on other sites

the drv folder exist on the root just like Windows would handle it.

It looks on the pc like C:\DRV

not $oem$\$1\drv

If I create a $WinPEDriver$ folder like $oem$\$1\$winpedriver$\driverfoldersandfiles

What happens to this folder later does it stay on the machine at c:\$winpedriver$?

Either way what I'm doing above appears to be working. Not sure how or why but hey it is working.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.