Yes, I've seen this a few weeks ago. Basically, if you are on a recent BES patch level, you should be good to go as it was a part of the update.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tavallali, Kevin Sent: Friday, June 10, 2011 11:07 AM To: '[email protected]' Subject: [Bes-admins] FW: BlackBerry Server Updates - Action Required by BES Administrators Before June 25, 2011 **PLEASE READ!!** Importance: High Has anyone seen or received this notice about an upgrade from RIM? We got this from our AT&T rep but nothing has been sent from RIM about this that I know of. I tried looking it up on Google but I didn't find anything. The link to the AT&T site at the bottom of the email is not even working... Kevin Tavallali IS Department Brouse McDowell 388 S. Main Street Suite 500 Akron, OH 44311-4407 Phone: 330.535.5711 Fax: 330.253.8601 www.brouse.com -----Original Message----- From: PATTEE, JASON B (ATTCINW) [mailto:[email protected]] Sent: Tuesday, May 31, 2011 11:51 AM Subject: BlackBerry Server Updates - Action Required by BES Administrators Before June 25, 2011 **PLEASE READ!!** Importance: High Good afternoon! I wanted to make sure all of you who have a BES server in the US has seen this. Please read through this message from RIM and visit the FAQ page provided by the link below if needed. Have a great day and I hope you had a great Memorial Day weekend! Jason Pattee Sales Executive [email protected]<mailto:[email protected]> Mobile: 440.522.2182/Fax: 440.716.3800 [cid:[email protected]] BlackBerry Server Updates - Action Required by BES Administrators Before June 25, 2011 Customers may need to update their firewall settings and verify that they are using the recommended BlackBerry Enterprise Server (BES) configuration in order to remain compatible with upcoming service updates. RIM is making changes to support future growth, including ongoing BlackBerry(r) Infrastructure plans. Customers must ensure that they are properly configured to take advantage of increased BlackBerry resiliency and connectivity features of the BlackBerry Infrastructure. Customers who implement the recommended configuration will also help ensure a greater continuity of service, which would be unavailable to others who are using a static IP address, or other non-recommended configuration. Customers who do not verify their configuration settings risk losing connectivity to the BlackBerry Infrastructure during upcoming service updates. If your customer has a BlackBerry Enterprise Server physically located in the U.S., they must verify their firewall and BlackBerry Enterprise Server configuration settings and make updates if they are not following the recommended settings. Customers who are allowing all the required IP address ranges through their firewall and are using the SRP address us.srp.blackberry.com will not have to make any updates. Customers who do not allow the required IP addresses through their firewalls or do not update their BlackBerry Enterprise Server configuration settings will not be able to take advantage of upcoming BlackBerry Infrastructure changes, and may lose connectivity to the BlackBerry Infrastructure. Customers who are not following the recommended configuration may not be able to automatically failover and may have to manually update to another IP address to reconnect. In some cases, if the proper IP addresses are not allowed through corporate firewalls, customers may experience delays or interruptions as their BlackBerry Enterprise Server attempts to connect to IP addresses that are not currently permitted. Please be advised that the IP addresses that supported the former Americas region will be removed from the us.srp.blackberry.com address pool on June 25, 2011. These actions must be taken by June 25, 2011 to ensure they maintain BlackBerry Enterprise Server connectivity. Call to Action: 1. Customers using BlackBerry Enterprise Servers that are physically located in the United States must ensure their BlackBerry Enterprise Server SRP settings are up to date. 2. The IP addresses, as specified in the knowledge base articles, are allowed through their corporate network firewall 3. Customers should review the Customer FAQ - BlackBerry Enterprise Server Updates document for more detailed information that may apply to their own unique BES installation. 4. Actions must be taken by June 25, 2011 to ensure they maintain BlackBerry Enterprise Server connectivity Please refer to the Customer FAQs<http://marketing.web.att.com/oil/download?oilID=9a32c2145301e9> for complete details. ***** DISCLAIMER: This electronic transmission contains confidential information from the law firm of Brouse McDowell, a Legal Professional Association. This information may be covered by the attorney-client privilege or constitute attorney work product. Information contained in this email is intended solely for the person or entity named above. If you are not the intended recipient of this communication, you hereby are notified that any dissemination, distribution, downloading, or copying of the contents is strictly prohibited and you are strictly prohibited from taking any action in reliance on the contents of this email. If you have received this communication in error, please notify us by reply email or contact the Firm's Client Support line at 330.535.5711, Ext. 311, and delete this email and destroy all copies. Thank you for your cooperation. ***** IRS Circular 230 Disclosure: To ensure compliance with U.S. Treasury rules, unless expressly stated otherwise, any U.S. tax advice contained in this communication (including attachments) is not intended or written to be used, and cannot be used, by the recipient for the purpose of avoiding penalties that may be imposed under the Internal Revenue Code. _______________________________________________ Bes-Admins mailing list [email protected] http://www.dataoutages.com/mailman/listinfo/bes-admins http://www.dataoutages.com http://www.dataoutagenews.com RSS Feed: http://feeds.feedburner.com/Bes-admins --------------------------------- Bes-Admins mailing list is sponsored by Dataoutagenews.com. http://www.dataoutagenews.com
