Improve the installer

[mickem]

Installer needs to be improved so it asks some questions such as "install service"/autostart/*

Also "uninstall" should clean-out registry entries.

[anonymous]

Agree - will probably need to switch to using the MSI to install/remove/start the service. I made a quick modification to have it call Nsclient /start after the nsclient /install, but 99% of the time it runs too quickly and fails because the service hasn't finished installing.

[Jeff Goldschrafe <goldschr@…>]

I can agree with automatically stopping and starting the service on upgrade, but is it really desirable in any sense to start the service before it's been configured?

[mickem]

LOL, indeed it is... as you will see in the next version :) All you need then is the following lines:

[/modules]
WebConfiguration.dll

[/protocols/WebConfiguration]
allow from host=127.0.0.1
bind=12345

and you will be able to configure things from the comfort of your web browser :) Now this is an *early* prototype so we shall see if it will be useful/work, but hopefully I will manage to get things working :)

// MickeM

[anonymous]

Replying to Jeff Goldschrafe <goldschr@cshl.edu>:

I can agree with automatically stopping and starting the service on upgrade, but is it really desirable in any sense to start the service before it's been configured?

Well I apply a transform to my MSI to install my own .ini file along with the application, so it is actually fully configured when it's installed at server startup by Group Policy. Actually starting the service is a bit hit and miss though because of the timing, and I don't know how to make the installer delay until it's finished installing everything before running the startup step.

Nothing another reboot doesn't fix, of course!

[anonymous]

Replying to mickem:

WebConfiguration?.dll

What I'd really like would be if it could be set to automatically contact a configuration server every so often. I thought of scripting this myself as part of the installer but then decided I was too lazy, plus there'd be no easy way of issuing an updated config to a running server.

In my ideal world, every hour or so it'd contact a central server as specified in the config we roll out with the MSI (HTTP GET or POST request, probably) and the server can supply it with a new configuration file if it chooses.

What do you think? Should I submit a feature request?

[mickem]

sounds like a cool idea actually... feel free to request away but don't expect anything soon, the 0.4.0 has been delayed a lot due to all the darn bugs I keep adding to the 0.3 branch, and I would expect something like that for 0.5.0 really...

// MickeM