Using a Win32 Service is an alternative option - you can use the SRVANY utility from the Resource Kit to "service-ify" pretty much any executable. (the key point there is: run the script asynchronously unless it's critical, or doesn't need to be run asynchronously cos it will always take no time at all. The computer startup process will be affected by the time it takes to run the program, though, so you might want to ensure you call it with the START command from a batch file, or specifying not to wait for the executable to complete in whatever script language you use. When domain-member computers access network resources, they generally (with exceptions) authenticate using their MACHINENAME$ account - which lets you set Share/NTFS permissions to allow a computer to access those resources.Ī startup script is a quick and easy way of getting a process running when the machine boots. as LocalSystem, as you noted, so they often can't access network drives which require a certain user or group membership to work.
The computer startup scripts run in the computer context, i.e. When using Active Directory, a similar interface is used to edit AD Forest-hosted group policy objects (GPOs), so the same settings are available across a bunch of machines. GPEDIT.MSC is the Group Policy editing console, and runs against the local computer's Local Group Policy store when it's used directly, so it's useful for setting local-only parameters. after computer startup, when a user logs on) in the User configuration bit. There's an equivalent logon script area (i.e. Computer Settings -> Windows Settings -> Scripts (Startup/Shutdown).Windows 2000 and above offer a computer Startup Scripts collection in the policy editor: Short answer: GPEDIT.MSC (Start, Run, GPEdit.msc)
0 kommentar(er)
