Yep, that's very close to the info that I found on Day 4 of it not working. Apparently the consultant we had doing it had never come across this issue before. LOL...and NO...it didn't take me 4 days to find the info, it took 15 minutes when I decided to try and help him out. Apparently he knew his a$$ was in a sling because the next day he put a 26'r of Single Malt Scotch on my desk! LOL!
On Wed, Aug 11, 2010 at 12:28 PM, Martin Blackstone <[email protected]>wrote: > Take a look at this: > > > http://briandesmond.com/blog/blackberry-enterprise-server-and-exchange-server-2010-throttling-policies/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+BrianDesmond+(Brian+Desmond's+Blog) > > > > *From:* Cameron [mailto:[email protected]] > *Sent:* Wednesday, August 11, 2010 9:25 AM > > *To:* MS-Exchange Admin Issues > *Subject:* Re: Exchange 2010 tools in a Exchange 2003 environment > > > > FYI - BES gotcha > > > > We just went through a very similar change...BES 4 to BES 5, Exchange 2003 > to Exchange 2003 to Exchange 2010 <and no, it's not a finger stutter!>. The > only real issue we found was with the new MAPI profile for the BESADMIN > account. It seems that it only accepts 20 connections, so 1/2 of our BES > users didn't work. You need to use a PS command to change the default > <unless I missed something> > > > > And yes, 2 days with RIM tech support didn't help either... > > On Tue, Aug 3, 2010 at 3:19 PM, Maglinger, Paul <[email protected]> > wrote: > > Good information everybody. Thanks to all! > > > -----Original Message----- > From: Paul Steele [mailto:[email protected]] > Sent: Tuesday, August 03, 2010 11:13 AM > To: MS-Exchange Admin Issues > Subject: RE: Exchange 2010 tools in a Exchange 2003 environment > > We just went through the same process. Although it is possible to do an > in place upgrade of BES and migrate all users at the same time, it > complicates things. We decided to put in a new BES server in place and > migrate users one at a time. It made the process easier for everyone. Be > warned, you will most likely need to involve BES tech support. We were > on the line with them many times during the switch. A lot of things > don't work exactly as documented (also known as buggy software). Tech > support was able to resolve all the issues though. > > -----Original Message----- > From: Martin Blackstone [mailto:[email protected]] > Sent: August-03-10 1:07 PM > To: MS-Exchange Admin Issues > Subject: RE: Exchange 2010 tools in a Exchange 2003 environment > > If you have a valid T-Support contract, you should get the Exchange 2010 > upgrade instructions from them. > > -----Original Message----- > From: Maglinger, Paul [mailto:[email protected]] > Sent: Tuesday, August 03, 2010 8:59 AM > To: MS-Exchange Admin Issues > Subject: RE: Exchange 2010 tools in a Exchange 2003 environment > > Brilliant! Thanks Martin! > > -----Original Message----- > From: Martin Blackstone [mailto:[email protected]] > Sent: Tuesday, August 03, 2010 10:50 AM > To: MS-Exchange Admin Issues > Subject: RE: Exchange 2010 tools in a Exchange 2003 environment > > This is a tough one. > BES does require the Exch 2003 tools, BUT, part of upgrading to Exch > 2010 > requires you to remove them and run on MAPI/ CDO. This worked fine for > my Exchange 2003 users. SO, YMMV. > http://www.microsoft.com/downloads/details.aspx?FamilyId=E17E7F31-079A-4 > 3A9- > BFF2-0A110307611E&displaylang=en > > > -----Original Message----- > From: Maglinger, Paul [mailto:[email protected]] > Sent: Tuesday, August 03, 2010 8:40 AM > To: MS-Exchange Admin Issues > Subject: Exchange 2010 tools in a Exchange 2003 environment > > We're in the planning stages of going from Exchange 2003 to 2010. We're > also wanting to upgrade our BES server to a system running Windows 2008. > BES requires the Exchange Tools to be installed on the server. Exchange > 2003 Tools will not install on Windows 2008. Will it work to install > the Exchange 2010 Tools on the BES server but still be running Exchange > 2003 for now? > > Paul > > > > > > > > > > >
