I am supporting the installation of a CCTV system from the Windows 2003 R2 Standard side of the equation, the intention was to use use a NAS for long term storage (quite a lot of data is generated in a fairly short time). The one snag we have run into is the CCTV software can only point to local drives and folders for its archival location.
I have looked at Junction Points (which are not supported on remote file systems), Symbolic Links (which are not available on Windows 2003) and Remote Storage Services (which is not available in Windows 2003 Standard).
Because the CCTV software runs as a Windows Service (4 of them to be exact), it is not immediately obvious how to do this, my current solution is as follows:
- Create a new local account for the services
- Add this account to the local Administrator Group
- Login using this account
- Setup the mapped network drive through
net use z: \nas\share /savecred
- Switch the four services to use the local account
- Restart the services
Surprisingly this worked, it feels like a horrible cludgy way to solve a problem. Is there a better way?
Windows occasionally "loses" mapped drives. You might want to run a periodic job to check for the existence of "Z:" and remount it if it's not there.
Unfortunately, that is probably your only option if the CCTV software cannot use UNC paths.
If your NAS supports iSCSI, you could instead use the Microsoft iSCSI Initiator to attach the server to a LUN which will show as a local drive.
Could you use a symbolic link?
Update: I don't think that symbolic links are available in Server 2003. Oh well.