[sp00f]

MAVERICKS CHOICE, on Mar 5 2007, 10:57 PM, said:

Hey guys few q's

How to stop windows on first show to setup further users? Also the home ofice network setup screen thing?

I have the following in my xml

[/code]  
 <OOBE>
				<HideEULAPage>true</HideEULAPage>
				<NetworkLocation>Other</NetworkLocation>
				<ProtectYourPC>3</ProtectYourPC>
				<SkipUserOOBE>true</SkipUserOOBE>
			</OOBE>
 [code]

Do I need to set skip machine oobe as well as Admin set & autologon toggled on.

[/code]

</settings>
	<settings pass="specialize">
		<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
			<Identification>
				<JoinWorkgroup>Workgroup</JoinWorkgroup>
[code]

Do I need to nominate something else in the ans file to skip the setup network lot?

Thanks Fellas

Update:

Choosing skip machine setting sorted the user screen as expected, although waik setting depracated. Works fine though.

I also changed my network setting from Other to Work however pops the network screen up with Work highlighted? Not a real biggy though.

I have the same problem.

[MAVERICKS CHOICE]

Yes still haven't found a way to kill the network page on first startup?

[sp00f]

MAVERICKS CHOICE, on Mar 13 2007, 07:57 PM, said:

Yes still haven't found a way to kill the network page on first startup?

Only more people with same prob

http://forums.microsoft.com/TechNet/ShowPo...6&SiteID=17

[prathapml]

I use the sample autounattend.xml in first post & the regtweak posted above, & i never get prompted for the network-location

[MAVERICKS CHOICE]

@prathapml

Yes I have the same Network setting as you & using the Ultimate 32 bit ver.

Well more work is obviously req'd here as it appears many other peers are xping the same issue now??

This post has been edited by MAVERICKS CHOICE: 14 March 2007 - 03:04 AM

[keul]

prathapml: is your oemlogo displayed when you use the autounattend file submitted in your 1st post ?
Mine doesn't as windows stores the path in a REG_SZ key instead of a REG_EXPAND_SZ

mc: I use a modded version of prathapml's autounattend file, set network as "home" and never get network page on 1st startup. And now that I use sysprep with a second xml file with network set a "home", I don't get it either... Tell me if you need more information.

This post has been edited by keul: 17 March 2007 - 08:48 AM

[sp00f]

<StartPanelOff>true</StartPanelOff> doesnt work , or need i more settings for this?

[MAVERICKS CHOICE]

mc: I use a modded version of prathapml's autounattend file, set network as "home" and never get network page on 1st startup. And now that I use sysprep with a second xml file with network set a "home", I don't get it either... Tell me if you need more information.
[/quote]

Taken on board, will incorporate.

EDIT: I also found a sharp reboot after install at first use gets rid of that page & doesn't pop up again, quick & dirty I know...

This post has been edited by MAVERICKS CHOICE: 28 March 2007 - 02:16 PM

[sp00f]

I tried this on a x64 version, but then WAIK shows lots of errors

Any one else tried this on x64 ?

[prathapml]

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

[sp00f]

prathapml, on Apr 14 2007, 07:40 AM, said:

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.

This post has been edited by sp00f: 16 April 2007 - 07:31 AM

[jaybot]

I would love a look at your x64 xml.

[sp00f]

jaybot, on Jun 6 2007, 12:52 AM, said:

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

[prathapml]

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.

Quote

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

[Stead]

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!

[MAVERICKS CHOICE]

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

[prathapml]

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.

[Stead]

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!

[prathapml]

Oh yes, it is part of WAIK.

[prathapml]

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):

prathapml, on Jul 27 2007, 06:39 PM, said:

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.

Quote

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