Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Sun, 17 Feb 2008 09:34:37 +0000,    group: microsoft.public.exchange.design        back       


migration project   
We are looking at migrating from FirstClass to some other communication 
system that is easily integrated into EPiserver and other systems being 
developed. Exchange is an obvious candidate.

What I am a bit worried about is the management costs in HR to maintain 
our current network as well as the Exchangeserver. The organisation 
isn't all that big;

(Currently) 4 main offices and a number of satellites
c 75 users at HQ office
c another 100-150 users worldwide
reality of bad connection to some offices (like bad power supply and low 
bandwidth) and users on the road

We would also possibly need webmail access to the server.

What would your general guesstimate be of resources in means of 
bandwidth to/from local offices, expertise in local office, expertise at 
  HQ office, number of servers and admin to manage it all from HQ.
Any suggestions on intro docs for setting up all this. and guesstimate 
of time for the migration project?
date: Sun, 17 Feb 2008 09:34:37 +0000   author:   Shieldfire am

Re: migration project   
I would suggest calling a Consultant who is a Microsoft Certified Partner or 
Microsoft Regional Sales Office.  They can assist you with any questions you 
may have regarding your interest in migrating to Exchange Server.  For such 
a critical migration I would not start guessing at what your bandwidth 
needs, among others, would be necessary without more detailed information 
about your network.

-- 
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner


"Shieldfire" <shieldfire@newsgroup.nospam> wrote in message 
news:uhHEOiUcIHA.5900@TK2MSFTNGP02.phx.gbl...
> We are looking at migrating from FirstClass to some other communication 
> system that is easily integrated into EPiserver and other systems being 
> developed. Exchange is an obvious candidate.
>
> What I am a bit worried about is the management costs in HR to maintain 
> our current network as well as the Exchangeserver. The organisation isn't 
> all that big;
>
> (Currently) 4 main offices and a number of satellites
> c 75 users at HQ office
> c another 100-150 users worldwide
> reality of bad connection to some offices (like bad power supply and low 
> bandwidth) and users on the road
>
> We would also possibly need webmail access to the server.
>
> What would your general guesstimate be of resources in means of bandwidth 
> to/from local offices, expertise in local office, expertise at HQ office, 
> number of servers and admin to manage it all from HQ.
> Any suggestions on intro docs for setting up all this. and guesstimate of 
> time for the migration project?
date: Sun, 17 Feb 2008 13:43:00 -0500   author:   John Oliver, Jr. [MVP]

Re: migration project   
John Oliver, Jr. [MVP] skrev:
> I would suggest calling a Consultant who is a Microsoft Certified Partner or 
> Microsoft Regional Sales Office.  They can assist you with any questions you 
> may have regarding your interest in migrating to Exchange Server.  For such 
> a critical migration I would not start guessing at what your bandwidth 
> needs, among others, would be necessary without more detailed information 
> about your network.
> 
Of course I can see that. What I'm more interested in is a general idea 
of resources needed to maintain the server.
When it comes to implementing this, we will of course use a consultant 
with extensive Exchange experience (if we decide to use Exchange).
date: Tue, 19 Feb 2008 05:52:13 +0000   author:   Shieldfire am

Re: migration project   
It really depends on how many servers.  One centralized server would make 
things easy to manage if you have no Admin staff at the other offices.  Now, 
with the slow links at some Offices it might be necessary to stick an 
Exchange Server at those offices or use Outlook Anywhere if they can work 
offline, but it really depends on how critical email is at the sites if they 
have no access to it for a period time.  Exchange 2007 Server is very robust 
messaging system and can accomodate any size network.  With that being said, 
reading up on Exchange 2007 Server Roles and placement of these would be 
helpful in your implemenation.  This a general response to your question 
that I can give.  Others may chime in but at least it gives you some general 
idea.

-- 
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner


"Shieldfire" <shieldfire@newsgroup.nospam> wrote in message 
news:%23zOUPvrcIHA.4332@TK2MSFTNGP06.phx.gbl...
> John Oliver, Jr. [MVP] skrev:
>> I would suggest calling a Consultant who is a Microsoft Certified Partner 
>> or Microsoft Regional Sales Office.  They can assist you with any 
>> questions you may have regarding your interest in migrating to Exchange 
>> Server.  For such a critical migration I would not start guessing at what 
>> your bandwidth needs, among others, would be necessary without more 
>> detailed information about your network.
>>
> Of course I can see that. What I'm more interested in is a general idea of 
> resources needed to maintain the server.
> When it comes to implementing this, we will of course use a consultant 
> with extensive Exchange experience (if we decide to use Exchange).
date: Tue, 19 Feb 2008 08:18:01 -0500   author:   John Oliver, Jr. [MVP]

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us