my2001

First of all: Benjamin should verify what I'm telling you now. Kay, let's start ... 1.) No, right now it isn't possible to change user settings (folders, etc.) for already existing users, i.e. users accounts already present before WIHU was started. And Benjamin isn't going to add add this feature before WIHU 2.1 stable. Why? There have been many problems doing that. Btw: it isn't recommended to use accounts with admins privs for daily work! ;-) 2.) Yes, I think this is a good proposal, but should be implemented after release of WIHU 2.1 stable. 3.1.) In my eyes current syntax is very nice. Isn't it more logical to have rename in one single line instead of two seperated lines? Because rename always consists of two parts. *hehe* 3.2.) Random password? I'm not sure if this is a good idea. I've _never_ heard of any bug/virus/etc. that tries to enable inactivte accounts. And without admin privileges local users won't be able to do it either. So maybe wanna explain why random passwords for those accounts? Windows isn't that insecure. *hehe*

Okay, I'll try to keep my answer short No, just keep it a little bit longer. WIHU is controlled by a an INI-file. So you have to adapt your entries of your previous configuration file (here: runonceex.cmd) first to the WIHU configuration file because the syntax differs. Afterwards you can/should delete your runonceex.cmd. Almost the same here: WIHU can handle these tasks, too, with help of its configuration file. So after you configured WIHU to do what you want with your user accounts you can/should delete useraccount.cmd and autologon.reg. Well, I suppose you're not German because there's a manual approaching. Maybe a sample INI file could help you understanding what to do. Just download WIHU, unzip the archive and look at the INI file included. Maybe this will answer some of your questions?!?

Yes, but that's no solution. We really need one who either translate this, or creates an own manual ... hehe may be I got the time to do this, but my english knowledge isn't enough to write a good manual. Besides wo fixes WIHU bugs then? Benjamin Yeah, of course, you're right! I didn't want to say that learning German is a solution here. I was just kidding. If there's someone who wants to translate my manual, sure, why not?! But I doubt we'll find somebody coz it's a looooong manual. *hehe* I for my own spent more than enough time on that, now it should be somebody's else turn. I don't matter who but I think Benjamin is pretty well busy with WIHU itself. @Alanoll Well, in case you're interested in German just look here (but only partly in English). Btw tenses in English are much more complex then in German. Isn't that nice?

Honestly, I believe German isn't a difficult language, grammar is more or less easy.

