Participant

Question

RUM reporting no updates when they are available in AUSST

Forum|Forum|1 year ago
June 13, 2024
2 replies
882 views

Like so many others in this community, I've found that using the internal AUSST server to provide updates to our end user machines is not reliable enough for continued deployment. I've been trying for years to make it workable, so not just teething problems. This only applies to the Creative Cloud side, Acrobat works no problem.

I'm looking for a simple and reliable alternative. Instead of using RUM, can I just apply the full application msi over the top of an existing install to update? If so, are there any downside or pitfalls to watch out for?

Thanks

This topic has been closed for replies.

Gurdeep.Singh

Adobe Employee

Hi @Tony332632626yk2

Thanks for contacting us.

In case you find managing updated difficult within your org, there are multiple options you can look at

1) Use RUM and use Automation so the applications are up to date ( Good only for Point updates )

2) AUSST is beneficial for Version upgrades

3) If you allow your users to self serv, they can manage the updated at their end

4) if you are looking for version upgrades, then create a package and deploy with the latest applications in it, the previous package that was used to deploy the previous version can be used for uninstallation of the older version by running it in uninstallation mode

5) You can define a policy on the admin console that ensures the applications are up to date if the users have local admin rights on the machine

I hope this helps

Regards,

Adobe

T

Tony332632626yk2Author

Participant

Hi,

Thanks for the advice.

I've explored all those options and unfortunately they either aren't reliable or our users don't have the access/rights to use them.

I'm only left with the option to apply a full package to do an update. All I need to know is whether I'd need to remove the existing install first or whether the new package can be applied without removing the existing install first.

Thanks

I

iCharles

Legend

Hi,

If you find using the internal AUSST server unreliable, you can create packages with specific versions on the Admin Console and deploy them as an alternative. This method can help ensure a consistent and controlled update process.

You can find detailed instructions on how to set this up in the help document here.

Hope this helps!

T

Tony332632626yk2Author

Participant

Hi,

Thanks for the advice.

I've gone round in circles reading Adobe help and following links I'm afraid. So much sounds promising but it never actually states that you can apply a new full package over an an existing install.
It used to be possible to create an update package in the admin console, which is mentioned in the documentation, but Adobe removed that feature not too long ago. Now it is only possible to create full deployment packages.

All I can see working reliably now is applying a completely new install but don't know if I'd have to remove the existing install first. Normally an application would manage that for you, but Adobe have made things so complicated with software deployment it's just not possible to tell if that is the case.

___Dom___

Community Manager

Hi,

All Admin Console packages are now full installers, to avoid the need to first install the base version of the product, so that any package can be installed whether or not the initial release is already present.

You can install a package from the Admin Console containing applications on top of previously installed versions of those Creative Cloud applications in order to update them. If a more recent version of one of the applications is installed, the package will fail to install.

If your users do not have local administration rights, you can set the options in an Admin Console package to display the list of applications and to allow users to install applications via Creative Cloud Desktop:

Create a managed package and tick the options "Enable self-service install" and "Allow non-admins to update and install apps". Deactivating these options will show a message instead of the list of applications in Creative Cloud Desktop.

More information on creating packages can be found here:

https://helpx.adobe.com/enterprise/using/create-nul-packages.html

To install the package, use the setup.exe in the "Build" directory on a Windows system, to ensure that all of its components are installed. Applying the MSI in this directory may result in not installing everything, depending on what the package contains.

I hope that helps explain.

Best wishes

Dom

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded