Originally posted here by mmelby
I will assume you are running a workgroup and not a domain. How about creating a batch file that is run in the startup group of the machine. The mapping can be done with a net use command and user name substitution. I think the eviornment variable is %username%. Does this make sense? IF not let me know a I can send you an example.

m2
First off - yes, it is a workgroup and not a domain. What you have described is pretty much what I was doing with the 9x clients. Trouble being that for XP Home you have to log on to the machine first, which isn't necessary with 9x.

Originally posted here by jinxy
I don't see how first setting up an account on the XP box's is inefficient as it allows a level of security not available on win 9x box's. You could just enable the guest account and let users log on with that, but that would be insecure.
The clients themselves are by their nature insecure. I am unconcerned with protecting the clients' hard drives and so forth, since everything of worth is stored on the server.

Having created accounts for each user on the xp box's you could map a network drive to each users personal folder on the server, with tools>>map network drive from within my computer. Then create a shortcut to each users folder on the server and place them on each users desktop.

Maybe a bit of work to set up but i would think not to much. But then i'm no networking guru.
Realistically it isn't that much work, especially considering the size of the network. However, it's inefficient and while the current setup works I was looking to optimize it.

Originally posted here by Tedob1
ive been watching this thread all night hoping someone could shed some light on this. i havn't had much experiance with "home" anything but occasional run accross it. ive never gotten it to join a domain though i havn't tried much.

having to create an account on each machine everytime someone moves or leaves and someone else comes in is very inefficient compared to a network loggin. which allows them no rights on the local machine but can logon anywhere (if allowed) yet keep their network privilages home directory and personalized mapping at any machine.
Although it's not a domain, you've basically outlined what I was trying to do in your second paragraph. Regardless, the solution I ended up with was:

-forcing automatic logon as a guest account for each XP Home box
-writing a vbscript which disconnected any old shares, got the user to enter their network username and password and then connected to their folders on the server.

A bit fiddly but definitely an improvement over before.

Thanks for all your replies