cancerface

Oups! Yes, that behaviour should not be there... In fact the same happened if only the Security Section is enabled. Tracked the error down and fixed it!Updated to v1.6: v.1.6 Changelog Rewrote the function that checks for admin privileges Fixed an error that would hide fields although the Parse[]Section flag was on Added support for Turkish (thanks KenanBalamir!) & Greek languages (Interface + message boxes) Updated first post and uploaded the new version Enjoy CF

Maybe ... (I am not using AutoLogon and AutoLogonCount in my winnt.sif and I don't get this forced autologon that you described)As for the password not being visible in the registry, this is normal if you used AutoLogon=1. Actually the password is encrypted and stored in the registry, as explained here CF

@vertigo The key you are looking for is REGEDIT4 [HKEY_LOCAL_MACHINE\\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "ForceAutoLogon"="x"with x=1 to enable it and x=0 to disable it I tested this in various different ways but couldn't get my program to write that value if the relevant box is not checked ... Are you sure the registry entry is created by my program? Could you use something like regshot to see if indeed that's the case? @mazin Yeah, I missed that. Fixed! Thanks for the feedback guys, appreciated as always CF

Could you try the attached file and see if you are getting the same error? I rewrote the function that checks for admin privileges just in case it is affected by your localization ... CF

@mazin If there is another admin account you can delete the original Administrator (renamed), but not on T12 (I am not sure if Txx runs in the context of the administrator or the system account) ... Interesting that you can't delete the renamed guest (I can't either) @vertigo I am sure that the winnt.sif entries have nothing to do with that error, I have used the same. I am also pretty sure that I cannot reproduce that error, unless I run the program as a domain admin without adding myself to the local admin group. In other words I have no clue why you are getting this How are you getting an error for CMDOW without placing CMDOW in your batch file? Are you sure you are running v.1.5 of the program, as the screenshot shows? There was a problem in previous versions which resulted in that error, but it has been fixed ... CF

My bad mazin, although I though seeing somewhere a discussion about deleting the built-in accounts, it seems that this is not possible. There was a discussion about renaming those accounts, and this feature was added to the program. I am not aware of any tool that deletes those account CF

@mazin There is no need to patch the registry for autologon, the program takes care of that. After storing the LSA secret the following registry entries are created: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "DefaultUserName" "${USERNAME}" HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "AltDefaultUserName" "${USERNAME}" HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon "AutoAdminLogon" "1"where ${USERNAME} is the name of the account created by the tool. As for deleting those accounts, I can confirm that both the SUPPORT_388945a0 and HelpAssistant accounts can be deleted at T12 (tested on a virtual PC). I am installing .NET after the first reboot so I am not sure for the aspnet account, however I do not see a reason why you can't delete it at T12. I have not tested deleting the renamed administrator/guest accounts but I think this has been discussed before and is feasible. CF

I am using direct API calls to set the new computer name and upon reboot the correct new name is displayed. There is also a freeware command line tool that does the same called compname.exe. Looking at your HTA script, you change the computer name in the registry only. I am under the impression that this is not the way to change the NetBios name and that's why you end up with the old name. CF

Hi mandrake10, I wrote a tool that can be used to change the computer name and registered owner/organization using a GUI. In addition it can take values from an INI file where you can specify different MACs for different PCs and depending on the MAC address detected upon execution, the appropriate values will be automatically picked from the INI file. It can be found in this thread CF

Excellent idea RogueSpear, will work on that.Finally I got some time to play around again with this project Many people requested that this program gets an international face-lift. I would like to avoid having multiple lang files and would prefer to have a single EXE that contains all the lang strings. My test trials with lang DLL files were not very successful and the only thing that seems to work quite nicely is embedding the different lang strings in the program itself. The downside of that is that the end user can't really change any of those strings, but then again this is what this thread is about, sharing and improving Since I am not able to translate the messages that pop-up in every language, I am attaching here the English strings used by the tool so that any interested parties can translate in their own language and re-attach the new files. The attached 7z archive contains two files, an INI with the interface strings and a TXT with the pop-up messages. Try to keep the messages as concise as possible, especially the ones in the INI file as their size will affect the layout of the GUI. It is important that you save the files as ANSI rather than Unicode, since the NSIS compiler used to make the program will not be able to read the translated characters. It would also be very helpful if people could provide the ANSI page code of the file with their strings. You can find a list of those codes here As soon as there are some extra languages to support I will release a new version that will also support the option to reboot as suggested by zbeta As always, your comments/suggestions are most welcome... CF English_Strings.7z

@zbeta This can be easily implemented, added on my list of things to doNote however that this may be tricky if you call the exe from Txx, as it will force a reboot once it finishes, although other things may be running ... You can use ResourceHacker to change any of the three icons, however you will break the CRC check so you will have to invoke the program usingCreateUser.exe /NCRCin order to be able to run it. The icons by the way are not compressed in the header. CF

@KenanBalamir I have been thinking about localizing the dialogs and adding new languages to the interface, something that Joc brought up in the past. The only reason why this hasn't been implemented yet is that the interface metrics would change from language to language, but I think I found a way around that now. I would like to have the different strings compiled into the main EXE as to avoid relying on multiple language files. I will post a file with all the text strings that are used and you can translate them in your language then post the translated file on this thread.@ZileXa Yes it is, although IMHO it defeats the whole purpose of this tool ... It should provide a way to access these settings at Txx/RunOnce/etc so that you have the option to interact with the GUI in case you want to change something.(added to the list of things to do) I am not sure why you think this is bad. In order to run the tool one should have admin privileges which means that he/she can access one way or another those settings. Not in the near future.However using multiple INI files you can run the EXE several times and achieve the desired effect (although I would also stick with Wihu for creating multiple accounts, or I would use a batch file). @ideas & @mgadallah I am glad you like it CF

Hi Pete_, I wrote a tool that handles user creation, provides a GUI and should be lang independant. I would be interested to know if it works in your case, in a Finnish OS. The relevant thread can be found here CF

@AJacobson How do you start the installation? From within PE? This message should appear only if the setup process has not generated a PNF file (%SysteRoot%\System32\$$WINNT$$.PNF) or if the account starting the program doesn't have admin rights. CF PS If you copied/pasted the batch file from the first post, you may want to place cmdow.exe in some path where windows can find it

@Yurek3 I can't reproduce the error that you are getting... You are running the tool at RunOnceEx and my assumption is that you are logged with the default 'administrator' account using the autologon from winnt.sif. I did the same and I don't get anything wrong, both on a virtual and a real PC. The above message by the way pops up only if the registry value is not 5.x. My only guess is that you can't read the registry, which doesn't make sense especially if you are logged with an unrestricted account. In general if you are able to run my app on the desktop there is no reason for it not to run during Txx or RunOnceEx. I'll dust it again however to see if there are any errors that I have missed... I am also releasing a new version with some minor improvements/fixes/additions Changelog v.1.5 Removed the ComputerInfoSections from the [ComputerInfo] section. Detection of the number of [ComputerInfo_n] sections is automatic now Added colors to the timeout bar at 75,50 and 25% of its length Added new options for audible warning during or at the end of the timeout ([interface] section) Updated first post and uploaded the new version CF

Sorry, maybe it wasn't clear ... I am looking for this: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "CurrentVersion"= CF

What is the value of CurrentVersion that you have in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion ? CF

@Yurek3 I am using an image of a virtual PC (XP Pro) which runs a batch file that pauses at cmdlines, so it's easy to copy over new versions and try them. The last version I uploaded worked fine in the above image and it didn't crash in several PCs when invoked from random folders... Thanks for testing it, and please post your findings! @All Thanks for trying it out and for providing feedback! CF

Good news It seems that it is stable again, so I uploaded v1.4 and updated the first post. Changelog v.1.4 Rewrote the MAC address detection function Fixed some GUI dependencies for enabling/disabling sections Rewrote the User enumeration function (caused errors in some systems) Corrected the Rename Administrator function (it now is disabled by default if the user running the tool is called 'Administrator') Enjoy CF

I am still not sure what the problem was. I can also confirm that there were random errors upon execution: the program would execute fine for a number of times then it would give an application error. Or it would not execute at all in certain cases. I changed as much as I could and I think that I found the error, if it was indeed an error. Changed the user enumeration function and at least now I am not getting any errors. I would however appreciate it if the those of you who had a problem in the first place, could download and test this version, and report back any problems. If everything is OK then I will release it also on the first page of this thread. Here it is: CF [Edit] Removed file - check first post

I am baffled then. I'll try to work it out ... I appreciate the input CF

That's bad news for me then since I am not getting this error! Do you get anything logged by DrWatson? CF PS Assuming that the handle calls cause the error, I am attaching another version that uses a different approach to call the main EXE. Could you test this and see if you are still getting the memory overflow? What OS are you running? Is the program in a looong path *with* spaces? Do you have AntiVirus soft. running? Not sure where to start [Edit] Removed file - check first post

@benners Right ... The checkbox issue was just a GUI glitch and was easy to fix. Fixed the other two aesthetic details and re-uploaded the same version (check the first page of this post). Since there are no functional changes I am not altering the version number @Yurek3 Glad you like it CF

I finished adding the extra features requested by benners as well as redesigning the GUI to fit into 640x480 resolutions after Yurek3's request. I really liked the idea of a progress bar and have been working for a while to get it operational. It is working now and I rewrote the timeout function so that any changes in the GUI will cancel the countdown. Updated to v1.3: v.1.3 Changelog Added new GUI options for section enable/disable Added progress bar for timeout Fixed (finally) the timeout bug: Timeout is cancelled if anything changes on the page Added new security section parameter: Forced Logon that enables autologon upon user logoff Added new security section parameter: Disable Administrator (disables the original/renamed administrator account) Redesigned the GUI so that it fits in 640x480 resolutions Updated first post and uploaded the new version Enjoy CF

After playing around with the layout a bit I ended up with a 624x430 window. That's as good as it gets from my side without any compromises ... It looks like this: Are these dimensions OK for your setup? If yes I can release this new version as soon as I get home CF