Oh isn't there something about DLL's, API files etc that Outlook installs that will conflict & generally wreck havoc with Exchange installation???
Really, you don't need to have a dedicated Outlook client setup to run rules on a resource mailbox. Connect to the resource mailbox with a separate profile, (not attach to it from your Outlook profile), setup server side rules to do what you want, close and forget about it ;). I've done this on multiple resource mailboxes. Using server side rules guarantees your uptime, as long as your Exchange server is up, the rules are running and if it's down, well the mailbox isn't receiving mail...... On Mon, Jul 13, 2009 at 9:50 AM, Evan Brastow <[email protected]>wrote: > Hi guys, > > > > Yes, I know this is flame bait. > > > > Assuming adequate CPU power, is there any known reason why I couldn’t > installed Outlook 2007 on a server? It would either be a W2k3 Server domain > controller, or a W2k Server box (non-dc) running Exchange 2003 Enterprise. > I’m leaning toward putting it on the former. > > > > The purpose of this is that I have a mailbox that my customer service > people attach to that receives all of our orders-related emails. I’d like to > have a box with guaranteed uptime available to run the Outlook client on so > that it can do rule-based filing and marking of items as they come in. > > > > Downsides? > > > > Thanks for your time J > > > > Evan > > > > > > -- Sherry Abercrombie "Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
