I'm working on a request from our lead SQL developer to set up a persistent, system-level mapped "Z" drive across various SQL servers in different environments like Dev, STG, and Prod. Each environment has its designated UNC path on a file server that's already configured. The goal is to have all Dev servers mapped to one UNC path, STG servers to another, and so on, with this setup being system-wide—not user-specific—and able to withstand reboots. I've been looking into using DFS namespaces along with a scheduled task running as SYSTEM for the mapping. However, I'm curious if anyone has a better or more efficient solution for this scenario.
1 Answer
If you're managing a domain, utilizing Group Policy Objects (GPOs) would be the most effective method for this. GPOs allow centralized management of Windows systems, so when you need to make changes, you can adjust it all from one place instead of tweaking each server separately.
Just keep in mind that mapped drives typically exist only for the logged-in user. If you're looking for something to be available to the machine itself, it's smarter to go with actual block storage solutions like iSCSI or whatever else you're using. If it's more for service accounts, consider just using UNC paths instead.