How the Agent 'Auto Upgrade' feature of DLO works

The 'Auto Upgrade' feature has been in DLO since version 8.x and allows remote DLO Clients to be automatically upgraded, following an upgrade of the DLO Administration server.

This feature is Enabled by default, but can be disabled by selecting the 'Disable Auto Upgrade' option in the Tools - Options menu - Global Settings - Options page, in the DLO Administration Console.

Below is a summary of how this Auto Upgrade process is carried out ;

•  The DLO server is upgraded and when complete, sends a private notification to each user via the .notify folder in the user NUDF path

• The next time the DLO Agent starts up, while connected to the network, it will contact the DLO server to check the current settings, etc and at that point will receive the private notification.
• If the DLO Agent is idle (not running backups) it will process that notification; if busy, it will either process it once it has completed the work or when the Agent is next started up.
• The DLO Agent checks the agent share path on the DLO server ( \\\DLOAgent ) and reads the DLOBuildInfo.ini, to see if the DLO version referenced in that is different to what the DLO Agent is currently running; the files in the Agent share path will have had the files updated as part of the server upgrade.
• If the DLO Agent detects it is running an older version than the server, it then creates a folder on the Agent machine (under C:\Users\\AppData\Local\Veritas\DLO\.dlo ) and copies across the AutomatedAgentUpgrade executable and ini file from the \\\DLOAgent\update_ subfolder on the DLO Server, along with a copy of the Edgeserver.ini and any certificate .crt & .key files, if an Edge server is configured.
• The process then uses that AutomatedAgentUpgrade executable file to upgrade the DLO Agent, silently in the background, closing the Agent console if open.
• The progress and result will be logged in the  DLOAgentInstall.log  & DLOinst.log  files, in the C:\Windows  folder of the client machine, along with the DLOClient log.
• Once complete, the Agent will notify the DLO Administration Server, so that the upgraded Agent version will now show against that machine.

Be aware that, depending on the number of Agents to be upgraded and and how busy they are, the upgrade may not occur straight away, but the notification will be processed eventually, unless an error occurs that prevents that.

The status of agent upgrades can be monitored over time in the DLO Administration  console, by checking either the Agent version under Setup tab - Computers  or in the Overview tab - Dashboard - Deployment Charts.

Troubleshooting

If Agents still show as older versions, several days after the DLO Server upgrade, then follow the guidance steps below;

• Check under Tools - Options menu - Global Settings - Options page of the DLO Administration Console and confirm that the 'Disable Auto Upgrade' option has not been ticked ; This will not be the case if any of the Agents have successfully auto-upgraded, as this setting impacts all clients.   
• Review the DLOAgentInstall.log, DLOinst.log and DLOClient.log  files on the client machines, for any errors that may have been logged during an attempted Auto Upgrade. 
• Attempt a manual upgrade by going to the Setup tab - Users in the DLO Administration console, right-click the User and select 'Upgrade User', to force the process to start
• Use the  DLOCommandu -Update  command, with the appropriate switches to re-Notify users of the upgrade  (see DLO Administration Guide for further information)
• Carry out a Manual upgrade at each Client machine, by connecting to the  \\\DLOAgent share and running Setup.exe from there