[lilweirddude]

yeah but i want it as an admin acount

[Sanjay]

I have run into a problem that I am unable to figure out. In the past I have been able to succesfully create multiple users with my Unattended CD. The only time I had problems was when I ran it in VMware, but otherwise in real installations I had no problems at all. I have been using the following method:

Quote

Three Step Process:

1. Make a file oobeinfo.ini and place it in '\$OEM$\$$\SYSTEM32\OOBE'.
Contents of oobeinfo.ini:

[UserInfo]
Identity000="User1"
Identity001="User2"
Identity002="User3"

Replace User1, User2 etc. with your names. You can add upto six users thru this process.

2. Make a file 'autologon.reg' and run it thru 'cmdlines.txt'.
Contents of autologon.reg:

Windows Registry Editor Version 5.00 

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

3. Make a file stopautologon.reg and place it in '$OEM$\$1\INSTALL\LOGON' and run it at guirunonce stage via 'Start.cmd'.
Contents of stopautologon.reg:

Windows Registry Editor Version 5.00 

; Stop further Auto-Logins
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"=""
"DefaultPassword"=""
"AutoAdminLogon"="0"

Start.cmd entries to run stopautologon.reg:

ECHO.
ECHO Stopping Auto Logon in Future
start /wait regedit /s %systemdrive%\Install\Logon\stopautologon.reg

I have not made an Unattended CD for a long time and now that I have made one I can't get this to work. I end up with the following error message:

Quote

Logon Message
The system could not log you on. Make sure your User Name and domain are correct, then type your password again. Letters in passwords must be typed using the correct case.

I for the life of me cannot figure out what is causing this. I have compared the following 'oobeinfo.ini, autologon.reg, stopautologon.reg, Start.cmd' from my older cd, where it works, with my current cd and can't find any difference at all. But for whatever reson it just won't work anymore.

The major difference between my earlier cds and the current one are that I am now using the 'RVM_Integrator_1.0.5.exe' integrator to integrade RyanVMs Update pack and other addon packs. This is something I did not do in any of my older cds. Just mentioning this, not that I think this could be the cause, but then you never know.
My Winnt.sif file has the following entries:

;SetupMgrTag
[Data]
	AutoPartition = 0
	MsDosInitiated = "0"
	UnattendedInstall = "Yes"
	AutomaticUpdates = Yes

[Unattended]
	UnattendMode = FullUnattended
	UnattendSwitch = Yes
	OemSkipEula = Yes
	OemPreinstall = Yes
	Hibernation = Yes
	TargetPath = \WINDOWS
	DriverSigningPolicy = Ignore

OemPnPDriversPath = "Drivers\SATA\SiI3112r;Drivers\SATA\SiI3114r;etc\etc"

[SystemFileProtection]
	SFCQuota = 0

[GuiUnattended]
	AdminPassword = "wxyz"
	EncryptedAdminPassword = NO
	OEMSkipRegional = 1
	OEMSkipWelcome = 1
	TimeZone = 190

[UserData]
	ProductKey = xxxx-xxxx-xxxx-xxxx-xxxx
	FullName = "J. Doe"
	OrgName = "Semtech XYZ Inc."
	ComputerName = Semtech

[Branding]
	BrandIEUsingUnattended = Yes

[Proxy]
	Proxy_Enable = 0
	Use_Same_Proxy = 1

[Identification]
	JoinWorkgroup = WORKGROUP

[Networking]
	InstallDefaultComponents = Yes

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

Could any of these be the problem?:

1. Having set a password for AdminPassword?
--> [GuiUnattended]
--> AdminPassword = "wxyz"

2. Or could this be the problem? The Error message did say something about a correct user name and domain.
--> [Identification]
--> JoinWorkgroup = WORKGROUP

3. Could it be something in RyanVM's Update pack and/or other addon packs causing the problem? This is the 'One' major change between my previous working Unattended CDs and the current non working ones.

Any and all help will be greatly appreciated.
Thanks.

This post has been edited by Sanjay: 16 March 2006 - 03:07 PM

[Sanjay]

I can't believe it, not one of you has anything to say about this. C'mon guys I am sure someone can help.

This post has been edited by Sanjay: 13 February 2006 - 10:39 PM

[Sanjay]

I am still looking for a solution for my problem described above in Post# 82
In the meantime I have had to make my Unattended DVD partially 'Attended'. In WinNT.sif I set 'UnattendSwitch = No' which brings up a couple of windows for eg. Auto Update 'ON' 'Off', Checking for Internet connectivity, Register online 'Yes' NO' etc. and then it opens the Windows Logon page with all my Users already created I then just click on the oe that I wish to use as my main 'Admin' user and from there on everything works just fine.

Although this method has enabled me to atleast have a successful install, it still is not a true 'Unattended DVD' which kinda sucks, specially considerign that my method outlined above had been working for me for so long. Any help in this matter will be sincerely appreciated.

Thanks,
Sanjay

This post has been edited by Sanjay: 16 March 2006 - 03:08 PM

[simcam68]

I am certainly no expert when it comes to domains and setup, but here is what I think you may have wrong. This is from the help file in the windows deployment tools.

[Identification]
DomainAdmin = "admin"
DomainAdminPassword = "adminpassword"
JoinDomain = domainname

I think you should have something like that instead of the workgroup entry.

As far as the loging in, if you are going to use the Identity000 account, You really don't need the reg files. The first one on the list in the oobe file is Always considered the Admin account. You really only need the reg entry if you want a user other than the first one in the oobe file. Just use:

[GuiUnattended]
AdminPassword = "password"
Autologon = Yes
AutologonCount = 2

The above would allow the account to logon twice and then revert back to normal. Just change the count number for how many times you would like to autologon.

Also, the reason the oobeinfo thing doesn't work with VMWare is because when it boots up the first time, and trys to create the users, If the screen resolution is not at least 800x600 it will fail. Not sure why that is. But if you have a real computer that for some reason has a odd video card that windows doesn't have a driver for and it boots up in 640x480, it will fail there too.

That's the reason I use the net user method. It works no matter what. Granted the oobeinfo method is easier and a little cleaner, but not as reliable.

I figure that's my $.02 or $.03 worth...

[karanmalhotra]

I am looking for some way if i can avoid the screen of adding additional users.

i.e I have created an image and then did sysprep -reseal. By using oobeinfo.ini i could skip couple of screens but the last one...where it ask me write 5 users.

I am not willing to add any extra users...rather i just want skip that screen and want my image to have just one Adminstrative account...(Default One)

[karanmalhotra]

Numinous, on Nov 4 2003, 12:16 PM, said:

$oem$\$$\system32\oobe

Guys!

Is there a way to entirely avoid user creation screen using oobeinfo.ini or any other file?

Attached File(s)

•  whowilluse.JPG (56.81K)
  Number of downloads: 15

[karanmalhotra]

Numinous, on Nov 4 2003, 10:34 AM, said:

just a quick one that works a treat.. an easy way to add 1-6 users

create the file oobeinfo.ini containing something like this

[UserInfo]
Identity000="Numinous"
Identity001="Hedley Smythe"
Identity002="Kool"
Identity003="The Gang"
Identity004="Chaz Manson"
Identity005="Nosmo King"

Identity000 will be the administrator account

place it in the folder $oem$\$$\system32\oobe

check your ref.chm for other options to add to oobeinfo.ini

Hi Numi

Can we specify password for these account instead of leaving them with Blank Password