I'm working with a small business located in a very rural area where the only high-speed Internet available is satellite. They currently have about 5 computers, all running Windows XP pro with POP3 email addresses provided by their previous dial-up ISP. The intent was to setup a single powerful server to initially share files centrally, while later using Exchange for email, shared contacts, calendars, etc.
I wanted to install the server with the least amount of disruption to users while one by one implementing and testing services. The wizard-oriented nature of SBS essentially requires you to "homerun" nearly the entire process of implementing the server. I didn't want to risk taking down the whole network by letting SBS change the settings on the router, automatically take control of DHCP, DNS, email, My Documents redirection, etc. In addition, the wizards don't always work. In my case, the connect computer wizard, on 3 of the 5 machines, did not successfully transfer the users profiles over to the newly created domain accounts. So, I have thus far avoided certain wizards and been OK.
My question now is regarding Exchange. I have read many posts stating that POP3 connectors are terrible, you MUST run the Internet Connect and Email Wizard to use them, etc. Currently the Outlook clients are still setup with their POP and SMTP settings from pre-existing dial-up email addresses and working OK as far as I can see. Should I want to move one "shared" account to a POP3 connector on the server so everyone can view the inbox, is it impossible to do it manually in Exchange System Manager or just strongly discouraged? Secondly, is it still more ideal to use Exchange purely even on this slow satellite connection? The ISP-hosted email also has strong SPAM filtering that would go away in the event that I switch to the Exchange SMTP server and change the MX records. What is the best setup in this situation?