What does BES 5 SP3 prepare for us?
Some time ago we installed and started testing BES 5.0.3 (SP3) on our corporate BlackBerry Enterprise server and want to talk a little about what's new for the users of our BES service after we install it in production environment (focusing on the beginning of May about).
I must say that for BES administrators, the release of this service pack is a long-awaited news, with which they pinned certain hopes. Any large server product updates — such as a BlackBerry Enterprise server — have 2 sides. One of them is important for the user of the service, because it adds new functions, improves the functioning of the existing ones, adds stability to the overall operation of the device-server bundle. The second is important for server administrators, bringing new options to management, changing (usually for the better) the work of key services, adding new elements and capabilities to an extremely rich BES server console.
Based on these two constants, we would like to highlight the changes that came with this service pack.
A very curious (and, as it seems, useful) function is called the BlackBerry Balance . I will describe its main features. For many, it is no secret that the BlackBerry smartphone connected to the BES server can be blocked or completely cleared by the BES server administrator if necessary. This is done through the so-called remote wipe option (some call it also remote kill - for what it does with the smartphone).
')
So, this operation deletes all the data on the phone and simultaneously blocks it. With the new BlackBerry Balance feature, it is possible to segregate enterprise data (actually able to represent core business value) from personal user data. Thus, custom customization will not be lost as a result of remote wipe. Of course, when the smartphone is lost, it does not make much sense to divide the data into types, but when the user saves the BlackBerry device after, say, leaving the company in which he used BES, this is valuable.
Another joyful innovation is the appearance of support for Microsoft's Office Communications Server (OCS) 2007 R2 and Lync Server 2010 . For a very long time, many companies waited for the start of OCS support and even postponed the transition to BES 5 * due to the lack of this support. It's nice that Lync server support came much faster.
This is how the OCS / Lync client finally communicates on your BlackBerry device with the OCS / Lync server.
Support has been added for S / MIME and PGP encrypted attachments, adding even more security to BES users.
User management in the console has become somewhat more convenient, sorting by columns and exporting to a csv file immediately from the search results helps in some cases :)
BlackBerry Enterprise Server has started supporting Microsoft Hyper-V Server 2008 R2 - an excellent innovation for those companies that give priority to Microsoft virtualization technologies.
The work of BES 5 with Exchange 2010 has long been, to put it mildly, a headache for the administrators managing these products. Their interoperability left much to be desired even after RIM’s declaration that the products were fully compatible. The biggest problems of mutual work of the two products were eliminated to BES 5 SP2, but from time to time the oldest and most annoying problem made itself felt - the delay in delivering messages to BlackBerry devices. This problem had several large root causes, the most recent of which is the high activity of the mailbox disk subsystem of servers on Exchange due to interaction with BES - was eliminated by the current service pack.
So now you can rightfully say that between Exchange 2010 and BES 5 * this state has occurred -
BlackBerry Enterprise Trait Tool - the Swiss knife of any self-respecting BES admin - has undergone changes and received several new features. It should be noted that this tool is not very well known among the interested public, moreover, some BES admins manage without it. However, this tool can be considered the same as for Exchange administrators is, for example, PowerShell . Yes, in terms of flexibility, they, of course, are no match, but they have in common with the fact that some of the tasks of the BES administration can be performed only with the use of this tool.
The BlackBerry MDS Integration Service (MDS-IS) has been retired, and we do not foresee any difficulties in this regard, since it was not used by anyone in the existing environment.
A large number of corrections and improvements have undergone BAS service - the main tool for managing BES server in BES of the 5th branch. This news is extremely pleasant and valuable for us, those who directly administer the server and can appreciate the work done by RIM .
Finally, BES 5.0.3 introduces several new IT policies aimed at further improving manageability and security, including a policy for managing a native client for access to SharePoint (!), Which is not there yet, but the emergence of this policy leads to good thoughts and coming soon.
Be sure to notify service users a few days before deployment and, we hope, you will also like the innovations, as we do!
I must say that for BES administrators, the release of this service pack is a long-awaited news, with which they pinned certain hopes. Any large server product updates — such as a BlackBerry Enterprise server — have 2 sides. One of them is important for the user of the service, because it adds new functions, improves the functioning of the existing ones, adds stability to the overall operation of the device-server bundle. The second is important for server administrators, bringing new options to management, changing (usually for the better) the work of key services, adding new elements and capabilities to an extremely rich BES server console.
Based on these two constants, we would like to highlight the changes that came with this service pack.
A very curious (and, as it seems, useful) function is called the BlackBerry Balance . I will describe its main features. For many, it is no secret that the BlackBerry smartphone connected to the BES server can be blocked or completely cleared by the BES server administrator if necessary. This is done through the so-called remote wipe option (some call it also remote kill - for what it does with the smartphone).
')
So, this operation deletes all the data on the phone and simultaneously blocks it. With the new BlackBerry Balance feature, it is possible to segregate enterprise data (actually able to represent core business value) from personal user data. Thus, custom customization will not be lost as a result of remote wipe. Of course, when the smartphone is lost, it does not make much sense to divide the data into types, but when the user saves the BlackBerry device after, say, leaving the company in which he used BES, this is valuable.
Another joyful innovation is the appearance of support for Microsoft's Office Communications Server (OCS) 2007 R2 and Lync Server 2010 . For a very long time, many companies waited for the start of OCS support and even postponed the transition to BES 5 * due to the lack of this support. It's nice that Lync server support came much faster.
This is how the OCS / Lync client finally communicates on your BlackBerry device with the OCS / Lync server.
Support has been added for S / MIME and PGP encrypted attachments, adding even more security to BES users.
User management in the console has become somewhat more convenient, sorting by columns and exporting to a csv file immediately from the search results helps in some cases :)
BlackBerry Enterprise Server has started supporting Microsoft Hyper-V Server 2008 R2 - an excellent innovation for those companies that give priority to Microsoft virtualization technologies.
The work of BES 5 with Exchange 2010 has long been, to put it mildly, a headache for the administrators managing these products. Their interoperability left much to be desired even after RIM’s declaration that the products were fully compatible. The biggest problems of mutual work of the two products were eliminated to BES 5 SP2, but from time to time the oldest and most annoying problem made itself felt - the delay in delivering messages to BlackBerry devices. This problem had several large root causes, the most recent of which is the high activity of the mailbox disk subsystem of servers on Exchange due to interaction with BES - was eliminated by the current service pack.
So now you can rightfully say that between Exchange 2010 and BES 5 * this state has occurred -
BlackBerry Enterprise Trait Tool - the Swiss knife of any self-respecting BES admin - has undergone changes and received several new features. It should be noted that this tool is not very well known among the interested public, moreover, some BES admins manage without it. However, this tool can be considered the same as for Exchange administrators is, for example, PowerShell . Yes, in terms of flexibility, they, of course, are no match, but they have in common with the fact that some of the tasks of the BES administration can be performed only with the use of this tool.
The BlackBerry MDS Integration Service (MDS-IS) has been retired, and we do not foresee any difficulties in this regard, since it was not used by anyone in the existing environment.
A large number of corrections and improvements have undergone BAS service - the main tool for managing BES server in BES of the 5th branch. This news is extremely pleasant and valuable for us, those who directly administer the server and can appreciate the work done by RIM .
Finally, BES 5.0.3 introduces several new IT policies aimed at further improving manageability and security, including a policy for managing a native client for access to SharePoint (!), Which is not there yet, but the emergence of this policy leads to good thoughts and coming soon.
Be sure to notify service users a few days before deployment and, we hope, you will also like the innovations, as we do!
Source: https://habr.com/ru/post/118135/
All Articles