1 2 3 Previous Next 34 Replies Latest reply on May 7, 2020 1:32 AM by rpleupen

    Has anyone gotten ENS v2 to work properly on-premise?

    hccvsphere Novice
      Just curious. We're having issues with ENS v2 on-premise and browsing through the forums, I see that others have had issues in the past. Is this still the case? Thanks.
        • 1. Re: Has anyone gotten ENS v2 to work properly on-premise?
          MATTHAYSMATTHAYS1 Novice
          We are still testing ENS v2 version 1.3.0.2 (ENS v2 on-premise) which is the latest release and fixes some known issues.  To get the correct unread badge count to change correctly, you literally have to refresh the Boxer Inbox then get out of Boxer for the count to display correctly.

          We had been waiting to test VIP Notifications as that is what has been missing.  SQL Always On is still not yet supported for ENS v2 in case you were looking to get that set up.  Hope that helps.

          Matt
          • 2. Re: Has anyone gotten ENS v2 to work properly on-premise?
            hccvsphere Novice
            Thanks for your input Matt. Interesting to see if the problem we are having is because of the ENS database being in an availability group. But I am seeing 400 errors such as the following in the MailNotificationService:

            ' Identity:notauth::
            Module:MailNotificationService.BusinessImpl.CNSHelper.ReadResponse
            Message: User Id:[ ] Failed To Post to CNS [https://cns.awmdm.com/nws/notify/apns] Error: [The remote server returned an error: (400) Bad Request.] Response: [{' status' :' failure' ,' errorReason' :' Unable to process json input' }]
            '
            • 3. Re: Has anyone gotten ENS v2 to work properly on-premise?
              MATTHAYSMATTHAYS1 Novice
              Ariel, we had to verify with VMware Support that the CNS was updated to 2.0 which it was.  Can you verify that with support as that is a supposed requirement for ENS v2.  And are you running the latest 1.3.0.2 release?
              And yes, it would be worth it to isolate the ENS db by not including it in an availability group.
              • 4. Re: Has anyone gotten ENS v2 to work properly on-premise?
                nandagopalchandiran Lurker
                We are trying to implement ENS v2 on premise and we are getting error ' Failed to run uploadRSAkeys.exe. The installation is getting completed after the error. However logs shows

                2018/11/20 07:58:31.296 UAEAWMDMPAP03 7b39ce38-a4f7-4bf8-bf79-a34f13151165 [0000000-0000000]   (1)   Info  MailNotificationService.Startup.LogOwinStartup MailNotificationService has started on [UAEAWMDMPAP03]
                2018/11/20 08:03:14.842 UAEAWMDMPAP03 2e2a882e-0211-45c9-86fd-b4c3760ff03f [0000000-0000000]   (30)  Debug MailNotificationService.Controllers.EnsController.GetPublicKey User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Processing Get Public key request for Userid[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1]
                2018/11/20 08:03:14.842 UAEAWMDMPAP03 656d2174-507f-4b7f-9b11-cba088a4fc6a [0000000-0000000]   (37)  Debug MailNotificationService.Controllers.EnsController.GetPublicKey User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Processing Get Public key request for Userid[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1]
                2018/11/20 08:03:59.854 UAEAWMDMPAP03 c840c28c-e8e4-49c2-ab3b-08621948dca0 [0000000-0000000]   (38)  Debug MailNotificationService.Controllers.EnsController.GetPublicKey User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Processing Get Public key request for Userid[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1]
                2018/11/20 08:04:10.033 UAEAWMDMPAP03 930ab670-3bed-4e9f-a4f2-081f4820bee7 [0000000-0000000]   (36)  Debug MailNotificationService.Controllers.EnsController.GetPublicKey User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Processing Get Public key request for Userid[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1]
                2018/11/20 08:04:15.083 UAEAWMDMPAP03 656d2174-507f-4b7f-9b11-cba088a4fc6a [0000000-0000000]   (36)  Debug MailNotificationService.BusinessImpl.GetPublicKeyBusiness.ProcessGetPublicKeyRequestAsync User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
                2018/11/20 08:04:15.083 UAEAWMDMPAP03 2e2a882e-0211-45c9-86fd-b4c3760ff03f [0000000-0000000]   (5)   Debug MailNotificationService.BusinessImpl.GetPublicKeyBusiness.ProcessGetPublicKeyRequestAsync User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
                2018/11/20 08:04:15.083 UAEAWMDMPAP03 2e2a882e-0211-45c9-86fd-b4c3760ff03f [0000000-0000000]   (5)   Debug MailNotificationService.Controllers.EnsController.GetPublicKey User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Get Public Key request processed. HttpStatusCode:[InternalServerError] ResponseCode:[UpdateFail]
                2018/11/20 08:04:15.083 UAEAWMDMPAP03 656d2174-507f-4b7f-9b11-cba088a4fc6a [0000000-0000000]   (36)  Debug MailNotificationService.Controllers.EnsController.GetPublicKey User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Get Public Key request processed. HttpStatusCode:[InternalServerError] ResponseCode:[UpdateFail]
                2018/11/20 08:04:18.624 UAEAWMDMPAP03 49d055c1-9f38-41fd-88f6-51a262b9d5b1 [0000000-0000000]   (43)  Debug MailNotificationService.Controllers.EnsController.GetPublicKey User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Processing Get Public key request for Userid[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1]
                2018/11/20 08:04:59.896 UAEAWMDMPAP03 c840c28c-e8e4-49c2-ab3b-08621948dca0 [0000000-0000000]   (43)  Debug MailNotificationService.BusinessImpl.GetPublicKeyBusiness.ProcessGetPublicKeyRequestAsync User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
                2018/11/20 08:04:59.896 UAEAWMDMPAP03 c840c28c-e8e4-49c2-ab3b-08621948dca0 [0000000-0000000]   (43)  Debug MailNotificationService.Controllers.EnsController.GetPublicKey User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Get Public Key request processed. HttpStatusCode:[InternalServerError] ResponseCode:[UpdateFail]
                2018/11/20 08:05:10.076 UAEAWMDMPAP03 930ab670-3bed-4e9f-a4f2-081f4820bee7 [0000000-0000000]   (43)  Debug MailNotificationService.BusinessImpl.GetPublicKeyBusiness.ProcessGetPublicKeyRequestAsync User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
                2018/11/20 08:05:10.076 UAEAWMDMPAP03 930ab670-3bed-4e9f-a4f2-081f4820bee7 [0000000-0000000]   (43)  Debug MailNotificationService.Controllers.EnsController.GetPublicKey User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Get Public Key request processed. HttpStatusCode:[InternalServerError] ResponseCode:[UpdateFail]
                2018/11/20 08:05:18.632 UAEAWMDMPAP03 49d055c1-9f38-41fd-88f6-51a262b9d5b1 [0000000-0000000]   (43)  Debug MailNotificationService.BusinessImpl.GetPublicKeyBusiness.ProcessGetPublicKeyRequestAsync User Id:[58d0e1530b84ee4f551dfe5e36f471bebfc09f347b8439ff8859446e256d39d1] Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

                Any advise will be appreciated . We have all necessary pre-requisites in
                • 6. Re: Has anyone gotten ENS v2 to work properly on-premise?
                  hccvsphere Novice
                  NANDAGOPAL ,
                  Did AirWatch provision CNS 2.0 for your environment? An error during installation is not a good sign. Until you get a successful installation, it might indicate a pre-requisite is missing.
                  • 7. Re: Has anyone gotten ENS v2 to work properly on-premise?
                    hccvsphere Novice
                    In case this helps anyone, apparently there is an error in the installation guide for On-Premise, on page 14 specifically. It says the ENSLinkAddress is  https://ens.getboxer.com/api/ens, where ens.getboxer.com gets replaced with the resolved name or IP of the on-premise ENS server. This does not seem to be correct. It should be https://ens.getboxer.com/MailNotificationService/api/ens

                    So far it has been working. And apparently there is a known issue on Android devices.

                    Also our ENS database is in an AlwaysON Availability Group and it is working.
                    • 8. Re: Has anyone gotten ENS v2 to work properly on-premise?
                      MATTHAYSMATTHAYS1 Novice
                      Yes, thanks for the corroboration on the ENSLinkAddress url as you correctly stated as we had to open a VMware Support ticket to get that corrected.  Interested though in how SQL Always On is working for you as it doesn't for us and we found that it is not yet supported?

                      Thanks.
                      • 9. Re: Has anyone gotten ENS v2 to work properly on-premise?
                        nemanjailic Novice

                        Nemanja I. I just install ENSv2 1.3.0.2 and configure it to work with AirWatch 9.2.3. Exchange 2016. I configure everything like it is explained in installation-guide. Thing that I'm not sure is about CNS. I find in AW console that I have to download CNS Secure Channel Certificate Installer and provide it to AirWatch Support. How to do that? And, in my configuration ENS sending messages to cnsurl: https://cns.awmdm.com/nws/notify/apns . Is that right configuration? I didn't find anithyng about isntaling some CNS role on premise.


                         Thanks.

                        • 11. Re: Has anyone gotten ENS v2 to work properly on-premise?
                          hccvsphere Novice
                          Has anyone tried ENS v2 1.3.0.3? It was supposed to address a bug with Android devices, but I found that it did not fix it and in addition, it broke iOS functionality. Now I see a lot of 401 Unauthorized errors that were not there before.

                          I had to go back to 1.3.0.2 in order to get iOS notifications back at least.
                          • 12. Re: Has anyone gotten ENS v2 to work properly on-premise?
                            nemanjailic Novice

                            Ariel, Thank You for Your reply. Yes, I use that guide for installation and settings. After that, I contacted air-watch support and upload them CNS certificate, Now they replay to me that they upload Secure Channel Certificate. Everything is configured now as it should be and I procced with testing.


                            Only thing that I'm not sure that I understand is CNS 2.0?  Do I have to install it (or something) or is it enough just to set cns url?

                            • 13. Re: Has anyone gotten ENS v2 to work properly on-premise?
                              hccvsphere Novice
                              CNS 2.0 is provisioned by AirWatch. You'll need to go through some configuration steps on your Console first though.
                              • 14. Re: Has anyone gotten ENS v2 to work properly on-premise?
                                hccvsphere Novice
                                With the release of ENS v2 1.3.0.4, notifications now appear to be working reliably for both iOS and Android devices. I do not see errors being logged anymore, which is a good sign.
                                1 2 3 Previous Next