Stuff that you said I don't know what is: EAS? CAS? We're running E2k3 Enterprise in each office, no FE. I have RPC/HTTPS running for most of the US company-issued laptops - haven't extended that to the other offices yet.
Stuff that I don't think you addressed, but I could be wrong: How do I centrally manage the devices - remote kill, ensure that only company-issued devices are used, etc., and how do I ensure that data at rest on the devices is secure? Kurt On Wed, Sep 3, 2008 at 7:16 PM, Michael B. Smith <[EMAIL PROTECTED]> wrote: > You enable/disable it per user (2003/2007). > > You establish policies and assign them to a user (2007). > > You have them configure their phones to access their regional mail server > (if your Exchange server is regionalized). > > EAS is enabled by default on any CAS (Exchange 2007) or FE (Exchange 2003) > server. > > Regards, > > Michael B. Smith > MCITP:SA,EMA/MCSE/Exchange MVP > http://TheEssentialExchange.com > > > -----Original Message----- > From: Kurt Buff [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 03, 2008 10:10 PM > To: MS-Exchange Admin Issues > Subject: Re: Blackberry, or something else? > > I'm willing to listen... > > How does that work? How do I manage it across three countries? What > else do I need to know? > > Kurt > > On Wed, Sep 3, 2008 at 7:08 PM, Michael B. Smith > <[EMAIL PROTECTED]> wrote: >> Bah humbug. I drink the Windows Mobile kool-aid instead of the BES > kool-aid. >> >> Just make sure your devices are WM 6.1. :-) >> >> (I just had to throw in an opposing opinion.) >> >> Regards, >> >> Michael B. Smith >> MCITP:SA,EMA/MCSE/Exchange MVP >> http://TheEssentialExchange.com >> >> >> -----Original Message----- >> From: Kurt Buff [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, September 03, 2008 9:51 PM >> To: MS-Exchange Admin Issues >> Subject: Re: Blackberry, or something else? >> >> Interesting. So it would seem that BES uses SQL as a backend for >> Exchange integration. >> >> The latency for our AU and UK offices is pretty consistently between >> 100-200ms, with regular spikes to above 500ms. That could prove >> interesting. >> >> Kurt >> >> On Wed, Sep 3, 2008 at 6:28 PM, Barsodi.John <[EMAIL PROTECTED]> wrote: >>> To add, I'm a huge BES fan as well. >>> >>> I have 7 BES servers worldwide...including the countries you have offices >> in. You need to keep your BES server as close to your Exchange server as >> possible, which would make sharing SQL difficult as Don suggested. You'll >> run into worker thread errors if you have high latency between BES & >> Exchange. I've gotten RIM support to confirm up to 300ms max, ideally >> nothing over 35ms. >>> >>> - John Barsodi >>> >>> -----Original Message----- >>> From: Don Andrews [mailto:[EMAIL PROTECTED] >>> Sent: Wednesday, September 03, 2008 6:11 PM >>> To: MS-Exchange Admin Issues >>> Subject: Re: Blackberry, or something else? >>> >>> Your mantra is spot on! >>> >>> I'll say up front that I'm a BES fan. The only limiting factor I can > think >> of is that in order to manage the whole environment as one is the need to >> share a SQL database across all your BES'. I'd think a sales support type >> could assist with some recommendations, trade offs etc. >>> >>> --------------------------------- >>> Sent from my BlackBerry Wireless Handheld >>> >>> ----- Original Message ----- >>> From: Kurt Buff <[EMAIL PROTECTED]> >>> To: MS-Exchange Admin Issues <exchangelist@lyris.sunbelt-software.com> >>> Sent: Wed Sep 03 18:51:46 2008 >>> Subject: Re: Blackberry, or something else? >>> >>> Yes, I'm all over the policy thing. Fortunately, I haven't yet set up >>> OMA/ActiveSynch/IMAP-over-SSL/whatever, and the migration from >>> Exchange 5.5 cut off the IMAP and POP for everyone - by design! - so >>> there has been some howling about that. >>> >>> I'm now almost ready to throw the bone to the crowd, but I want it to >>> be the right bone in the right way. >>> >>> Centrally managed on company-issued devices only - that's my mantra. I >>> want the data secure both in transit and at rest. >>> >>> Kurt >>> >>> On Wed, Sep 3, 2008 at 4:59 PM, Troy Meyer <[EMAIL PROTECTED]> >> wrote: >>>> Hey Kurt, >>>> >>>> Any set of devices might work for you, if you guys have money, go with >> Blackberry and BES because its got a nice central management for what you >> are looking for. >>>> >>>> I would say put more effort into shaping policy than worrying about >> phones. We made that mistake about 2 years ago and found ourselves with 3 >> mobile mail solutions (activesync, goodlink, BES) and phones from all > sorts >> of vendors and providers and it's a support nightmare. (try telling the > one >> exec using a Palm 600 he needs to upgrade or move to a blackberry). I > also >> wish we had set policy in the beginning regarding security and encryption >> because its always harder retroactively. >>>> >>>> Note: I was not employed here during original implementation, but would >> have loved to be in your position to consider all of the policy side > before >> implementation. >>>> >>>> -troy >>>> >>>> >>>> -----Original Message----- >>>> From: Kurt Buff [mailto:[EMAIL PROTECTED] >>>> Sent: Wednesday, September 03, 2008 4:54 PM >>>> To: MS-Exchange Admin Issues >>>> Subject: Blackberry, or something else? >>>> >>>> All, >>>> >>>> I'm getting a lot of pressure to get mobile devices to users in our >>>> US, UK and AU offices. As you might imagine, the sales staff in the AU >>>> and UK offices travel internationally quite a bit, so I have to think >>>> beyond the boundaries of those countries, into Europe and Asia. Sales >>>> and other mobile staff would total perhaps 50-75 people worldwide. >>>> >>>> We have E2k3 servers in each office, but I want central control - the >>>> ability to remote kill and otherwise manage this, if possible. >>>> >>>> What have been your experiences - and what would you recommend? >>>> >>>> I haven't worked with Blackberry or anything else mobile for Exchange >>>> before, so am more than a bit uncertain about this, especially the >>>> risk to company data on these things floating around. >>>> >>>> Any help much appreciated. >>>> >>>> Kurt >>>> >>>> ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ >>>> ~ http://www.sunbeltsoftware.com/Ninja ~ >>>> >>>> ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ >>>> ~ http://www.sunbeltsoftware.com/Ninja ~ >>>> >>> >>> ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ >>> ~ http://www.sunbeltsoftware.com/Ninja ~ >>> >>> >>> ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ >>> ~ http://www.sunbeltsoftware.com/Ninja ~ >>> >>> ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ >>> ~ http://www.sunbeltsoftware.com/Ninja ~ >> >> ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ >> ~ http://www.sunbeltsoftware.com/Ninja ~ >> >> >> ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ >> ~ http://www.sunbeltsoftware.com/Ninja ~ >> > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > ~ http://www.sunbeltsoftware.com/Ninja ~ > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > ~ http://www.sunbeltsoftware.com/Ninja ~ > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
