strange user logon behavior

[scorpy]

I have my setup create one user with the name "Hunter". There is no password by default, and it auto-logs in twice. The computer name is CustomPC. Now, my problem is that a few OEM folders install into Hunter/Desktop, but when it logs me in for the first time, I am logged in as "Hunter.CustomPC".

Here is the real bizarre part. My start menu name says Hunter, my user account in CP says Hunter, but my docs and settings folder says Hunter.CustomPC. There is a Hunter folder, but thats not what is used. Strange! Below are the relevant files.

winnt.sif

[UserData]
    FullName="CustomPC"
    OrgName="home"
    ComputerName=Custompc

useraccounts.cmd

net user Hunter /add
net localgroup Administrators Hunter /add
net accounts /maxpwage:unlimited
REGEDIT /S autologon.reg
EXIT

autologon.reg

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="Hunter"
"DefaultPassword"=""
"AutoAdminLogon"="2"

[MCT]

hi this is caused by having that user already exist ...

ive had this problem & it was a bad reg tweak that caused my problem.. look over your tweaks.. compare them with them on the board & http://winguides.com

[scorpy]

I think I may have figured out why it does this. In my OEM folder, I have it install 2 files to desktop. So it is laid out $OEM$ - $Docs - Hunter - Desktop. So when Windows goes to create a user, it already has a Hunter user. Now, is there a way to copy these over regardless of user name, so I don't have to specify the name in the OEM folder ? I do have files that also will go in UserProfile - Application Data - etc, so a self extracting exe wouldnt work.

[Jito463]

I ran into a similar issue when copying some batch files to the All Users desktop. Here's what I did. I copied them first to a directory called OEM on the root ( C:\OEM ). Then, in my GuiRunOnce in winnt.sif, I call a batch file - that was previously copied to the System32 dir - that copies my files to the All Users desktop:

[GuiRunOnce]

    Command0="C:\Windows\System32\OEMPrep.bat"

COPY C:\OEM\bit.bat "C:\Documents And Settings\All Users\Desktop"

COPY C:\OEM\Sysprep.bat "C:\Documents And Settings\All Users\Desktop"

Hope this helps.

[sleepnmojo]

Well I'm glad to see you aren't using variables Jito463 . I pretty much do the same thing. I compress the contents of each of the folders, and expand them using the provided variables, or ones I make.

[MHz]

I think I may have figured out why it does this. In my OEM folder, I have it install 2 files to desktop. So it is laid out $OEM$ - $Docs - Hunter - Desktop. So when Windows goes to create a user, it already has a Hunter user. Now, is there a way to copy these over regardless of user name, so I don't have to specify the name in the OEM folder ? I do have files that also will go in UserProfile - Application Data - etc, so a self extracting exe wouldnt work.

You can use $OEM$\$DOCS\Default User\ ? or $OEM$\$DOCS\All Users\ ?

Can insert your desktop items, templates, application data, etc. via this method.

[sleepnmojo]

You can use $OEM$\$DOCS\Default User\ ? or $OEM$\$DOCS\All Users\ ?

Can insert your desktop items, templates, application data, etc. via this method.

This wouldn't solve his problem. It would still exist if he had the All Users folder or Default User profile. It would append Machine name to the end. The only way I have found around this is, create an archive, and extract it.

Somebody wrote a batch file to automate all this. You have to do a search, but I believe it worked.

[scorpy]

Yea, I did end up making one large exe. It saved the full folder info, so I just pointed it to C:\ and let it auto-extract.

[MHz]

I think I may have figured out why it does this. In my OEM folder, I have it install 2 files to desktop. So it is laid out $OEM$ - $Docs - Hunter - Desktop. So when Windows goes to create a user, it already has a Hunter user. Now, is there a way to copy these over regardless of user name, so I don't have to specify the name in the OEM folder ? I do have files that also will go in UserProfile - Application Data - etc, so a self extracting exe wouldnt work.

