-
Notifications
You must be signed in to change notification settings - Fork 812
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DataDog agent installation failed on windows #3840
Comments
I tried MSI on windows server 2016 failed on AWS but EXE succeeded |
@minzhuo @cvkrreddy thanks for reporting these issues. Since these issues seem quite specific to your environments, please contact our support team and send them your logs. Thanks! |
MSI on windows server 2016 also fail on Azure 2016 image (CIS hardened) but EXE succeeded |
Same issue in Windows Server 2016 on-prem. Couldn't get MSI to work. Couldn't find exe to try. |
If you are installing the agent on a Domain Controller, a service account must be created in Active Directory and the following parameters must be passed during the install DDAGENTUSER_NAME & DDAGENTUSER_PASSWORD. See here --> https://docs.datadoghq.com/agent/faq/windows-agent-ddagent-user/#installation-in-a-domain-environment |
this fails for myself as well. As per Datadog Docs: |
@Phatix I encountered this problem but I was able to install it with a normal domain user account. No further permissions needed. |
We seemed to be encountering something similar when installing onto our domain controller. Every attempt to install was rolling back. Finally, we tried what @privojustin suggested and created the service account in AD manually first, then passing the username and password parameters into the msiexec command. It looks like the installer could NOT create the account automatically, as implied by the docs, but if it already existed, then it worked. We then tried to reset the service account password. We changed the PW in AD, and then went to |
I had the same issue and error log file contents, on two machines, attempting an upgrade from agent versions:
My issue was caused by a misinterpretation, on my behalf, of the Upgrading instructions in the upgrading tab: I had downloaded using the instead of using the which links to: When running the latter installer, my upgrades worked correctly. |
I tried the .exe and .msi both way. didn't work.
Output of the info page
Additional environment details (Operating System, Cloud provider, etc):
windows 7 (64bit)
Steps to reproduce the issue:
The text was updated successfully, but these errors were encountered: