I thought I had this licked but apparently not. I have server applications running on 2008 and its on a NT 4.0 domaiin. When logged in as a domain admin and in the past when the server applications auto logged in as the domain admin and the server applications auto started as deskop apps, the mapping of drives and/or usage of UNC paths worked fine for the server applications to see. Now that I am running the 2008 service applications as services using the default LocalSystem account, I am issues keeping a persistent mapping under the system account. Researching the steps to allow services see mapped drives, pointed to the basic idea that when the mapping is done, it has to the done under the account the application will be using. So using PSEXEC, I logged in as the local admin for the 2008 machine, open a command prompt window and typed: psexec -s cmd.exe net use m: \\nt-machine\sharedfolder dom-adm-password /user:domain\dom-adm-name /persistent:yes exit When this is active, the service applications can now see drive m: However, this was done last week and I thought it was solved, but here I am seeing that the mapping is lost somehow and becomes unavailable and I have the repeat the steps above. This has to be resolved administratively. Proabably we will need to add new application logic to help operators prepare shared networking requirements but I am not sure yet what are the programming requirements (steps), but for backward compatibility with existing installtions we need to resolve this for ourselves and also pass this info on to customers. Is there is some "locked down" security issue that is in 2008 that I need to override? Thanks Hector Santos, http://www.santronics.com Via Wildcat! Live Exchange NNTP Gateway http://opensite.winserver.com

This KB sort of explains these situation INFO: Services and Redirected Drives The KB says for XP, "However, drive letters that are mapped from a service that is running under the local system account are visible to all logon sessions." How does 2008 (where the services are running) apply here? It seems to behaving like the KB describe for 2000 and 2003. ThanksHector Santos, http://www.santronics.com Via Wildcat! Live Exchange NNTP Gateway http://opensite.winserver.com