MicrosoftMicrosoftWe've been testing the new Auto Agent Upgrade feature for Azure Arc-enabled servers as part of the public preview. After enabling the enableAutomaticUpgrade property on a few servers, we noticed that the scheduled task responsible for the upgrade runs nightly but completes within seconds, and the agent version remains unchanged.
Interestingly, when we manually trigger the scheduled task or run the underlying script directly, the agent updates successfully.
This behavior suggests that the automatic upgrade mechanism might not be functioning as expected in some scenarios. Is this a known issue with the preview release, or are there specific conditions under which the upgrade is skipped?
Would appreciate any insights or guidance from the product team or community.
MicrosoftThat’s interesting. There shouldn’t be a difference between running the scheduled task manually and it running on its own. What agent version was the machine running on prior to the successful upgrade? Is this a Windows machine? What does the "Last Run Result" and "Last Run Time" say in Task Scheduler?
This is very likely the "Internet Explorer - First Run" issue with PowerShell. Since the task is executing under SYSTEM privileges and basic parsing is not used in PowerShell when downloading the agent, it fails to execute completely.
Executing the same command defined in the scheduled task as an administrator will work without issues.
We have enabled the new property for about 20 Arc-Enabled machines with versions between 1.52-1.54.
It doesn't seem to work for any of them. The task is running every night but is completed within 4 seconds.
Last Run Result: (0x1)
We are now testing to enable the "Run with highest privileges" property on the scheduled task itself to see if it would make a difference.
https://www.souldo.net/2015-11-07-internet-explorer-disable-first-run/,
This blog should be a work around to get the scheduled task working.
TL;DR, create a registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\DisableFirstRunCustomize" with value "2"
MicrosoftHey Jeroen, I've reached out to you privately about some additional details to help debug the issue.
