Finally, creating a standalone bundled endpoint license separate from the headend gives you choice when selecting different headend platforms and services. Fourth, moving to a term-based model allows budget planning to shift from a bursty CAPEX and ongoing support budget exercise to a more smooth OPEX planning process. This is also more in line with general business trend of enterprises trying to make employees more productive and thus always connected. Third, focusing on total users removes having to guess how many people need service and then having to buy pandemic licenses, which sit idle most of the time.
Second, focusing on user vs endpoint removes the variability that comes when the remote end-user has multiple devices connected simultaneously, a common issue with knowledge workers. <įirst, going with a total user count is very much in line with general trend towards enterprise license / seat count model which enterprises can track and manage much better than endpoints. This greatly simplified licensing calculation and consumption in a number of areas. To help address these issues, we moved Cisco Secure Client to a total unique user, term-based licensing model.
Moreover, with the growing number of mobile devices that need VPN connections combined with older ASAs refreshed to newer platforms there were also budget concerns with having to rebuy licenses. Based on feedback, we found that device based session capacity planning and per appliance license management was a constant guessing game and operational challenge. With Cisco Secure Client 4.x, Cisco introduced a new licensing model. This document describes the answers to frequently asked Cisco Secure Client licensing questions.
0 kommentar(er)
