update a custom package > new Maintenance release 11.22.22

@Bloopa , this is the process direct for 11.22:

https://documentation.commvault.com/11.22/expert/2101_creating_custom_package_for_windows_computers_using_download_manager.html

I’m thinking you need to download the actual media as you likely just updated and didn’t grab the full install media.

Hi @Bloopa 

You won’t be able to use a MR update package to update an already created custom package. The custom package version is fixed with the media used to create the package and can’t be updated later.

You have 2 choices at this stage:

1. Create a new custom package using new media for 11.22.22.
2. Leave your custom package on the older version 11.22.13 and run an update from the software cache on newly installed clients to bring them up to the same version as the Commserve and rest of the environment.

Thanks,

Stuart

Thanks to all for your replies.

@Laurent reply helped me a lot. I have created the new packages directly from the setup on software cache. Just before that I used the copy software option to copy the maintenance release 11.22.22  to the software cache, then I clicked on commit.

I can update directly old client with the new version from the commserve console. and for the new clients, I gave the custom package to the ansible engineer, now all new clients are deployed with the updated version.