Jump to content

Featured Replies

  • Replies 9
  • Views 1.4k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • salmanrehani
    salmanrehani

    @Saurabh Jhunjhunwala @Simon Frankiewicz Thank you both for your updates. What I meant by "we still have to run the APNs renewal script" is that we are still required to execute the script ever

  • 2 weeks later...
  • 10 months later...
  • 2 weeks later...
  • Community Expert

Hi @salmanrehani,

I can confirm that I’ve also migrated the APNs for Applications entries to Cloud Notification Service (CNS) for several clients. I haven’t renewed the APNs for Applications certificate separately. However, based on what I see, support is recommending replacing it, most likely due to the upcoming transition of FQDNs from VMware domains to new Omnissa-related ones.

In my opinion, it’s worth doing both – migrating to CNS and updating the FQDNs in the console – especially since notifications might still work even without updating the FQDNs, which could be misleading.

As for support – experiences have varied over time, so everyone should assess the situation individually and choose whether to go with option 1, option 2, or both.

@Saurabh Jhunjhunwala @Simon Frankiewicz
Thank you both for your updates.

What I meant by "we still have to run the APNs renewal script" is that we are still required to execute the script every year to keep the APNs certificate from expiring. I initially thought that migrating to CNS meant the APNs certificate would no longer be necessary, and therefore the annual renewal process would be eliminated — but apparently, that’s not the case.

Create an account or sign in to comment