Exchange Server Forums

Average Deployment Cycle

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Installation >> Average Deployment Cycle

Page: [1]

Message

<< Older Topic Newer Topic >>

Average Deployment Cycle - 12.Oct.2009 5:04:41 PM

grobinson23

Posts: 3
Joined: 12.Oct.2009
Status: offline

Hey gang!

We've got Exchange 2007 on our project list, and we were give a proposed time of 4 months for the deployment (we've got a hosted solution now and will be migrating). Where would be the best place to look for an average deployment time for Exchange 2007 (Enterprise cluster)?

Is 4 months reasonable? We'd like 6. My lead stated that a cited example of a deployment cycle would be the best way to go about this.

Thanks!

Grant

Post #: 1

Featured Links*

RE: Average Deployment Cycle - 12.Oct.2009 5:18:51 PM

mark@mvps.org

Posts: 6811
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline

One Enterprise cluster?
Deployment and Migration?

Err, that would be like a week, maybe two weekends.

What's you actual (i.e. full!) question... There has to be more inside your six months idea than you have thus far mentioned.

_____________________________

Mark Arnold (Exchange MVP)
List Moderator

(in reply to grobinson23)

Post #: 2

RE: Average Deployment Cycle - 13.Oct.2009 10:59:25 AM

grobinson23

Posts: 3
Joined: 12.Oct.2009
Status: offline

What? You mean my REALLY general question didn't provide enough information? SHEESH! Alrightalrightalright....

Phase 1

We need to buy the servers. We want 2 servers for an Enterprise cluster (not doing the edge server), and one of my colleagues has suggested an additional server for archiving purposes. I don't know if that's necessary, but we need at least 2 servers for failover clustering.

Phase 2:

We then have to install and configure the servers, and (here's the crux of the whole thing) I'm the only person with any experience (limited experience) installing Exchange. No clustering, no 2007, but 2003 with one mailbox. I didn't even set up OWA. So. We would then have to train ourselves on Exchange and learn as much as we possibly could before deploying the boxes into production. We're going to want a full-feature set. OCS, UM, Anti Virus and Anti Spam, Clustering, OWA, Public folders, shared calendars, the whole nine yards.

Phase 3: Deploying the boxes into production.

This would involve us migrating all of our mail over from our offsite mailboxes to the new server(s).

An Exchange admin would solve our problems, but we have been informed that this will not be taking place. The bottom line is that we think 4 months isn't enough time. There are too many variables in the equation.

Does this clarify things? Let me know if you need additional information.

Thanks!

Grant

< Message edited by grobinson23 -- 13.Oct.2009 2:46:49 PM >

(in reply to mark@mvps.org)

Post #: 3

RE: Average Deployment Cycle - 13.Oct.2009 2:31:16 PM

mark@mvps.org

Posts: 6811
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline

See, it's not that hard is it? :-)
Well, you want more than two servers for an Enterprise cluster because you can't put the CAS or HT roles on an Exchange 2007 cluster. So you're already a box light on the deal.

And then there's the OCS thing. That's another couple of boxes. And the UM thing; that's another box

I think six months would be more realistic for you from architectural sign-off of all the components to having it up and running with everyone on it.

It's going to take you a while to get up to speed on the whole SIP thing, connecting to a phone system and integrating OCS with UM and the client.

Sounds like a fun project.

_____________________________

Mark Arnold (Exchange MVP)
List Moderator

(in reply to grobinson23)

Post #: 4

RE: Average Deployment Cycle - 13.Oct.2009 2:47:10 PM

grobinson23

Posts: 3
Joined: 12.Oct.2009
Status: offline

Thanks for the info!

(in reply to mark@mvps.org)

Post #: 5

RE: Average Deployment Cycle - 19.Oct.2009 10:23:20 AM

adrian.pettitt

Posts: 240
Joined: 24.Sep.2009
From: UK
Status: offline

I would, in general, second Mark on the 6 months. Although that is for Exchange only.
You seem to be in a similar boat to me.
Currently now rolling out Exchange 2007 in SCC with NLB CAS/HUB.
Including design, ordering hardware, building a test/dev environment and building and going to Pilot/rollout has been 5 months.
We have been delayed by also having to migrate to a new AD, IPV6 (very flakey) and the fact that I have never really run an Exchange system before so I have had to learn everything, and I am still learning.
I would then say add UM on top and then OCS. Which will be the next parts of this project sometime next year as we have several thousand users to move to Exchange.

Adrian

(in reply to grobinson23)

Post #: 6