Once you’ve completed any desired testing, all Code42 apps will update automatically according to your global delay setting. If needed, you can also deploy to individual devices for targeted testing. This allows for sequenced testing with multiple test groups. For example, if you’ve set your global delay to the thirty day maximum, you can arrange for the IT organization to receive the update on the general availability date, and for the marketing organization to receive the new app ten days after the release. These will become your test organizations. Once you’ve selected your global delay, you can specify organizations as “exceptions” to the delay date. Customers who do not set a global delay will continue to receive new versions of the Code42 app automatically on release date. The selected global delay becomes the date on which all endpoints will receive a new version of the Code42 app after its release. This delay can be set for up to thirty days. In most cases, you will be notified one week prior to the release date so that you can prepare for the start of the testing period.įirst, you must opt into this functionality by setting a global delay for all Code42 app updates. With the new delayed client updates functionality, Code42 cloud deployment customers have up to thirty days to test new versions of the Code42 app before all endpoints are updated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |