|
|
|
date: Mon, 1 Oct 2007 10:50:22 -0700,
group: microsoft.public.exchange.tools
back
Re: wewbe questing about Smart Phone/Blackberry users...
Well, we're up to six Blackberrys now, so the Small Business Edition of
Blackberry Server for Exchange is on its way. Any tips for a Blackberry
neophyte? Installation and administration is up to me...(this in addition to
to our existing Treo 750/WM5 units).
John
"Lanwench [MVP - Exchange]"
wrote in message
news:umyk6mT%23HHA.1168@TK2MSFTNGP02.phx.gbl...
> John Schmidt wrote:
>> I don't like it either, but while we have a dozen Treo 750's working
>> just fine with WM5 and ActiveSync, we have one manager who insisted
>> on having a Blackberry, and I'm not going to contract a Blackberry
>> Server for just one user!
>
> You can get a BES license included for 1 user, I think. But yeah, I know
> what you mean. I'd still use the web connect option rather than the
> desktop redirector, tho.
>>
>> John
>>
>> "Lanwench [MVP - Exchange]"
>> wrote in
>> message news:eMJU3f79HHA.600@TK2MSFTNGP05.phx.gbl...
>>> True, but I really don't recommend this....it doesn't work reliably,
>>> it requires that the user stay logged in all the time, and it can't
>>> be centrally managed. It's suitable for a home user, but I wouldn't
>>> use it in corporate environment.
>>>
>>> The *other* option (also clumsy) would be the Blackberry Internet
>>> Service/Web Client, which can act as a proxy for OWA. It won't do
>>> anything for contacts/calendars/tasks/notes, but for limited email,
>>> it'll work. The right way to do this is BES, or a Windows Mobile device.
>>>>
>>>> John
>>>>
>>>> "Mike Cook" wrote in message
>>>> news:917E1C1B-3573-44DA-87F9-13C3D58D661A@microsoft.com...
>>>>> Kelvin
>>>>>
>>>>> You are correct, there is additional components required.
>>>>>
>>>>> When dealing with Blackberry, you have to get the Blackberry
>>>>> Enterprise server component to support your mobile users. That is
>>>>> a piece of software that resides on a SEPARATE server and has to
>>>>> talk with a SQL 2000 or SQL 2005 backend database.
>>>>>
>>>>> If you have Windows Mobile based devices, you can just use the
>>>>> Exchange Server ActiveSync component on the Windows Mobile device
>>>>> to handle the communication.
>>>>>
>>>>> I run Exchange 2003, so I can't vouch for any improvements in the
>>>>> service in Exchange 2007, but the Windows Mobile devices were
>>>>> pretty much unmanageable when running Exchange 2003. With the
>>>>> Blackberry, you get some pretty impressive tools to ensure device
>>>>> security and enforce IT policies.
>>>>>
>>>>> My personal preference is the Windows Mobile devices. Not that the
>>>>> hardware is better, not that the administrative functions are
>>>>> easier, but because when you get an attachment to an email, you
>>>>> open it in the Pocket version of the application it was authored
>>>>> in. With Blackberry, all of the attachments must be converted on
>>>>> the Blackberry server, then streamed to the client device. The
>>>>> attachment service adds overhead on the Blackberry server, if you
>>>>> go down that route, buy large. On a side note, the Blackberry
>>>>> support team is excellent, if a little
>>>>> expensive. They will not stop until the problem you call in with
>>>>> has been resolved. You pay per year for support on the product,
>>>>> unlike calling Microsoft for a couple of hundred dollars per phone
>>>>> call. <Kelvin Beaton> wrote in message
>>>>> news:uZqUaa98HHA.1208@TK2MSFTNGP05.phx.gbl...
>>>>>> We are getting ready to install MS Exchange 2007 and our owner
>>>>>> wants a Blackberry so he can take his contacts with him and have
>>>>>> access to his email while on the road.
>>>>>>
>>>>>> I thought I had read that if Backberry user want to access the
>>>>>> Exchange Server we'd have to buy an additional module so they can
>>>>>> access the system.
>>>>>>
>>>>>> It's my understanding that Windows based Smart phone have the
>>>>>> software to access our Exchange Server built in.
>>>>>>
>>>>>> Can someone shed some light on what options we will have for
>>>>>> mobile users...
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Kelvin
>
>
>
date: Mon, 1 Oct 2007 10:50:22 -0700
author: John Schmidt
Re: wewbe questing about Smart Phone/Blackberry users...
John Schmidt wrote:
> Well, we're up to six Blackberrys now, so the Small Business Edition
> of Blackberry Server for Exchange is on its way. Any tips for a
> Blackberry neophyte? Installation and administration is up to
> me...(this in addition to to our existing Treo 750/WM5 units).
I'd personally want this on its own server. I think BB now *supports* it if
you run it on your Exchange box, but it's still not what I'd want.
>
> John
>
> "Lanwench [MVP - Exchange]"
> wrote in
> message news:umyk6mT%23HHA.1168@TK2MSFTNGP02.phx.gbl...
>> John Schmidt wrote:
>>> I don't like it either, but while we have a dozen Treo 750's working
>>> just fine with WM5 and ActiveSync, we have one manager who insisted
>>> on having a Blackberry, and I'm not going to contract a Blackberry
>>> Server for just one user!
>>
>> You can get a BES license included for 1 user, I think. But yeah, I
>> know what you mean. I'd still use the web connect option rather than
>> the desktop redirector, tho.
>>>
>>> John
>>>
>>> "Lanwench [MVP - Exchange]"
>>> wrote in
>>> message news:eMJU3f79HHA.600@TK2MSFTNGP05.phx.gbl...
>>>> True, but I really don't recommend this....it doesn't work
>>>> reliably, it requires that the user stay logged in all the time, and it
>>>> can't
>>>> be centrally managed. It's suitable for a home user, but I wouldn't
>>>> use it in corporate environment.
>>>>
>>>> The *other* option (also clumsy) would be the Blackberry Internet
>>>> Service/Web Client, which can act as a proxy for OWA. It won't do
>>>> anything for contacts/calendars/tasks/notes, but for limited email,
>>>> it'll work. The right way to do this is BES, or a Windows Mobile
>>>> device.
>>>>>
>>>>> John
>>>>>
>>>>> "Mike Cook" wrote in message
>>>>> news:917E1C1B-3573-44DA-87F9-13C3D58D661A@microsoft.com...
>>>>>> Kelvin
>>>>>>
>>>>>> You are correct, there is additional components required.
>>>>>>
>>>>>> When dealing with Blackberry, you have to get the Blackberry
>>>>>> Enterprise server component to support your mobile users. That
>>>>>> is a piece of software that resides on a SEPARATE server and has
>>>>>> to talk with a SQL 2000 or SQL 2005 backend database.
>>>>>>
>>>>>> If you have Windows Mobile based devices, you can just use the
>>>>>> Exchange Server ActiveSync component on the Windows Mobile device
>>>>>> to handle the communication.
>>>>>>
>>>>>> I run Exchange 2003, so I can't vouch for any improvements in the
>>>>>> service in Exchange 2007, but the Windows Mobile devices were
>>>>>> pretty much unmanageable when running Exchange 2003. With the
>>>>>> Blackberry, you get some pretty impressive tools to ensure device
>>>>>> security and enforce IT policies.
>>>>>>
>>>>>> My personal preference is the Windows Mobile devices. Not that
>>>>>> the hardware is better, not that the administrative functions are
>>>>>> easier, but because when you get an attachment to an email, you
>>>>>> open it in the Pocket version of the application it was authored
>>>>>> in. With Blackberry, all of the attachments must be converted on
>>>>>> the Blackberry server, then streamed to the client device. The
>>>>>> attachment service adds overhead on the Blackberry server, if you
>>>>>> go down that route, buy large. On a side note, the Blackberry
>>>>>> support team is excellent, if a little
>>>>>> expensive. They will not stop until the problem you call in with
>>>>>> has been resolved. You pay per year for support on the product,
>>>>>> unlike calling Microsoft for a couple of hundred dollars per
>>>>>> phone call. <Kelvin Beaton> wrote in message
>>>>>> news:uZqUaa98HHA.1208@TK2MSFTNGP05.phx.gbl...
>>>>>>> We are getting ready to install MS Exchange 2007 and our owner
>>>>>>> wants a Blackberry so he can take his contacts with him and have
>>>>>>> access to his email while on the road.
>>>>>>>
>>>>>>> I thought I had read that if Backberry user want to access the
>>>>>>> Exchange Server we'd have to buy an additional module so they
>>>>>>> can access the system.
>>>>>>>
>>>>>>> It's my understanding that Windows based Smart phone have the
>>>>>>> software to access our Exchange Server built in.
>>>>>>>
>>>>>>> Can someone shed some light on what options we will have for
>>>>>>> mobile users...
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Kelvin
date: Mon, 1 Oct 2007 19:14:05 -0400
author: Lanwench [MVP - Exchange]
Re: wewbe questing about Smart Phone/Blackberry users...
"John Schmidt" wrote in
news:#QGfNPFBIHA.4880@TK2MSFTNGP03.phx.gbl:
> Well, we're up to six Blackberrys now, so the Small Business Edition
> of Blackberry Server for Exchange is on its way. Any tips for a
> Blackberry neophyte? Installation and administration is up to
> me...(this in addition to to our existing Treo 750/WM5 units).
>
> John
>
> "Lanwench [MVP - Exchange]"
> wrote in
> message news:umyk6mT%23HHA.1168@TK2MSFTNGP02.phx.gbl...
>> John Schmidt wrote:
>>> I don't like it either, but while we have a dozen Treo 750's working
>>> just fine with WM5 and ActiveSync, we have one manager who insisted
>>> on having a Blackberry, and I'm not going to contract a Blackberry
>>> Server for just one user!
>>
>> You can get a BES license included for 1 user, I think. But yeah, I
>> know what you mean. I'd still use the web connect option rather than
>> the desktop redirector, tho.
>>>
>>> John
>>>
>>> "Lanwench [MVP - Exchange]"
>>> wrote in
>>> message news:eMJU3f79HHA.600@TK2MSFTNGP05.phx.gbl...
>>>> True, but I really don't recommend this....it doesn't work
>>>> reliably, it requires that the user stay logged in all the time,
>>>> and it can't be centrally managed. It's suitable for a home user,
>>>> but I wouldn't use it in corporate environment.
>>>>
>>>> The *other* option (also clumsy) would be the Blackberry Internet
>>>> Service/Web Client, which can act as a proxy for OWA. It won't do
>>>> anything for contacts/calendars/tasks/notes, but for limited email,
>>>> it'll work. The right way to do this is BES, or a Windows Mobile
>>>> device.
>>>>>
>>>>> John
>>>>>
>>>>> "Mike Cook" wrote in message
>>>>> news:917E1C1B-3573-44DA-87F9-13C3D58D661A@microsoft.com...
>>>>>> Kelvin
>>>>>>
>>>>>> You are correct, there is additional components required.
>>>>>>
>>>>>> When dealing with Blackberry, you have to get the Blackberry
>>>>>> Enterprise server component to support your mobile users. That
>>>>>> is a piece of software that resides on a SEPARATE server and has
>>>>>> to talk with a SQL 2000 or SQL 2005 backend database.
>>>>>>
>>>>>> If you have Windows Mobile based devices, you can just use the
>>>>>> Exchange Server ActiveSync component on the Windows Mobile device
>>>>>> to handle the communication.
>>>>>>
>>>>>> I run Exchange 2003, so I can't vouch for any improvements in the
>>>>>> service in Exchange 2007, but the Windows Mobile devices were
>>>>>> pretty much unmanageable when running Exchange 2003. With the
>>>>>> Blackberry, you get some pretty impressive tools to ensure device
>>>>>> security and enforce IT policies.
>>>>>>
>>>>>> My personal preference is the Windows Mobile devices. Not that
>>>>>> the hardware is better, not that the administrative functions are
>>>>>> easier, but because when you get an attachment to an email, you
>>>>>> open it in the Pocket version of the application it was authored
>>>>>> in. With Blackberry, all of the attachments must be converted on
>>>>>> the Blackberry server, then streamed to the client device. The
>>>>>> attachment service adds overhead on the Blackberry server, if you
>>>>>> go down that route, buy large. On a side note, the Blackberry
>>>>>> support team is excellent, if a little
>>>>>> expensive. They will not stop until the problem you call in with
>>>>>> has been resolved. You pay per year for support on the product,
>>>>>> unlike calling Microsoft for a couple of hundred dollars per
>>>>>> phone call. <Kelvin Beaton> wrote in message
>>>>>> news:uZqUaa98HHA.1208@TK2MSFTNGP05.phx.gbl...
>>>>>>> We are getting ready to install MS Exchange 2007 and our owner
>>>>>>> wants a Blackberry so he can take his contacts with him and have
>>>>>>> access to his email while on the road.
>>>>>>>
>>>>>>> I thought I had read that if Backberry user want to access the
>>>>>>> Exchange Server we'd have to buy an additional module so they
>>>>>>> can access the system.
>>>>>>>
>>>>>>> It's my understanding that Windows based Smart phone have the
>>>>>>> software to access our Exchange Server built in.
>>>>>>>
>>>>>>> Can someone shed some light on what options we will have for
>>>>>>> mobile users...
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Kelvin
>>
>>
>>
Load BES on it's own server if possible, certainly not of the Exchange
server. For 6 users you don't need much. I run a 12 user BES on a
standard P4 3.0Ghz, 512Mb RAM and a 40Gb disk. Just load W2K3 on it.
Make sure you load the Exchange admin tools on that server. The BES needs
to have CDO.DLL and MAPI.DLL from Exchange, and be at the same version. I
found that easiest way to do that is the load the Exchange Manager, and
apply Exchange service packs to the BES.
If you're behind a firewall, BES requires an outbound connection on port
3101 to communicate with RIM.
Other than that, it basically runs itself.
date: Fri, 19 Oct 2007 10:41:31 -0700
author: Asher_N
Re: wewbe questing about Smart Phone/Blackberry users...
This is great thread as I am in the same position. I now know about the
outbound port, but what is the inbound port? OR does the device reply to the
exchange server itself via SMTP that then gets routed to the BES?
--
Bettie
"Asher_N" wrote:
> "John Schmidt" wrote in
> news:#QGfNPFBIHA.4880@TK2MSFTNGP03.phx.gbl:
>
> > Well, we're up to six Blackberrys now, so the Small Business Edition
> > of Blackberry Server for Exchange is on its way. Any tips for a
> > Blackberry neophyte? Installation and administration is up to
> > me...(this in addition to to our existing Treo 750/WM5 units).
> >
> > John
> >
> > "Lanwench [MVP - Exchange]"
> > wrote in
> > message news:umyk6mT%23HHA.1168@TK2MSFTNGP02.phx.gbl...
> >> John Schmidt wrote:
> >>> I don't like it either, but while we have a dozen Treo 750's working
> >>> just fine with WM5 and ActiveSync, we have one manager who insisted
> >>> on having a Blackberry, and I'm not going to contract a Blackberry
> >>> Server for just one user!
> >>
> >> You can get a BES license included for 1 user, I think. But yeah, I
> >> know what you mean. I'd still use the web connect option rather than
> >> the desktop redirector, tho.
> >>>
> >>> John
> >>>
> >>> "Lanwench [MVP - Exchange]"
> >>> wrote in
> >>> message news:eMJU3f79HHA.600@TK2MSFTNGP05.phx.gbl...
> >>>> True, but I really don't recommend this....it doesn't work
> >>>> reliably, it requires that the user stay logged in all the time,
> >>>> and it can't be centrally managed. It's suitable for a home user,
> >>>> but I wouldn't use it in corporate environment.
> >>>>
> >>>> The *other* option (also clumsy) would be the Blackberry Internet
> >>>> Service/Web Client, which can act as a proxy for OWA. It won't do
> >>>> anything for contacts/calendars/tasks/notes, but for limited email,
> >>>> it'll work. The right way to do this is BES, or a Windows Mobile
> >>>> device.
> >>>>>
> >>>>> John
> >>>>>
> >>>>> "Mike Cook" wrote in message
> >>>>> news:917E1C1B-3573-44DA-87F9-13C3D58D661A@microsoft.com...
> >>>>>> Kelvin
> >>>>>>
> >>>>>> You are correct, there is additional components required.
> >>>>>>
> >>>>>> When dealing with Blackberry, you have to get the Blackberry
> >>>>>> Enterprise server component to support your mobile users. That
> >>>>>> is a piece of software that resides on a SEPARATE server and has
> >>>>>> to talk with a SQL 2000 or SQL 2005 backend database.
> >>>>>>
> >>>>>> If you have Windows Mobile based devices, you can just use the
> >>>>>> Exchange Server ActiveSync component on the Windows Mobile device
> >>>>>> to handle the communication.
> >>>>>>
> >>>>>> I run Exchange 2003, so I can't vouch for any improvements in the
> >>>>>> service in Exchange 2007, but the Windows Mobile devices were
> >>>>>> pretty much unmanageable when running Exchange 2003. With the
> >>>>>> Blackberry, you get some pretty impressive tools to ensure device
> >>>>>> security and enforce IT policies.
> >>>>>>
> >>>>>> My personal preference is the Windows Mobile devices. Not that
> >>>>>> the hardware is better, not that the administrative functions are
> >>>>>> easier, but because when you get an attachment to an email, you
> >>>>>> open it in the Pocket version of the application it was authored
> >>>>>> in. With Blackberry, all of the attachments must be converted on
> >>>>>> the Blackberry server, then streamed to the client device. The
> >>>>>> attachment service adds overhead on the Blackberry server, if you
> >>>>>> go down that route, buy large. On a side note, the Blackberry
> >>>>>> support team is excellent, if a little
> >>>>>> expensive. They will not stop until the problem you call in with
> >>>>>> has been resolved. You pay per year for support on the product,
> >>>>>> unlike calling Microsoft for a couple of hundred dollars per
> >>>>>> phone call. <Kelvin Beaton> wrote in message
> >>>>>> news:uZqUaa98HHA.1208@TK2MSFTNGP05.phx.gbl...
> >>>>>>> We are getting ready to install MS Exchange 2007 and our owner
> >>>>>>> wants a Blackberry so he can take his contacts with him and have
> >>>>>>> access to his email while on the road.
> >>>>>>>
> >>>>>>> I thought I had read that if Backberry user want to access the
> >>>>>>> Exchange Server we'd have to buy an additional module so they
> >>>>>>> can access the system.
> >>>>>>>
> >>>>>>> It's my understanding that Windows based Smart phone have the
> >>>>>>> software to access our Exchange Server built in.
> >>>>>>>
> >>>>>>> Can someone shed some light on what options we will have for
> >>>>>>> mobile users...
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>>
> >>>>>>> Kelvin
> >>
> >>
> >>
>
>
> Load BES on it's own server if possible, certainly not of the Exchange
> server. For 6 users you don't need much. I run a 12 user BES on a
> standard P4 3.0Ghz, 512Mb RAM and a 40Gb disk. Just load W2K3 on it.
> Make sure you load the Exchange admin tools on that server. The BES needs
> to have CDO.DLL and MAPI.DLL from Exchange, and be at the same version. I
> found that easiest way to do that is the load the Exchange Manager, and
> apply Exchange service packs to the BES.
>
> If you're behind a firewall, BES requires an outbound connection on port
> 3101 to communicate with RIM.
>
> Other than that, it basically runs itself.
>
>
date: Thu, 10 Jan 2008 15:04:01 -0800
author: Bettie Claxton
Re: wewbe questing about Smart Phone/Blackberry users...
A BES doesn't need an inbound port. Don't know about the US but here in
Europe al BB-traffic goes through their servers in Ireland.
A BES is also connecting with Ireland trough port 3101.
"Bettie Claxton" wrote in message
news:B5F5083D-DD11-41A0-802E-A31177291E34@microsoft.com...
> This is great thread as I am in the same position. I now know about the
> outbound port, but what is the inbound port? OR does the device reply to
> the
> exchange server itself via SMTP that then gets routed to the BES?
> --
> Bettie
>
>
> "Asher_N" wrote:
>
>> "John Schmidt" wrote in
>> news:#QGfNPFBIHA.4880@TK2MSFTNGP03.phx.gbl:
>>
>> > Well, we're up to six Blackberrys now, so the Small Business Edition
>> > of Blackberry Server for Exchange is on its way. Any tips for a
>> > Blackberry neophyte? Installation and administration is up to
>> > me...(this in addition to to our existing Treo 750/WM5 units).
>> >
>> > John
>> >
>> > "Lanwench [MVP - Exchange]"
>> > wrote in
>> > message news:umyk6mT%23HHA.1168@TK2MSFTNGP02.phx.gbl...
>> >> John Schmidt wrote:
>> >>> I don't like it either, but while we have a dozen Treo 750's working
>> >>> just fine with WM5 and ActiveSync, we have one manager who insisted
>> >>> on having a Blackberry, and I'm not going to contract a Blackberry
>> >>> Server for just one user!
>> >>
>> >> You can get a BES license included for 1 user, I think. But yeah, I
>> >> know what you mean. I'd still use the web connect option rather than
>> >> the desktop redirector, tho.
>> >>>
>> >>> John
>> >>>
>> >>> "Lanwench [MVP - Exchange]"
>> >>> wrote in
>> >>> message news:eMJU3f79HHA.600@TK2MSFTNGP05.phx.gbl...
>> >>>> True, but I really don't recommend this....it doesn't work
>> >>>> reliably, it requires that the user stay logged in all the time,
>> >>>> and it can't be centrally managed. It's suitable for a home user,
>> >>>> but I wouldn't use it in corporate environment.
>> >>>>
>> >>>> The *other* option (also clumsy) would be the Blackberry Internet
>> >>>> Service/Web Client, which can act as a proxy for OWA. It won't do
>> >>>> anything for contacts/calendars/tasks/notes, but for limited email,
>> >>>> it'll work. The right way to do this is BES, or a Windows Mobile
>> >>>> device.
>> >>>>>
>> >>>>> John
>> >>>>>
>> >>>>> "Mike Cook" wrote in message
>> >>>>> news:917E1C1B-3573-44DA-87F9-13C3D58D661A@microsoft.com...
>> >>>>>> Kelvin
>> >>>>>>
>> >>>>>> You are correct, there is additional components required.
>> >>>>>>
>> >>>>>> When dealing with Blackberry, you have to get the Blackberry
>> >>>>>> Enterprise server component to support your mobile users. That
>> >>>>>> is a piece of software that resides on a SEPARATE server and has
>> >>>>>> to talk with a SQL 2000 or SQL 2005 backend database.
>> >>>>>>
>> >>>>>> If you have Windows Mobile based devices, you can just use the
>> >>>>>> Exchange Server ActiveSync component on the Windows Mobile device
>> >>>>>> to handle the communication.
>> >>>>>>
>> >>>>>> I run Exchange 2003, so I can't vouch for any improvements in the
>> >>>>>> service in Exchange 2007, but the Windows Mobile devices were
>> >>>>>> pretty much unmanageable when running Exchange 2003. With the
>> >>>>>> Blackberry, you get some pretty impressive tools to ensure device
>> >>>>>> security and enforce IT policies.
>> >>>>>>
>> >>>>>> My personal preference is the Windows Mobile devices. Not that
>> >>>>>> the hardware is better, not that the administrative functions are
>> >>>>>> easier, but because when you get an attachment to an email, you
>> >>>>>> open it in the Pocket version of the application it was authored
>> >>>>>> in. With Blackberry, all of the attachments must be converted on
>> >>>>>> the Blackberry server, then streamed to the client device. The
>> >>>>>> attachment service adds overhead on the Blackberry server, if you
>> >>>>>> go down that route, buy large. On a side note, the Blackberry
>> >>>>>> support team is excellent, if a little
>> >>>>>> expensive. They will not stop until the problem you call in with
>> >>>>>> has been resolved. You pay per year for support on the product,
>> >>>>>> unlike calling Microsoft for a couple of hundred dollars per
>> >>>>>> phone call. <Kelvin Beaton> wrote in message
>> >>>>>> news:uZqUaa98HHA.1208@TK2MSFTNGP05.phx.gbl...
>> >>>>>>> We are getting ready to install MS Exchange 2007 and our owner
>> >>>>>>> wants a Blackberry so he can take his contacts with him and have
>> >>>>>>> access to his email while on the road.
>> >>>>>>>
>> >>>>>>> I thought I had read that if Backberry user want to access the
>> >>>>>>> Exchange Server we'd have to buy an additional module so they
>> >>>>>>> can access the system.
>> >>>>>>>
>> >>>>>>> It's my understanding that Windows based Smart phone have the
>> >>>>>>> software to access our Exchange Server built in.
>> >>>>>>>
>> >>>>>>> Can someone shed some light on what options we will have for
>> >>>>>>> mobile users...
>> >>>>>>>
>> >>>>>>> Thanks
>> >>>>>>>
>> >>>>>>> Kelvin
>> >>
>> >>
>> >>
>>
>>
>> Load BES on it's own server if possible, certainly not of the Exchange
>> server. For 6 users you don't need much. I run a 12 user BES on a
>> standard P4 3.0Ghz, 512Mb RAM and a 40Gb disk. Just load W2K3 on it.
>> Make sure you load the Exchange admin tools on that server. The BES needs
>> to have CDO.DLL and MAPI.DLL from Exchange, and be at the same version. I
>> found that easiest way to do that is the load the Exchange Manager, and
>> apply Exchange service packs to the BES.
>>
>> If you're behind a firewall, BES requires an outbound connection on port
>> 3101 to communicate with RIM.
>>
>> Other than that, it basically runs itself.
>>
>>
date: Fri, 11 Jan 2008 00:30:21 +0100
author: Gerritjan
Re: wewbe questing about Smart Phone/Blackberry users...
Thanks. It must be using SMTP then directly to the Exchange server.
--
Bettie
"Gerritjan" wrote:
> A BES doesn't need an inbound port. Don't know about the US but here in
> Europe al BB-traffic goes through their servers in Ireland.
> A BES is also connecting with Ireland trough port 3101.
>
>
> "Bettie Claxton" wrote in message
> news:B5F5083D-DD11-41A0-802E-A31177291E34@microsoft.com...
> > This is great thread as I am in the same position. I now know about the
> > outbound port, but what is the inbound port? OR does the device reply to
> > the
> > exchange server itself via SMTP that then gets routed to the BES?
> > --
> > Bettie
> >
> >
> > "Asher_N" wrote:
> >
> >> "John Schmidt" wrote in
> >> news:#QGfNPFBIHA.4880@TK2MSFTNGP03.phx.gbl:
> >>
> >> > Well, we're up to six Blackberrys now, so the Small Business Edition
> >> > of Blackberry Server for Exchange is on its way. Any tips for a
> >> > Blackberry neophyte? Installation and administration is up to
> >> > me...(this in addition to to our existing Treo 750/WM5 units).
> >> >
> >> > John
> >> >
> >> > "Lanwench [MVP - Exchange]"
> >> > wrote in
> >> > message news:umyk6mT%23HHA.1168@TK2MSFTNGP02.phx.gbl...
> >> >> John Schmidt wrote:
> >> >>> I don't like it either, but while we have a dozen Treo 750's working
> >> >>> just fine with WM5 and ActiveSync, we have one manager who insisted
> >> >>> on having a Blackberry, and I'm not going to contract a Blackberry
> >> >>> Server for just one user!
> >> >>
> >> >> You can get a BES license included for 1 user, I think. But yeah, I
> >> >> know what you mean. I'd still use the web connect option rather than
> >> >> the desktop redirector, tho.
> >> >>>
> >> >>> John
> >> >>>
> >> >>> "Lanwench [MVP - Exchange]"
> >> >>> wrote in
> >> >>> message news:eMJU3f79HHA.600@TK2MSFTNGP05.phx.gbl...
> >> >>>> True, but I really don't recommend this....it doesn't work
> >> >>>> reliably, it requires that the user stay logged in all the time,
> >> >>>> and it can't be centrally managed. It's suitable for a home user,
> >> >>>> but I wouldn't use it in corporate environment.
> >> >>>>
> >> >>>> The *other* option (also clumsy) would be the Blackberry Internet
> >> >>>> Service/Web Client, which can act as a proxy for OWA. It won't do
> >> >>>> anything for contacts/calendars/tasks/notes, but for limited email,
> >> >>>> it'll work. The right way to do this is BES, or a Windows Mobile
> >> >>>> device.
> >> >>>>>
> >> >>>>> John
> >> >>>>>
> >> >>>>> "Mike Cook" wrote in message
> >> >>>>> news:917E1C1B-3573-44DA-87F9-13C3D58D661A@microsoft.com...
> >> >>>>>> Kelvin
> >> >>>>>>
> >> >>>>>> You are correct, there is additional components required.
> >> >>>>>>
> >> >>>>>> When dealing with Blackberry, you have to get the Blackberry
> >> >>>>>> Enterprise server component to support your mobile users. That
> >> >>>>>> is a piece of software that resides on a SEPARATE server and has
> >> >>>>>> to talk with a SQL 2000 or SQL 2005 backend database.
> >> >>>>>>
> >> >>>>>> If you have Windows Mobile based devices, you can just use the
> >> >>>>>> Exchange Server ActiveSync component on the Windows Mobile device
> >> >>>>>> to handle the communication.
> >> >>>>>>
> >> >>>>>> I run Exchange 2003, so I can't vouch for any improvements in the
> >> >>>>>> service in Exchange 2007, but the Windows Mobile devices were
> >> >>>>>> pretty much unmanageable when running Exchange 2003. With the
> >> >>>>>> Blackberry, you get some pretty impressive tools to ensure device
> >> >>>>>> security and enforce IT policies.
> >> >>>>>>
> >> >>>>>> My personal preference is the Windows Mobile devices. Not that
> >> >>>>>> the hardware is better, not that the administrative functions are
> >> >>>>>> easier, but because when you get an attachment to an email, you
> >> >>>>>> open it in the Pocket version of the application it was authored
> >> >>>>>> in. With Blackberry, all of the attachments must be converted on
> >> >>>>>> the Blackberry server, then streamed to the client device. The
> >> >>>>>> attachment service adds overhead on the Blackberry server, if you
> >> >>>>>> go down that route, buy large. On a side note, the Blackberry
> >> >>>>>> support team is excellent, if a little
> >> >>>>>> expensive. They will not stop until the problem you call in with
> >> >>>>>> has been resolved. You pay per year for support on the product,
> >> >>>>>> unlike calling Microsoft for a couple of hundred dollars per
> >> >>>>>> phone call. <Kelvin Beaton> wrote in message
> >> >>>>>> news:uZqUaa98HHA.1208@TK2MSFTNGP05.phx.gbl...
> >> >>>>>>> We are getting ready to install MS Exchange 2007 and our owner
> >> >>>>>>> wants a Blackberry so he can take his contacts with him and have
> >> >>>>>>> access to his email while on the road.
> >> >>>>>>>
> >> >>>>>>> I thought I had read that if Backberry user want to access the
> >> >>>>>>> Exchange Server we'd have to buy an additional module so they
> >> >>>>>>> can access the system.
> >> >>>>>>>
> >> >>>>>>> It's my understanding that Windows based Smart phone have the
> >> >>>>>>> software to access our Exchange Server built in.
> >> >>>>>>>
> >> >>>>>>> Can someone shed some light on what options we will have for
> >> >>>>>>> mobile users...
> >> >>>>>>>
> >> >>>>>>> Thanks
> >> >>>>>>>
> >> >>>>>>> Kelvin
> >> >>
> >> >>
> >> >>
> >>
> >>
> >> Load BES on it's own server if possible, certainly not of the Exchange
> >> server. For 6 users you don't need much. I run a 12 user BES on a
> >> standard P4 3.0Ghz, 512Mb RAM and a 40Gb disk. Just load W2K3 on it.
> >> Make sure you load the Exchange admin tools on that server. The BES needs
> >> to have CDO.DLL and MAPI.DLL from Exchange, and be at the same version. I
> >> found that easiest way to do that is the load the Exchange Manager, and
> >> apply Exchange service packs to the BES.
> >>
> >> If you're behind a firewall, BES requires an outbound connection on port
> >> 3101 to communicate with RIM.
> >>
> >> Other than that, it basically runs itself.
> >>
> >>
>
>
>
date: Thu, 10 Jan 2008 15:44:00 -0800
author: Bettie Claxton
Re: wewbe questing about Smart Phone/Blackberry users...
No, it is not! Like I said it doesn't need anything else then port 3101
outbound.
> Thanks. It must be using SMTP then directly to the Exchange server.
> --
> Bettie
>
>
> "Gerritjan" wrote:
>
>> A BES doesn't need an inbound port. Don't know about the US but here in
>> Europe al BB-traffic goes through their servers in Ireland.
>> A BES is also connecting with Ireland trough port 3101.
>>
>>
>> "Bettie Claxton" wrote in
>> message
>> news:B5F5083D-DD11-41A0-802E-A31177291E34@microsoft.com...
>> > This is great thread as I am in the same position. I now know about
>> > the
>> > outbound port, but what is the inbound port? OR does the device reply
>> > to
>> > the
>> > exchange server itself via SMTP that then gets routed to the BES?
>> > --
>> > Bettie
>> >
>> >
>> > "Asher_N" wrote:
>> >
>> >> "John Schmidt" wrote in
>> >> news:#QGfNPFBIHA.4880@TK2MSFTNGP03.phx.gbl:
>> >>
>> >> > Well, we're up to six Blackberrys now, so the Small Business Edition
>> >> > of Blackberry Server for Exchange is on its way. Any tips for a
>> >> > Blackberry neophyte? Installation and administration is up to
>> >> > me...(this in addition to to our existing Treo 750/WM5 units).
>> >> >
>> >> > John
>> >> >
>> >> > "Lanwench [MVP - Exchange]"
>> >> > wrote in
>> >> > message news:umyk6mT%23HHA.1168@TK2MSFTNGP02.phx.gbl...
>> >> >> John Schmidt wrote:
>> >> >>> I don't like it either, but while we have a dozen Treo 750's
>> >> >>> working
>> >> >>> just fine with WM5 and ActiveSync, we have one manager who
>> >> >>> insisted
>> >> >>> on having a Blackberry, and I'm not going to contract a Blackberry
>> >> >>> Server for just one user!
>> >> >>
>> >> >> You can get a BES license included for 1 user, I think. But yeah, I
>> >> >> know what you mean. I'd still use the web connect option rather
>> >> >> than
>> >> >> the desktop redirector, tho.
>> >> >>>
>> >> >>> John
>> >> >>>
>> >> >>> "Lanwench [MVP - Exchange]"
>> >> >>> wrote
>> >> >>> in
>> >> >>> message news:eMJU3f79HHA.600@TK2MSFTNGP05.phx.gbl...
>> >> >>>> True, but I really don't recommend this....it doesn't work
>> >> >>>> reliably, it requires that the user stay logged in all the time,
>> >> >>>> and it can't be centrally managed. It's suitable for a home user,
>> >> >>>> but I wouldn't use it in corporate environment.
>> >> >>>>
>> >> >>>> The *other* option (also clumsy) would be the Blackberry Internet
>> >> >>>> Service/Web Client, which can act as a proxy for OWA. It won't do
>> >> >>>> anything for contacts/calendars/tasks/notes, but for limited
>> >> >>>> email,
>> >> >>>> it'll work. The right way to do this is BES, or a Windows Mobile
>> >> >>>> device.
>> >> >>>>>
>> >> >>>>> John
>> >> >>>>>
>> >> >>>>> "Mike Cook" wrote in message
>> >> >>>>> news:917E1C1B-3573-44DA-87F9-13C3D58D661A@microsoft.com...
>> >> >>>>>> Kelvin
>> >> >>>>>>
>> >> >>>>>> You are correct, there is additional components required.
>> >> >>>>>>
>> >> >>>>>> When dealing with Blackberry, you have to get the Blackberry
>> >> >>>>>> Enterprise server component to support your mobile users. That
>> >> >>>>>> is a piece of software that resides on a SEPARATE server and
>> >> >>>>>> has
>> >> >>>>>> to talk with a SQL 2000 or SQL 2005 backend database.
>> >> >>>>>>
>> >> >>>>>> If you have Windows Mobile based devices, you can just use the
>> >> >>>>>> Exchange Server ActiveSync component on the Windows Mobile
>> >> >>>>>> device
>> >> >>>>>> to handle the communication.
>> >> >>>>>>
>> >> >>>>>> I run Exchange 2003, so I can't vouch for any improvements in
>> >> >>>>>> the
>> >> >>>>>> service in Exchange 2007, but the Windows Mobile devices were
>> >> >>>>>> pretty much unmanageable when running Exchange 2003. With the
>> >> >>>>>> Blackberry, you get some pretty impressive tools to ensure
>> >> >>>>>> device
>> >> >>>>>> security and enforce IT policies.
>> >> >>>>>>
>> >> >>>>>> My personal preference is the Windows Mobile devices. Not that
>> >> >>>>>> the hardware is better, not that the administrative functions
>> >> >>>>>> are
>> >> >>>>>> easier, but because when you get an attachment to an email, you
>> >> >>>>>> open it in the Pocket version of the application it was
>> >> >>>>>> authored
>> >> >>>>>> in. With Blackberry, all of the attachments must be converted
>> >> >>>>>> on
>> >> >>>>>> the Blackberry server, then streamed to the client device. The
>> >> >>>>>> attachment service adds overhead on the Blackberry server, if
>> >> >>>>>> you
>> >> >>>>>> go down that route, buy large. On a side note, the Blackberry
>> >> >>>>>> support team is excellent, if a little
>> >> >>>>>> expensive. They will not stop until the problem you call in
>> >> >>>>>> with
>> >> >>>>>> has been resolved. You pay per year for support on the
>> >> >>>>>> product,
>> >> >>>>>> unlike calling Microsoft for a couple of hundred dollars per
>> >> >>>>>> phone call. <Kelvin Beaton> wrote in message
>> >> >>>>>> news:uZqUaa98HHA.1208@TK2MSFTNGP05.phx.gbl...
>> >> >>>>>>> We are getting ready to install MS Exchange 2007 and our owner
>> >> >>>>>>> wants a Blackberry so he can take his contacts with him and
>> >> >>>>>>> have
>> >> >>>>>>> access to his email while on the road.
>> >> >>>>>>>
>> >> >>>>>>> I thought I had read that if Backberry user want to access the
>> >> >>>>>>> Exchange Server we'd have to buy an additional module so they
>> >> >>>>>>> can access the system.
>> >> >>>>>>>
>> >> >>>>>>> It's my understanding that Windows based Smart phone have the
>> >> >>>>>>> software to access our Exchange Server built in.
>> >> >>>>>>>
>> >> >>>>>>> Can someone shed some light on what options we will have for
>> >> >>>>>>> mobile users...
>> >> >>>>>>>
>> >> >>>>>>> Thanks
>> >> >>>>>>>
>> >> >>>>>>> Kelvin
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >> Load BES on it's own server if possible, certainly not of the Exchange
>> >> server. For 6 users you don't need much. I run a 12 user BES on a
>> >> standard P4 3.0Ghz, 512Mb RAM and a 40Gb disk. Just load W2K3 on it.
>> >> Make sure you load the Exchange admin tools on that server. The BES
>> >> needs
>> >> to have CDO.DLL and MAPI.DLL from Exchange, and be at the same
>> >> version. I
>> >> found that easiest way to do that is the load the Exchange Manager,
>> >> and
>> >> apply Exchange service packs to the BES.
>> >>
>> >> If you're behind a firewall, BES requires an outbound connection on
>> >> port
>> >> 3101 to communicate with RIM.
>> >>
>> >> Other than that, it basically runs itself.
>> >>
>> >>
>>
>>
>>
date: Sat, 12 Jan 2008 00:12:42 +0100
author: Gerritjan
|
|
