> Hi Mark -
> It should be pretty close to that straight-forward. If you're using
> profiles, you'll naturally want to copy those over from your SBS with your
> Exchange data. Using a spare box has several advantages - 1) you get to
> migrate your existing domain (instead of creating new) which keeps those
> / Win2k / XP clients happy (and profiles intact), 2) you don't have any
> remains from an NT4 -> Win2k upgrade on your final production network
> your final production server is a clean install, 3) You're free to name
> new server the same as the old server without any conflicts. 4) If you run
> into problems while upgrading the spare box, your original SBS is still
> intact, and you can re-attach it to the LAN and be back up and running . .
> I'm pretty sure you've got to use plain NT to create the spare box - I
> think NT from the SBS disks gives you the option to install as a BDC, but
> could be wrong.
> SBS2k still only allows for a maximum of 50 workstations, but this
> is going to have to be projecting some serious growth in the next 18 - 24
> months to view this as a potential problem. Add that SBS is in essence
> per-seat licensing with a single CAL allowing a workstation to connect to
> the SBS (Win2k / Exchange / SQL) and any Win2k member server, and the
> licensing is going to be less expensive as well. In addition to the price
> savings with SBS, there are other advantages currently out there. With
> new version of SBS nearing release, Microsoft is offering Software
> for SBS for only $99 - which is a considerable savings. Also, if this
> customer decides to go with SBS and you install it before June 30, you can
> claim a rebate from Microsoft for up to $500 (see
> http://members.microsoft.com/partner/campaign/SBS2000.aspx) for more
> Chad A. Gross
> Lerman's Law of Technology: Any technical problem can be overcome given
> enough time and money.
> Corollary: You are never given enough time or money.
> > Chad,
> > Wow. It can't be THAT straigthforward, can it? Two quick follow-ups:
> > 1) Regarding creating an NT 4 box, can I simply use the current SBS CD,
> > do I have to hunt around for an old NT 4.0 server CD (non-SBS)?
> > 2) I'll check out the pricing on SBS 2000 and see whether I might
> > my client towards this direction; if I remember, SBS 2000 allows for
> > CALS than does SBS 4.5, right?
> > Thanks for your help. This may save us some real grief!
> > You must be
> > > Hi Mark -
> > > Take a spare box, load up NT4 as a BDC to your SBS4.5 domain. Use
> > > to export your Exchange mailboxes (and manually export any public
> > > you have to pst files). Remove the SBS and promote the spare box to
> > > Updgrade the spare box to Win2000. Load up Win2000 on your new server
> > > old SBS if you're using the same hardware) and join it to the domain.
> > > Promote to PDC and dcpromo the temp server out of the domain. Load
> > > Exchange, use Exmerge to import your user mailboxes and manually
> > any
> > > public folders . . .
> > > But, as Susan stated - there are significant cost savings with SBS2k
> > > straight Win2k + Exchange, especially in a 9 node network.
> > > --
> > > Chad A. Gross
> > > Lerman's Law of Technology: Any technical problem can be overcome
> > > enough time and money.
> > > Corollary: You are never given enough time or money.
> > > > Please forgive the cross-posting, but I'm not seeing that my
> > > falls
> > > > neatly into any particular newsgroup. Also, please forgive if this
> > > > FAQ.
> > > > I have the difficult task of migrating a client from his current
> > setup --
> > > > SBS 4.5 with about 9 users -- to a new setup, Windows 2000 server(s)
> > > > Exchange 2000. My client does not use all the other features of SBS
> > > and
> > > > so believes that upgrading to SBS 2000 is not the right thing to do.
> > is
> > > > intent on going to the more modular and flexible Windows 2k server
> > and
> > > > Exchange 2000 installation.
> > > > The wrinkle here, of course, is that he wishes to do a direct
> > of
> > > > current usernames/profiles and Exchange 5.5 mailboxes to the new
> > of
> > > > Windows 2000 (presumably with AD) and Exchange 2000. I've seen that
> > there
> > > > are various whitepapers on the SBS site for upgrading to SBS 2k, but
> > > haven't
> > > > come across my particular situation.
> > > > Might some kind soul direct me to some URL or other that could get
> > > > started?