How to create a custom service?

[Guest /u/69yuri69]

Coming from UNIX background I can't wrap my head around creating a custom service on a recent Microsoft Server instance. The task is really basic - start a simple app listening at a port on boot and keep it up and running when it crashes, etc.

 

It seems like srvany.exe is the way to go even according to Microsoft. However, after toying with it for few moments it seems it doesn't handle such basic task as to reflect the status of the app to the service state.

 

This felt odd. Googling revealed there are multiple third-party utilities providing a "better srvany" implementation. Some of those really felt like cobbled together by a single guy in a shed. Definitely not something complying to corporate security regulations.

 

Is this rally the reality of Windows Server in 2024?

 

I mean UNIX has a range of service managers which are native and easy to use - SysV init, OpenRC, systemd, etc. Does any custom Windows Server service need to implement a Windows API to be managed as a "true Windows service"?

 

submitted by /u/69yuri69

[link] [comments]

 

Continue reading...