Mikael Braad Nielsen I could not understand the following point in the question -
"After installering/updating to AzureMonitorWindowsAgent version 1.11.0.0 on a Windows 2012 r2, i created a data collection rule and associated the server to the rule."
There are 2 ways to install Azure Monitor Agent (AMA) on a VM
Using the agent extension - This method adds the extension after DCR has been created and associated with the VM. (There are other ways to enable it as well, which is available in the link here). As you have mentioned that you can see the extension option in VM to always show extension in "creating" state, I assume that you have followed this step for enabling the AMA. The following steps should help troubleshoot/diagnose this issue further
- On the Arc connected machine, run
azcmagent show
. Ensure that the "Agent Status" is available as connected, and all the "Dependent Service Status" are in running state (if not, the arc agent on the local machine is not able to connect to the Azure platform which is causing the status of extension to be stuck in Creating state) - You could run
azcmagent log
to collect all the associated logs for the arc enabled machine and see if there are any errors in one of them. Also, check the extension report available in %ProgramData%\GuestConfig\extension_reports for any errors related to extension installation itself. - The general troubleshooting steps available in the following article should also help you troubleshoot this issue better - General troubleshooting for Ar enabled server's extension installation
- In case the steps above do not help, I would suggest opening a support ticket to help investigate this issue in detail. You can see this link for details.
Using Windows Client Installer - Based on the nature of this issue, I dont think this method was used.
Please let me know if you have any questions. Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.