+1 I had tried it and got results as expected described by Ben here. In fact it calls a Java app and it would make Explorer.EXE puke - I had to remote registry from another machine to remove the reg entry to get the server back.
Dave -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Monday, January 05, 2009 2:45 PM To: NT System Admin Issues Subject: Re: Launch .BAT on machine start On Mon, Jan 5, 2009 at 5:37 PM, Erik Goldoff <[email protected]> wrote: > Couldn't you just put the command in the RUN key under HKLM/Software...... > (you know the way, right) You're talking about the HKLM\Software\Microsoft\Windows\CurrentVersion\Run key? That runs after login, in the context of the user. The Group Policy Startup Script runs before login (indeed, before the login dialog appears at all), and in the context of the machine account. Aside from timing and file ownership, if users don't have admin rights (and one hopes they don't), the script wouldn't be able to install software or otherwise modify the system. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
