Dave
Fri Oct 24 11:20:03 CDT 2003
User accounts set up in the conventional SBS way are mail enabled. Go to
Active Directory Users and Computers. In the Users section, r-click on your
account and click properties. If you see an e-mail addresses tab, you have
a server mailbox, whether you're using it or not.
If your users really are not mail-enabled, go to ESM and click Recipient
Policy (under Recipients). You should have a policy that is named after
your server. Check the default policy to see what e-mail addresses will be
created. You'll probably have a default for SMTP of
username@yourdomain.com. If not, run the ICW to create a policy for the
domain suffix that you use for e-mail. (You can skip this whole paragraph
if you want to set up the addresses manually for each user).
To mail-enable the user accounts, r-click them in AD Users and Computers,
Exchange Tasks. A wizard will come up and one of the choices is to create a
mailbox.
You can view mailboxes in ESM under server, first storage group (drill
down - I can't remember the exact names). But, mailboxes don't show up
there until they've been "initialized" by having a message sent to them.
It sounds like your service company left a big job undone, but if you see
this through you'll have an enterprise-class mail system that will help your
company in ways you haven't even thought of yet, and you'll probably get a
raise.
"Kaj" <anonymous@discussions.microsoft.com> wrote in message
news:0bce01c39a44$7c1e4cc0$a501280a@phx.gbl...
> We do not have server mailboxes. We use email addresses
> provided by our ISP. I believe our user accounts were
> created without mailboxes. Also I am not sure that the
> company we hired to set up the SBS quite fully set up the
> Exchange server. I do see on the server a drive letter
> for exchange and a public folder under it. Can you help
> further?
> Thanks
> >-----Original Message-----
> >You can't create public folders in a PST, and for a large
> variety of reasons
> >you shouldn't be using PST's anyway. In a network with
> Exchange Server, all
> >of your users' mailboxes and public folders should be
> stored in the Exchange
> >Server database. Chances are, all of your users already
> have server
> >mailboxes, so what you need to do first is to import
> their data from the PST
> >files to the mailboxes.
> >
> >Do this on your own account first so you get used to the
> procedure. Open
> >Outlook on your desktop machine. Click view/folder
> list. At the top of the
> >list, you'll have Outlook Today [Mailbox - Username].
> That's your server
> >mailbox. Below that, you'll have a PST file, which is
> what you're using
> >now. Use the wizard at file/import and export to import
> the messages from
> >the PST to the server mailbox. Back in the folder list,
> r-click on the PST
> >and close it. Shut down Outlook. Find that PST in
> windows explorer and
> >rename it so you don't use it by mistake (when you're
> sure everything
> >worked, you can delete it completely). Go to control
> panel/mail. In your
> >profile settings, change the "deliver new e-mail to the
> following location"
> >from the PST to the Mailbox - Username entry.
> >
> >(I suppose there is a very slim chance your user accounts
> were created
> >without mailboxes, so if you don't see the Mailbox-
> Username option, post
> >back).
> >
> >Now, you're using the server mailbox instead of the PST.
> There are a
> >zillion reasons why this is better.
> >
> >To create public folders, use Outlook from your desktop
> machine. Folder
> >list again, r-click on all public folders, new. Make
> sure you choose the
> >right type - e-mail, calendar, etc. After you create the
> folder, you can
> >r-click on it to set other properties and permissions.
> >
> >Anything that can be done from Outlook on your desktop
> machine should be
> >done that way. Only use ESM on the server for settings
> like limits, etc.
> >that can't be changed using Outlook. You may not need to
> use the server for
> >any public folder administration if you don't need the
> more advanced
> >features.
> >
> >Some people (myself included) do not have problems after
> installing Outlook
> >on the server, but others do. It's not a MS-recommended
> configuration
> >because Outlook installs files that can interfere with
> Exchange Server
> >files. My advice would be to leave Outlook on the server
> since it's already
> >installed, but if you need a mail client on the server,
> use OWA.
> >
> >
> >"Kaj" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:0a5801c39a37$29e9c1d0$a501280a@phx.gbl...
> >> If I don't load Outlook on the server, how do I share
> >> contacts, calendar, tasks etc from a .pst file that all
> >> employees/groups in our company can use.
> >>
> >> >-----Original Message-----
> >> >Don't load Outlook on your server. The server should
> not
> >> be used as a
> >> >workstation!
> >> >
> >> >Marina
> >> >
> >> >"Kaj" <anonymous@discussions.microsoft.com> schreef in
> >> bericht
> >> >news:0a9701c39a33$9bd4ccd0$a401280a@phx.gbl...
> >> >> Thanks. I think I have a handle on the ICW and
> setting
> >> up
> >> >> the POP and SMTP etc. However I am royally confused
> >> with
> >> >> Outlook and Exchange. I loaded Outlook on the SB
> Server
> >> >> 2000. When I launch Outlook it looks the same as a
> >> Stand
> >> >> alone app that I have on my laptop. ie I don't see
> any
> >> of
> >> >> the Public Folders. I created a test contact folder
> and
> >> >> tried to "Send link to this folder.." but it is
> grayed
> >> >> out. What am I Missing??????
> >> >> >-----Original Message-----
> >> >> >What you're describing is the system we use here.
> Run
> >> >> the ICW to set up ISA
> >> >> >appropriately for POP incoming mail and SMTP
> outgoing.
> >> >> Then set up your
> >> >> >users' mailboxes in the POP connector using ESM.
> >> Outlook
> >> >> should point to
> >> >> >each user's server mailbox, which is where both
> >> incoming
> >> >> Internet and local
> >> >> >e-mail will end up.
> >> >> >
> >> >> >Use public folders for shared contacts and
> calendars.
> >> >> >
> >> >> >All of this is pretty well documented - check the
> SBS
> >> >> deployment docs for
> >> >> >the ICW and POP connector details. Both are pretty
> >> >> easy. The ICW has help
> >> >> >for most or all of the screens that you see while
> >> running
> >> >> it, and if you
> >> >> >mess something up, you can just run it again.
> Public
> >> >> folders are created
> >> >> >and configured from Outlook, and you can probably
> get
> >> >> details from Outlook
> >> >> >help if you need them.
> >> >> >
> >> >> >I'd take the plunge with setting this up, and post
> back
> >> >> more questions if
> >> >> >and when you run into roadblocks.
> >> >> >
> >> >> >
> >> >> >"Kaj" <kaj.patel@aesolns.com> wrote in message
> >> >> >news:0bdd01c3996f$cf836420$a301280a@phx.gbl...
> >> >> >> We have SBS2000. We have not set up Exchange and
> >> >> Outlook
> >> >> >> on it yet. I would like to set both up for shared
> >> >> >> calendaring, task management, shared contacts, IM,
> >> >> however
> >> >> >> I do not want to host our own email server. We
> use
> >> POP3
> >> >> >> email accounts provided by our ISP. Can anyone
> >> help. I
> >> >> >> have already been on MS website and went thru all
> the
> >> >> >> SBS2000 deployment guide but all seem to omit the
> >> above.
> >> >> >
> >> >> >
> >> >> >.
> >> >> >
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >