• State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 13388 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The License Portal Has Been Contacted

Corrigun
over 7 years ago

I see this message every hour on the hour. Is there a reason it has to call home so frequently? What happens if it cannot for some reason?

Not a big deal but it seems a little odd.

Parents
  • 0 over 7 years ago
    The rate of License Portal contact was designed with certain features in mind for some of our larger customers. The Licnese Portal gives you the ability to grant additional licenses to sub-customers (if you are an MSP), disable agents from backup, check status, etc. all from the License Portal which is accessible from the Internet. In many instances MSPs or other large customers may not have direct or immediate access to a core server. So to speed the process of those changes propogating down to a core we set the heart beat for the core to 1 hour. That way MSPs don't have to manually go to each core to force a contact to make their changes take effect quickly. The rate of contact is not too quick that it causes unnecessary overhead, but it's fast enough that a change is realized efficiently in that sort of situation. The check takes very little time and very little overhead on a core server. Other than the notification (which you can turn off in notification settings) you shouldn't even notice it.
Reply
  • 0 over 7 years ago
    The rate of License Portal contact was designed with certain features in mind for some of our larger customers. The Licnese Portal gives you the ability to grant additional licenses to sub-customers (if you are an MSP), disable agents from backup, check status, etc. all from the License Portal which is accessible from the Internet. In many instances MSPs or other large customers may not have direct or immediate access to a core server. So to speed the process of those changes propogating down to a core we set the heart beat for the core to 1 hour. That way MSPs don't have to manually go to each core to force a contact to make their changes take effect quickly. The rate of contact is not too quick that it causes unnecessary overhead, but it's fast enough that a change is realized efficiently in that sort of situation. The check takes very little time and very little overhead on a core server. Other than the notification (which you can turn off in notification settings) you shouldn't even notice it.
Children
No Data