Decommissioning the original Microsoft Exchange

Transcription

1 Decommissioning the original Microsoft Exchange Originally posted: March 2002 Affected software versions BlackBerry Enterprise Server version 2.0 and version 2.1 for Microsoft Exchange (all service pack releases) Summary As part of the installation process, an Administrator is required to install the BlackBerry administration on a single Microsoft Exchange Server located within an Exchange site that contains proposed BlackBerry users. These.dll files are placed in the Add-Ins folder on the installation server and are replicated to all other Microsoft Exchange Servers within the same site through the Microsoft Exchange replication process. If the original Microsoft Exchange Server, on which the BlackBerry administration are installed, is decommissioned, the following issue occurs. The BlackBerry administration are removed (through Exchange replication) from the affected Microsoft Exchange site. As a result, the BlackBerry Servers object and the BlackBerry tab within each BlackBerry enabled mailbox disappear. The BlackBerry Enterprise Server service, however, continues to function, since all of the information that it requires is stored in the administrative mailbox that is created as part of the installation process. As a side effect, the administration of the current BlackBerry user population is not possible until further actions are taken. Explanation This section describes the step-by-step procedure necessary to resolve the situation. Step 1: Record all BlackBerry Enterprise Server information 1. Open the Microsoft Exchange Administrator. 2. Connect to an existing Microsoft Exchange Server. 3. Under the appropriate Site object, select the Configuration container. 4. Double-click the BlackBerry Servers object. The BlackBerry Servers Properties window appears, as in Figure Research In Motion Limited Page 1 of 8

2 Figure 1: BlackBerry Servers Properties window 5. In the Server Config section, from the drop-down list, select the BlackBerry Enterprise Server name and click System Info. The BlackBerry Enterprise Server System Info window appears, as in Figure 2. Figure 2: BlackBerry Enterprise Server System Info window 6. In the appropriate fields, type the BlackBerry Enterprise Server name, SRP Identifier, and SRP Authentication Key. 7. Click OK. Note: The server name, SRP Identifier, and SRP Authentication Key must be typed accurately. You might want to copy and paste the above information into a.txt file for later use. Ensure that the proper information is recorded for each associated BlackBerry Enterprise Server. 8. In the BlackBerry Servers Properties window, click License Manager. The License Manager window appears, as in Figure Research In Motion Limited Page 2 of 8

3 Figure 3: License Manager window 9. In the Number of Licenses field, type the number of BlackBerry licenses in your environment. 10. Click OK. Figure 4: BlackBerry Enterprise Server System Info window Note: The License Manager is a global setting that will not affect the proper re-homing of the BlackBerry administration, or the operation of BlackBerry service. Step 2: Decommission the targeted Microsoft Exchange Server 1. Follow supported Microsoft documentation on decommissioning a Microsoft Exchange Server. Make note of the decommissioning process, if this is the first Microsoft Exchange Server in the site. 2. Wait until the replication period within the Microsoft Exchange site is complete. This may take a while, depending on your Microsoft Exchange site architecture. Step 3: Verify the absence of the BlackBerry Enterprise Server administration Assuming that the decommissioned Microsoft Exchange Server is the original server on which the BlackBerry administration are installed, verify that the are removed from all the Microsoft Exchange Servers within the affected site: 1. Open the Microsoft Exchange Administrator and verify that the BlackBerry Servers object does not appear under the Configuration container within the affected Microsoft Exchange site. 2. Repeat the above procedure by connecting to each Microsoft Exchange Server in the affected site and verifying the above to ensure that the Microsoft Exchange Server intrasite replication process is complete Research In Motion Limited Page 3 of 8

4 Step 4: Install BlackBerry Enterprise Server administration version 2.0 Service Pack 2 1. Log in to any computer on your network that is running Windows NT, using a Domain Administrator account. This is required because the installation script writes into the Add-ins folder of the targeted Microsoft Exchange Server. 2. Open the installation program from the BlackBerry Enterprise Server version 2.0 Service Pack 2 software CD or from a network drive. The installation CD home screen appears, as in Figure 5. Figure 5: Installation CD home screen 3. Click Install Microsoft Exchange Extensions. The Welcome screen appears, as in Figure 6. Figure 6: Welcome screen 4. On the Welcome screen, click Next. The Software License Agreement screen appears Research In Motion Limited Page 4 of 8

