If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Scheduled Task to Access Network Resource
Hi,
Does anyone know if it's possible to create a scheduled task to run as the System account, but use other credentials to access a network resource? I have a script that is in the Netlogon share of our DC's. I want to run a regular task on a 2003 server which runs this script from the DC's. It needs to run as the local System account, but needs to access the share with a domain\user account. Is this possible? Thanks, Steve |
Ads |
#2
|
|||
|
|||
Scheduled Task to Access Network Resource
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. "SteveJHU" wrote: Hi, Does anyone know if it's possible to create a scheduled task to run as the System account, but use other credentials to access a network resource? |
#3
|
|||
|
|||
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. |
Thread Tools | |
Display Modes | |
|
|