Hi! Enventually WIHU has got an official documentation, verified by its developer Benjamin! Stats about the manual: language: German file format: PDF (you'll need at least Acrobat Reader v6) reflects WIHU version: 2.1.2.0 manual version: 1.0827.0 file size: 990 kB author: Andreas H. aka my2001 link: deutsche Bedienungsanleitung Notes: I know it isn't perfect, but I tried to do my best, remember it was voluntary. *g* It should at least give you a review of the available command line parameters, configuration file directives and in addition some useful information about other things which might be interesting for users of WIHU. If there's anybody who likes to translate it, don't hesitate. Just drop me an email in advance, please. Excerpt from the contents: 1. Programmbeschreibung 2. Systemanforderungen & Installation 3. Programmablauf 4. Konfiguration 4.1. Befehlszeilenparameter 4.2. Konfigurationsdatei [*]5. Unterstützung des Programmentwicklers [*]6. Verweise und Quellen [*]7. Rechtliches

Jep, I once thought about that, 2.

Yes, interesting question. At first glance it seems to be more logical not to display this section name in the software selection dialog because user can't know what it stands for nor is able to edit it.

Olá! I'm in contact with Benjamin and according to what I know there were big problems dealing with modifying already existing users. That's why he has chosen to remove the feature or at least replace it with some easier methods. Generally I agree with that because it's better not to have a function then to have it but not working properly. I don't think it would help much to disable or enable it by a command line switch because the feature has to be coded, of course, and that is what brings the trouble, not necessarily using it. Yes, I agree with that. GUI would be nice, too. Até a proxima vez

Yes i think this is very important (...) I'll care about this. Hhm, I don't know if this is a good idea. In a log file there should be as much as possible and necessary because it is created to troubleshoot problems and bugs. And usually the log file isn't viewed by "normal users" repectively deleted after successful operation. Moreover if someone want's to see what is really done by WIHU he just has to look into the INI files. So I plead for showing everything in the log file and not hide anything!

Thank God! Please don't add too many features to WIHU. Isn't it supposed to be a Windows Installation Helper Utility, right - and not a eierlegende Wollmilchsau as we call it in German?

@opensurf Now that Benjamin has released a new version, are those errors gone you reported before?

@Tommy Maybe u wanna look here: Changelog

Well, as long as a method does what it is intended to it's a good method, isn't it! I'd by the way do it the same way like you. Maybe there're other methods, too, but the only way you can execute a command in WIHU is the command.x.y.z directive and a possible command to delete files is indeed cmd /c rd I guess another way would be using an INF-file, but don't ask me how this exactly works. But one thing is clear: INF files would be much more complicated! Furthermore I don't think it would be a good idea to add an extra file deletion command to WIHU because this isn't the programm's original purpose.

This thread is supposed to be a little introduction for users who might be interesed in WIHU but don't know what it is. Q1) What does "WIHU" stand for? A1) "WIHU" is an abbreviation for "Windows Installation Helper Utility" Q2) What does WIHU do, what is it intended for? A2) WIHU is an easy to use tool for user account creation and software installation, i.e. it allows the user to select software which should or should not be installed. After selection is finished it runs the desired applications automatically. Automated software installation is by the way the main purpose of WIHU. And moreover user accounts can be modified/created/deleted as well including their specific settings like placement of the windows system folders like "My pictures" etc. WIHU is generally intended to be used for unattended windows installations. Q3) But aren't there already other ways to achieve that? A3) Yes, but WIHU is meant to be a good-looking, easy-to-use replacement for batch files, RunOnceEX, etc. based unattended. Just give it a try and it's very likely that you're gonna like it. *hehe* By the way: nLite isn't comparable to WIHU, these are two programs with different objectives. Q4) How does it work, how do I tell WIHU what to do? A4) WIHU is mainly controlled by command line parameters and configuration files; the latter ones, of course, you have to create on your own according to your needs. But don't panic, it ain't no XML, it's just simple INI-syntax. With those configuration files you tell WIHU what to do, i.e. how to install which software and so on. Once you've configured WIHU acoording to your own needs, it can work in a totally unattended way but you can (no must) also give the user sitting in front of the PC an opportunity to change your pre-configured settings. This is up to you. You'll also notice that WIHU offers you some nice features, e.g. checking for already existing files on your computer and dependent on the result let WIHU install the software or not. This was just one example. Q5) Is it a DOS-based program? A5) No. It's a normal Windows program with an own graphical user interface. And it works no matter which Windows service pack is installed. Q6) Where can I get more information? A6) First of all look at the homepage (see link list below). There're you'll find some useful information and also some screenshots of the tool. If you download the file you'll also get some example files included with it. And last but not least there's this board here where you can search for already answered questions or ask new ones. Q7) Is there a manual for WIHU? A7) Yes, WIHU is in fact now one of the rare tools with a documentation. But unfortunately there's only a German version of it right now. Manuals in other languages might follow as soon as people create them. For more information there's a manual thread. Q8) Who's the developer of WIHU? A8) Benjamin Kalytta, a German student. He's a member of this board. By the way: WIHU, of course, adapts to the language of your own system. Q9) Where can I get WIHU? A9) http://www.kalytta.com/wihu.php There you can download the tool. Also see link list below. Here's a list of WIHU-related links: download current main release of WIHU (ZIP file) download official German manual for WIHU developer's homepage MSFN WIHU forum thread A closing note for this FAQ: Let's only have additional contributions to the FAQ in this thread, please post any questions you have as a new thread in the forum, or as posts in the appropriate thread (if a similar subject already exists).

Hhm, but why's GUI support for this issue important? Can't this be done much more easily by the configuration files? Yes, you're right, this could be a nice feature. Wow! Well, I haven't tried this yet but is it really possible? I always thought Windows takes care that there is always at least one admin account present. But maybe I'm wrong?

(removed by me - accidentially posted a private message here)

So let me be the fifth. I laready wondered when someone would move your tool into that section here, but now wondering has an end.

Searched on the forum and the net but unfortunately couldn't find helpful information, so I'll try it here: I install my XP Pro silently and activate it afterwards manually over the internet. Okay so far. But how can I keep the activation key for the next unattended installations on that same system, i.e. to get rid of activating XP again and again? What I found out is that just saving and copying back of wta.* like almost everybody suggests doesn't seem to help?!

