Exchange question

[Moley]

Hi folks,

I work for a company which has small offices worldwide and all users individually connect to a POP/SMTP service for email and use calendar publishing built into outlook 2007 to share calendars.

The UK office that I work for is now expanding from just three of us to 10-20 people and we will be taking an office space in London and can now justify a server based IT solution rather than us all using our own laptops at home.

What I want to know is, can I use an Exchange based system for just the UK office and have it use POP/SMTP to our current ISP in order to send/receive external emails using our companies current domain.com address?

I want exchange for calendar sharing, central storage/backup of all emails and webmail - but I'm unsure if we could retain the current ISP model for the rest of the world or if we would in fact have to switch to exchange globally. We're not quite ready for that.


Thanks

 

[leigh_boy]

I would suggest you go down hosted exchange as it does not sound like you know your way around an exchange server.

but to awnser your question you start the services for pop / imap
you will need a static ip from your isp and a basic understanding of nat / firewalls to make it all work.

 

[#Chri5#]

Hi folks,

I work for a company which has small offices worldwide and all users individually connect to a POP/SMTP service for email and use calendar publishing built into outlook 2007 to share calendars.

The UK office that I work for is now expanding from just three of us to 10-20 people and we will be taking an office space in London and can now justify a server based IT solution rather than us all using our own laptops at home.

What I want to know is, can I use an Exchange based system for just the UK office and have it use POP/SMTP to our current ISP in order to send/receive external emails using our companies current domain.com address?

Thanks

You could have an Exchange Server in the UK accept e-mail for the whole company. You'd have to configure your public domain (eg abc123.com) to be an internal relay domain rather than authoritative (as below), otherwise you won't be able to exchange mails with users on the hosted server.

When you configure an internal relay domain, some or all of the recipients in this domain don't have mailboxes in this Exchange organization. Mail from the Internet is relayed for this domain through Hub Transport servers in this Exchange organization. This configuration is used in the scenarios that are described in this section.

An organization may have to share the same SMTP address space between two or more different e-mail systems. For example, you may have to share the SMTP address space between Microsoft Exchange and a third-party e-mail system, or between Exchange environments that are configured in different Active Directory forests. In these scenarios, users in each e-mail system have the same domain suffix as part of their e-mail addresses.

 

[satanicguardian]

As mentioned by leigh boy, I'd definitely go down the route of hosted exchange servers tbh. You can then use that all over the world, I highly recommend office 365, I just recently migrated my company onto it. Dead easy to administrate and maintain, very easy for users to sign on and set up mobile devices, + you can log into it from any browser window with one username and one password

 

[visibleman]

'Thirded' leigh_boy and satanicguardian's solution of using hosted exchange; certainly would the easiest and simplest solution for providing global email.

Obviously there are pro's and con's with both (internal Exchange server or hosted).