[MrJinje]

Hey Walrus, if you want to try editing the registry as trustedinstaller without changing permissions, might be easier with the dvexexec.exe tool

devxexec.exe /user:TrustedInstaller regedit.exe

Or maybe you can edit this snip to reg add as TrustedInstaller at the command line. Keeps it simple and stupid, compared to batch scripting SetACL take ownership. EDIT: It cannot pass a variable to the command line, but it can run a batch file directly, so that's a start.

devxexec.exe /user:TrustedInstaller mybatch.cmd

reg add HKLM\Wim_Software\Microsoft\Windows\CurrentVersion\Explorer\CommandStore\shell\Windows.delete /v "Icon" /t REG_EXPAND_SZ /d "C:\pathto\myicon.ico"

This post has been edited by MrJinje: 30 September 2012 - 06:06 AM

[TheWalrus]

That doesn't sound bad. Will give it a shot. Thanks.

[Mikka]

Hi,

I've got an annoying problem with my current autounattend.xml (generated and successfully checked by SIM).

I want to flexibly install Windows 7 x86 SP1 (and x64 later on) for any edition (at start selected by the user).
Unfortunately, while processing the xml file Windows setup throws an error, saying that the settings for unattended setup couldn't be applied [offlineServicing].
Edit: A screenshot of this error has been posted here.

I tried commenting out the offlineServicing part, that didn't fix it. I verified version="6.1.7601.17514" and stuff, but no chance.

Now, I've got no clue what's wrong as I cannot check for logs in the virtual machine for the (failed) installation (some MSCE guy advised that).

See below what I've got so far.
Any tips, tweaks and additions are highly welcome!

 Autounattend.xml (15.65K)
Number of downloads: 15

This post has been edited by Mikka: 25 October 2012 - 07:46 AM

[Tripredacus]

Try your install without using the <servicing> object you have at the top.

There seems to be some issues with how those are setup anyways. For example, you have "FreeCell" but the help says "InboxGames\FreeCell" instead.
Is every install to be disabling these packages? Did you try using DISM to disable these features in the install.wim?

WSIM validating is not a 100% check on everything, because it has rules for the objects, and checks the XML syntax but it doesn't actually compare it against a live setup. So there are still ways to have a valid (as per WSIM) xml and still generate an error, such as you have seen here.

[maxXPsoft]

<servicing> is most likely the answer as Tripredacus said.
I have Win 7 Pro and from the feature export Dism /image:C:\zMountDir /Format:Table /Get-Features > %userprofile%\Desktop\zFeatures.txt
on a mounted image there is this which means it is removing it anyway which might cause errors.

Feature Name : Hearts
State : Disable Pending

Feature Name : FreeCell
State : Disable Pending

There is a way to capture the log files. Look here
http://www.msfn.org/...486#entry888486

[Mikka]

Tripredacus, on 25 October 2012 - 08:03 AM, said:

Try your install without using the <servicing> object you have at the top.

There seems to be some issues with how those are setup anyways. For example, you have "FreeCell" but the help says "InboxGames\FreeCell" instead.

You were right, after removing <servicing> the setup doesn't complain any more.
Good idea checking for "InboxGames\...", however it doesn't work. It's a tedious task to check which line is the culprit.

