This is caused by missing registry keys.

What sort of registry keys would be needed?

This key is missing here:
HKLM\System\CurrentControlSet\Services\Alerter\Parameters

This key is now created by the provision script, the one for bug 4934 too. More patches to setup/provision.reg are welcome :-)

Jelmer, we aren't able to fix this issue until we have a case insensitive registry backend running. The problem is, that in some RPC's the key "SYSTEM" is called as "System" and in others as "SYSTEM". We have to figure out, how we are able to do case insensitive searches in LDB.

Fixed in Subversion :-) We support case insensitive key / value names now.

Jelmer, here we fail because the value "AlertNames" under "Alerter/Parameters" is missing.

Any idea what it should be set to ? Patches to setup/provision.reg are welcome :-)

"Alerts" seems to work now on my test environment. I'm able to add new computer- and usernames. The other issue to be handled is if SAMBA also supports the settings.

Created attachment 3151 [details]
Registry improvements

Here I've a improved version of the provision.reg. It adds also the NT version number which seems to be necessary for this operation. I've chosen the one of Windows 2003 Server.
I also changed "System" in majuscule "SYSTEM" to match Windows but it's esthetically because the registry backend is case insensitive.

Thanks, I've applied your patch. Is this bug fixed now?

No, we have to bring up the right RPC's.

The alerts (function) as such works now (it uses the registry), but we don't send them because we haven't implemented this.
So my question here: Should we continue to work on it or let it uncompleted? I personally don't find it necessary.

I think we should keep this open as there may be some people interested in it but just keep it very low priority.

I think we should keep this open as there may be some people interested in it but just keep it very low priority.