
Fixed in this release
3
Activation fixed issues
When you tried to activate a BlackBerry® device running BlackBerry® Device Software 5.0 or later with the
synchronization type of the Organizer data folder list to Device to server, the activation process stopped at 11%.
(DT 815305)
After the BlackBerry® Enterprise Server activated a new user, it did not send timezone records to the device. (DT
616535)
BlackBerry Administration Service fixed issues
If you configured a BlackBerry® Administration Service pool, in certain circumstances, one of the BlackBerry
Administration Service instances would stop processing messages, and the BlackBerry Administration Service pool
no longer performed as expected. (DT 1055331)
The BlackBerry Administration Service did not stop trying to send invalid notifications, which generated large log
files, caused performance issues, and prevented administrators from logging in. (DT 993127)
In an environment that included a large number of users and applications, the BlackBerry Administration Service
reconciled tasks slower than expected. (DT 980881)
If the BlackBerry Administration Service generated and queued a large number of tasks and the BlackBerry
Administration Service instance that started processing the tasks stopped, the processing took longer than
expected until the instance started again. (DT 968146)
In earlier releases of BlackBerry® Enterprise Server, for optimal performance, you could only install 4 BlackBerry
Administration Service instances in a pool. (DT 900359)
An issue existed in the BlackBerry Administration Service whereby proxy access configurations were not
appropriately encoded when stored in the database. (DT 894703)
If you applied the Disallow Third Party Application Downloads IT policy rule to a BlackBerry device, the BlackBerry
Administration Service created a job task to remove existing third-party and RIM add-on applications associated
with software configurations from the device. (DT 890899)
When you installed Microsoft® Office Communications Server 2007 R2 or Microsoft® Lync™ Server, and navigated
to BlackBerry Solution topology > Component view > Collaboration, the BlackBerry Administration Service listed
IBM® Lotus® Sametime® as the component name in the Instance information section. (DT 890401)
Release Notes
Fixed in this release
8
Komentarze do niniejszej Instrukcji