1) How to perform Force Update on product manifest file within cache, Noticed that product.manifest updates only when a package request for new version in client machine, despite of adding multiple versions in the server and server restart/reset
i.e.; once all the versions are cached any changes made in server product.manifest does not reflect in product.manifest file in client, until you delete one of the folders and Runtime is again applied when package requests for it. So how to force update
2)Not all Runtime versions are cached even when multiple Runtime versions are mentioned in Fetch Version of product.manifest in server.
Ex: with Base version as 184.108.40.206
Fetch version as [220.127.116.11, 18.104.22.168, 22.214.171.124] could see 126.96.36.199 in cached folder, only few dll files for 188.8.131.52 could not see 184.108.40.206 in the folder
3)Does cached runtime version gets deleted or removed from client, once one of the fetch version is deleted from product.manifest in server?
Current Fetch Version; [220.127.116.11, 18.104.22.168]
If we delete 22.214.171.124 from fetch version in server, will it automatically remove that folder from runtime cache folder?
1) You can also restart Pega Updater Service (or restart machine) or, and I think it would be optimal solution, set "PreFetchMins" parameter on Synchronization Server side (in appsettingsRepo.json) so that it checks for updates every N minutes. By default it equals 0 meaning it is disabled. If it is enabled, it updates product.manifest and pre-fetches product versions per configuration.
Note that PreFerchMins change itself requires restart of Synchronization Server and Pega Updater Service, so that it is applied on client machines.
2) Please make sure you performed server reset after manifest change and required bundle version is imported on Synchronization Server. Please check if you see "version.ready" file under each cache/<product_version> folder on client machine. If there are some files but there is no "version.ready" then it means download failed for some reason. Anyway, first of all, check %programdata%/Pegasystems/Updater/UpdaterService.log to see when changes were pulled last time and if there are any errors.
3) No, cache is not removed from client machine in this case, only product.manifest is updated.