RE: Startup script security context

2009-11-30 Thread Christopher Bodnar
rvices Guardian Life Insurance Company of America Email: christopher_bod...@glic.com Phone: 610-807-6459 Fax: 610-807-6003 _ From: Kennedy, Jim [mailto:kennedy...@elyriaschools.org] Sent: Monday, November 30, 2009 1:09 PM To: NT System Admin Issues Subject: RE: Startup script security contex

RE: Startup script security context

2009-11-30 Thread Jackson, Jeff
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

RE: Startup script security context

2009-11-30 Thread Kennedy, Jim
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

RE: Startup script security context

2009-11-30 Thread Jackson, Jeff
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 proble

RE: Startup script security context

2009-11-30 Thread Ken Schaefer
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 u