Exchange 2003 setup question

Hi,
I am planning on moving my small company (30 users) from having our e-mail
hosted by our ISP to Exchange 2003. I have SBS 2003 with Exchange, as well
as Exchange 2003 installed on another Windows 2003 Server. The reason for
having both, is I really want to use the Windows 2003 Server with Exchange
rather than the SBS2003 Server because it already has a load of apps on it,
and the Windows 2003 Server has more memory and disk space, but it's part of
SBS, so I left it installed.
Anyway, I'm looking for advice on the steps I need to take to make this a
smooth transition and which Server I should use. All users have Outlook 2003
and are pointed directly to the ISP's POP3 and SMTP servers.
Looking at the Exchange Deployment Guide, it talks about migrating from
older versions of Exchange, but I don't see anything with regard to bringing
e-mail into Exchange from being hosted by our ISP. Any advice? -Mike

NA
Tue Aug 23 11:11:19 CDT 2005

> Looking at the Exchange Deployment Guide, it talks about migrating from
> older versions of Exchange, but I don't see anything with regard to
> bringing
> e-mail into Exchange from being hosted by our ISP. Any advice? -Mike

Mike,
This is going to take a little work on your part. Go to each
workstation
and add a PST file to the profile if they don't already have one. Copy all
their email to the PST entry. Take note of the path to their pst file.
Go to the control panel and blow away their profile. Create a new one
connecting to an Exchange Server and add the pst file reference.

In the future I suggest you look at this product for maintenance.
Outlook Profiler
http://goffconcepts.com/products/windows/profiler/index.html


Helpful Hints:
GOFF Concepts

Mike
Tue Aug 23 12:31:14 CDT 2005

Hi, Thanks for the response. If this response to your answer sounds silly,
please forgive me, I'm just learning about Exchange. Each user has an
outlook.pst file where their email/contacts/calendar reside on a server, and
their Outlook on their desktop points to the location on the server where
their .pst file resides. With that setup, would I still need to create one?

Mike


"NA" wrote:

> > Looking at the Exchange Deployment Guide, it talks about migrating from
> > older versions of Exchange, but I don't see anything with regard to
> > bringing
> > e-mail into Exchange from being hosted by our ISP. Any advice? -Mike
>
> Mike,
> This is going to take a little work on your part. Go to each
> workstation
> and add a PST file to the profile if they don't already have one. Copy all
> their email to the PST entry. Take note of the path to their pst file.
> Go to the control panel and blow away their profile. Create a new one
> connecting to an Exchange Server and add the pst file reference.
>
> In the future I suggest you look at this product for maintenance.
> Outlook Profiler
> http://goffconcepts.com/products/windows/profiler/index.html
>
>
> Helpful Hints:
> GOFF Concepts
>
>
>

Al
Tue Aug 23 12:54:14 CDT 2005

If that's the case, then you *could* create a new profile for the users, and
attach the existing PST to the new profile. The reason to do this is
because the mail already resides in the inbox (as of the last download
anyway; that's why you'll want to move the MX records for the domain before
doing this to ensure new mail is delivered to the mailbox on the Exchange
server) and you don't want to have the client pulling POP from one account
and pulling mail from another. There is an issue with Outlook if you do
this, although it has to do with the sending vs. the receiving.

As for the resources, you can import the PST to the mailbox if you want, but
I would guess that just importing the calendar and task items would be more
than you need. Legacy mail is still available to the users in the PST so it
provides them with a clean start to the mailboxes.

Al

"Mike" <Mike@discussions.microsoft.com> wrote in message
news:9F252003-3251-42FC-811A-8BF03998D6B2@microsoft.com...
> Hi, Thanks for the response. If this response to your answer sounds
> silly,
> please forgive me, I'm just learning about Exchange. Each user has an
> outlook.pst file where their email/contacts/calendar reside on a server,
> and
> their Outlook on their desktop points to the location on the server where
> their .pst file resides. With that setup, would I still need to create
> one?
>
> Mike
>
>
> "NA" wrote:
>
>> > Looking at the Exchange Deployment Guide, it talks about migrating from
>> > older versions of Exchange, but I don't see anything with regard to
>> > bringing
>> > e-mail into Exchange from being hosted by our ISP. Any advice? -Mike
>>
>> Mike,
>> This is going to take a little work on your part. Go to each
>> workstation
>> and add a PST file to the profile if they don't already have one. Copy
>> all
>> their email to the PST entry. Take note of the path to their pst file.
>> Go to the control panel and blow away their profile. Create a new one
>> connecting to an Exchange Server and add the pst file reference.
>>
>> In the future I suggest you look at this product for maintenance.
>> Outlook Profiler
>> http://goffconcepts.com/products/windows/profiler/index.html
>>
>>
>> Helpful Hints:
>> GOFF Concepts
>>
>>
>>

Mike
Wed Aug 24 05:48:03 CDT 2005

Al,

Just so I understand correctly, are you saying, just to set up new Exchange
mailboxes for all the users, have the ISP change the MX records to point to
my server instead of theirs, and let "new" mail start flowing to the Exchange
mailboxes as a clean start. Then the user's outlook.pst file can be like an
archived mailbox still availble to them through outlooks 2003? Do I have to
do something to make this happen? Do I have to do something to the users
machines to change it from IMO to the Corporate/Workgroup setting as well?
Thanks,
Mike


"Al Mulnick" wrote:

> If that's the case, then you *could* create a new profile for the users, and
> attach the existing PST to the new profile. The reason to do this is
> because the mail already resides in the inbox (as of the last download
> anyway; that's why you'll want to move the MX records for the domain before
> doing this to ensure new mail is delivered to the mailbox on the Exchange
> server) and you don't want to have the client pulling POP from one account
> and pulling mail from another. There is an issue with Outlook if you do
> this, although it has to do with the sending vs. the receiving.
>
> As for the resources, you can import the PST to the mailbox if you want, but
> I would guess that just importing the calendar and task items would be more
> than you need. Legacy mail is still available to the users in the PST so it
> provides them with a clean start to the mailboxes.
>
> Al
>
> "Mike" <Mike@discussions.microsoft.com> wrote in message
> news:9F252003-3251-42FC-811A-8BF03998D6B2@microsoft.com...
> > Hi, Thanks for the response. If this response to your answer sounds
> > silly,
> > please forgive me, I'm just learning about Exchange. Each user has an
> > outlook.pst file where their email/contacts/calendar reside on a server,
> > and
> > their Outlook on their desktop points to the location on the server where
> > their .pst file resides. With that setup, would I still need to create
> > one?
> >
> > Mike
> >
> >
> > "NA" wrote:
> >
> >> > Looking at the Exchange Deployment Guide, it talks about migrating from
> >> > older versions of Exchange, but I don't see anything with regard to
> >> > bringing
> >> > e-mail into Exchange from being hosted by our ISP. Any advice? -Mike
> >>
> >> Mike,
> >> This is going to take a little work on your part. Go to each
> >> workstation
> >> and add a PST file to the profile if they don't already have one. Copy
> >> all
> >> their email to the PST entry. Take note of the path to their pst file.
> >> Go to the control panel and blow away their profile. Create a new one
> >> connecting to an Exchange Server and add the pst file reference.
> >>
> >> In the future I suggest you look at this product for maintenance.
> >> Outlook Profiler
> >> http://goffconcepts.com/products/windows/profiler/index.html
> >>
> >>
> >> Helpful Hints:
> >> GOFF Concepts
> >>
> >>
> >>
>
>
>

Al
Wed Aug 24 06:21:25 CDT 2005

I don't know how exactly the desktops are setup now, but basically yes,
that's what you'd have to do. Corporate mode == mapi access.
The important bit after that is to make sure you take care to choreograph
the move so that you don't strand mail in the ISP mailbox.

Al


"Mike" <Mike@discussions.microsoft.com> wrote in message
news:BF47C668-1977-450B-8706-C9DE76DFCEAB@microsoft.com...
> Al,
>
> Just so I understand correctly, are you saying, just to set up new
> Exchange
> mailboxes for all the users, have the ISP change the MX records to point
> to
> my server instead of theirs, and let "new" mail start flowing to the
> Exchange
> mailboxes as a clean start. Then the user's outlook.pst file can be like
> an
> archived mailbox still availble to them through outlooks 2003? Do I have
> to
> do something to make this happen? Do I have to do something to the users
> machines to change it from IMO to the Corporate/Workgroup setting as well?
> Thanks,
> Mike
>
>
> "Al Mulnick" wrote:
>
>> If that's the case, then you *could* create a new profile for the users,
>> and
>> attach the existing PST to the new profile. The reason to do this is
>> because the mail already resides in the inbox (as of the last download
>> anyway; that's why you'll want to move the MX records for the domain
>> before
>> doing this to ensure new mail is delivered to the mailbox on the Exchange
>> server) and you don't want to have the client pulling POP from one
>> account
>> and pulling mail from another. There is an issue with Outlook if you do
>> this, although it has to do with the sending vs. the receiving.
>>
>> As for the resources, you can import the PST to the mailbox if you want,
>> but
>> I would guess that just importing the calendar and task items would be
>> more
>> than you need. Legacy mail is still available to the users in the PST so
>> it
>> provides them with a clean start to the mailboxes.
>>
>> Al
>>
>> "Mike" <Mike@discussions.microsoft.com> wrote in message
>> news:9F252003-3251-42FC-811A-8BF03998D6B2@microsoft.com...
>> > Hi, Thanks for the response. If this response to your answer sounds
>> > silly,
>> > please forgive me, I'm just learning about Exchange. Each user has an
>> > outlook.pst file where their email/contacts/calendar reside on a
>> > server,
>> > and
>> > their Outlook on their desktop points to the location on the server
>> > where
>> > their .pst file resides. With that setup, would I still need to create
>> > one?
>> >
>> > Mike
>> >
>> >
>> > "NA" wrote:
>> >
>> >> > Looking at the Exchange Deployment Guide, it talks about migrating
>> >> > from
>> >> > older versions of Exchange, but I don't see anything with regard to
>> >> > bringing
>> >> > e-mail into Exchange from being hosted by our ISP. Any
>> >> > dvice? -Mike
>> >>
>> >> Mike,
>> >> This is going to take a little work on your part. Go to each
>> >> workstation
>> >> and add a PST file to the profile if they don't already have one. Copy
>> >> all
>> >> their email to the PST entry. Take note of the path to their pst file.
>> >> Go to the control panel and blow away their profile. Create a new one
>> >> connecting to an Exchange Server and add the pst file reference.
>> >>
>> >> In the future I suggest you look at this product for maintenance.
>> >> Outlook Profiler
>> >> http://goffconcepts.com/products/windows/profiler/index.html
>> >>
>> >>
>> >> Helpful Hints:
>> >> GOFF Concepts
>> >>
>> >>
>> >>
>>
>>
>>