Hello KS-Soft,
thank you to have accepted my account request on your forum.
We are a company who use your software for years now, and we never had problems. I did not know where to post my request, here in Bugs, or in "Installation/Configuration", so sorry if i did a mistake.
So, we started rolling up our server to versions Windows Server 2025.
RMA Service is ok on all server except for the Domain Controller. The service just wont start and tell "the service did not respond in a timely fashion". In eventvwr, i just see that the service did not respond fast enough and did a time out to the request.
Those are "in place upgraded" server, where the service was correctly installed previously.
This also happen on fresh deployed DC server 2025.
Weird behavior is, if i start the rma application manually by clicking on the exe and close it, then i can start the service...
If I restart the server, the service wont start again.
The service is installed and configured to "passive RMA", with "Local system account".
I tried to let run the service with the "administrator" account, and then it works. But this can't be configured like that for security reason, and i can't make any local admin user regarding the fact this is a domain controller, so no local users.
For the moment i just run manually the exe when my servers restart to have the monitoring up and running, but before i can go ahead with the 2025 upgrade in our whole DataCenter, i need to find a solution to this problem, otherwise i will have too much server services to "watch on" myself.
Can you please advice me some "configuration" step to solve this problem?
RMA agent wont start as a service on DC Server 2025
Re: RMA agent wont start as a service on DC Server 2025
There are always some problems with new Windows releases..
Sorry, so far we have no idea what can be wrong. RMA never had any startup problems and service startup problem that relates to "local system" account but not to admin account sounds strange.
What version of RMA do you use?
x86 or x64 version?
Can you use RMA started on another system for DC monitoring? Usually single RMA started under domain account can monitor entire domain so you don't need to install it on DC itself.
Regards
Alex
Sorry, so far we have no idea what can be wrong. RMA never had any startup problems and service startup problem that relates to "local system" account but not to admin account sounds strange.
What version of RMA do you use?
x86 or x64 version?
Can you use RMA started on another system for DC monitoring? Usually single RMA started under domain account can monitor entire domain so you don't need to install it on DC itself.
Regards
Alex
Re: RMA agent wont start as a service on DC Server 2025
As I see your support term expired 8 years ago so I assume you are using pretty old HostMonitor and RMA?
Somehow its not rare behavior: install new Windows right away and keep using the same old version of HostMonitor for 15 years
I would suggest to try up to date RMA version. Normally you need to update ALL components of the software at the same time (HostMonitor, RCC, RMA, Web Service, etc) but in order to test if RMA service will start, you may try to update just this single agent.
Regards
Alex
Somehow its not rare behavior: install new Windows right away and keep using the same old version of HostMonitor for 15 years

I would suggest to try up to date RMA version. Normally you need to update ALL components of the software at the same time (HostMonitor, RCC, RMA, Web Service, etc) but in order to test if RMA service will start, you may try to update just this single agent.
Regards
Alex
Re: RMA agent wont start as a service on DC Server 2025
Hi,
thank you for your reply.
You are right, we are using a pretty old version of the agent, version 5.0.30.443 x86.
And your right again when saying we use the same old agent, when i deploy new server, i just copy/paste my RMA folder to the new computer and simply run the tools to install it as a service.
I forgot to tell in my orginal post that i did try to deploy the latest version of the agent 8.44 X64, just to see if this was solving the service problem, but this version have the exact same behavior than our old one, so i just revert the change and still use our old agent.
Untill now, this has never give any problem
You know, when it's working, don't touch it.
I just tried to monitor the DC from another server where service is starting, i get different error regarding remote access not allowed or remote registry not accessible so to implemnt this i will have to "tune" server access settings. I do not have a lot of time now so i will leave it like that untill a solution for the service registration on a Domain Controller will be found.
thank you for your reply.
You are right, we are using a pretty old version of the agent, version 5.0.30.443 x86.
And your right again when saying we use the same old agent, when i deploy new server, i just copy/paste my RMA folder to the new computer and simply run the tools to install it as a service.
I forgot to tell in my orginal post that i did try to deploy the latest version of the agent 8.44 X64, just to see if this was solving the service problem, but this version have the exact same behavior than our old one, so i just revert the change and still use our old agent.
Untill now, this has never give any problem

You know, when it's working, don't touch it.
I just tried to monitor the DC from another server where service is starting, i get different error regarding remote access not allowed or remote registry not accessible so to implemnt this i will have to "tune" server access settings. I do not have a lot of time now so i will leave it like that untill a solution for the service registration on a Domain Controller will be found.
Re: RMA agent wont start as a service on DC Server 2025
For some test methods you should provide account using Connection Manager (menu View->Connection Manager) or using "Connect as" options located in Test Properties dialogI just tried to monitor the DC from another server where service is starting, i get different error regarding remote access not allowed or remote registry not accessible so to implemnt this i will have to "tune" server access settings.
And of course RMA should not be started under "local system" account, it's only for local system monitoring.
https://www.ks-soft.net/hostmon.eng/mfr ... htm#conmgr
We will check Windows Server 2025 Domain Controller but officially we do not support Windows 2025 yet. Its hard to support new systems when new behavior (and some bugs) are not well documented.I do not have a lot of time now so i will leave it like that untill a solution for the service registration on a Domain Controller will be found.
While old RMA v5 was not tested on Windows Server 2019 or 2022 either.
Regards
Alex
Re: RMA agent wont start as a service on DC Server 2025
PS
We tested Passive and Active RMA 8.44 on Windows Server 2025, service mode, local system account, tried on Domain Controller and regular server - in all cases services start fine
We tested Passive and Active RMA 8.44 on Windows Server 2025, service mode, local system account, tried on Domain Controller and regular server - in all cases services start fine
