Username and computer name mix-up

[Sp0iLedBrAt]

This is to confirm something I noticed, and want to check if it is true.

I recently did three nLite sessions; in the first two, I used the same name for computer and username (e.g. Jake) and in both sessions the username was made with a limited account (although I made to be with Administrator account).

After changing the computer name (Jake1) in the third session, everything was OK again.

Has this been reported before?

Thanks in advance

[Kelsenellenelvian]

Yes I have read of this before...

[Guest]

I've been using username and computer name as the same without issues. Unless you are talking about the administrator's accounts name, not username.

[Ponch]

... numerous times, I confirm.

[Sp0iLedBrAt]

I've been using username and computer name as the same without issues. Unless you are talking about the administrator's accounts name, not username.

Sorry if I wasn't clear: I never touch the built-in Administrator account, it's good the way it is. When I used "Administrator", I meant the privileges of the user.

Thank you for your prompt replies, and -X-, we should definitely compare our Last Sessions (or Winnt.sif) to see how you do it.

[Guest]

winnt.sif

[UserData]
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
ComputerName=X
FullName="X"
OrgName="X"

Last Session_u.ini

;
; nLite private info
; (don't post it on the net, it's not important for debugging)

[Personal]
TimeZone = (GMT-05:00) Eastern Time (US & Canada)
CDKey = "XXXXXXXXXXXXXXXXXXXXXXXXX"
ComputerName = X
Organization = X
Language = English (United States)
Locale = English (United States)
Keyboard = US
DomainAdmin = 
DomainPass = 
Expirepassword = 0
JoinDomain = 
JoinWorkgroup = Workgroup
Owner = X

Last Session.ini

[Unattended]
UnattendMode = 1
ComputerType = Automatic
HibernationNo
AutoLogon = Adminstrator

or

[Unattended]
UnattendMode = 1
ComputerType = Automatic
HibernationNo
AutoLogon = Renamed

I've been using same names for PC and user since 1999 (or 1995 if 9x was the same. too long ago to remember) and have never encountered a problem even when I started using nLited installs(maybe 2004?).

Edit: It's different but there was some mention of WindowsXP-WindowsMedia-KB973540 causing problem with accounts when used with nlite here. It's towards the bottom of the thread.

Edited September 7, 2009 by -X-

[Sp0iLedBrAt]

hm... the only difference I see is that you've set Administrator to Auto logon. I don't use any auto logon, although I admit it's useful if you want to make sure RunOnce will execute.

Edit: I don't use WindowsXP-WindowsMedia-KB973540.exe

Edited September 7, 2009 by Sp0iLedBrAt

[Guest]

I'm still not clear on something. I'm using the built in admin account. Are you creating a new admin account? Maybe that's why I don't see it.

[Sp0iLedBrAt]

I'm still not clear on something. I'm using the built in admin account. Are you creating a new admin account? Maybe that's why I don't see it.

Yes, I am. And instead of admin, it has limited account privileges.

[Guest]

Sorry but now that you say that, I'm still not clear on something. I plan on doing a test run as I changed my unattended yesterday and want to replicate the issue. When you create the new admin account are you naming it the same as the PC or just the 'full name' on the owner and network id tab or both? In other words, paste (they don't allow hotlinking) these into your browser so you know what I'm taking about .

http://windowsx.50webs.com/nliteimages/unattendedusers.png

http://windowsx.50webs.com/nliteimages/unattendedownerandnetworkid.png

[Sp0iLedBrAt]

I create a new account with admin privileges (e.g. JOHN) and I give the same computer name (JOHN again). After the completion of the installation, the user account JOHN has limited, not admin privileges. Furthermore, if I want RunOnce to run, I have to login into the Administrator (built-in) account (which is shown on the Welcome screen). The full name of the user (owner) is always different as it also contains a last name.

None of this happens if I just name the computer JOHN1.

BTW, there is a new hotfix from MS released for XP x86, WindowsXP-KB956844-x86-ENU. When will you be able to comment on your website whether it replaces any other older hotfix?

Thanks

Edited September 8, 2009 by Sp0iLedBrAt

[Guest]

Yeah today is patch Tuesday. Waiting on the bulletins.

OK, I understand fully now. My accounts name is Administrator or I've taken to renaming it lately, the stuff in the owner and network id tab is what I named the same as the PC. I'll try to confirm what you see later on.

[Guest]

Here's the changes for Sept.

Add WindowsXP-KB956844-x86-ENU.exe

Add WindowsXP-WindowsMedia-KB968816-x86-ENU.exe

If IE6 add WindowsXP-KB971961-JS57-x86-ENU.exe. If you slipstream IE8 add IE8-WindowsXP-KB971961-x86-ENU.exe instead.

Remove WindowsXP-WindowsMedia-KB952069-v2-x86-ENU.exe as it was replaced by WindowsXP-WindowsMedia-KB968816-x86-ENU.exe

Edited September 9, 2009 by -X-

[GrofLuigi]

Remove WindowsXP-WindowsMedia-KB952069-v2-x86-ENU.exe as it was replaced by WindowsXP-WindowsMedia-KB968816-x86-ENU.exe

I think 952069-v2 shouldn't be removed, it also contains updated Logagent.EXE and Wmnetmgr.DLL.

Yes, KB968816 contains (only the) newer Wmvcore.DLL.

GL

[Guest]

Strange. I'm just going by the bulletin: MS09-047 Bulletins Replaced by this Update: MS08-076

I'll wait a few days and see if they issue a correction and I'm about to run a VM test so I'll see if WU complains about 952069.