Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Terminal services network drive

Status
Not open for further replies.

InvalidResponse

IS-IT--Management
Jun 27, 2002
22
GB
Im running win2k server, with a bunch of thin client machines connected up to it. I want a network drive pointing to the company filing structure to be available to everyone. I have written a batch file and then in the Domain group policy set it to run on logon.

For some reason I get no network drive, in fact im not even sure if the batch file is running. Im new to Group Policies so perhaps im going about things the wrong way. Does anybody have any ideas??

Thanks in advance. They say hard work never killed anyone. But dont like taking chances.
 
Is the network drive on the Terminal Server? Can you post the contents of the bat file? James Collins
Field Service Engineer
A+, MCP

email: butchrecon@skyenet.net

Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.
 
Can you put the bat in the profiles tap of a user in Active Directory and see what happens? Try running the batch file manually with a pause statement at the end to see what is happening. Good luck. Glen A. Johnson
Microsoft Certified Professional
glen@nellsgiftbox.com
[americanflag]

"Science is built up with facts, as a house is with stones. But a collection
of facts is not more a science than a heap of stones is a home".
Henri Poincare (1854 - 1912) French mathematician
 
The contents of the batch file are as follows:

@echo on

net use z: \\Swan\CDRIVE\Directory "Password" /USER:TST-LTD\Administrator

If I run the file manually then it installs the network drive as I want it.

Yes the network drive is on the termina
l server.

Thanks They say hard work never killed anyone. But dont like taking chances.
 
*bump* They say hard work never killed anyone. But dont like taking chances.
 
try putting the batch file into the Startup folder for All Users on the Terminal Server instead of as a policy.
 
Worked fine.

Thanks. They say hard work never killed anyone. But dont like taking chances.
 
If you want to do it a bit neater, add a line to the winnt\system32\usrlogon.cmd at the start to "call ?:\?\my_file.cmd" and that will run the batch file for everyone regardless!

Cheers,
Carl.
 
I tried adding the net use commmand inside the usrlogon.cmd file itself, but I didnt think of trying to use another file. Thanks. They say hard work never killed anyone. But dont like taking chances.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top