Copy link to clipboard
Copied
Hi!
I tried working with AUSST but ultimately decided not to use it and downloading updates online. How can I remove the client-side configuration so clients don't try to contact internal AUSST and ultimately fail to update?
I tried removing the ovveride-Files from:
%SYSTEMDRIVE%\ProgramData\Adobe\AAMUpdater\1.0\
%SYSTEMDRIVE%\Program Files (x86)\Common Files\Adobe\UpdaterResources
Stripping the log-files (from Remote Update Manager Tool) to what I guess is relevant:
Error before removing the override files:
| 10100 | The FFC override url derived from redirection file is ... (http://xxx.yyy.zzz/updates/Adobe/ACC/services/ffc/products/ffc.xml)
Error after removing the override files:
14856 | FFC override file does not exist ... (C:\Program Files (x86)\Common Files\Adobe\UpdaterResources\AdobeUpdater.Overrides)
14856 | Starting UpdaterCore CheckForUpdate...
| 14856 | UpdaterCore failed for CFU errorCode(220) curRefId((null)) errorCodeString(U41M1C220)
Error code 220 means that the Update server is not accessible so it seems the client is still not checking online repositories.
Kind Regards!
Hi!
I might have solved the problem myself - we are using a proxy (configured with .pac proxy configuration file) and when executing RemoteUpateManager remote (cmd), the proxy server needs to be set for the executing user For example: netsh winhttp set proxy 10.0.0.6:8080
So deleting the override files seems to actually "disable" AUSST for a client.
Kind Regards
Copy link to clipboard
Copied
Hi!
I might have solved the problem myself - we are using a proxy (configured with .pac proxy configuration file) and when executing RemoteUpateManager remote (cmd), the proxy server needs to be set for the executing user For example: netsh winhttp set proxy 10.0.0.6:8080
So deleting the override files seems to actually "disable" AUSST for a client.
Kind Regards