I agree, setup rules that are not client based and setup OWA if you really want to check on the server. Then you are just using IE which is installed anyway, and rules run when the messages show up without having Outlook on the DC, or exchange server.
-----Original Message----- From: KenM [mailto:kenmli...@gmail.com] Sent: Monday, July 13, 2009 10:13 AM To: NT System Admin Issues Subject: Re: Installing Outlook 2007 on a server? I would highly recomend against either. You should not be checking mail on a DC. and outlook should not be installed on an exchange server becuase of the mapi.dll. If I were you and needed outlook to be running all the time I would create a VM or get a old workstation. On Mon, Jul 13, 2009 at 10:50 AM, Evan Brastow <ebras...@automatedemblem.com> 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 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
