View Single Post
  #3  
Old February 20th 08, 02:24 PM posted to microsoft.public.windowsxp.security_admin
SteveJHU
external usenet poster
 
Posts: 2
Default Scheduled Task to Access Network Resource


Thanks Anteaus, that's not a bad idea regarding the batch file. And I
obviously agree concerning the change.

Strange thing is that the System account must be able to use different
credentials at some point...hence Startup Scripts configured with AD Group
Policy. I believe Startup Scripts run from the System account, but use the
domain computer account credentials to gain access to the Netlogon share. So
I think there's got to be a way, but maybe just not published.

Steve



"Anteaus" wrote:


There is a change in behaviour with WinXP as compared to earlier Microsoft
OS's, in that with XP, drive mappings apply to the user, and are only
accessible to the account which created them. In earlier versions, network
resources applied to the computer.

Personally I think this is a detrimental change as it makes it very hard to
perform network operations with services. But, that's the way it is.

Your options are to run the process as a non-system user, or to use a
batch-file to establish the share-connection when the process starts.


Ads