prathapml

a sample autounattend.xml - working good

77 posts in this topic

The xml in first post is for 32-bit only. The x64 will be similar but processorArchitecture & publicKeyToken might change.

thx , any one has an example xml for x64 ?

EDIT:

Never mind, i made one myself.

Edited by sp00f
0

Share this post


Link to post
Share on other sites
I would love a look at your x64 xml.

I just opened the x86 one , and added the same things in a new x64 one

0

Share this post


Link to post
Share on other sites

Came across this bit of info recently - I'm assuming it will be available in Vista SP1 as well, and if so, it finally solves the driver problem in a simple manner.

Windows Server Longhorn Automatic Driver Injection

During WinPE the system looks for the directory named $WinPEDriver$ at the root of all visible drives given a drive letter of C or greater. If this directory exists, the module then adds this path to the list of paths that it maintains to search for driver packages. When this operation is complete, the module continues to scan the answer file, if present, for additional driver paths.

Because of this operation, drives that contain a $WinPEDriver$ directory in the root cause Setup to recursively search this directory for driver packages to be imported into the image during the WinPE phase. This includes hard drive partitions and removable media like floppy disk drives and flash drives. Type-27 hidden partitions are assigned a driver letter during the WinPE phase of Setup and are also searched.

LINK to source - HTML from google cache | or MSword file

0

Share this post


Link to post
Share on other sites

Hi, i've been searching around and I can't find what i'm looking for, is there documentation explaining this xml file completly with all available components listed and options, or has anyone made a program to help automate it?

I'd be interested in writing a simple app to toggle things on and off if there isn't already one, I know we have vlite but i'd like to be able to keep the source clean and just use an answer file

many thanks!

0

Share this post


Link to post
Share on other sites

I find the waik /wsim reference to be very helpful. There a few tools you mention on this board for automating an xml.

0

Share this post


Link to post
Share on other sites

Yes indeed, resources for this with detailed help do exist, which is actually what I used.

WAIK - a set of packages around 900 MB in size, free download from oem.microsoft.com

WSIM - a graphical tool to help renerating an xml (unfortunately, an xml that passes validation by wsim will not always work as expected during setup, which is why I felt the need to post a known-to-be-working file on the forum).

documentation - yes there are some CHM files contained in the WAIK and are a very useful reference, might total up to hardly 5 MB.

0

Share this post


Link to post
Share on other sites

thanks!, i'll have to start downloading and reading.. one last thing, isthe WSIM a ms tool or a user made one? ... I'm half guessing its included in the waik?, very tired, about togoto bed but just thought i'd check this quickly whilst i can, shall be looking into it as soon as i get some free time, i like the download speed from microsoft servers, seem to forget i have a 8mb connection with most sites seemingly limited!

0

Share this post


Link to post
Share on other sites

Still waiting upon the direct drop-in folder of "Updates" to automatically install updates post-SP1.

And the other drop-in folder mentioned earlier (quoted below):

Came across this bit of info recently - I'm assuming it will be available in Vista SP1 as well, and if so, it finally solves the driver problem in a simple manner.
Windows Server Longhorn Automatic Driver Injection

During WinPE the system looks for the directory named $WinPEDriver$ at the root of all visible drives given a drive letter of C or greater. If this directory exists, the module then adds this path to the list of paths that it maintains to search for driver packages. When this operation is complete, the module continues to scan the answer file, if present, for additional driver paths.

Because of this operation, drives that contain a $WinPEDriver$ directory in the root cause Setup to recursively search this directory for driver packages to be imported into the image during the WinPE phase. This includes hard drive partitions and removable media like floppy disk drives and flash drives. Type-27 hidden partitions are assigned a driver letter during the WinPE phase of Setup and are also searched.

LINK to source - HTML from google cache | or MSword file

0

Share this post


Link to post
Share on other sites

Hi there! First of all - fantastic samples!

Now my question - i couldnt solve the problem yet to run a simple batchfile after installation .. as i see some of thoose samples added a line with a batchfile, follow:

<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>%SystemDrive%\install\GUIrunOnce.cmd</CommandLine>
<Description>customises settings</Description>
<Order>20</Order>
</SynchronousCommand>
</FirstLogonCommands>

OK here comes the question:

How do i copy the install-dir into the system-drive and how could i add the variable systemdrive - or does it work after i copied the directory to the sysdir?

You know .. i dont have alot of time to spend on my own Vista-DVD, thats why i dont want to get ride of WAIK, id rather use some own batchfiles to add updates and registrytweaks after installation, i think its the best solution because the implementation of updates and software dont works at all (many users reported problems on waik).

i hope someone could tell me how to copy a directory from the dvd, including sub-dirs and all files and tell me if it works with the batchfile-run-line in the unattented.xml lines ive posted in the code-tag up of my post.

And yes .. err .. what does the order-line means? why it counts 20?

i would be very happy if someone which knows what im asking for would help me.

thanks alot allready, a very interesting community, im sorry for myself that i cant spend alot of time into this, im very busy.

greets,

max

Edited by max1234
0

Share this post


Link to post
Share on other sites

I've been searching but have not found the answer yet. In XP there were limitations within the different answer files as to the length the string could be, i.e. DriverPaths was limited to 2048 or 4096 depending upon the answer file.

Are there any such limitations on any of the Vista answerfiles path type strings? My boss wants to put as many of the drivers and other files apps that we can on the network to install unattendedly instead of putting them in the image but the UNC path to the folder containing everything is already 40 characters long and I don't think there is a way for me to remapped it to a drive letter that will be there whenever it is needed without creating even bigger headaches.

God i hate management sometimes.

0

Share this post


Link to post
Share on other sites
Hi

to add drivers to the winPE pass you have to use :

<Microsoft-Windows-PnpCustomizationsWinPE> In the Windows PE Pass

The Microsoft-Windows-PnpCustomizationsWinPE component is used to add one
or more out-of-box drivers to a Windows installation. Drivers that are located in the
path specified by DriverPaths are copied to the driver store of the Windows installation
during the windowsPE configuration pass.

You can add boot-critical as well as non-boot-critical drivers with this component to a
Windows image before it is installed.

To add them during the Offline servicing pass Use :

<Microsoft-Windows-PnpCustomizationsNonWinPE>

Those 2 ways Allows you to add Critical drivers NEEDED by the system. (Mass Strorage or network if use use net shares during installation.)

To add them copied during the auditSystem Pass, use :

<Microsoft-Windows-PnpCustomizationsNonWinPE> Int the AuditSystem Pass

The Microsoft-Windows-PnpCustomizationsNonWinPE component is used to add one or more
out-of-box drivers to a Windows installation. Drivers that are located in the path specified by
DriverPaths are copied to the driver store of the Windows installation during the auditSystem
configuration pass. When the system runs Plug and Play, these out-of-box drivers are available
to install hardware on the system.

Tha means To install Vista on a RAID Array, you have to use WinPE to add drivers.

if you want to add video drivers, you can just use the audit pass.

If I try to add drivers during auditSystem I get an error, and everything hangs. I am modifying the answer file to see if I can't install the drvers during offlineServicing.

Anybody knows why is this happening?

Thank you

0

Share this post


Link to post
Share on other sites

@prathapml

Empty your inbox! It's full.:)

0

Share this post


Link to post
Share on other sites

@atolica

Thanks. :) I've just been putting off clearing my personal messages - shall take some time out to sort, archive and download them all.

In the meantime, if you have any queries for me, just post in any of the threads to which I am subscribed.

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.