[TheWalrus]

To add to the confusion, if I create TWO new users, the 2nd one is actually created and logged on. What the hell is this? What am I doing wrong?

[Tripredacus]

Your logon count is set for 3, which means it will only log on automatically 3 times. Try using a higher number like a million.

[bphlpt]

@Tripredacus, he said he specifically did not want to do it that way.

TheWalrus, on 09 April 2012 - 01:26 AM, said:

1) What do I change where (registry-wise I guess) to make a local account autologon PERMANENTLY? Not setting silly stuff like logoncount=9999. Run netplwiz and uncheck the usual tickbox is exactly what I want to achieve. Any pointers?

Cheers and Regards

[TheWalrus]

Exactly. I can of course do this manually after installation, but I am trying to achieve as much as possible automatically (and learn new stuff).

At the moment I am going nuts over the account creation and Aero themes though.

[Tripredacus]

I can't say about the Account problem, as I never enable the built-in Administrator account. So I have no experience with the OS' behaviour during unattended setup with it enabled.

For AutoLogon, I'm not sure why you wouldn't want to use the AutoLogon in Unattend. Presuming you get your account creation thing taken care of, you'll see that it shouldn't be a problem. The only issue you'll run into after that is any user accounts created via Unattend will have their password expire after 2-3 months. Running this in your FirstLogonCommands will fix that:

wmic useraccount where "name='AccountName'" set PasswordExpires=false

It may also be possible to set AutoLogon using WMI, but I did a quick look in UserAccount with the WMI Object Browser but didn't see it there. Another option may be to write to the appropriate registry values.

[TheWalrus]

Well, permanent autologon is very handy for home computers. I am installing a new laptop for my father in law these days. He is the only one who will use it, so there is absolutely no reason for 1) having to type a password 2) creating extra account, which would be administrator anyway.

My problem with autologon in unattended setup is that you ONLY can set finite amount of logons. Of course one million is probably enough until the thing gets replaced in a few years, but I want to do stuff "proper" way. There is a manual way, but I'd like to achieve that this way. Of course maybe it's impossible just like the themes.

[Tripredacus]

There is no harm in creating a second account. He would never end up seeing it unless he did a log-off and saw the welcome screen. Having an extra account can come in handy if the primary account becomes corrupted or has a virus in it or whatever.

[TheWalrus]

You are probably right. But is it possible to create a new account which will be an administrator AND have the default Administrator account enabled at the same time?

[TheWalrus]

The computer is playing with me!

                    <LocalAccount wcm:action="add">
                         <Name>blabla</Name>
                         <DisplayName>blabla</DisplayName>
                        <Group>Administrators</Group>
                        <Password>
                            <Value>aaa</Value>
                            <PlainText>true</PlainText>
                        </Password>
                    </LocalAccount>

The account is a guest! What the hell!

This post has been edited by TheWalrus: 10 April 2012 - 09:59 AM

[maxXPsoft]

Autologon credentials are deleted from the unattended installation answer file after Windows® Setup is complete.
So settinga number means nothing as long as it is 1 for intended passes, not like you going to re-do them passes

Valid Passes = auditSystem, oobeSystem, specialize
You don't add them normally unless you do audit

TheWalrus, on 10 April 2012 - 09:58 AM, said:

The computer is playing with me!

                    <LocalAccount wcm:action="add">
                         <Name>blabla</Name>
                         <DisplayName>blabla</DisplayName>
                        <Group>Administrators</Group>
                        <Password>
                            <Value>aaa</Value>
                            <PlainText>true</PlainText>
                        </Password>
                    </LocalAccount>

The account is a guest! What the hell!

Remove the <PlainText>true</PlainText>, other than looking at your log files don't set a default value. xml is very tricky with UA. 1 thing will cause you to blue screen or do weird things

This post has been edited by maxXPsoft: 10 April 2012 - 05:04 PM

[TheWalrus]

Well, it definitely does log the user in the number of times I set there, I tested that. But still doesn't solve my problem




Btw where do you think it's better to install drivers and software at? I switched over from firstlogoncommands to setucomplete.cmd and it works just fine, sadly with the exceptions of funky stuff like Synaptics Touchpad and 3D DriveGuard. Was thinking to put it in the former as I wouldn't have to rewrite answer file for different PC then and just flip the batch files instead. Besides, one can easily just close the **** cmd windows when the desktop is already accessible (lots of lusers do that).

[Tripredacus]

maxXPsoft, on 10 April 2012 - 05:03 PM, said:

Autologon credentials are deleted from the unattended installation answer file after Windows® Setup is complete.
So settinga number means nothing as long as it is 1 for intended passes, not like you going to re-do them passes

This is true, the password gets removed, however the number does get used. I've tested with both 1, 3 and 10. I wonder where that value is kept in the OS?

[TheWalrus]

I believe it's HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon




I am playing around with my batch files and am wondering whether there is a way to make the cmd window impossible to close.

[nice_guy75]

TheWalrus, on 11 April 2012 - 09:42 AM, said:

I believe it's HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon




I am playing around with my batch files and am wondering whether there is a way to make the cmd window impossible to close.

Use Autoit commands with SW_HIDE flag, I use the same for hiding cmd window.

[TheWalrus]

Out of question, but thanks for tips anyway.

[bphlpt]

I have a very basic question that has to do with making a dual-arch AutoUnattend xml file. If anyone has already addressed this somewhere, please just point me to the link.

The way I understand it, 32bit Win7 only processes the x86 sections, while 64bit Win7 processes BOTH the x86 and the amd64 sections? Is there any way to make a 64bit Win7 process ONLY the amd64 section?

The reason I ask this is that a friend of mine is putting together a dual arch file. There are a few things that he needs to ONLY run in the 32bit OS and some that he ONLY wants to run in a 64bit OS. But if he puts the 32bit only file in the x86 section then the 64bit OS tries to run that as well. How can we prevent this but still have it available where the 32bit OS will pick it up?

Thanks in advance.

[myselfidem]

Maybe you can find some help here: (example for Windows 7 AIO):

Create your own Autounattend.xml All-In-One (x86/amd64)

Regards

[bphlpt]

Thanks, myselfidem,

I'll pass along the info

Cheers and Regards