PryGuy

UPDATED! The new version verifies if the new user account was successfully created, and only in this case it writes the new DefaultUserName value in Registry and disables the Administrator account. So now if the RegisteredOwner value will contain any of the following characters: /\[]";|<>+=,&* it won't make your Windows unusable after the installation, it will create the default (Administrator) account instead of that. Hello all! Well, I haven't seen such a thing on the MSFN Forums so I decided to post my script that allows you to create username automatically based on the registration data (Registered user and Computer name) you provide during setup before the T-12 stage and won't create the Administrator account by default. You also have to put Unattendswitch="Yes" in the WINNT.SIF file, blah,blah,blah... So let me start saying that you also have to add the following line in your CMDLINES.TXT file: "WSCRIPT.EXE ADDUSER.VBS" This line will execute the VBS Script and it's important to write it this way, with the executable program and not only a link to the "ADDUSER.VBS" file! Now create a new file, call it ADDUSER.VBS and put the following text in it and save it into your $OEM$ directory: on error resume next set ws = WScript.CreateObject("WScript.Shell") Owner = ws.RegRead ("HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\RegisteredOwner") Computer = ws.RegRead ("HKLM\SYSTEM\CurrentControlSet\Control\ComputerName\ComputerName\ComputerName") if uCase(Owner) <> uCase(Computer) then ws.Run ("net user "&Chr(34)& Owner &Chr(34)&" /add"),0,1 ws.Run ("net localgroup Administrators "&Chr(34)& Owner &Chr(34)&" /add"),0,1 set CheckUser = GetObject("WinNT://./"&Owner) if err.number = 0 then ws.RegWrite "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultUserName",Owner ws.Run ("net user Administrator /active:no"),0,1 end if end if That's it. The script takes the values from the keys where the Registered Owner and Computer Name information is provided during the setup, verifies if they are not equal, and if they are not - it creates a new user account using the Registered Owner value, puts it to the group Administrators, writes new DefaultUserName Value in Registry and finally disables the Administrator account. Have Fun!

UPDATED! The new version uses VBScript instead of the CMD file and it doesn't show up at all during your first logon into your newly created user account. I have also solved the problem that used to take place on some machines when "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu2\Programs" key was already created before the launch of my previous version of the script. The new version first deletes the MenuOrder key and all the sub keys and then it creates the new key without the values and sets permissions using the REGPERM.EXE tool. Hello all!!! I have found a working solution that allows you to make the default account (and all the other user accounts created in the system later) autoarrange your Start Menu in alphabetical order. It runs once automatically on the first logon using the RunOnce registry key (I presume that you have the "OemPreinstall=Yes" line in your WINNT.SIF file). First of all, you'll need the REGPERM utility. Then, you'll have to put the regperm.exe file in your $OEM$\$$\System32\ folder which is located in in your Windows distribution folder. Next you'll have to create the following file, call it "autoorder.vbs" and also put it in $OEM$\$$\System32\: set ws = WScript.CreateObject("WScript.Shell") ws.Run ("REG DELETE "&Chr(34)&"HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder"&Chr(34)&" /F"),0,1 ws.Run ("REG ADD "&Chr(34)&"HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder"&Chr(34)&" /F"),0,1 ws.Run ("REGPERM.EXE /K "&Chr(34)&"HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder"&Chr(34)&" /A:Everyone:R"),0,1 Now you'll have to add the following line to your CMDLINES.TXT file (thanks for the tip, prathapml): "REG ADD HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce /V AutoOrder /D autoorder.vbs /F" (Don't forget to insert the line [COMMANDS] above the line if you're creating a new file!) Now make your ISO, burn it and you're done!

Please try to understand me, I know it HAS TO WORK, but it doesn't! I have installed the latest version of nLite, and inspected the two versions of the NLITE.IN_ (one with the No Sounds tweak on and another one without it) as MCT suggested. The difference is in one line, it writes the registry value to the key in the [HKEY_CURRENT_USER\AppEvents\Schemes] section. It sets the default value to ".None". I really have this thing later in the [HKEY__USERS\.DEFAULT\AppEvents\Schemes] but my default user account (as well as the other ones created after the installation) have the default settings with the sounds on and the default value in the [HKEY_CURRENT_USER\AppEvents\Schemes] section set to ".Current". I really don't know how to override this problem. I haven't tried to install the modified nLite installation, probably it modifies something else and there's no such provlem with it, but I'm still not sure it is a registry issue. Again, what do I want to see, I want to leave all the sounds and themes, but just choose the No Sounds theme by default. Astalavista, I'm really sorry I made you feel angry, but there's a problem I still can't understand.

Still I can't dig what do you mean... this? or this? But that's the same... One has to apply it everytime you create a new account... Or I just couldn't find the right tweaks...

And where's it? You mean the settings (the only settings I know) below applied on the T-12 stage will work?

That's okay, Astalavista... I'm so happy that there are so many smart guys all over the world. This is the No Sounds problem that worries me a lot at this time! Thanks everybody!

Hello all! Can ANYONE ON EARTH tell me of the successfull unattended Windows installation with the No Sounds Sound Scheme applied by default. All the newly created users should get the No Sounds scheme after the account creation. I'm so very angry I can't understand how it applies the sounds I'm sure it is applied by the Luna.theme file or the Luna visual style. And registry just stores the values from these files (as in case with the screensaver). I tried to edit the Luna.theme file but there's no luck. I can't understand how it all works. Any ideas?

I HAVE FOUND HOW TO TURN OFF THE NASTY "SLIDE TASKBAR BUTTONS" OPTION DURING THE SETUP BY DEFAULT"!!! Yes, "TaskbarAnimations"=dword:00000000 really turns off the Taskbar Animation, but it doesn't work if you put it in the REG file and apply it using the CMDLINES.TXT or the [GuiRunOnce] section in the WINNT.SIF file. I think that's because of the fact that Windows kinda tests your system to see if it's possible to handle all the silly eye candies everytime you create a new user account. But I have discovered that one can override it putting the following lines in your REG file and importing it using the CMDLINES.TXT method: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VisualEffects\TaskbarAnimations] "DefaultValue"=dword:00000000 "DefaultByAlphaTest"=dword:00000000 Already tested it, works fine!

Hello all! Well, I have a problem disabling the nasty taskbar animations durin the Windows Unattended Installation. I apply the following registry setting during the installation process using CMDLINES.TXT: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "TaskbarAnimations"=dword:00000000 Windows installs, boots up, and first thing I see is the bloody taskbar animations! I have an idea that it just overwrites my setting with it's own settings during the account creation process. I have tried applying it with the [GuiRunOnce] section in the WINNT.SIF file, but it doesn't work as well... I have the same problems disabling screensaver and applying No Sounds scheme.