Comments on: How to create windows services (Command Line) http://technology.amis.nl/2008/02/13/how-to-create-windows-services-command-line/?utm_source=rss&utm_medium=rss&utm_campaign=how-to-create-windows-services-command-line Friends of Oracle and Java Sun, 31 Aug 2014 06:57:42 +0000 hourly 1 http://wordpress.org/?v=3.9.2 By: Mythreyi http://technology.amis.nl/2008/02/13/how-to-create-windows-services-command-line/#comment-5186 Fri, 19 Feb 2010 01:53:58 +0000 http://technology.amis.nl/blog/?p=2852#comment-5186 The space after the “=” after the option type to specify the value was what was missing.
This post help me get over it.
Really helpful! Thanks

]]>
By: Chris Gralike http://technology.amis.nl/2008/02/13/how-to-create-windows-services-command-line/#comment-5185 Fri, 03 Jul 2009 09:55:25 +0000 http://technology.amis.nl/blog/?p=2852#comment-5185 If it helps, after reading some additional documentation on the subject regarding the NT boot process i found the following.

both the system and boot switches are related to “drivers” that need to be loaded at boot time by one of the following components.

boot driver => loaded by NTLDR at system boot.
system driver => loaded by ntoskrnl.exe after “boot” drivers.
automatic drivers => loaded much later when the GUI is started in the following process.

]]>
By: Chris Gralike http://technology.amis.nl/2008/02/13/how-to-create-windows-services-command-line/#comment-5184 Fri, 03 Jul 2009 09:18:36 +0000 http://technology.amis.nl/blog/?p=2852#comment-5184 Hello Matthew,

Im not sure if boot in this case actually means at system boot (windows boot logo). More because of the windows architecture where all services marked “automatic” will be started at system startup directly after logon.

If you actually want something to start at the earliest possible time you might want to use the windows policies instead of system services.
By means of scripting this might be an outcome.

If this is preferred there are two moments you can use to script your task (script a service startup for instance ;) )

1. At system startup.
Only problem here is that the explorer process isnt started yet, so WMI and VB arnt an option here and you are bound to batch scripting. another downside might be that all user information isnt available yet. In effect this means that you have a DOS environment and its capabilities to do some basic very early administrative tasks.

2. At system logon.
This is where the user has finished logging on and all “automatic” services have started and all env information is available to you. Usually used for domain logon scripting.

Both can be configured using the windows group policy editor.
>start>run…>MMC
[ctr+m]>add>Group policy editor>add>local computer>finish>close>ok

If you want to test the boot option, i got windows to accept it by using the following command..

C:\Documents and Settings\chris>sc create MySystemCmdBox binPath= “C:\windows\system32\cmd.exe /k cmd” type= own error
= ignore start= boot start= auto
[SC] CreateService SUCCESS

Rgrds,

]]>
By: Matthew http://technology.amis.nl/2008/02/13/how-to-create-windows-services-command-line/#comment-5183 Mon, 29 Jun 2009 10:58:33 +0000 http://technology.amis.nl/blog/?p=2852#comment-5183 Hi,

Thanks for the tutorial.

I’m getting a problem with the Failed 87 error.

I’m trying to set a service so it runs at boot. which i’m trying to use the start= boot switch.

But, using the example above and just changing that switch it generates Failed 87.

Any idea why this is? It works if i use the example above, exactly, but i need this service to run at boot.

Thanks,

Matthew Millar

]]>