Blackberry PROFESSIONAL SOFTWARE FOR MICROSOFT EXCHANGE - - RELEASE NOTES Instrukcja Użytkownika Strona 39

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 66
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 38
If you attempt to push an application to multiple devices running different versions of the BlackBerry® Device Software using
the BlackBerry Administration Service, a directory should be referenced in a single line in the .alx file. For example, if the .alx
file contains the following lines, only the last line will be read by the BlackBerry Administration Service and the applicaiton
may not be successfully pushed to devices running the BlackBerry Device Software version 4.6.0. (DT 579943)
<directory _blackberryVersion="[4.5.0,4.5.1)">For_4.5.0</directory>
<directory _blackberryVersion="[4.6.0,4.6.1)">For_4.6.0</directory>
<directory _blackberryVersion="[4.6.1,4.6.2)">For_4.6.0</directory>
Workaround: Add the release version of the BlackBerry Device Software in one line. For example, list the the complete version
of BlackBerry Device Software 4.6.x in a single line in the .alx file as follows:
<directory _blackberryVersion="[4.5.0,4.5.1)">For_4.5.0</directory>
<directory _blackberryVersion="[4.6.0,4.6.2)">For_4.6.0</directory>
When you upgrade BlackBerry® Enterprise Server to 5.0 SP2, the Use persistent sockets option for the BlackBerry MDS
Connection Service is not turned on. (DT 544316)
Workaround:
1. In the BlackBerry Administration Service, navigate to BlackBerry Solution topology > BlackBerry Domain >
Component view > MDS Connection Service.
2. Select the BlackBerry MDS Connection Service instance that you want to change.
3. Click Edit instance.
4. Change Use scalable sockets to Yes.
5. Click Save.
When the BlackBerry MDS Connection Service downloads an attachment from a web server that uses HTTPS, the BlackBerry
MDS Connection Service writes an IOCancelledException error message to its log file and cannot download the attachment.
(DT 531836)
In some circumstances, you cannot push applications that rely on the vendor ID over the wireless network using the BlackBerry
Enterprise Server. The vendor ID must use a hexadecimal value for the vendor ID. (DT 522454)
After creating a certification authority profile and assigning the IT policy to the device, when a user enrolls a certificate, the
device might display a "The server is unable to find the specified certification authority profile" and not enroll the certificate.
(DT 501581)
Workaround: Wait 10 to 15 minutes and try again. This workaround might not resolve all situations.
Release Notes
BlackBerry MDS Connection Service known issues
37
Przeglądanie stron 38
1 2 ... 34 35 36 37 38 39 40 41 42 43 44 ... 65 66

Komentarze do niniejszej Instrukcji

Brak uwag