W2K vs W2K3 - drive mapping behavior changes ?

Hi all,

Did the behavior with regards to the visibility of mapped drives change significantly between W2K and W2K3 ? I have an application running as a service under a domain account, that, on W2K, is perfectly able to access a remote share via a mapped drive letter once that mapping is established interactively, via Explorer.

On W2k3 however, this does not seem to work; the service does not even see the mapped drive.

All protections and permissions are wide open, and the accounts involved are all domain accounts belonging to the Administrator group on both machines.

I know that for XP and on the official recommendation is to use UNC path names, but for legacy reasons that is not an option.

Any helpful pointers to articles or tech notes would be greatly appreciated. TIA.

Mike
.

Relevant Pages

  • Re: W2K vs W2K3 - drive mapping behavior changes ?
    ... Did the behavior with regards to the visibility of mapped drives change ... service under a domain account, that, on W2K, is perfectly able to ... On W2k3 however, this does not seem to work; ...
    (microsoft.public.windows.server.general)
  • W2K vs XP - drive mapping behavior changes ?
    ... Did the behavior with regards to the visibility of mapped drives change significantly between W2K and XP? ... I have an application running as a service under a domain account, that, on W2K, is perfectly able to access a remote share via a mapped drive letter once that mapping is established interactively, via Explorer. ...
    (microsoft.public.windowsxp.general)
  • Re: Services fail to start
    ... it shouldn't but since you're changing to a domain account you must require network resources available to your service. ... Just remember mapped drives won't natively exist so always best to use UNC paths. ... Microsoft MVP [Windows] ...
    (microsoft.public.windows.server.general)