Don't forget to read the header and include the QS udf as it is a dependency of EnumNetworkDrives.
Our Kix-based login script (see my web site) deals with this situation by defining a list of "ad-hoc" drive letters that users may employ for custom mappings. The script then unmaps all drives except for those in that list.
To keep administrative control, we limit the ad-hoc list to 3-4 drive letters at most, even on small networks. We tell users that those are the only letters available for personal use, and that all other drives will be unmapped at login.
It sounds like you need to get some business policies under control in addition to these firefighting scripts.
Glenn
_________________________
Actually I
am a Rocket Scientist!
