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

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

Reply

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

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