
If the computer did not have sufficient disk space, the setup application might have stopped responding. You might
have encountered this issue if the setup application needed to install the JRE™ but there was not enough disk
space for the setup application to extract the JRE installation files. (DT 622355)
If you chose not to use a drive, the setup application still checked the drive for disk space and displayed a warning
message if the disk space requirements were not met. (DT 568730)
When you proceeded to the License dialog box or restarted the computer during the installation process, the setup
application was slow to launch and so it seemed like the setup application was not responding. In this release, the
setup application displays a progress bar. (DT 530832)
During the installation process, if you added the SRP address and BlackBerry® CAL key and then imported SRP
information from a file, the setup application did not display the SRP address or BlackBerry CAL information in the
dialog box. (DT 494069)
The setup application displayed the Database mirroring dialog box after you selected SQL authentication to connect
to the database server, even though database mirroring was not supported with SQL authentication. (DT 401891)
If you chose the database mirroring option during the installation process and the principal BlackBerry
Configuration Database was not available, the setup application stopped at the BlackBerry Monitoring Service
dialog box and wrote error messages to the log file. (DT 390871)
When the setup application backed up the krb5.conf file, MdsLogin.conf file, and rimpublic.property file, it did not
create unique file names for the backed up files and might have overwritten previous backed up files. (DT 376496)
BlackBerry Collaboration Service fixed issues
If your organization's environment included Microsoft® Office Communications Server 2007 and Microsoft® Office
Live Communications Server 2005, users on Microsoft Office Communications Server 2007 could not contact users
on Microsoft Office Live Communications Server 2005. Instead the presence showed up as Unknown. (DT 822579)
When a user activated a device and then tried to log in to Microsoft Office Communications Server 2007, the device
logged in to the instant messaging server with the selected status but then changed to the Available status within
seconds. (DT 814508)
When a device logged in to Microsoft Office Communications Server 2007, and the BlackBerry® Collaboration
Service failed over, the user could not send or receive messages except to the desktop client. The desktop client
could not reply to the BlackBerry® Client messages. (DT 788056)
Release Notes
BlackBerry Collaboration Service fixed issues
24
Komentarze do niniejszej Instrukcji