When the client needs to access the files on the server, the company suggest not using “\\server\mpn”, instead they want “s:\mpn”, wher s: is mapped to \\server.
If the software gives you the option of where you want to install it at, install it to a location like “c:\program\mpn” and then share out the “c:\program” folder. If it doesn’t give you the option of where to install it, and you have to share out the entire c:\ drive, then the program is total crap. Call them and let them know your security concern. Surely they have a way to work around it.
The only way to map a drive would be to map to a UNC path.
I would take a hard look at the security changes you are going to be making. By allowing everyone full control over that network share you’ll be giving everyone full control of the OS volume of the companies server. If someone gets a virus on there computer it WILL infect the server and cause all sorts of problems.
I believe the vendor would have everyone map a local drive letter to the UNC path, then access the software through the local drive letter. This would typically be done through a login script.