When the Agent is installed, the Service is started automatically right after the installer finished although in the wrapper.conf file the wrapper.ntservice.starttype is set to DEMAND_START
This does not allow to put any configuration changes in place before the Agent Service starts for the first time.
In fact, the wrapper.ntservice.starttype=DEMAND_START in the wrapper.conf is taken in by the Windows service wrapper setup during the APMIA agent installation to set the Windows service startup type. Upon the completion of the Window service wrapper setup, this 3rd-party Windows service wrapper installer would automatically start up the Windows service and let the Window service comply with the "Manual" startup type for the subsequent system restart. This wrapper installer doesn't appear to have an option to achieve what you would like to do unless finding a way to change the wrapper installer implementation. You can observe this behavior by directly running the appropriate wrapper installer, e.g. wrapper-windows-ia-64.exe, wrapper-windows-x86-32.exe, or wrapper-windows-x86-64.exe.
As a consequence the wrapper.ntservice.starttype=DEMAND_START in the wrapper.conf needs to be set prior to APMIA agent installation and the Windows service initial setup and the observed result is working as expected. Any subsequent change to the property wrapper.ntservice.starttype in the existing wrapper.conf would require reinstalling the APMIA agent Windows service.
If wrapper.ntservice.starttype=DEMAND_START is set prior to the installation of the APMIA agent Windows service, the service would be installed with the "Manual" startup type and would require to start-up manually but only after each system restart. The Windows services would be started right after the initial APMIA agent installation, but they would not be running automatically in the subsequent restart.
DX APMIA Infrastructure Agent 21.3
The following enhancement request user story has been submitted to our PM/dev team for review and prioritization:
US823580: ER APMIA agent service to support an option not to start up right after installation.
As a workaround, you could stop the installed Windows service manually to make any ad-hoc configuration changes followed by starting the service instead of updating wrapper.ntservice.starttype=DEMAND_START requiring to remember to start up manually the Windows service upon each subsequent system restart.
The following KB can be also useful in troubleshooting other similar issues in general:
How to configure DXI APM SaaS agents or On premise 11.x, 19.x, 20.x, 21.x Agents to connect to APM EM 10.7 On-premise?
DX APM - Installation of Multiple Instances of the Infrastructure Agent not honoring the blanks in the display_name.
DX APM - Installation of Multiple Instances of the Infrastructure Agent not registering SysEdge as a second service.
DX APM - Infrastructure Agent Stops Tomcat Service on SDM Server if started with default port 8085
DX APMIA Windows could not start the CA SystemEDGE service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion.
DX APM - SysEdge Agent not reporting any metrics when installing Multiple Instances of the Infrastructure Agent