NT to SBS 2003

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Good morning all,

We are upgrading our network from Windows NT and Exchange 5.5 to SBS 2003
R2. I've downloaded the SBS_MigratingSBS45.doc and
SBS_SetupRequirements.doc, but have a couple of questions:

I'll be using for SBS a server which is currently the PDC - single
processor, 1 MB RAM.. Exchange is on a BDC. We also have a NT member server
acting as a fileserver. I plan on the following:
1. Back up EVERYTHING to tape.
2. Promote the Exchange server to PDC and use it as the source server.
3. Format the system drive on the current PDC, and use it as a destination
server.
4. Following migration, the current Exchange server will either go away
completely or be formatted and used as a file server.

Questions:

1. Can I put an NT4 member server in an SBS domain?

2. The current PDC has all the user and public folders - is this a problem?
Or should I plan on formatting all the drives and restoring from tape? It's
a huge amount of data and would take 15-20 hours to restore, so I'm hoping
no...

3. Any good documents out there for the client PCs? I still have a couple of
Windows 98 boxes out there, those I imagine will have to be moved to the new
manually - or is this a problem also?

4. Any good advice or warnings that aren't in the document I should know
about? Or links or docs that I should check before beginning?

Thanks in Advance and sorry for crossposting - I forgot to add this ng
earlier,

SusanV






.

Relevant Pages

  • Re: So why SBS?
    ... Public folders will be in the next version.. ... The sad part of most of us is that we haven't even tried or practiced a backup/restore and we freak out over a 'single" SBS box when we haven't even tried to restore it from a harddrive. ... Exchange seems to mix its words and titles, the global/generic use of POP and SMTP for just about every Exchange function is dumb, MailEnable understands post office protocol and simple mail transfer protocol in a "meaningfull" way. ... The standard profiles in Server are quite effective assuming you add new users to the correct account in the first place and your note running more than 1 file server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Easy to use second 2000 Server for Exchange?
    ... Existing Exchange 2000 server - therefore have the CALs - so no new ones are ... Frank McCallister SBS MVP ...
    (microsoft.public.windows.server.sbs)
  • Re: So why SBS?
    ... Public folders will be in the next version.. ... If SBS isn't for you...that's fine. ... Mailenable is an example of a freeware or pay for extra's, mail server. ... It is infinitly simpler to configure than Exchange once installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: Email for second domain
    ... The Microsoft Exchange MTA Stacks service is normally disabled on Exchange 2003 Servers on SBS 2003. ... You can safely ignore the MTA warning messages on the SBS 2003 server. ...
    (microsoft.public.windows.server.sbs)
  • RE: Configuring exchange 2003 in SBS
    ... As I know, this is not related to per user mailbox, it refer to the mailbox ... store on the whole Exchange server. ... This newsgroup only focuses on SBS technical issues. ... What minimum requirement if I want this server for a fileserver? ...
    (microsoft.public.windows.server.sbs)