General discussion

Locked

batch file connect to home share

By techgirl75 ·
We have an existing batch file that connects users to a specific drive/folder/subfolder on our network. In the batch file, it connects all other network drives by there share name, however on this drive which points to specific folder it only says "net use x: /home". I have changed in User Manager - the home directory for the x: drive - does it take a while to propogate? This is the only share I am having problems with. I want the users to connect to a new set of server drives on a server I am building to replace the existing one (to which they are still pointing). Does it matter if the new server is a BDC right now? Thanks!

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

batch file connect to home share

by Gigelul In reply to batch file connect to hom ...

Hi,
If I understand correct, you can't map a non shared folder.

Collapse -

batch file connect to home share

by techgirl75 In reply to batch file connect to hom ...

Poster rated this answer

Collapse -

batch file connect to home share

by techgirl75 In reply to batch file connect to hom ...

Sorry, i figured it out.. I did a synch between the PDC and BDC and it worked out. However the NT/2000 workstations are not being mapped by the login script now, can you tell me why that is? Thanks!

Collapse -

batch file connect to home share

by jsarinana In reply to batch file connect to hom ...

Check the share
try " net use \\servername\home "

Good luck

Collapse -

batch file connect to home share

by techgirl75 In reply to batch file connect to hom ...

Poster rated this answer

Collapse -

batch file connect to home share

by vh_s In reply to batch file connect to hom ...

You have it correctly.

The command :
NET USE X: /HOME

is saying to assign drive x: to the home directory specified in the User Manager / Profile.

Should you change it, it should (and shall) change the home directory directly. If it doesn't, only one conclusion: persistent connection has been establish. Therefore break this persistent connection first before re-establishing the home directory. Try use:

NET USE X: /DELETE

If it doesn't work, go to the workstation one by one, and right-click on network drive and click 'Disconnect'.


Second question: no, it doesn't matter if your new server is the BDC. Anyway, you are using the workstation name of the BDC in the path name, something like:

\\BDC_PCNAME\share

Therefore, it doesn't have any relationship whatsoever with the status of BDC or PDC.

Collapse -

batch file connect to home share

by techgirl75 In reply to batch file connect to hom ...

Poster rated this answer

Collapse -

batch file connect to home share

by dgbarner In reply to batch file connect to hom ...

It is really a good idea to include a net use x: /del in your batch file before making the mapping. You should consider doing that for any drives that you create in the script. This gets rid of any existing connections that may interrupt new connections. Also in User Manager, check your profile tab to see if the new home directory location is entered correctly and also that the share exists and is accessible by the users. For troubleshooting purposes, you may want to turn echo on and watch the batch to see if any messages are generated.

Collapse -

batch file connect to home share

by techgirl75 In reply to batch file connect to hom ...

Poster rated this answer

Collapse -

batch file connect to home share

by techgirl75 In reply to batch file connect to hom ...

This question was closed by the author

Back to Windows Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums