I am a fellow Exchange 5.5 customer who is thinking about migrating to 2000 or 2003 next year. The question is related to Microsoft ceasing support of 5.5 at the end of next year, and how others are managing their migrations because of it.
We have a native 2000 AD network with a half dozen or so 5.5 servers. The databases are stored on the SAN, we have 2000 user accounts, OWA and Public folders are fully utilized. The issue is we are time constrained with a more important project that does not end until August next year (I'm sure that sounds familiar to many of you). Currently that project is all encompassing and we do not plan to invest time in the mail migration until the other project is fully completed. Ideally I would have the Exchange migration already completed before the time we are currently planning to start it. My concern is we need a decent cushion of time before 5.5 support ends, incase of interoperability problems, I envisage a mixed 5.5 2k/2k3 migration. It may be that in a mixed 5.5 2k/2k3 environment MS would provide support while we fully move to a support Exchange, even after the PSS cut off time. Any thoughts would be appreciated, am I being over concerned, or should I be pushing to make this more important? E-mail is as important a component to our organization as most people, just the other project is moving our main premises to a new location, including datacenter. Thanks in advance. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
