Tom said:
Thanks Roger,
So what do you suggest can be done to connect one roaming
user (using a Laptop with XP Pro) to two geographically
seperate domains belonging to two seperate and unrelated
companies. He provides consulting services to both anf
commutes regulary between the two companies? Thanks, Tom.
Batch scripts that the user runs manually. One for Site1, one for Site2.
Have it come up and ask them for the username/password (requires some third
party applications, but in order to make end-users happy, this isn't too
hard) and in the batch scripts, use those inputs from the user in the NET
USE command directly..
In other words, your batch script for Domain1 may contain:
net use h: \\server_a\users\username /user:domain1\%1 %2 /PERSISTENT:NO
net use s: \\server_b\shared_group_files /user:domain1\%1 %2 /PERSISTENT:NO
And your batch script for Domain2 may contain:
net use h: \\server_c\users\username /user:domain2\%1 %2 /PERSISTENT:NO
net use s: \\server_d\shared_group_files /user:domain2\%1 %2 /PERSISTENT:NO
That way your input to the batch/cmd script would be the username (%1) and
password (%2). Now you could just put the persons username/password in the
batch script, but that is not sceure and if the admins of Domain1 and
Domain2 are worth their salt, they have a password policy in place that
would make the user change it every so often, meaning you or the end user
would have to change the batch script. With the variables, they have to
manually run and input their information every time - thus the scripts
always work as long as the user knows their username and password for each
domain. I guess you could get away with putting the username in each - but
I like multifunctional scripts. =)