Have run into a problem. Upgrading a server from Win2K Std to Win2K3 Enterprise (DB server – needs more RAM), and batch jobs which rely on network shares are failing due to the security model of the Win2K3 Drive letter NameSpaces.
The jobs see the drive letters (proven by examining WMI’s Win32_LogicalDisk), but can not access the contents of the network shares (all network shares show as ‘unavailable’).
Both machines are using local accounts – same username/passwords.
This configuration worked fine under Win2K, but this does not work under Win2K3. We’ve narrowed this down to drive letter namespaces – the shares that are set up under the individual accounts on the Win2K3 box are not retained between sessions like they were with Win2K.
We’re looking for a quick, cross the board fix to this problem such that it can be maintained at the server admin level, rather than at the individual job level.