• Replies 5 replies
  • Subscribers 582 subscribers
  • Views 443 views
  • Users 0 members are here
Options
Related

Citect 2018 Deployment - more than 2 versions required on client ...

Gordon

Hi All,

I have a pending need to be able to manage how many deployed 'versions' are managed/maintained on a client. At present, it appears I am restricted to only having 2 versions maintained on the client. Rolling out a further deployed version results in the deletion of the 'oldest' version of the 2 current ones.

I have noticed the file c:\citect\config\SE.Asb.Deployment.Node.WindowsService.exe.config, which has a parameter called 'PackagesToKeep' set to a value of '2'. Changing the value seems to have no effect, and I've no way of knowing if the parameter has anything to do with what I want anyway.

Does anyone know if/how I can amend the number of deployed versions that can be managed/maintained on a client ?

Thanks in advance.

Parents

  • Hi Olivier,

    (Note: We're currently using Update Oct 9, but about to update to latest, if that helps.)

    Yep, I've been regularly restarting the Deployment Client Service when making mods. No luck there, I'm afraid. The parameter is only defined on the Deployment Client, not the Deployment Server. However, I also regularly restart the Deployment Server service as well.

    It would appear that the parameter is used to manage the number of cached versions maintained on the deployment client. That is, it maintains (by default 2) cached versions (as zips/blobs of some sort). I can amend the parameter to a value of (say) 10, and can then see 10 cached versions being maintained. I think it is more to manage comms between deployment server/client when flicking backwards/forwards between versions. It certainly has no effect in our environments on the number of version folders that are maintained on the deployment client.

    regards,
    Gordon.

Reply

  • Hi Olivier,

    (Note: We're currently using Update Oct 9, but about to update to latest, if that helps.)

    Yep, I've been regularly restarting the Deployment Client Service when making mods. No luck there, I'm afraid. The parameter is only defined on the Deployment Client, not the Deployment Server. However, I also regularly restart the Deployment Server service as well.

    It would appear that the parameter is used to manage the number of cached versions maintained on the deployment client. That is, it maintains (by default 2) cached versions (as zips/blobs of some sort). I can amend the parameter to a value of (say) 10, and can then see 10 cached versions being maintained. I think it is more to manage comms between deployment server/client when flicking backwards/forwards between versions. It certainly has no effect in our environments on the number of version folders that are maintained on the deployment client.

    regards,
    Gordon.

Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.