• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 297
  • Last Modified:

Exchange Server Implementation

Hi,

We are about to embark on setting up an Exchange Server company-wide, & I have no experience whatsoever with Exchange, so I am looking for some advice.

At the moment all of our mail comes from 1&1 Hosting which is fed through End Users Outlook 2003/2007/2010 clients & all PST files are local to their respective PCs/laptops.

The Exchange Server will not be linked to Active Directory at the moment but it will in the future.

I believe this will be a major job as we have about 450 staff & all of their PST files will have to be transferred to the Exchange Server once it is up & running. Is there any automation software which can make this part easier?

Any pointers for an Exchange newbie would be fantastic!
0
craigaddison
Asked:
craigaddison
  • 2
  • 2
2 Solutions
 
Minoru7Commented:
First, I'm not sure what you mean by Exchange and Active Directory won't be linked, as that's a requirement for Exchange.  You can't run Exchange without Active Directory.  Once you have your Exchange server built, and all users are configured to use it, then you can use the Export/Import commands to import the PST files into the individual mailboxes.  I don't know of any easy ways to do this automatically, as you'll have to tie each PST to a specific mailbox.  Which means you'll probably be running an individual command for each mailbox.  This will definitely not be an easy task.
0
 
Simon Butler (Sembee)ConsultantCommented:
I would suggest that you hire a consultant.
Mistakes made at the implemenation stage can be hard to undo, I know because that is what I spend most of my time doing as a consultant.
Exchange is not really a run setup and accept the defaults configuration, some work has to go in to the design of both hardware and the systems to ensure that you cover business needs. High availability, storage considerations are the two main things that cause problems.

You are also going to have to run two systems at once for a period and that will require very careful planning.

The skills required for the Exchange implementation planning and deployment are quite different from those required day to day, and you would be much better getting consultant assistance for the former so it is done right and concentrating your own energies on how to look after it.

Simon.
0
 
Minoru7Commented:
I agree with Simon.  That's very sound advice!  The PST import is the least of your worries in this situation.  And it'll save you a lot of headaches to get the Exchange system up and running in the correct manner using a knowledgeable resource.  After the system is up, then you can worry about importing PSTs from the old system.
0
 
Kernel_Recovery_ToolsCommented:
Hello, once your Exchange server is setup, you may still continue to keep all the messaging data in the end users’ Outlook client as PSTs as you do now. Downside is that it will be quite an inefficient practice from storage perspective as single instance storage architecture of Exchange will not work in that case.
0
 
Simon Butler (Sembee)ConsultantCommented:
Single instance storage wouldn't apply in this case for two reasons:

1. You don't get SIS with a PST import.
2. There is no SIS in Exchange 2010.

Simon.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now