addusers.exe

Soldato
Joined
15 Dec 2004
Posts
3,819
Hi,

At work, we use addusers.exe from the W2K resource kit to add users in bulk to our network. Now I don't go back until september and need the CSV file format for it. I've searched on google for literally hours but all it returned was CSVDE which is no use as I cannot specify passwords with it so could anyone tell me the layout for the CSV file? Also, is it possible to add exchange mailboxes with addusers.exe at the same time as adding the users or is it done automatically?

Thanks

Ben
 
Q2. google for "create mailbox tool exchange"

Q1. I've just found the w2rktool.chm....


-------
AddUsers File Structure
AddUsers requires that each section in the comma-delimited input/output file have a heading to denote what type of information follows. These headings are [User], [Global], and [Local]. Use the dump users (/d) option to create a file that will demonstrate the use of these headings.

Syntax is section-specific for each entry (line) in the different sections, as follows:

[User]

UserName,FullName,Password,Comment,HomeDriveAndPath,Profile,Script,

[Global]

GlobalGroupName,Comment,UserName, ...

[Local]

LocalGroupName,Comment,UserName, ...

The entries (lines) in the [Local] and [Global] group sections can have 0 or more UserName entries after the comment field. Each user name will be added to that group. Lines must end with a comma (or the appropriate separator character).




Notes


To change the separator character from the default comma, use the /s:x command-line switch.
Global Groups will appear to be added to computers running Windows 2000 Professional. However, since Windows 2000 Professional does not support Global Groups, they are not actually added.

----------

hth :)
 
Last edited:
Example: AddUsers File
Please note that the blank lines between the sections are not required. If blank lines are used, they must be completely empty (no spaces or tabs, only the return character).

[User]
Administrator,,,Built-in account for administering the computer/domain,,,,
Guest,,,Built-in account for guest access to the computer/domain,,,,
IUSR_INTEROP80,Internet Guest Account,,Built-in account for anonymous access to Internet Information Services,,,,
IWAM_INTEROP80,Internet Guest Account,,Built-in account for anonymous access to Internet Information Services out of process applications,,,,
MTS_INTEROP80,MTS_INTEROP80,,Component Services system package administrator account,,,,
TsInternetUser,TsInternetUser,,This user account is used by Terminal Services.,,,,
[Global]
None,Ordinary users,Administrator,Guest,MTS_INTEROP80,TsInternetUser,IWAM_INTEROP80,IUSR_INTEROP80,
[Local]
Administrators,Members can fully administer the computer/domain,USER1\Administrator,USER1\MTS_INTEROP80,SYS-WINNT\Domain Admins,DOMAIN1\user1,
Backup Operators,Members can bypass file security to back up files,
Guests,Users granted guest access to the computer/domain,USER1\Guest,USER1\TsInternetUser,USER1\IWAM_INTEROP80,USER1\IUSR_INTEROP80,
Power Users,Members can share directories and printers,
Replicator,Supports file replication in a domain,
Users,Ordinary users,SYS-WINNT\Domain Users,
USER1 Admins,USER1 Admins - Members can create and manage Webs,BUILTIN\Administrators,
USER1 Authors,USER1 Authors - Members can create and modify folders and files in Webs,
USER1 Browsers,USER1 Browsers - Members can read documents in Webs,
MTS Administrators,Microsoft Component Services Administrators,USER1\MTS_INTEROP80,
MTS Impersonators,Microsoft Component Services trusted process identities.,
WMI Users,Members get read only access to WMI,


----
was that OK then ?
 
Last edited:
Back
Top Bottom