5 5. If you agree to the terms of the license agreement, click Yes. The MS Exchange Server Entry screen appears, as in Figure 7. Figure 7: MS Exchange Server Entry screen 6. In the Server field, type the name of any existing Microsoft Exchange Server within the affected site. 7. Click Next. The Choose Destination Location screen appears, as in Figure 8. Figure 8: Choose Destination Location screen 8. Click Browse, and select the folder in which you want to place the installation. 9. Click Next, the Setup Complete screen appears. 10. Click Finish Research In Motion Limited Page 5 of 8

6 Note: Wait until Microsoft Exchange has completed its intrasite replication process. You can verify this step by ensuring that the Add-Ins folder on each Microsoft Exchange Server within the target site has the proper BBMailboxExt and BBServerExt folders and all associated files. Step 5: Confirm the BlackBerry Enterprise Server administration extension installation 1. To confirm that all have been installed properly, open the Microsoft Exchange Administrator, as shown in Figure 9. Figure 9: Microsoft Exchange Administrator 2. In the left pane, select the Configuration container and, in the right pane, double-click the BlackBerry Servers icon. The BlackBerry Servers Properties window appears, as in Figure Research In Motion Limited Page 6 of 8

7 Figure 10: BlackBerry Servers Properties window Step 6: Add the BlackBerry Enterprise Server information 1. In the BlackBerry Servers Properties window, click Add Server. The BlackBerry Enterprise Server System Info window appears, as in Figure 11. Figure 11: BlackBerry Enterprise Server System Info window 2. In the fields, type the same BlackBerry Enterprise Server information that you typed earlier, and click OK Research In Motion Limited Page 7 of 8

8 Note: Type the BlackBerry Enterprise Server information carefully. For each BlackBerry Enterprise Server, typing anything other than the matching SRP Identifier forces users to insert their handhelds in the cradle to enable redirection. 3. On the BlackBerry Server Properties window, click License Manager. The License Manager window appears, as in Figure 12. Figure 12: License Manager window 4. In the Number of Licenses field, type the number of licenses in your environment, and click OK. Step 7: Test functionality Send test messages to and from BlackBerry handhelds configured on each of the BlackBerry Enterprise Servers to ascertain that everything is functioning properly. Part number: TAE Research In Motion Limited. All rights reserved. The BlackBerry and RIM families of related marks, images and symbols are the exclusive properties of Research In Motion Limited. RIM, Research In Motion, 'Always On, Always Connected', the envelope in motion symbol and the BlackBerry logo are registered with the U.S. Patent and Trademark Office and may be pending or registered in other countries. All other brands, product names, company names, trademarks and service marks are the properties of their respective owners. The handheld and/or associated software are protected by copyright, international treaties and various patents, including one or more of the following U.S. patents: 6,278,442; 6,271,605; 6,219,694; 6,075,470; 6,073,318; D,445,428; D,433,460; D,416,256. Other patents are registered or pending in various countries around the world. Please visit for a current listing of applicable patents. RESEARCH IN MOTION LIMITED (RIM) ON BEHALF OF ITSELF AND ITS AFFILIATES MAKES NO REPRESENTATIONS ABOUT THE SUITABILITY OF THE INFORMATION OR GRAPHICS CONTAINED IN THIS ADVISORY FOR ANY PURPOSE. THE CONTENT CONTAINED IN THIS DOCUMENT, INCLUDING RELATED GRAPHICS, ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. RIM HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL RIM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF INFORMATION CONTAINED HEREIN. THIS DOCUMENT, INCLUDING ANY GRAPHICS CONTINED WITHIN THE DOCUMENT, MAY CONTAIN TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. UPDATES ARE PERIODICALLY MADE TO THE INFORMATION HEREIN AND RIM MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED HEREIN AT ANY TIME Research In Motion Limited Page 8 of 8