Phil's suggestion might be what you need. Look up the NET command in this file:C:\WINNT\system32\ntcmds.hlp
I did this once & I found it to be a pain. (Maybe there isan easy way I didn't think of.) Some suggestions that you probably already know. To handle batch control of ownership you will need to use xcacls from the NT4 Res Kit and to handle batch assigning of shares you will need rmtshare from the same Res Kit. You will probably need Showmbs from the same Res Kit to generate your list of users for the batch files. Watch out how you copy the shares too. The so-called shares created by the user manager are pseudo-shares not true shares. Access is controlled through ownership and not through share permissions. Some copying strategies will not work because administrators do not have ownership access. Taking ownership will lock the users out of their directories. You might use use Scopy from the resource kit but that might generate copies you can not touch without fixing ownership with xcacls.
Here is a portion of a sample batch file we use to create users. It creates the individual hidden shares as well. You could modify it to use the FOR command to loop through user lists generated by showmbs. Just take the parts you want.
@echo off
REM command file to create user accounts
REM needs NT Server 4.0 Resource Kit
REM parameters Userid, password, full name, user directory, group, server, comment
NET USER %1 %2 /add
NET USER %1 /scriptpath:LOGON.BAT /passwordchg:no /passwordreq:yes
NET USER %1 /times:M-F,7AM-7PM
NET USER %1 /fullname:%3 /comment:%7
NET GROUP %5 %1 /ADD
MD %4\%1
XCACLS.EXE %4\%1 /t /c /g administrator:fo;fo webmaster:f;f %1:f;f /y
NET USER %1 /homedir:%4\%1
RMTSHARE \\%6\%1$=%4\%1 /grant %1:f users:1 /remark:%3
RMTSHARE \\%6\%1$ /grant administrators:f
RMTSHARE \\%6\%1$ /grant %1:f
I think there is a simpler way of just moving the shares. Just copy them with Scopy from the resource kit and then go into the server registry and do a change all on share info. Then run NET USER for all user ID to update the user directory. Of course, they will still be pseudo-shares not real shares.
athname
