#376 closed defect (fixed)
Installer dependancy on firewall breaks DCs
|Reported by:||gfilion||Owned by:||MickeM|
Although similar to #314, I didn't wan to hijack this other ticket because I think the nature of the problem is different.
Currently, the .msi installer for NSClient++ requires the firewall to be active during the installation so that rules can be added. If the firewall is not running, it starts it automatically for a short period.
This period, however short it is, is enough to crash a domain controller: domain controllers must never have a firewall activated, else they loose sync with the other DCs and all services get confused, causing a serious crash.
The problem is I'd still like to monitor the DC, but I can't have nscp install silently when I need to push an update.
having an option to be able to prevent the installer from starting the firewall would be great.