While I live and play in the land of Apple, where rainbow-farting unicorns frolic in the meadows, I work in a Windows world. While being a card-carrying member of the International Brotherhood of Apple Pundits dictates otherwise, I don’t view Microsoft as the Great Satan; a computer is but a tool to do a job. While I believe OS X is far superior to Windows, I’m not going to think a great injustice has been done if you make me use Windows.
However, a perfect storm of circumstances has required me to work remotely a greater-than-average amount of time. Since I am rarely within arm’s reach of my MacBook, my boss was gracious enough to let me use it as my primary computer. With all the discussions on what Apple has to do to get accepted in the enterprise, I found the faults actually lay more on the Microsoft side.
One disclaimer to get out of the way: As far as our IT group is concerned, my Mac is unsupported, unsanctioned, and likely an unwelcome presence. Therefore, Mac users who are actually able to call their IT groups for support may have a different experience.
File, Print and Email
One of the enterprise-related slides in Apple’s recent WWDC keynote talked up its file and print services. I can attest to this. Getting connected to our HP color printer on Windows usually involves ritual sacrifice with two goats and a chicken; on OS X it showed up as a Bonjour printer and, boom, it worked. Apple also talked up file sharing — no, not that kind of file sharing, the kind you do in an office with servers. I’ve found connecting to Windows servers can be touchy. Sometimes it works, sometimes it doesn’t, and sometimes when it doesn’t, my domain account gets locked out. Fun times.
For email, I use Microsoft Entourage to connect to our Exchange webmail server. I connect to that rather than our internal server to make it easy for me to check email when I’m not on the corporate LAN. Unfortunately, the only way I can do global address lookups is to use this AppleScript utility. Also, because of this, when I send out meeting invites, I can’t see Free/Busy information. No biggie; I can use webmail for that if I need to.
We’re also still on Exchange 2003, so none of the Exchange enhancements in Snow Leopard will help me out.
I’m a tech writer for a large organization that uses Microsoft SharePoint as its document repository. Because it’s a Microsoft product, it pretty much refuses to play nice with any browser that’s not Internet Explorer. As a result, I can only perform the most basic of tasks. I can upload and approve documents, but I can’t edit a document directly on the server as I can if I’m accessing the library on Internet Explorer and a Microsoft SharePoint-compatible application. It’s kind of a pain downloading and re-uploading documents when the changes are relatively minor. Later this year, Microsoft is planning on adding the ability for Office 2008 to interact directly with SharePoint, so that might help.
I’m also responsible for some of the site administration tasks, and those only work under IE as well. If someone clicks on the “request access” link, I can give the proper access from the email I get. However, if I need to grant a user account access without that email, I need IE to perform that task — this has to do with how I choose the user in the browser; clicking the link in e-mail auto-populates some fields that don’t render properly. So far, the only way I can fully manage SharePoint is to run XP under Parallels.
We use a proprietary IM application that is PC-only. While employees can add my AIM account to their buddy lists, any group chat requests that originate on the corporate side don’t come across to Adium. Once again, the only solution is Parallels.
Like a lot of tech writers, I use Visio for my diagramming. I also like to embed the diagram as a Visio object in Word so it can be updated in-place without the source document. Simply put, there’s no way to replicate this functionality on the Mac. The closest I can come is using OmniGraffle Pro to create a Visio document. I’ve run into some serious compatibility issues on the Visio side during the conversion — curved lines and some fills get mangled.
Mac-PC Word transfers
With Word 2004, the only issues I ran into were Word documents with embedded Visio files. Now, with Word 2008, I haven’t noticed those problems. My standard template is somewhat complex and I’ve had zero issues going back and forth between the platforms.
While your experiences with Macs in the enterprise may vary, the more entrenched your organization is with Microsoft’s enterprise products, the harder your integration will be. While Microsoft is showing signs of realizing people use browsers other than Internet Explorer, making its products fully accessible by non-Microsoft operating systems is going to take a sea change within the company that could take years to even get started.
For me, the biggest issues are interacting with SharePoint and the lack of a true Visio application for OS X (and the ability to embed Visio drawings into Word 2008). While I’m looking forward to Microsoft improving SharePoint access with the current version, I’m hoping the next full release of Office has greater interactivity with Microsoft back-end products.
Right now, though, using my Mac in an enterprise environment means running Windows in a virtual machine to do some core tasks. That’s hardly an ideal situation.