BPS is identical to BES with some MDS restrictions and currently does
not support HTML email.  Big features we have been SCREAMING for for
months.  If you want HTML, Full BES is the only option.  No eta except
first quarter for an upgrade to BPS.

 

From: Jim Majorowicz [mailto:[email protected]] 
Sent: Wednesday, December 17, 2008 3:27 PM
To: NT System Admin Issues
Subject: RE: Blackberry Storm Upgrade

 

That's how I setup users after I add them, so it sounds like my plan
should work.  I'll find out tomorrow morning.

 

From: David Mazzaccaro [mailto:[email protected]] 
Sent: Tuesday, December 16, 2008 9:09 AM
To: NT System Admin Issues
Subject: RE: Blackberry Storm Upgrade

 

If BPS is anything like BES, all I do is right-click on the user in BES,
and select "set activation password".

I then type in any password, and on the device, go through enterprise
activation.

For this, all you need is their email address, and the password you
created in the BES.

HTH

 

 

________________________________

From: Jim Majorowicz [mailto:[email protected]] 
Sent: Tuesday, December 16, 2008 11:59 AM
To: NT System Admin Issues
Subject: Blackberry Storm Upgrade

I've got a client that uses the Blackberry Professional Software 4.1.4.2
on a Windows 2003 SBS to connect his 8830 to the Exchange.  He is the
only user on the server.  He's getting ready to upgrade to a Storm.
Depending on what I read, where, it will work with the latest firmware
on the Storm, but he'll lose HTML email, something I don't think he knew
he was getting.

 

Normally, when a client gets a new Blackberry and wants to get it setup
on his server, I just delete him as a user and re-add him then provision
the Blackberry as if it's the first time the user been connected.  I'm
wondering if that's the best course of action here or if I should do
something different.  Anything anyone could add would be helpful.

 

I was not the person who setup the BPS.  The technician who set it up
put the software on the wrong server (Despite my explicit instructions)
and caused a real mess when it was added.  The user is understandably a
bit gun shy about the process, he knows this could get a bit messy, but
I want to try and make this as painless as possible.

 

 

 

 

 

 

 

 

 

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to