BACKGROUND
We are migrating on-premises BlackBerry Enterprise Server/BES 5 (i.e. legacy BlackBerry devices with OS 7 or below) and Exchange servers of an enterprise with multiple domains to Exchange Online and BlackBerry Business Cloud Services/BBCS (a free component within Office 365).
They use a single Office 365 tenant contoso.com as the User Principal Name (UPN) which manages everything, including all of their email domains (contoso.com, fabrikam.com, tailspin.com, woodgrovebank.com) which they use as primary SMTP/email address for different users.
PROBLEM
We are having a problem migrating BES 5 to BBCS for some of the domains (tailspin.com, woodgrovebank.com) where Blackberry Enterprise Activation would fail with any of the below messages shown on the legacy BlackBerry devices:
On BBCS web interface, we can see that the accounts that fail show the state as “Initializing” (which should have been “No PIN” or “Running”), and mailbox agent state as “Trying to connect” (which should have been “Working”):
ADDITIONAL INFORMATION / CLUES
The domains where Enterprise Activation succeeds (contoso.com, fabrikam.com) have the following characteristics:
The domains where Enterprise Activation fails (tailspin.com, woodgrovebank.com) have the following characteristics:
For reference, below is a list of domain names in the SAN certificate: Subject Alternative Name
DNS Name=autodiscover.contoso.com
DNS Name=contoso.com
DNS Name=autodiscover.fabrikam.com
DNS Name=fabrikam.com
In other words, there is no problem activating BBCS user accounts where primary SMTP is contoso.com or fabrikam.com; the problem only occurs to those accounts where primary SMTP address is tailspin.com or woodgrovebank.com which uses CNAME and is not included in the SAN certificate.
NOTES
Any solutions/workarounds/suggestions would be appreciated.
У меня есть Microsoft и Blackberry, которые работают над одной и той же проблемой в течение последних 30 дней, и MS медлит с действием / ответом - однако в моем случае среда полностью облачная, нет миграция, без мультидоменного SSL.
Сегодня я зашел в систему, чтобы проверить, получил ли я ответ от MS - ни одного. Затем я решил ПЕРЕЗАГРУЗИТЬ ПОЛЬЗОВАТЕЛЯ в консоли BES Cloud - статус агента изменился с «Пытается подключиться» на «Выполняется», и я просто попросил клиента попробовать активировать полужирный шрифт.