Re: How Best to Use Exchange in Our Company
- From: "Tom Bombadill" <Genius_poster@xxxxxxxxx>
- Date: Thu, 31 Jan 2008 08:27:39 -0800
Hi Owen,
It seems like the connector solution is the easiest of the 2, as I
understand it.
Let's see if I got this right. In the connctor wizard, you provide the
external email address, and that will be linked to you windows domain
account, so that when you connect to Exchange from within Outlook, that is
the email account that will be used to send and receive your email. Right?
I have a couple of questions.
1- Will the 15 min interval be enforced for sending the emails as well as
downloading them?
2- How do you enable Calendar sharing through public folders? The only way I
know is by allowing it from the source and adding it where the additional
calendar will be viewed.
3- I'm using webroot AntiSpyware + AV for the server and clients. Will that
cause any issues with Exchange? According to their tech, there should be no
issues whatsoever.
Thanks Owen!
"Owen Williams [SBS MVP]" <Owen@xxxxxxxxxxxxxxxxxx> wrote in message
news:MPG.220af5d5e61837869896ad@xxxxxxxxxxxxxxxxxxxxx
In article <#doRpS6YIHA.1208@xxxxxxxxxxxxxxxxxxxx>,
Genius_poster@xxxxxxxxx says...
My boss has decided to create an all new network based on SBS 2003 R2 SP2
Standard edition and Vista Business edition clients. The hardware is all
Dell, consisting of 1 server and 4 desktop machines.As the unofficial
network administrator, it has naturally fallen to me to make this happen.
FYI, in our existing setup all users have Internet email accounts (POP3)
managed by our hosting ompany. Everybody downloads email directly from
the
POP3 account into their Outlook. With the SBS we wish to implement
Calendar
sharing and make use of other possible features of Exchange. I have some
previous experience with Exchange, but am totally new to SBS.
In that case, pay close attention to the three rules of SBS ... Unless
there is no other way:
1. Use the wizards.
2. Use the wizards.
3. Use the wizards.
And, since you've apparently worked with Windows servers before but are
new to SBS, the following is good reading and will probably save you
from a world of hurt:
http://www.microsoft.com/Downloads/details.aspx?FamilyID=71211053-ccd6-
4f2b-bbd9-5e7b97c232ec&displaylang=en
My question is, how do you suggest Exchange be implemented in our
situation?
Please keep in mind that the Windows Domain name (MyCompany.Local) is
different than our publicly registered Internet domain name
(MyCompany.com).
I'm trying to hopefully avoid having 1 set of private/Exchange email
account
and another Public/POP3 account for each user.
There is absolutely no relationship between your internal and external
domain names, so that's not a problem. On my own server, the internal
domain is similar to: FullCompanyName.office while the external domain
is: ShortName.com.
When you Connect to the Internet in Server Manager you will be asked to
provide your public domain (MyCompany.com). Exchange Recipient Policies
will be configured to automatically give each user account both a
name@xxxxxxxxxxxxxxx and a name@xxxxxxxxxxxxx address. The primary
address will be name@xxxxxxxxxxxxx, which can be used internally with no
problems. In other words, you do NOT have to send internal mail to your
boss as boss@xxxxxxxxxxxxxxxx In fact, you will most likely not see the
e-mail address for internal users since you will select them from the
Exchange Global Address List by name.
The two preferred implementation options for Exchange are:
1. Use the POP3 Connector to retrieve the mail and change the Outlook
clients to use Exchange.
2. Switch to directly delivered SMTP mail and change the Outlook clients
to use Exchange.
The pros and cons of each have been discussed at length numerous times
in this group; you can search for posts for more information:
http://groups.google.com/group/microsoft.public.windows.server.sbs/topic
s?hl=en
You can also use both POP3 and SMTP simultaneously. I do this on my own
server, receiving business mail via SMTP and personal mail via POP3.
Most consultants consider the POP3 Connector to be a short-term
transition tool until SMTP can be implemented. While I generally agree
with that, there are specific circumstances where it makes sense to use
POP3 long-term. I have one client who has used it for the past 3 years
and, as noted above, I use it myself for personal mail.
Technically, you can setup multiple e-mail accounts in Outlook, both
POP3 and Exchange, but some people have reported problems doing this and
it can get messy. I try to avoid it.
Calendar sharing can be implemented with Public Folders or by setting up
a separate user account (just to create a mailbox) which will host the
shared calendar. Sharepoint (Companyweb) also provides some shared
calendar functionality. It depends on what you are trying to accomplish.
I usually setup a Public Folder.
-- Owen Williams [SBS MVP]
.
- Follow-Ups:
- Re: How Best to Use Exchange in Our Company
- From: Lanwench [MVP - Exchange]
- Re: How Best to Use Exchange in Our Company
- References:
- How Best to Use Exchange in Our Company
- From: Tom Bombadill
- Re: How Best to Use Exchange in Our Company
- From: Owen Williams [SBS MVP]
- How Best to Use Exchange in Our Company
- Prev by Date: Re: POP3 Connector not downloading emails
- Next by Date: Re: Policy for My Network Places
- Previous by thread: Re: How Best to Use Exchange in Our Company
- Next by thread: Re: How Best to Use Exchange in Our Company
- Index(es):
Relevant Pages
|
