FirstLogonCommands failing

[leozack]

Do you have a sample autounattend.xml and setupcomplete.cmd or whatever it is you are using for your vista build then? If autounattend can boot to auditmode and do the dotnet 4 install/updates there and the dotnet351 updates and tweak and then reboot and all is well then I am happy to do it that way.

I just tested with a clean win7 build with a few component removals/tweaks but with dotnet4 installed at setupcomplete.cmd time. It had the appwarnings about .net optimisation service! So I tried the same build without dotnet4 going on and now it has no applog warnings!

I just installed the first of the 3 dotnet351 updates and bang - applog warnings .net optimization service 1130 everywhere again :/ I can't be the only one! There must be a solution! I need it ASAP I wanted to image on monday! >_<

Maybe these applog warnings should be ignored and as expected? Argh - why must I be a perfectionist in this build! D:

Edited November 17, 2011 by leozack

[maxXPsoft]

sample in 2nd post here

[myselfidem]

Infos about Audit mode:

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

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

[leozack]

Maxxpsoft looking at your 2nd post there it seems you just have this

    <settings pass="auditSystem"> 
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
            <AutoLogon> 
                <Enabled>true</Enabled> 
                <LogonCount>2</LogonCount> 
                <Username>Admin</Username> 
            </AutoLogon> 
            <Display> 
                <ColorDepth>32</ColorDepth> 
                <HorizontalResolution>1024</HorizontalResolution> 
                <VerticalResolution>768</VerticalResolution> 
            </Display> 
            <UserAccounts> 
                <LocalAccounts> 
                    <LocalAccount wcm:action="add"> 
                        <Password> 
                            <Value></Value> 
                            <PlainText>true</PlainText> 
                        </Password> 
                        <Group>Administrators</Group> 
                        <Name>Admin</Name> 
                    </LocalAccount> 
                </LocalAccounts> 
            </UserAccounts> 
        </component> 
    </settings> 
    <settings pass="auditUser"> 
        <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
            <RunSynchronous> 
                <RunSynchronousCommand wcm:action="add"> 
                    <Order>400</Order> 
                    <Path>cmd /C start /wait %systemdrive%\Install\AuditUser.cmd</Path> 
                </RunSynchronousCommand> 
            </RunSynchronous> 
        </component> 
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
            <Display> 
                <ColorDepth>32</ColorDepth> 
                <HorizontalResolution>1024</HorizontalResolution> 
                <VerticalResolution>768</VerticalResolution> 
            </Display> 
        </component> 
    </settings> 

which seems to just make an admin user called admin with no password and set it to logon twice automatically (doing what each time?) and sets it to run audituser.cmd (what does that do?)

Just not sure why I'd be using audit mode - what will change/make a difference? As far as I'm aware you can setup windows not in audit mode and then reboot it with sysprep and image it and it should be ok?

[maxXPsoft]

It don't login 2 times thats nothing, once done and oobe it won't go back

You can log in with a user my example Admin which is an Administrator and run anything. Install whatever then reboot into OOBE

The AuditUser.cmd run's my program to install all my applications

Remember that once this is done when you hit desktop everything is done. You can do things with Firstlogon and setupcomplete though.

My Cleanup.cmd reboot into OOBE with this.

REM Reboot OOBESYSTEM Pass

FOR %%d 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 %%d\OOBEAudit.xml SET DVDroot=%%d

Echo.

sysprep.exe /oobe /reboot /unattend:%DVDroot%\OOBEAudit.xml

REM To Generalize erase above line and use this

REM sysprep.exe /generalize /oobe /shutdown /unattend:%DVDroot%\OOBEAudit.xml

OOBEAudit.xml all it contains is <settings pass="oobeSystem">

Do you have WAIK help files? unattend and waik.chm are real handy http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=2458#QuickInfoContainer

[leozack]

I know I'm being a right id*** here but I'm just not seeing any reason why I need it to do any audit system/user mode

I have here a build where I used the vanilla win7sp1 media and then installed the 3 dotnet 351 updates and then installed dotnet4. No warnings in applog!

Then 20m later or something without diong anything - 1 shows up. Now days later none since!

Should I just get on and deploy a build and ignore these 1130 errors? I can't find any good information online to fix them and they're only warnings not errors. It just annoys me as I'd like a clean build with clean event logs not generating spam.

I don't mind doing dotnet 4 at setupcomplete.cmd time in passive mode and I don't mind running my script of updates to dotnet351 or other stuff at firstlogoncommands time - I don't see why I should go into audit mode - especially when it may be rebooted many times when being configured before it will be sysprep'd (and I've recently been confused as to what the /generalize command on sysprep does - I read somewhere it just deletes the admin account or something? O_o

[maxXPsoft]

That is what audit does, can install everything and be done with it.

don't do audit then. use what you was doing. If I need net4 I'll let WU do it.

[leozack]

That is what audit does, can install everything and be done with it.

don't do audit then. use what you was doing. If I need net4 I'll let WU do it.

Like I said I'm not trying to be pedantic here but I'm not seeing WHY you use winaudit (or what you script in winaudit). I haven't tried winaudit yet because from everything I've read (yes I do read your links and the guides etc) it just says it's for OEM's to configure a PC ready for repackaging for an end user. Ok so technically after this build installs I configure it and then image it out for a certain PC model at a certain site, but I'm used to just doing that in normal windows then sysprepping so I haven't used audit mode and audit mode still requires sysprepp'ing afterwards with /oobe, and I see nothing about audit mode that will eid me scripting installs which run as firstlogoncommands anyway?

so if you have a secret reason to use audit mode then tell me - otherwise I just don't see the difference.

I'm currently ignoring the build problems and trying to work out what I need in a new unattend.xml made JUST for sysprepp'ing a machine to /generalise then reboot and join itself to a domain automatically ready for a user. Because that is the sysprep I run before taking the image so when the imaged PCs bootup they just ask for a pcname then autojoin the domain and everything is ready for a user

[myselfidem]

Tested successfuly with my Administrator account inside Autounattend.xml file. No errors with Windows 7 Ultimate x86 SP0 and Windows 7 Ultimate SP1 whithout using SetupComplete.cmd!

It is just an example and adapt this one to your needs for the donetFx40 path!

FirstRun.cmd and dotNetFx40_Full_x86_x64.exe are set inside= Distribution_Folder\sources\$OEM$\$$\Setup\scripts

FirstRun.cmd

@echo off
REM Called from %windir%\Setup\Scripts\FirstRun.cmd
REM Which is copied from [InstallDrive]\sources\$OEM$\$$\Setup\Scripts\FirstRun.cmd
echo              Installing .NET 4.0 ...Please wait...
echo.
cd /d %~dp0
%~dp0dotNetFx40_Full_x86_x64.exe /q /norestart
echo              Now rebooting ...
shutdown -r -t 30

Partial Autounattend.xml file

            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>9999999</LogonCount>
                <Username>Paul</Username>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Description>Password never expires</Description>
                    <CommandLine>cmd /C wmic useraccount where "name='Paul'" set PasswordExpires=FALSE</CommandLine>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <Description>Installing Net Framework 4.0</Description>
                    <CommandLine>cmd /c %Windir%\Setup\scripts\FirstRun.cmd</CommandLine>
                    <Order>9</Order>
                    <RequiresUserInput>false</RequiresUserInput>
                </SynchronousCommand>
            </FirstLogonCommands>
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value></Value>
                            <PlainText>true</PlainText>
                        </Password>
                        <DisplayName>Paul</DisplayName>
                        <Name>Paul</Name>
                        <Group>Administrators</Group>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>

Installation images

I hope that can help you!

Edited December 9, 2011 by myselfidem