[Spooky]

Geckotek, on Nov 5 2003, 12:18 AM, said:

According to this, you can't have both OOBE and an unattended gui install.

http://support.micro...om/?kbid=289657

Edit: Somehow I figured it out.  I edited my winnt.sif w/ setupmgr and for some reason it showed it was trying to join a domain (even though I had pulled that section out.)  Go figure.  So running setupmgr reset some of my settings and things all work fine now.

Thanks for the info Num....it was very helpful.

read the link. Thanks

It always gives me a laugh when MS says:

"STATUS
This behavior is by design. "

[Numinous]

hehehe they're full of crap

[GreenMachine]

Thanks once again for the research, Numinous. Was afraid for a moment that we'd lost you in an endless loop.

"This behavior is by design." ... Gotta love it!

[Numinous]

it's not over yet im digging into msobmain.dll .. some interesting password stuff going on .. we'll see if theres another way .. don't get yer hopes up though

[kukris]

I have a question: If i make an unattended W2K-Installation with the following data, which user will be logged on the first time, Administrator or User1?

oobeinfo.ini

[UserInfo]
Identity000="user1"

winnt.sif

[GuiUnattended]
    AdminPassword=test
    EncryptedAdminPassword=Yes
    OemSkipWelcome=1
    AutoLogon=Yes
    AutoLogonCount=1

[UserData]
    ProductID=???
    FullName=User2
    ComputerName=computer

[Spooky]

kukris, on Nov 28 2003, 02:33 PM, said:

I have a question: If i make an unattended W2K-Installation with the following data, which user will be logged on the first time, Administrator or User1?

oobeinfo.ini

[UserInfo]
Identity000="user1"

winnt.sif

[GuiUnattended]
    AdminPassword=test
    EncryptedAdminPassword=Yes
    OemSkipWelcome=1
    AutoLogon=Yes
    AutoLogonCount=1

[UserData]
    ProductID=???
    FullName=User2
    ComputerName=computer

I think since Identity000="user1" , and "Identity000" is always the administrator account and if this is the only thing you have in the file then the user1 will be logged in first?

[prathapml]

I thought I could chip in with what I have done:

First ensure that "unattendedswitch=yes" (in winnt.sif), because that is the only way you can disable the manual OOBE and instead configure it for automation.
my oobeinfo.ini

[UserInfo]
Identity001="Normal Usage"
Identity002="testing"
Identity003="Config"

For more info, see the deploy.cab's chm files.
Place oobeinfo.ini in - "$OEM$\$$\System32\OOBE\".

And, apply this thru a .reg at cmdlines.txt stage:

;logs in user "Config" the first time
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="Config"
"DefaultPassword"=""
"AutoAdminLogon"="1"

The above directly logs in the user Config (if you've disabled that OOBE with UnattendSwitch=Yes) and continues with your guirunonce.


The below, if run thru a .reg thru guirunonce stops subsequent auto-logging in:

;first of all, stop further auto-logins
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"=""
"DefaultPassword"=""
"AutoAdminLogon"="0"

Then, do this thru a .cmd (during guirunonce):

ECHO Applying usernames and passwords...
net user testing mypassword
net user Config mYpA$$w0rD
net localgroup Administrators "Normal Usage" /delete
net localgroup Users "Normal Usage" /add
ECHO.

change the word "mypassword" to the password you want to assign.
The (now) limited-user called Normal Usage will still be able to click his name at the user-welcome screen and login without providing any password.


I have tested this many,many,MANY times and it works perfectly.
Tell me if you liked it. (i wanted something like what i have described above since 4 months before i got trickles of ideas about this. I then put together the entire *WORKING* process to help others who want the same). Turned out to be pretty simple, right?


hoping this helps
Cheers !!!

[prathapml]

Quote

According to this, you can't have both OOBE and an unattended gui install.

no, you can, as you can see in the last post above.
using both in conjunction fixes a crucial missing link in the chain of absolutely unattended install.

[Numinous]

thanks for tidying things up prathapml .. good job

[Ignis]

for some reason, my administrator account isn't being created anymore, so the only accounts i have is those i create at the oobe welcome screen...

dont ask my why... coz i dont know

[Numinous]

it does still exist .. its hidden if another administrator profile is created

open Administrator Tools\Computer Management, browse to Local Users and Groups\Users and you should see it listed

[Ignis]

actually it doesnt exist, thats the strange thing :S

[Numinous]

strange indeed lol .. more secure without it anyway .. bonus

[prathapml]

Taking this technique forward, it results in great reductions to some head-aches.
All thanks to numinous who was the first to inform about this!!!!!!!

@Ignis

Quote

actually it doesnt exist, thats the strange thing :S

Well, it does exist, but not visible in other accounts. Start-up in safe mode, and you'll see the "Administrator" ID available for logon.
Or, run the command prompt, and type the command

net user

to see a wide listing of all local users (where the Administrator account will show up as well).

[tr4ck]

I have my oobeinfo.ini in $OEM$\$$\System32\oobe. In it I have 1 user:
[UserInfo]
Identity000="V"

I tested my unattended cd with vmware, when it tries to autologin it says "the system could not log you in" when I hit ok it logs me in as "Administrator". And when I do the command net user it doesn't show the user V. Can someone help me?

Thanks.

[prathapml]

Well, you do know that if you create only one user from oobeinfo.ini, windows will log you in automatically without needing any password, until you set the password for that user. Also the account will be made part of the "Administrators" group with equal privileges.

What you seem to be unaware of, is that the userID you create from oobeinfo.ini should be atleast 5 characters and the ID should not be "Administrator" or "guest".


And, on your part, you have posted sufficient info to diagnose the issue. This is what I'd say:
1. Whatever steps you have already taken are right.
2. Just give a longer user-name.

---------------
Further info:

My oobeinfo.ini contents-

[UserInfo]
Identity001="Normal Usage"
Identity002="Vaidh"

The registry chunk that I apply at cmdlines.txt stage:

;logs in user "Vaidh" the first time
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="Vaidh"
"DefaultPassword"=""
"AutoAdminLogon"="1"

And this is the chunk I apply after first log-in (at GUIrunonce atage):

;first of all, stop further auto-logins
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"=""
"DefaultPassword"=""
"AutoAdminLogon"="0"

[tr4ck]

I still have the same problem even with a longer name.

oobeinfo.ini is in $OEM$\$$\System32\oobe and its contents are:
[UserInfo]
Identity000="Vishal"

In $OEM$ I got CMDLINES.TXT which calls autologin.reg whose contents are:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="Vishal"
"DefaultPassword"=""
"AutoAdminLogon"="1"

Here are the contents of my winnt.sif file:
[Data]
AutoPartition=0
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
TargetPath=\WINDOWS
FileSystem=*
UnattendSwitch="yes"
WaitForReboot="No"
Repartition=No
OemPnPDriversPath="drivers\graphics"
DriverSigningPolicy=Ignore
KeyboardLayout="US"

[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1

[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
FullName="Vishal"
OrgName=""
ComputerName=Home

[Display]
BitsPerPel=16
Xresolution=1024
YResolution=768
Vrefresh=75

[TapiLocation]
CountryCode=107
Dialing=Tone
AreaCode=604

[RegionalSettings]
LanguageGroup=1
Language=00000409

[Branding]
BrandIEUsingUnattended=Yes

[URL]
Home_Page=http://www.google.ca/
Search_Page=http://www.google.ca/

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=1

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=No

[NetAdapters]
Adapter1=params.Adapter1

[params.Adapter1]
INFID=*

[NetProtocols]
MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]
DNS=Yes
UseDomainNameDevolution=No
EnableLMHosts=Yes
AdapterSections=params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]
SpecificTo=Adapter1
DHCP=Yes
WINS=No
NetBIOSOptions=0

[Shell]
DefaultThemesOff = Yes

[GuiRunOnce]
%systemdrive%\install\start.cmd

Is there anything else that I am missing?

Thanks for the help.

[prathapml]

Well, whaddaya know - found the culprit !!!!!!

@ tr4ck
Read my previous post here (the one just above your detailed description).
You'll find your oobeinfo.ini starts with

Identity000

While mine starts with

Identity001

Looks like OOBE doesn't parse the Zero'th identity - it only starts from the first identity (i.e., from number 001, instead of 000).

[tr4ck]

I got the Identity000 from the very first post of this thread. But it doesn't seem to matter I changed it to Identity001 and it still doesn't work. I'll try it with only the oobe folder and nothing else and see if that works.

[data0002]

Hi all

I have looked at this topic, but what i need is the main screen so the end user adds their own names when they get their pcs/laptops.

With thanks