After last month's column, a reader wrote in and asked how to assign resources to locations, not to users. For some resources, such as printers, it's less important who you are than where you are. In that case, you can still use the Wscript.Network object we already discussed, but employ the ComputerName property to get the name of the local computer.
What about IP addresses, you ask? We'll get to those -- they're a bit more involved -- and that's a problematic way of identifying a user machine anyway because so many people use Dynamic Host Configuration Protocol (DHCP). It's not out of the question, but it is more involved.
Scripting School: More on connecting to network resources
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
|ABOUT THE AUTHOR:|
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.