$OEM$ - $Docs - Hunter - Desktop

@sleepnmojo

This created the problem. Creating a userprofile with $oem$, during text setup, then creating the same profile at the end of setup. The system saw Hunter at the end of setup , it chooses not to overwrite, so Hunter.CustomPC is created.

Please get your information correct so others can learn from it.

[sleepnmojo]

$OEM$ - $Docs - Hunter - Desktop

@sleepnmojo

This created the problem. Creating a userprofile with $oem$, during text setup, then creating the same profile at the end of setup. The system saw Hunter at the end of setup , it chooses not to overwrite, so Hunter.CustomPC is created.

Please get your information correct so others can learn from it.

My information is correct, and is the reason why I use the archives. Your method works fine, except it will put it in the Hunter directory, but when the os is looking for a file, it will be looking in the Hunter.CustomPC directory. Same with All Users, and Default User. My method works, yours doesn't, so get your facts straight.

[MHz]

I think I may have figured out why it does this. In my OEM folder, I have it install 2 files to desktop. So it is laid out $OEM$ - $Docs - Hunter - Desktop. So when Windows goes to create a user, it already has a Hunter user. Now, is there a way to copy these over regardless of user name, so I don't have to specify the name in the OEM folder ? I do have files that also will go in UserProfile - Application Data - etc, so a self extracting exe wouldnt work.

@ sleepnmojo

Hunter.CustomPC ? This shouldn't exist. Have you not figured that out yet, and what causes this?

Stick with your archives and batch files, if you believe that it is good option.

I'm sticking with the $oem$ method, proven to work, time and time again. Even though you say that it does not???

[Jito463]

MHz: Scorpy already explained above what caused his problem. He created a $OEM$\$DOCS\Hunter\Desktop directory that - during the file copy phase - created the Hunter profile under Documents And Settings. This had the unfortunate side effect that when he went to create the actual Hunter account, the directory already existed so it appended the machine name to the end (Hunter.CustomPC). I've experienced this myself and know all about it. Now, I can't say this will happen using Default User or All Users in the $OEM$\$DOCS setup, but I do know for a fact it happens when you send to a non-default account using that method.

[MHz]

@ Jito463

You do understand the reason. Using Hunter in $docs was a mistake.

Using all users or default user in $docs does not cause any issues.

non-default account? whatever this is , should not be used.

I am glad that you understand.

btw.

I use $docs\all users and $docs\default user for templates, start menu items etc.

I also use an archive for my themes from runonceex. (spacesaver, instead of using $oem$).

This method does not create a name.machine name nor have the os looking into name.machine name? Shoot me if it ever does.

[sleepnmojo]

@ sleepnmojo

Hunter.CustomPC ? This shouldn't exist. Have you not figured that out yet, and what causes this?

Stick with your archives and batch files, if you believe that it is good option.

I'm sticking with the $oem$ method, proven to work, time and time again. Even though you say that it does not???

Yes, I know why the problem occurs. It occurs when the directory is already in the Documents and settings folder. This can happen if your Doc & settings folder is on a different drive, which won't get erased in a format for a clean install. So yes, I do know what I am talking about. I have proven your method not to work, as well as others on this board. Do a search, or read back from before you came, and you will see. This is why I go with my archives.

[Jito463]

@ Jito463

You do understand the reason. Using Hunter in $docs was a mistake.

Using all users or default user in $docs does not cause any issues.

non-default account? whatever this is , should not be used.

I am glad that you understand.

btw.

I use $docs\all users and $docs\default user for templates, start menu items etc.

I also use an archive for my themes from runonceex. (spacesaver, instead of using $oem$).

This method does not create a name.machine name nor have the os looking into name.machine name? Shoot me if it ever does.

What I was trying to get across is that it sounded like you didn't understand. And by "non-default account", I was referring to any account not created by Windows during setup (e.g. any user account besides All Users and Default User).