Same thing stated at WES as well...sp2 gets you R2, I think you can run
but not officially supported, much like the SQL clustering, can run but
not officially supported yet.....

 

And yes, the new can be 2003, we are currently in the same boat,
exchange 2003 and BES 4.1.6, have a new environment with 5.0.1 on
separate environment using BES Transporter to migrate, our biggest
obstacle we are dealing with now is the named property limits within
exchange 2003 being reached and causing migration issues for certain
users.

 

From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: Tuesday, June 01, 2010 2:46 PM
To: MS-Exchange Admin Issues
Subject: RE: OT - BES upgrade

 

Do you have a link? I called two weeks ago, and was told that R2 support
wouldn't be coming until 5.0 sp2.

 

Thanks.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Jeff Brown [mailto:2jbr...@gmail.com] 
Sent: Tuesday, June 01, 2010 2:39 PM
To: MS-Exchange Admin Issues
Subject: Re: OT - BES upgrade

 

RIM support told me I could run it on R2, but only with the most recent
update.

On Tue, Jun 1, 2010 at 1:29 PM, Michael B. Smith <mich...@smithcons.com>
wrote:

Not supported.

 

Regards,

 

Michael B. Smith

Consultant and Exchange MVP

http://TheEssentialExchange.com

 

From: Andy Shook [mailto:andy.sh...@peak10.com] 
Sent: Tuesday, June 01, 2010 2:29 PM


To: MS-Exchange Admin Issues

Subject: RE: OT - BES upgrade

 

Why not R2?  Inquiring minds want to know....

 

Shook

 

From: John Cook [mailto:john.c...@pfsf.org] 
Sent: Tuesday, June 01, 2010 2:27 PM
To: MS-Exchange Admin Issues
Subject: Re: OT - BES upgrade

 

Well I just suffered through this so here goes - do backups at every
stage, set up a new server (2008 SP2 not R2) if at all possible and
migrate users (RIM has a tool for this)between servers. Upgrades are
rarely clean or pretty. Open a case with RIM prior to starting, it will
help mitigate down time. 
HTH 
John W. Cook 
Systems Administrator 
Partnership for Strong Families

 

________________________________

From: Tammy George <tammy.geo...@acadiau.ca> 
To: MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> 
Sent: Tue Jun 01 14:19:25 2010
Subject: RE: OT - BES upgrade 

Yes.

 

 

From: John Cook [mailto:john.c...@pfsf.org] 
Sent: June 1, 2010 3:14 PM
To: MS-Exchange Admin Issues
Subject: Re: OT - BES upgrade

 

Running on server 2003? 
John W. Cook 
Systems Administrator 
Partnership for Strong Families

 

________________________________

From: Tammy George <tammy.geo...@acadiau.ca> 
To: MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> 
Sent: Tue Jun 01 14:12:12 2010
Subject: RE: OT - BES upgrade 

Version 4.1.6.10 and 36 users.

 

 

 

From: John Cook [mailto:john.c...@pfsf.org] 
Sent: June 1, 2010 3:06 PM
To: MS-Exchange Admin Issues
Subject: Re: OT - BES upgrade

 

What version of 4.1? You'll need to upgrade to 4.1.7 first (DB changes)
then 5. How many users? 
John W. Cook 
Systems Administrator 
Partnership for Strong Families

 

________________________________

From: Tammy George <tammy.geo...@acadiau.ca> 
To: MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> 
Sent: Tue Jun 01 13:55:48 2010
Subject: OT - BES upgrade 

Looking for any offers of advice or suggestions - 

 

I will be upgrading our BES server from 4.1 to 5.0 in preparation for
our Exchange upgrade from 2003 to 2010.  I have *no* experience with BES
so I need to familiarize myself with it first and go from there.   Lots
to learn!

 

Just wondering if anyone is familiar with useful lists or forums?  Is
the process straightforward or complex?

 

If there's anything at all that you'd be willing to share to get me
started, it would be greatly appreciated!

 

Thanks in advance.

 

 

-- 

Tammy George

Sr. Systems Operator

Technology Services

Acadia University

tel: (902) 585-1158

fax: (902) 585-1066

 

 

________________________________

CONFIDENTIALITY STATEMENT: The information transmitted, or contained or
attached to or with this Notice is intended only for the person or
entity to which it is addressed and may contain Protected Health
Information (PHI), confidential and/or privileged material. Any review,
transmission, dissemination, or other use of, and taking any action in
reliance upon this information by persons or entities other than the
intended recipient without the express written consent of the sender are
prohibited. This information may be protected by the Health Insurance
Portability and Accountability Act of 1996 (HIPAA), and other Federal
and Florida laws. Improper or unauthorized use or disclosure of this
information could result in civil and/or criminal penalties.
Consider the environment. Please don't print this e-mail unless you
really need to.

This email and any attached files are confidential and intended solely
for the intended recipient(s). If you are not the named recipient you
should not read, distribute, copy or alter this email. Any views or
opinions expressed in this email are those of the author and do not
represent those of the company. Warning: Although precautions have been
taken to make sure no viruses are present in this email, the company
cannot accept responsibility for any loss or damage that arise from the
use of this email or attachments.

 

________________________________

CONFIDENTIALITY STATEMENT: The information transmitted, or contained or
attached to or with this Notice is intended only for the person or
entity to which it is addressed and may contain Protected Health
Information (PHI), confidential and/or privileged material. Any review,
transmission, dissemination, or other use of, and taking any action in
reliance upon this information by persons or entities other than the
intended recipient without the express written consent of the sender are
prohibited. This information may be protected by the Health Insurance
Portability and Accountability Act of 1996 (HIPAA), and other Federal
and Florida laws. Improper or unauthorized use or disclosure of this
information could result in civil and/or criminal penalties.
Consider the environment. Please don't print this e-mail unless you
really need to.

This email and any attached files are confidential and intended solely
for the intended recipient(s). If you are not the named recipient you
should not read, distribute, copy or alter this email. Any views or
opinions expressed in this email are those of the author and do not
represent those of the company. Warning: Although precautions have been
taken to make sure no viruses are present in this email, the company
cannot accept responsibility for any loss or damage that arise from the
use of this email or attachments.

 

________________________________

CONFIDENTIALITY STATEMENT: The information transmitted, or contained or
attached to or with this Notice is intended only for the person or
entity to which it is addressed and may contain Protected Health
Information (PHI), confidential and/or privileged material. Any review,
transmission, dissemination, or other use of, and taking any action in
reliance upon this information by persons or entities other than the
intended recipient without the express written consent of the sender are
prohibited. This information may be protected by the Health Insurance
Portability and Accountability Act of 1996 (HIPAA), and other Federal
and Florida laws. Improper or unauthorized use or disclosure of this
information could result in civil and/or criminal penalties.
Consider the environment. Please don't print this e-mail unless you
really need to.

This email and any attached files are confidential and intended solely
for the intended recipient(s). If you are not the named recipient you
should not read, distribute, copy or alter this email. Any views or
opinions expressed in this email are those of the author and do not
represent those of the company. Warning: Although precautions have been
taken to make sure no viruses are present in this email, the company
cannot accept responsibility for any loss or damage that arise from the
use of this email or attachments.

 

Reply via email to