WORKGROUP

You're not specifying the relation between the workstations and the server. Do they logon, with logon script? Or just map drives through network neighbourhood, or through a startup batch?

Of course, manually visiting each PC will do. Just change the network properties.
You can automate the process if
a) They do logon to the W2K server and run a logon script stored there.
b) In the script, you can decide to which workgroup the machine goes depending on something you 'know' at that time. Like its name, or IP address etc. And if there is no simple relationship between names and workgroups, write a KIX script referring to a simple Ascii table (on the server) in which you have done the mapping manually! E.g.
wsname1 wg_a
wsname2 wg_b
wsname3 wg_a

Have fun,

- The Netherlands

etc.

For a LAN with over 10 computers, it is generally more efficient to use a domain to administer. You are going to have nightmares trying to keep all the username/password changes updated on every single machine that shares resources. On the win2k server can set up the active directory to separate to the two groups required, and then just assign permissions to the resources required for each group. Here's a good link for more information on Active Directory to get you started: http://www.labmice.net/ActiveDirectory/

For a LAN with over 10 computers, it is generally more efficient to use a domain to administer. You are going to have nightmares trying to keep all the username/password changes updated on every single machine that shares resources. On the win2k server can set up the active directory to separate to the two groups required, and then just assign permissions to the resources required for each group. Here's a good link for more information on Active Directory to get you started: http://www.labmice.net/ActiveDirectory/

This question was auto closed due to inactivity