Discussion Locked

Moving NT4/Exchange 5.5 to SBS 2003?

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm currently running a small business LAN of 2 servers: a PDC running Windows NT Server 4 and a second server running NT 4 and Exchange 5.5. I'm considering upgrading the whole network and obtaining a third server to help with the process.

It's been suggested to me that I consider moving to Small Business Server 2003 since it has both Windows 2003 Server and Exchange 2003 Server rolled into one and can support up to 75 users.

I've also been told that my SBS server would have to be the domain controller, as well as that the server running Exchange should not be a domain controller because it will make future upgrades more difficult.

Given all of this, my basic questions are these:

Would it be wise for me to try to migrate my network over to Small Business Server 2003? What would be the limitations? And what would be the cleanest, safest method of making this transition with the least amount of down time possible?

7 replies

by curlergirl

I think your perceptions of SBS are a little off - It is true that your SBS server would have to be the domain controller - it also has to be the Exchange server. The primary "limitation" if you will of SBS is that all of the bundled applications have to be run on one server. You don't say how many users you have, but my personal feeling is that is fine if you are only running Exchange and not any other of the bundled applications like ISA Server, web servers, SQL server, or anything else on the same box. For a network of more than 25 or so users, I wouldn't want to run all of those apps on the same box anyway.

That said, you can do it if you configure your hardware accordingly. Since you can't connect an SBS Exchange server to any other Exchange server or to any other domain controller, you will need to set up the new SBS server as a totally new domain. Then, the easiest way to migrate Exchange would be to export all of your user mailboxes to PST files and then re-import them once you have your new domain set up.

Hope this helps!

by instrumentality

Thanks for your feedback.

We only have maybe half a dozen users who would be utilizing the network for anything other than e-mail. The rest of the people (let's say 20-30) would be accessing Exchange through POP or Outlook Web Access, not through a full-blown MS Outlook/Exchange connection. The SBS server would need IIS solely for the purpose of running OWA. I'm envisioning running any other applications (virusscan server, spam filtering software, etc.) on a separate server running pure Windows 2003 Server.

Your point about not being able to connect SBS Exchange to another Exchange server is something I was not previously aware of, and it may make a big difference. I may be able to use the PST method for mailboxes, but I also have several public folders with custom forms as well as a message journal. Is there a way for me to port these items over to SBS?

by curlergirl

Answer to your comments - you can export and import items within public folders just like you do from a mailbox. You have to have the correct permissions for the public folder(s), of course, but otherwise the process is the same. Since you can't join an SBS site to any other Exchange site, this would be the only way to do the public folders as well as the mailboxes.

Hope this helps!

by instrumentality

OK...you've helped me on both the pure Win2k3/Exchange 2k3 approach and the SBS approach. I guess it comes down to this...

For purposes of ease of transition, minimization of down-time, speed of migration, and future expansion/migration capabilities, assuming we can afford either route, would you say it's worth the extra cost to go with full-blown exchange and Windows 2003 rather than using SBS? The idea of exporting to PDF and then re-importing sounds really tedious and time-consuming and unstable, especially when we're talking about public folders. But maybe that's just because I've never had to go through the process.

by curlergirl

Given the size of your organization - 20-30 users (it doesn't matter how they access Exchange, they are still Exchange users), and given all of the other conditions you've listed, I would recommend going with the full-blown versions rather than SBS. Taking both hardware and software into account, and the fact that you need more than one server anyway, the cost differential isn't THAT much. Also, as an administrator, I feel the learning curve with SBS is in fact greater than with the standard applications, because SBS uses a lot of "wizards." How, IMHO, wizards are great if your objective is to get the system set up in a standardized manner quickly. However, if you have any kind of special requirements (like you do in terms of multiple servers, users with different methods of connecting to Exchange, etc.) the wizards don't do you that much good and, I think, can give you a false sense of security. If you run into a problem, you don't know exactly everything the wizard has done (in the background where you didn't see it) and so it's harder to troubleshoot problems and issues down the road. Plus, of course, the transition with SBS would entail more down time, which I know is one of your major concerns.

That's my 2 cents' worth, anyway :-)

by instrumentality

I am not a fan of having wizards try to dumb down procedures and make it difficult or impossible for me to know what's going on behind the scenes. Windows XP was bad enough in this regard when I first started using it--I spent almost as much time trying to figure out how to turn off idiot mode for the Start Menu, Network settings, etc. as I did actually configuring the OS.

Thanks again for your advice.

This discussion is closed to new replies.