Unattended not working

[mail4skwarka]

Hello

During the installation I have a message

"Windows Could not parse or process

unattend answer file [C: \ Windows \ Panther \ unattend.xml] for pass

[oobesystem]. "

thnx for help

autounnatend.xml version x86 create Windows 7 Toolkit

<?xml version="1.0" encoding="utf-8"?>
<!--Created by Windows 7 Toolkit v1.3.0.96-->
<unattend xmlns="urn:schemas-microsoft-com:unattend">
	<settings pass="windowsPE">
		<component name="Microsoft-Windows-Setup" 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">
			<UserData>
				<AcceptEula>true</AcceptEula>
			</UserData>
		</component>
	</settings>
	<settings pass="specialize">
		<component name="Microsoft-Windows-Shell-Setup" 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">
			<ComputerName>ROCK</ComputerName>
		</component>
		<component name="Microsoft-Windows-Security-SPP-UX" 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">
			<SkipAutoActivation>true</SkipAutoActivation>
		</component>
	</settings>
	<settings pass="oobeSystem">
		<component name="Microsoft-Windows-Shell-Setup" 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">
			<OOBE>
				<HideEULAPage>true</HideEULAPage>
				<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
				<NetworkLocation>Work</NetworkLocation>
				<ProtectYourPC>1</ProtectYourPC>
			</OOBE>
			<RegisteredOrganization>FREEWORLD</RegisteredOrganization>
			<UserAccounts>
				<LocalAccounts>
					<LocalAccount wcm:action="add">
						<Name>SerwiS</Name>
						<Group>Administrators</Group>
						<Password>
							<Value>serwis</Value>
							<PlainText>true</PlainText>
						</Password>
						<DisplayName>SerwiS</DisplayName>
						<Description>SerwiS</Description>
					</LocalAccount>
				</LocalAccounts>
			</UserAccounts>
			<AutoLogon>
				<Password>
				<Value>serwis</Value>
				<PlainText>true</PlainText>
				</Password>
				<Enabled>true</Enabled>
				<LogonCount>0</LogonCount>
				<Username>SerwiS</Username>
			</AutoLogon>
			<TimeZone>Central European Standard Time</TimeZone>
		</component>
	</settings>
</unattend>

Autounattend.xml

Edited January 24, 2012 by mail4skwarka

[myselfidem]

Try: <LogonCount>3</LogonCount> !

[mail4skwarka]

What an instant answer!

Maybe you're right:

Auto Logon is set to 0 (default setting -> infinitely?)

or 0 exactly zero?

[myselfidem]

Infinitely value: <LogonCount>9999999</LogonCount> !

Maybe you can try also to give another value for password, because it's the same value for your user account !

Thanks to try it and let us know.

[mail4skwarka]

myselfidem

Your advice has solved my problem.

Thank you very much!!!

[myselfidem]

Thanks and enjoy!

[mail4skwarka]

Does the use of file unnatended.xml setupcomplete.cmd excludes the use of a file?

I used the folder options in the DVD root directory $OEM$\$$\SETUP\SCRIPTS\SETUPCOMPLETE.CMD and unfortunately did not work.

In XP, turn on the OEM Preinstall options, here it should work straight away right?

[myselfidem]

No, you can use Autounattend.xml file and SetupComplete.cmd.

Could you attach your SetupComplete.cmd, please, to see if there is some errors ?

[mail4skwarka]

The problem is that after installation there was no file in the directory scripts setupcomplete.cmd.

File setupcomplete running from the DVD to work correctly.

Are you in Autounattend.xml disable User Account Control?

I created a universal file into two versions of x86 and x64 systems.

At this time, I test the x86 version

setupcomplete.zip

Edited January 24, 2012 by mail4skwarka

[myselfidem]

Try to create your $OEM$ folders inside:

%SystemDrive%\Folder_Location_Name\sources\$OEM$\$$\Setup\scripts\SetupComplete.cmd

However it's not really a good idea to install programs like this and the registry keys for the current user can't be integrated!

It's better to use RunOnceEx method (works also for reg keys to current user):

or Windows 7 Toolkit and Addons,

or Windows Post-Install Wizard (WPI).

It's just my advice!

However it's possible to install programs with Autounattend.xml file using:

<FirstLogonCommands>

Edited January 24, 2012 by myselfidem

[hornet512]

you can use Autounattend.xml file and SetupComplete.cmd.

What is SetupComplete.cmd?

I have never used it

[myselfidem]

More infos about SetupComplete.cmd:

http://technet.microsoft.com/en-us/library/cc766408(WS.10).aspx

http://technet.microsoft.com/en-us/library/cc766314(WS.10).aspx

[mail4skwarka]

Question about the priority:

in Autounattend.xml disable User Account Control???

For <FirstLogonCommands> You mean this syntax?

<FirstLogonCommands>
   <SynchronousCommand wcm:action="add">
	  <CommandLine>c:synccommands\command1.exe</CommandLine>
	  <Description>Description_of_command1</Description>
	  <Order>1</Order>
   </SynchronousCommand>
   <SynchronousCommand wcm:action="add">
	  <CommandLine>c:synccommands\command2.exe</CommandLine>
	  <Description>Description_of_command2</Description>
	  <Order>2</Order>
   </SynchronousCommand>
</FirstLogonCommands>

But if there is no error?

<CommandLine>c:synccommands\command1.exe</CommandLine>

should probably be so

<CommandLine>c:\synccommands\command1.exe</CommandLine>

How to use the dvd drive path?

Edited January 24, 2012 by mail4skwarka

[myselfidem]

Using FirstLogonCommands, like this to start from the DVD:

Example with WPI:

<FirstLogonCommands>
				<SynchronousCommand wcm:action="add">
					<Order>1</Order>
					<Description>Password never expires</Description>
					<CommandLine>cmd /c wmic useraccount where "name='myselfidem'" set PasswordExpires=FALSE</CommandLine>
					<RequiresUserInput>false</RequiresUserInput>
				</SynchronousCommand>
				<SynchronousCommand wcm:action="add">
					<Order>2</Order>
					<Description>Installing Apps with WPI</Description>
					<CommandLine>cmd /c for %i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %i:\wpi\wpi.exe start %i:\wpi\wpi.exe</CommandLine>
					<RequiresUserInput>false</RequiresUserInput>
				</SynchronousCommand>
			</FirstLogonCommands>

SetupComplete.cmd is executed before FirstLogonCommands !

*Edit: Maybe you can start a new topic about this questions, because it's out of this topic ?

Edited January 24, 2012 by myselfidem

[mail4skwarka]

I understand that I can use instead WPI.exe eg RunFirstLogon.cmd?

Do I need to create the user, since I have it already defined?

Probably still located in the category does not work unattended, going all the time in question, I think so?

I will take the test, the rest of the questions later.

Thanks a lot

Edited January 24, 2012 by mail4skwarka

[myselfidem]

We can read inside: Unattended Windows Setup Reference for Windows 7.chm:

Download

http://www.microsoft.com/download/en/details.aspx?id=2458

FirstLogonCommands

The FirstLogonCommands setting specifies commands to run the first time a user logs on to the computer. These commands run only once.

When a user with administrative privileges logs in for the first time, these commands are run with elevated access privileges.

Note: If you create a user account that does not include administrative privileges, the following commands may not be executed:

• If User Account Control is enabled, then when that user logs in for the first time, a dialog box appears, prompting the user with an option to allow an administrator to apply the commands. If the user selects Cancel, these commands are not executed.
  
• If User Account Control is disabled, these commands are not executed.
  

The commands run after logon, prior to showing the desktop.

The commands run in the order specified. Each command must finish before the next command runs.

If the command launches a separate system process, the system process will run independently of the commands. This enables you to create commands that terminate quickly, allowing the user to reach the desktop faster.

Other processes, such as services, are not restricted by FirstLogonCommands and will continue to start or to terminate independently.

For your two questions: Yes!

Edited January 24, 2012 by myselfidem

[Legolash2o]

What an instant answer!

Maybe you're right:

Auto Logon is set to 0 (default setting -> infinitely?)

or 0 exactly zero?

If Logon Count is not checked then AutoLogon is set to 999999 or something like that.

[mail4skwarka]

Legolash2o:

Maybe it would be good to put this information in Windows 7 Tololkit in Unnaetneded Creator / Main / AutoLogon/ Logon Count something like this example: If the Logon Count is not checked then AutoLogon is set to 999,999 (infinitely).It would be clearer about what's going on