Microsoft Support for VM agent extensions is limited to first-party extensions that are developed and published directly by Microsoft.
Support is available to customers who purchased a valid Azure support plan.
Support for third-party VM agent extensions is provided directly by the vendor.
Current agents support matrix
|VM agent extension||Reference||Microsoft Support policy||Link for support|
|DSC||Azure PowerShell DSC (Desired State Configuration) extension||Supported by Microsoft||https://manage.windowsazure.com/?getsupport=true|
|MSEnterpriseApplication||System Center Role Authoring Extension||Supported by Microsoft||https://manage.windowsazure.com/?getsupport=true|
|BGInfo||Background Info extension||Supported by Microsoft||https://manage.windowsazure.com/?getsupport=true|
|VMAccessagent||VM Extension to enable Remote Desktop and password reset||Supported by Microsoft||https://manage.windowsazure.com/?getsupport=true|
|Chefclient||Chef software agent||Supported by Chef software||http://www.getchef.com/support/|
|PuppetEnterpriseAgent||PuppetLabs agent||Supported by PuppetLabs||http://puppetlabs.com/solutions/microsoft|
|Symantec Endpoint Protection||Symantec antivirus||Supported by Symantec||http://www.symantec.com/business/support/index?page=contactsupport&key=54619|
|Trend Micro Deep Security Agent||Trend Micro antivirus||Supported by Trend Micro||http://www.trendmicro.com/us/business/saas/deep-security-as-a-service/index.html|
The VM agent lets you start, run, and monitor a VM extension that will perform specific tasks in the virtual machine (VM).
The VM agent has to be running for the agent to run extensions.
How do I know whether the problem is with the agent or with extensions?The VM agent consists of three services that must be running:
- Windows Azure Guest Agent
- Microsoft Azure Telemetry Service
Steps to verify the installation/startup error for the extensions:
When the agent is running, it will log a summary of extensions operations. This summary includes the following:
To determine which extension is failing, open the log, and then look for the word "error" in the log.
An example of an error in starting the VMAccess extension is as follows:
 [04/08/2014 23:25:07.80] [INFO] Successfully installed plugin Microsoft.Compute.BGInfo 1.1.
 [04/08/2014 23:25:07.80] [INFO] plugin (name: Microsoft.Compute.BGInfo, version: 1.1) enabled successfully. Code: 0
 [04/08/2014 23:27:04.11] [ERROR] Install command of Microsoft.Compute.VMAccessAgent has not exited on time! Killing it...
Use the table that is mentioned in the "Summary" section to request support for the extension that is failing.
ID članka: 2965986 - Poslednji pregled: 04.09.2015. - Verzija: 1