(Nice Microsoft ****-up by the way, thank SatanGod I'm no "regular" Windows admin.)

maxXPsoft, on 25 October 2012 - 10:00 AM, said:

I have Win 7 Pro and from the feature export Dism /image:C:\zMountDir /Format:Table /Get-Features > %userprofile%\Desktop\zFeatures.txt
on a mounted image there is this which means it is removing it anyway which might cause errors.

Hm, I'd played around with dism 2 years ago, there were quite a few glitches giving me a rough time.
Maybe I'll revert to WinToolkit 1.5.0.1 to sort out some components.

maxXPsoft, on 25 October 2012 - 10:00 AM, said:

There is a way to capture the log files. Look here
http://www.msfn.org/...486#entry888486

Thanks for the hint, I'll have a look at it.


Unfortunately, my Autounattend.xml still has got some flaws...
I'd like to install whatever w7 edition was selected at start, without pasting keys from \sources\product.ini.
That's why I manually changed the <ProduKey><Key /> part and also the file ei.cfg to read:

Quote

[EditionID]

[Channel]
OEM
[VL]
0

Now the following window pops up:

 nag1.jpg (21.27K)
Number of downloads: 9

I need to unset the tick and click on Skip / Überspringen to continue. That's bad.
After that another window appears to activate some default settings, in short: my unattended setup is gone!

This post has been edited by Tripredacus: 25 October 2012 - 02:42 PM

[Tripredacus]

Mikka, on 25 October 2012 - 01:28 PM, said:

(Nice Microsoft ****-up by the way, thank SatanGod I'm no "regular" Windows admin.)

Language like this will not be tolerated. Don't do it again.

[Mikka]

Sorry for the expression, I was miffed about the SIM labour...
It won't happen again.

[TheWalrus]

I could use some help with some batch files basics.

I am installing various software during FirstLogonCommands. It is done with two different commands actually, one is basic installation package for anything, and the other are some additions for specific machines. The last command starts the WinSAT index "recount" or however is it called.

I am not very educated about batch scripting, and I could use some help explaning a few things.

What exactly is the difference between simply putting "somefile.cmd" in the command and using "cmd /c" and "start /wait"? I read some documentation on ss64 but it's very unclear to me.

I also don't want the commands to run in parallel, I need them to be executed one after each other.



edit: Let me elaborate further.

            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <CommandLine>cmd /c start /wait %SystemRoot%\setup\scripts\install-basic.cmd</CommandLine>
                    <Description>ruzne instalace</Description>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <CommandLine>cmd /c start /wait %SystemRoot%\setup\scripts\install-extra.cmd</CommandLine>
                    <Description>ruzne instalace</Description>
                </SynchronousCommand>
                <SynchronousCommand wcm:action="add">
                    <Order>3</Order>
                    <CommandLine>cmd /c start /min winsat formal</CommandLine>
                    <Description>WinSAT</Description>
                </SynchronousCommand>
            </FirstLogonCommands>

Why does the above open command prompt, run the script, BUT doesn't close the window when finished installing what it should? If I type exit it moves onto the next one. I don't get it.

This post has been edited by TheWalrus: 02 December 2012 - 03:58 PM

[maxXPsoft]

Using the Start /wait they should run one after the other

put Exit on last line of each file
on the winsat you could put cmd /k which tells it to carry it out and continue

[TheWalrus]

I unclearly remember I didn't use exit at all and it did work at some point in past... It's really weird.




When I use only start or start /wait, the batch files aren't even executed at all. I really don't understand the differences.

[TheWalrus]

Also, aren't they supposed to run one after another by design of synchronouscommand in the first place anyway?

[maxXPsoft]

TheWalrus, on 03 December 2012 - 05:04 AM, said:

Also, aren't they supposed to run one after another by design of synchronouscommand in the first place anyway?

yes but I figured you knew that by your <Order>

It takes experimenting to figure out exactly what you need for your particular files. Some things run or start a process and it switches causing the original cmd script to drop out.
I add Exit to all my cmd files.

I've never got the start to work consistently alone so I use the cmd /c start /wait

[TheWalrus]

That's what I've always used as well, and it always worked. I am not sure whether I tried launching batch files before, though. Must be that.

Maybe going only cmd /c would be sufficient? I am still trying to figure out the difference from start (/wait). Sometimes it's a huge mystery.

[Tripredacus]

I always use exit, but I think if you use CMD /C with /WAIT but without the EXIT, the command prompt will stay on the screen with either a flashing cursor, or a C prompt after executing the script. This can also cause anything after it (in the chain of events) not work until the CMD is manually closed.

[maxXPsoft]

cmd /c opens a new command prompt and executes the command given. Theres no waiting or nothing and it will leave a window open as Tripredacus said
/c Carries out the command specified by String and then stops. Reason to use the Exit in cmd files
/k Carries out the command specified by String and continues. If you want to wait till command finishes this won't work because it will start the command line and then move on to next

Start is actually a command by itself but doesn't work as intended so we use the cmd /c Start /wait together. Even this is not perfect for all things, I have had trouble with some Autoit scripts

Windows Command Reference still in use even on Windows 8 http://www.microsoft...ls.aspx?id=2632

This post has been edited by maxXPsoft: 04 December 2012 - 08:25 PM

[Tripredacus]

Max, I used your example to create an unattend to install a program in Audit Mode. I set the logon count to 1, and added a WillReboot to Always. The problem I have is that when you use that AuditSystem pass to create the user, it isn't temporary. I would really prefer that after the Audit Mode work is done, that it reboot back into the built-in Administrator account automatically, then I would need to delete that "Admin" account. Any ideas on how to accomplish this?

This post has been edited by Tripredacus: 05 December 2012 - 01:50 PM

[maxXPsoft]

Why not go into Audit as the Administrator?

    <settings pass="specialize">
        <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>1</Order>
                    <Description>Enable Admin Account</Description>
                    <Path>net user administrator /active:yes</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>

Quote

Both Microsoft-Windows-Shell-Setup | Autologon and Microsoft-Windows-Shell-Setup | UserAccounts | AdministratorPassword sections are needed to auto logon to a computer in audit mode. Both of these settings should be added to the auditSystem configuration pass.

[Tripredacus]

I had considered that... is there a way to disable that again and audit mode still work properly?
I might even abandon this AuditSystem thing altogether...

[maxXPsoft]

Audit is to set things up for all users I guess like an OEM would do with drivers and their Oem programs and such
I hadn't tried removing a user but then the things you done with them would Prob be a mess.