Entourage has always been the biggest Mac-related pain I have to deal with*. Local user mail databases get hosed and have to be rebuilt all the time, though I haven't ever had it trash an Exchange mailbox. That would be the end of it for me, and I'd seriously think about using my long-saved deviance credits to banish it once and for all.
But, (there's always a but...) There is *supposed* to be a better way to connect Entourage to Exchange than WebDAV in something called "Entourage 2008, Web Services Edition", but we can't use it. We're still on Exchange 2003 and it requires 2007. * A close second would be Mac fonts and whatnot where the important stuff is actually stored in the resource fork. You have to be very careful storing these on Windows shares or you can lose them. From: Eric Woodford [mailto:ericwoodf...@gmail.com] Sent: Friday, October 23, 2009 2:03 PM To: NT System Admin Issues Subject: Re: Ammo for apple mac sales pitch I don't know much myself about Mac's. From my off-hand experience trying to help wife (on her school provided machine), I've found that: 1. It appears that they don't logon to an AD domain. Maybe just the schools implementation of low bandwidth to schools. 2. Entourage (Mac Exchange client) uses ActiveSync so your users will need duel logon. 3. My wife's school district hasn't implemented password security, so she's had the same password since she started 7years ago. Guessing this is because she doesn't actually logon to AD, so she can't change it by herself? 4. Corporate experience - our Mac tech at a former employer would just wipe and rebuild the machines each time they had technical issues. Further, he'd ask for the mailbox to be rebuilt (delete/recreate on server) as it appeared Entourage would corrupt it (E2003). On Thu, Oct 22, 2009 at 4:24 PM, Glen Johnson <gjohn...@vhcc.edu> wrote: Our boss wants my assistant and me to meet with a rep who wants us to put in some macs. We are a %100 windows shop, no mac experience and with only two of us, we really don't want any more added to our overloaded plates. Other than the cost to train one or both of us, cost for some centralized patching, centralized management, what other reasons can yall recommend we use to prevent this from happening. I don't want to be dishonest with him, but I would hate to see this dumped on us without us presenting all the valid reasons we can come up with. We have a windows 2008 domain and I think you have to turn on some less secure authentication in the domain to allow them to login. Anyone know if that is correct? What about centralized password policies, screen savers, and such? Thanks for any ammo anyone cares to provide. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
