Ah, you are probably right about that, my brain was translating that to running something from the Startup folder under the All Programs menu.
From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org] Sent: Monday, November 30, 2009 10:09 AM To: NT System Admin Issues Subject: RE: Startup script security context Brilliant idea. But change it to 'At Startup' for the context of how he describes when it runs now? From: Jackson, Jeff [mailto:jeff.jack...@rbza.com] Sent: Monday, November 30, 2009 1:07 PM To: NT System Admin Issues Subject: RE: Startup script security context How about running the script as a scheduled task? Set the task up on the "At logon" schedule. And, of course, use "Run as:" to define the account you want it to run as. Jeff From: Ken Schaefer [mailto:k...@adopenstatic.com] Sent: Monday, November 30, 2009 7:59 AM To: NT System Admin Issues Subject: RE: Startup script security context I don't believe that is possible in any supported way. The GPO policy processing engine invokes the various extensions for processing each policy, and that runs as LocalSystem, and invokes each engine as LocalSystem. What problem are you trying to solve? It may be possible impersonate another user (though probably not safely via script, but your script could invoke something else) Cheers Ken From: Christopher Bodnar [mailto:christopher_bod...@glic.com] Sent: Monday, 30 November 2009 11:37 PM To: NT System Admin Issues Subject: Startup script security context I have a startup script running as part of the local group policy on a server. I know it's running in the context of the Local System account. Is there any way to modify that to use a different account? Thanks, ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
