• Replies 5 replies
  • Subscribers 582 subscribers
  • Views 439 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.

  • Hi Gordon,
    That does look like the correct parameter to modify. Could you modify the value then restart the 'Citect Deployment Client Server' service?
    Let me know how you go.
    Kind regards
    Olivier

  • 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.

  • Hi Gordon,

    The 'PackagesToKeep' setting is specifically designed to define how many versions are kept on that client. There is no central way to define that all clients maintain the same number of versions.
    Technically though it is that value - 1, as the oldest gets overwritten (So specify 3, retains 2). I was using this a couple of months back on 2018 and it was working as expected. If I get a chance tomorrow I will try it again just in case the xmas period has blurred my memory :)

    Cheers,

    bradley

  • Thanks for that Bradley.

    A parallel/related query...

    Are you able to elaborate on what it is that actually 'manages' the deletion of old version folders?

    It appears that deployment (ie creation of new version folders on client) is done via the Deployment Client service.

    However, if I don't have the Client RunTime Manager running, then I can readily have a growing list of unmanaged version folders. It appears the the deletion mechanism is triggered once the Citect32.exe has restarted to the latest version, and not before.

    When is the INI file updated, and by which process etc ?


    Your thoughts/knowledge ?

  • Hi Gordon,

    The Deployment Client Service does the cleanup in response to a message from Runtime Manager. So you definitely need both of those running.

    The Citect.ini deployment section would be updated by the Citect Client process.

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