Are you really really doing this yourself ? I know of course that it would be better to work with restricted rights but there are far too many problems currently with different applications so it is a real pain to do this. Also, since I am the only user on my PC I like to do all kinds of administrative tasks while doing other stuff on my PC so I would need to constantly switch between Administrator and User account. Not really my idea of working with a PC. Security is important and I do whatever I can but I don´t want to restrict my rights while I am doing stuff on my PC. Things are different for companies or more public PC´s, I agree. Ciao, Alex Hi Alex! Well, to be honest: Yes, I do use restricted rights when working at my computer here. Because this is one of the most powerful things to increase security and at the same time not very difficult nor problematic, believe me. Working under admin privs is just a no-no. Many people think there would be too many problems when they set back to restricted rights, but this isn't really true. Most of the programs (Office, bla bla) are designed to work with restricted rights, even more, this is the level intended for daily work, not admin privileges! Nowadays only a few programs don't work properly with those limited rights, but this is a minority and furthermore it's no big deal to get rid of these probs. You just have to change the rights of a few directories and/or registry keys, that's all. And what do you get? Security. It's up to everyone to decide what he or she prefers. But afterwards people shouldn't complain about viruses and a faulty operating system, bla bla *hihi* And by the way: I want to do administrative tasks as well with my pc, sure! But no problem as well, just log on as an admin for some minutes, do your stuff, and then use user rights again. *hehe* I don't t want to administer my system whole day long, this is what isn't my idea of working with a pc.

Well, no comment. But German isn't the only language with so long words, just take a look at Finnish or Hungarian, they use the same system, even much more complex. Hhm, admittedly I don't know any Belgian, maybe a pity, I dunno, but the French and Dutch people I know are nice guys, too! I don't give much about those stereotypes, at least I try to do so. And as regards weather, I'm pretty satisfied with what we've got here. No need to complain.

I am confused! First, why this change ? Second, if users.ini contains this code for user 0: Group.0=1 he should be part of the Administrators group and not become a limited user after first logon. Or what do you mean by "Primary user" ? Bye, Alex This idea from Benjamin is very good from my point of view, let me explain it a little bit: 1.) Now DefaultUser (in German: Standardbenutzer) just got a new name: Primary User. 2.) Since many installation routines do need administrator privileges or they will fail, during installation part WIHU gives the primary sser account those Admin rights, no matter what the user's choice was. This is no problem at all because firstly it is necessary for the installations under Windows and secondly it doesn't affect the user's choice due to the fact the account is set back to the desired status after installation! For example: The user chose to create the primary user account with restricted privileges. WIHU will use admin rights for installations and afterwards set the status back to restricted prileges. If the user's choise is to create primary user account with admin rights, WIHU won't set it back, of course, after installations are finished. So, as u see: no difference, WIHU just assigns admin rights to the primary user account _during installation_ because this is needed for most installations under Win. Furthermore: for daily work one should never use admin rights.

Hey my2001! I did read the guide and of course I know about the need to add REGISTRY tweaks that should affect all future users during the T13/12 stage. But you do not need Wihu for this. A simple Regedit /s called from commandlines.txt will do the same. I do not understand the advantage of installing all your software at that early stage or even worse, add users at that stage ... that makes no sense to me, but I am sure you can explain your reasons behind that Bye, Alex Hi midiboy! Well, both ways, of course, are possible, just dependent on one's own needs. Certainly it's possible, too, to import a registry file with some tweaks at T-13 mark. But many installation routines only write data into registry's HKCU hive and I don't really want to search for those entries and add them to every user manually; this can be done much more nicer by let's call it "T-13-method". Yeah, and what is even more, often some files are copied to Application Data in the profile folders directory and so on, these files will be copied later to every newly created user account automatically which wouldn't be the case if I don't install software during T-13.

Hhm, I guess this could be something for a poll? ... Or maybe a new per command-instruction for the ini-files?!? *hehe* This way everybody would be happy except the programmer who would've got more work to do.

Oh no! Please don't call it "Hauptbenutzer" in German. Term "Hauptbenutzer" is already in use by Windows terminology which is the same as the English "Power User". In German: Benutzer (restricted privileges) Hauptbenutzer (elevated privileges) Administrator (highest privileges)

I prefer running WIHU at this early stage. Most because of the "Default User" fact which is described on unattended.msfn.org.