We are currently testing out the Silent/Unattended installation process for the DT Agent on .NET, but we need the ability to start the agent with actually going into the DT configuration Module. If we have do that for every servers that would be tedious. Ops has can modify the Registry files, but we need to activate the agent once done and we don't want to have access the server do so.
Solved! Go to Solution.
Activating the agent is nothing more than registering the DLLs (which the installer should have done) and then setting COR_PROFILER and COR_ENABLE_PROFILING environment variables. So if you already modified the registry files ask your Ops team to also set those variables after the installer ran.