This article only applies to Ahsay software version 7

Article ID 5248
Reviewed : 2017-10-16

Product Version:
AhsayACB / AhsayOBM: 7.5.0.0 to 7.x
OS: All platforms

ATTENTION 1st January, 2022: v7 officially End-of-Life [details]

This document contains instruction on how to force another Auto Update on backup client agents when AhsayCBS remains the same version. Modification had been made to the client application, I need to ensure that the newly updated files are dispatched to the client software via Auto Update (AUA) without user interaction. How can I do that?

Example:
You currently run the same AhsayCBS version (example AhsayCBS version 7.11.0.0) but have rebuilt your AhsayOBM / ACB version 7.11.0.0 clients due to branding changes, and want to push the latest changes automatically to all your customers.

Assumptions:

• The Auto Update function has already been enabled on AhsayCBS.
  
• The AhsayOBM / ACB user account is selected for Auto Update on AhsayCBS.
  
• The AhsayOBM / ACB client machine must be powered on.
  
• The AhsayOBM / ACB client machine must be connected to the internet.
  
• The AhsayOBM / ACB scheduler services on the client machine must be running.
  
• The AhsayOBM / ACB scheduler services is connecting to AhsayCBS server using the latest login credentials.
  
• The AhsayOBM / ACB application GUI on the client machine must be closed.

To force another update after you've made changes to the AhsayOBM/AhsayACB client installer:

1. Create a copy of %CBS_HOME%\download\liveUpdate\index.xml as backup.
   
   
2. Edit %CBS_HOME%\download\liveUpdate\index.xml.
   
   
3. Search for : <AutoUpdate product="acb" and modify "version=" to increment by one revision version.
   
   Example:
   Assume AhsayCBS v7.11.0.0, search for:
   <AutoUpdate product="acb" version="7.11.0.0" compatible="7.x.x.x" host="" edition name="%ACB_FULL_NAME_SYSTEM%">
   
   Change version="7.11.0.0" to increment by one revision dot version ("7.11.0.1"):
   <AutoUpdate product="acb" version="7.11.0.1" compatible="7.x.x.x" host="" edition name="%ACB_FULL_NAME_SYSTEM%">
   
   Important: We do not recommend you repeatedly rebuild client and increment this version variable, as then your "version" may be greater than the next AhsayCBS release and cause future AUA upgrade problem.
   
   Also, a sub-revision version, such as "7.11.0.0.1" is invalid.
   
   
4. Search for : <AutoUpdate product="obm" and modify "version=" to increment by one revision version.
   
   Example:
   Assume AhsayCBS v7.11.0.0, search for:
   <AutoUpdate product="obm" version="7.11.0.0" compatible="7.x.x.x" host="" edition-name="%OBM_FULL_NAME_SYSTEM%">
   
   Change version="7.11.0.0" to increment by one revision dot version ("7.11.0.1"):
   <AutoUpdate product="obm" version="7.11.0.1" compatible="7.x.x.x" host="" edition name="%OBM_FULL_NAME_SYSTEM%">
   
   Important: We do not recommend you repeatedly rebuild client and increment this version variable, as then your "version" may be greater than the next AhsayCBS release and cause future AUA upgrade problem.
   
   Also, a sub-revision version, such as "7.11.0.0.1" is invalid.
   
   
5. Save the changes.
   
   
6. Enable AUA for the user(s).
   
   
7. Inform client to close their client user interface. The AUA cannot upgrade the client if the application user interface is opened.
   
   
8. Within the next 720-minutes, the client's AUA service will automatically check if the "index.xml" version number is greater than the installed version. If yes, it will perform an auto update.
   
   The client version after update will remain as the true client version, and not of the "version=" value.

force, AUA, auto upgrade