I mentioned last month that Wsh.Network has a MapNetworkDrive method you can use to map a remote path to a local drive letter. On a shared computer, what happens to all those drive mappings?
The answer is that these mappings are not persistent, which means that they're erased when the user logs off. Since this is a logon script, this won't affect the user -- they'll always see drive J. However, this means that other people on the same computer won't see this mapping, and updating the mapping is as easy as updating the script.
If the script attempts to map a network drive to a drive letter already in use, the script will fail with an error.
Requires Free Membership to View
Scripting School: More on connecting to network resources
Introduction
What happens to all those mapped drives?
What about location-based mappings?
How do I map printers?
Does Select Case support wildcards?
How to put the script together
MapResources sample script
Summary
Read Christa's previous columns:
Beginner's guide to scripting
It's time to increase your scripting expertise
Scripting: Connect users to network resources
| ABOUT THE AUTHOR: |
|
Christa Anderson When Christa Anderson began working with Windows Server operating systems in 1992, she became increasingly interested in finding more efficient and flexible ways of performing routine tasks. Christa has written extensively about administrative scripting and taught technical sessions on the subject at conferences such as Comdex and CeBIT, helping people who had never done any scripting to write their own scripts in half a day. In addition to her interest in scripting Windows management, Christa is an authority on server-based computing and the program manager for Terminal Services licensing in Longhorn. If you have a scripting question for Christa, please e-mail her at scripting@SearchWinSystems.com. |
Enterprise Server Strategies for the CIO
Join the conversationComment
Share
Comments
Results
Contribute to the conversation