FirstLogonCommands log to where?

Question

When you screw up with your "FirstLogonCommands -> SynchronousCommand" where does it log this catastrophic failure too?

They're in my unattend.xml (a cut down of the autounattend.xml).

In my case, its a powershell thing to rename the interfaces from ローカル ネットワーク接続 to the slightly more elegant LAN1.

powershell.exe C:\test\renamelan1.ps1

It's almost certainly pilot error...

---

=^x^=

Answer 1

In the Windows directory, there are some log files: Setuperr.log an setupact.log. You should also check out the logs in the \Windows\Pather\Unattend folder.

-Sean

---

www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WES 7, XP Embedded Advanced, Pro Guide to POS for .NET

Answer 2

As always, I appreciate your prompt replies.

I see mention of the actual command in \Windows\Panther\UnattendGC\setupact.log but all it says there is:

<time> [Shell Unattend] Running 'oobeSystem' pass

<time> [Shell Unattend] LogonCommands: Set command 'powershell.exe C:\test\renamelan1.ps1'

<time> [Shell Unattend] Exiting 'oobeSystem' pass with status 0x0000000

Yet from the name of the interface, it is clear that this command didn't run.

Could it be that I am trying to use FirstLogonCommands in the wrong way?

---

=^x^=

Answer 3

If you run it manually in the image post install, does it work?

One more thing you might want to put in the hard coded path to powershell.exe - just in case. I used the full path when I set PowerShell as the shell to the system: http://www.annabooks.com/Articles/Articles_WES7/PowerShellasShellV1.1.pdf

-Sean

---

www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WES 7, XP Embedded Advanced, Pro Guide to POS for .NET

Answer 4

Indeed, it does run manually, it prints "renaming intel ... to LAN1"

Another command i put in "sc config sysmain start= disabled" gives every appearance of having worked.

I'll try the full path next (in a couple of hours), I'm just mystified at the moment.

---

=^x^=

Answer 5

I have seen issues with trying to make network changes during installation. this might be one you have to run post install and be fore running sysprep.

-Sean

---

www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WES 7, XP Embedded Advanced, Pro Guide to POS for .NET

Answer 6

Over 10000 points, congratulations.

Using the full path for powershell appears to be the winner.

---

=^x^=

Answer 7

This is good to know. Setting up th lan during install has been an issue. If PowerShell does the trick, there is a solution.

-Sean

---

www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WES 7, XP Embedded Advanced, Pro Guide to POS for .NET

Answer 8

# find the 82579V and rename it.
$Nics = Get-WMIObject -Class Win32_NetworkAdapter -filter "PhysicalAdapter=True"
	Foreach ( $nic in $Nics ) {
		# check the device is really the device we want, look for 82579V
		#
		if ($nic.name -match "82579V" ) {
			$FoundAffy = $nic.DeviceID
			$nic.NetConnectionID="LAN1"
			Write-Host -nonewline "Renaming: " $nic.Name
			Write-Host -nonewline " to " $nic.NetConnectionID
			Write-Host
			$nic.put() | out-null
		}
	}

Something simple like this, it isn't very elegant but it does the job because this box has different chips for wireless, lan1 and lan2. One thing that is weird is that it likes to make a new interface when booted on ostensibly identical hardware. I haven't worked that one out yet.

not even a diff of devices.pmq tells me why.

---

=^x^=