In this topic, you’ll learn what you need to know to plan and distribution applications to an organisation. To get the best use of this article you should be familiar with the upKeeper manager, upKeeper groups and upKeeper applications server.
When it comes to distribute application it should be done thru groups. In your upKeeper environment there should be groups so when introducing a new application it would be added to necessary groups or if the application is aimed to a new groups of computers the groups should be created.
When updating an application you should use replace application function to the update simple and controlled. You can update or replace applications by remove the old applications from groups and computers where the application is added and then add the new application to the same groups and computers but is more administration and the possibility that you forgetting to add the new application to the correct groups and computers increases.
Further you can throttle simultaneously client changes by adding max concurrent changes property in application configuration file. This means if property is set to 100 there are a maximum of 100 client making changes at the same time. Benefit of limiting the number of changes in the environment is that network traffic and number of clients accessing file share are kept at an acceptable level and will not affect other traffic on the network or services in the environment. Keep in mind setting max concurrent changes will limit all client actions and that actions taking long time will affect the total time it take before all clients are up to date. During times where max concurrent connections is meet system may feel unresponsive. The max concurrent connections property should be use as an extra safety feature and not like an distribution spread mechanism.
Please sign in to leave a comment.