Jump to content

cancerface

Member
  • Posts

    135
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Posts posted by cancerface

  1. You can try compname.exe from here.

    I have also created a small program with similar functionality - you can find it in this thread, however it will not (yet) join the computer to a domain, but it will provide a GUI which can be useful in some cases (or it can run on full unattended mode based on an INI file that you generate).

    Hope this helps,

    CF

  2. @midiboy

    I have not used Vista nor have I access to it so I cannot really tell you how the program will behave there ...

    Judging from the amount of security issues that I see on the NSIS development forum I would say that it would not work at its current status, but then again I have no way of checking this.

    Folder redirection is a matter of changing registry entries which is easy to implement and I had thought about it in the past, however everything breaks when the order of mounted drives changes and as such I have not added that option. For example, in my setup, at T13/12 there is a certain layout for my HDD which changes at GUIRunOnce, but my user is created at T12 so any folders that would be associated with the user's profile are bogus after a few reboots based on the new layout (assuming that the folders are not on 'C')

    CF

  3. @Ulrich

    Yes that doesn't sound right ...

    After a close look it appears that AutoLogon would be set to 'on' for strange reasons. This value is tied to ForcedLogon as well as the Parse directives.

    Long story short, it would not behave.

    I am releasing yet another version of this program:

    v.1.8.4

    • Fixed AutoLogon (combination of parameters would result in AutoLogon being 'on' although it would be explicitly set to 'off')

    Updated first post to v.1.8.4

    Enjoy!

    CF

  4. This is embarrassing ... Lesson learned, always test a lot before releasing something ...

    It turns out that if I use a timeout of 30sec, as in Ulrih's case, the timeout fails. However if I use 10 or 20 or 60 it works. The real problem was hidden away in the code that calculates the position of the count-down bar which results after a few simple math operations to a negative value in some cases. Unfortunately for me the condition to start execution after the countdown is over expects to have a value of zero ...

    Long story short, I think I fixed it so I am updating the first post yet again!

    Thanks Ulrih for trying out several times the different versions! Hopefully this one works flawlessly for you as well :)

    Updated first post to v.1.8.3

    v.1.8.3

    • Fixed (again!) timeout code

    Enjoy!

    CF

  5. @Ulrich

    Excuse my ignorance but after watching your video I cannot quite understand why you are creating a user called Ulrich giving him admin privileges (in the User Details frame), then you are renaming the Administrator account (whatever that name is in Russian) to Ulrich in the Security Options frame ... Obviously this will not work since a user called 'Ulrich' already exists at that point, and happens to belong to the Administrators group ... You are also renaming the Guest account from whatever name it has in Russian, to ... 'Guest' (!) Not much use is it?

    Anyway I hope this versions works for you and you don't get the timeout problem again

    CF

  6. A bug indeed.

    Strangely enough I missed it because if I set Confirm=1 at the [interface] section the timeout occurs and the program is executed. However with your settings it does not execute!

    Updated first post with v1.8.2 of the program.

    v1.8.2

    • Fixed timeout when Confirm was set to 0
    • Rewrote the user/group enumeration function
    • Rewrote the Administrator detection function

    CF

  7. The timeout works as long as you set EnableTimeOut=1 in the [interface] section and you do not make any changes to the window while the program is running. This was implemented so that the program would run automatically and at the same time give a GUI for the user to change the created user/computer etc details if need be. In my scenario the program runs and sometimes I need to change some option so by clicking anywhere in the GUI the countdown stops.

    If you want to have a countdown you should make sure everything is in place in the INI file before calling the program and you should not disturb the GUI while the program is running.

    CF

  8. Has tested by the virtual machine - all works perfectly.

    With one condition - in the distribution kit it is necessary to integrate the drivers from Wim Leers (BashratTheSneaky) Chipset and LAN

    Huh? You lost me there ...

    Greetings cancerface.

    Thanks for the made changes, the program it became ideal, but through my fault in the interface discrepancy has crept in.

    Here [Field 41]

    I used unfairly long expression, therefore it was not located completely. I hasten to rectify the error.

    Ulrih

    No worries.

    Updated the first post to v.1.8.1 changing the Russian GUI label for Registered Organization so that it fits in the interface

    CF

  9. Yet another update, this time with a major change on the way that values are parsed from the INI file.

    Ulrih suggested yesterday to somehow tie the MAC address detection to specific User and Security info besides the Computer name/workgroup etc info. It turned out to be really easy to implement just by adding one flag to the [interface] section that allows for extra flags to be parsed if a matching MAC address is found in a [ComputerInfo_n] section.

    In the new program version if the MACAddressOveridesSections flag is active in the [interface] section then the following values can also be parsed from the [ComputerInfo_n] section that contains a matching MAC address:

    ParseSecuritySection

    FirstName

    LastName

    Description

    UserName

    Password

    UnlimitedPass

    AutoLogon

    Admin

    FakeAdmin

    FakeGuest

    RenameAdmin

    RenameGuest

    DisableAdmin

    ForcedLogon

    NewAdminName

    NewGuestName

    HideNewAdmin

    These values will now override the ones in [userInfo] and [securityInfo] sections!

    If however there is no match of the MAC values from each section to the MAC address of an ethernet controller on the target PC then the values from the initial [ComputerInfo] [userInfo] and [securityInfo] section will be used instead.

    This way one can have different users and security options applied to different machines :thumbup

    Updated first post to v.1.8

    Enjoy!

    CF

  10. @iperoni

    Glad you like it :hello:

    Check this part of the thread and download the file with the English strings. If you post here a file with the spanish translation (in ANSI) I can implement it into the main executable and change the dimensions of the interface to accommodate the Spanish button labels.

    You need to edit both the InterfaceEN.ini and LangStringsEN.txt files. The $xxxxx$ entries are variables so you do not need to edit them.

    The program should not fail to change the default Administrator account in any language as it looks for accounts by their SID which is language independent. However if you are logged using the Administrator account and then you try to change the name of that account, the process will fail ...

    CF

  11. @supergudrun

    Not sure where you fail to login with the generated user.

    Just deployed a freshly integrated SP3 disc and called the create user tool from T12 as always. The user was successfully created and autologin worked as expected. I did not use a blank password. Same result if I use the PasswordCheck flag in order to generate a user with a blank password...

    Have you ever used this tool with an SP2 install without any problems? If not, I suggest having a look at the INI file, maybe you missed something there?

    CF

  12. I've looked for that netdom.exe but it seems that the name have to be hard coded.
    ?

    I am not in a AD environment so I cannot really test this ... But my understanding after reading the netdom.exe discription is that it is able to join your machine to a domain if you supply it with the machine's name and have enough privileges to do so. As for the name, this is something that you can do using the tool of this thread. You can even add a list of different names based on the MAC address of each PC you would like to name and the tool will pick the appropriate name each time. This is supported right now. There is no support for joining an AD tree as this requires a lot more checking and I have not written the code yet + it is difficult to do so when you cannot test it ...

    My idea was that you can get a GUI for the name and a temporary workgroup, then after rebooting run netdom.exe to join the domain.

    So for example in the GUI part you get to specify the name, then after rebooting get the name (by using wmic or any other way you know off), place it in an environmental variable then pass it to netdom.exe with your domain name.

    I am sorry, but I do not know of any tool that will do what you are after with a GUI ...

    CF

  13. @Kingskawn

    I am not aware of any tools that will give a GUI for what you are after, however, you could use something like netdom.exe from the 2000 support tools to join the domain.

    What you may want to try is running the user creation tool of this thread (from cmdlines) with only ParseComputerSection set to 1 (so that no UserInfo and Security info will be active/parsed), get a GUI for generating the computer account (in a workgroup) then after rebooting you can call netdom.exe in order to join the domain:

    netdom join COMPUTERNAME /domain:DOMAIN /userd:DOMAIN\USERID /passwordd:PASSWORD

    with USERID and PASSWORD the username and password of a domain account with privileges to add computers to the domain. The downside of this is that you need to supply the username and password in a cmd script in order to join the domain.

    I played around a bit with advapi32 and there are functions that will join a computer to the domain, however, modifying the user creation GUI to accommodate that functionality would be rather involved ...

    [placed on my list of things to do]

    :rolleyes:

    CF

  14. After a loooong delay I managed to get some time and updated this little tool with the latest lang strings ...

    Updated to v1.7:

    v.1.7 Changelog

    • Added French GUI support (thanks kSaMi!)
    • Added PasswordCheck switch to disable password checking and force a blank password

    As always comments/suggestions are welcome

    Updated first post and uploaded the new version

    Enjoy :)

    CF

  15. @DJPro

    The French strings are not yet implemented. Once I include the strings in the main EXE, it will automatically detect your language and will swap to French if necessary

    The password by design is checked regardless of the CheckValues variable. It cannot be empty.

    If however you feel that this may be needed, I can add another switch so that password checking can be omitted (which is a BAD idea, especially if the two passwords do not match) ...

    CF

  16. :blushing:

    Not discontinued, nor abandoned, I am just up to my neck with things to do.

    I think I will have some time during the weekend to update this, adding the French lang support etc.

    @KenanBalamir

    I think that the cancel button label is embedded in my nsis compiler like that, I will look into it and post a request for a fix in the NSIS forums.

    @colc

    I will play around with this and see if it is a bug indeed

    @Yurek3

    Can you provide any info on the reason why these versions do not work for you? Maybe I could upload a debug version for you and we could track the problem down ...

    @vertigo

    Hmmm... I have been running from cmdlines without any problems and I have tested from svcpack without problems as well. Maybe it is indeed something else in your setup that overwrites the autologon entry?

    CF

  17. Well, unless you specified username=Administrator in the INI file or set the name to administrator in the GUI I do not see how the program can write the wrong value in the registry...

    Are you sure that commenting the winnt.sif values out is the same as deleting them? I do not know if this is the case to be honest. Another way to test this is to use EncryptedAdminPassword = Yes

    which disables autologon, if I am not mistaken ...

    All I can tell you is that the program gets a value from the INI file, places it in the GUI, then takes the same value (username) from the GUI and places it in the registry. I cannot see how the wrong value can make it to the registry :no:

    CF

×
×
  • Create New...