[Doogy]

Hello,

I created a "autounattend.xml" using WAIK. The problem is that when I want to integrate applications at the end of the installation, sysprep runs and then after a few moments the PC off. I think the concern is when I put it in my file autounattend.xml:

"% WINDIR% \ system32 \ sysprep \ Sysprep.exe / quiet / audit"

An idea?

Sorry for my English ...

This post has been edited by Doogy: 28 January 2009 - 03:47 AM

[Kelsenellenelvian]

The sysprep is used for manufacturers and PC makers. When you use that command it cleans out the serial and sets it to a "Factory" state.

This is so the end-user\consumer starts the PC up then it asks for the serial and the user names, all of that info.

[Doogy]

If I understand correctly, when I run this command, it deletes all the information that I inserted in my file "autounattend.xml" to customize the installation of seven? Yet in the tutorial firegeier (http://firegeier.una...troduction.html) to use this command to start the silent installation of applications? When I create a vista unattended, this worked very well

Attached File(s)

•  autounattend.xml (7.94K)
  Number of downloads: 127

This post has been edited by Doogy: 27 January 2009 - 06:56 AM

[Kelsenellenelvian]

I see what you are talking about.

But his guide says to use the /audit switch in the commandline also.

[Doogy]

I'm sorry, I made a mistake in my first post (I have corrected). The time or installation stops, it is this command line (even with the / audit)

>% WINDIR% \ system32 \ sysprep \ Sysprep.exe / quiet / audit

[Doogy]

I saw that it was possible to activate the logs to install drivers for example, is it possible to choose the path where they are registered, to bring them on a removable media. Which would analyze the error.