New year, new problems
Today i tried to add the last server in a new network to my icinga monitoring, but on this machine installing the agent failed.
I tried both the powershell framework and just downloading the agent from packages.icinga.com
The server is Windows Server 2012 R2 and .NET Framework seems to be v4.8
The only hint about why the installtion failed is from windows’ event display, which tells me that the server couldnt be registered with DCOM
ID is 10010
Im not 100% sure its related though.
Sadly i couldnt find anything close to this on google or here.
Yeah, thats what i meant with “powershell framework”.
This way is how i normally do it now, but sadly it failed this time.
I thought at first that maybe theres an issue with icingas servers, but i installed it on a new vm in my own network without issues.
Well, that looks strange…
I have yet to use the new Icinga for Windows installation stuff, but the False kind of looks like the agent is considered to not be installed.
Is there a switch for that somewhere maybe?
Have you tried the way over the IMC? If I understand correctly you are currently using the configuration/answer file method?
Im not really sure what you mean with that.
The method i used was the IMC. If im not mistaken this installs the agent.
Thats how i normally install the agent and it has always worked until now.
Thanks for trying to help anyway
Im sorry, english isnt my first language so some things might not be as clear as they should be.
With install file i meant the installer you can download from https://packages.icinga.com/IcingaForWindows/stable/agent/
Im not really familiar with github, but i will try it there if noone else has any ideas in the near future.
i tried following command on powershell, and installation work fine ahter that.
Uninstall-IcingaAgent -RemoveDataFolder
Remove-Item -ErrorAction SilentlyContinue -Path “C:\ProgramData\icinga2” –recurse -Force
Remove-Item -ErrorAction SilentlyContinue -Path “C:\Program Files\icinga-framework-service” –recurse -Force