How often should I buy new server?

From: Danny Bloodworth (dbloodworth_at_infinitechs.com)
Date: 11/18/04


Date: 18 Nov 2004 08:29:35 -0800

I'm on the fence about a new server and/or OS upgrade for a client.
Their current server is a Poweredge 1300 PIII 500Mhz, 256Mb... ,
currently running SBS 4.5, 30 or so users, Exchange, File Sharing,
SQL7.0, VPN, Intranet, etc. I am considering either upgrading the OS
to Windows 2003 SB Server (Premium) , or buying a new server with that
software installed. I feel like they could benefit from having the
newer version of the software for many reasons, but am worried about
putting it on the old machine. The machine meets all minimum
requirements, but isn't that like putting a great set of wheels on a
Gremlin? I'd appreciate the opinions of others who may have faced this
situation.

Also, if we do buy a new server, what division of functionality would
be best for each server? The new server would be another Dell with an
up-to-date but "average" small business config. (i.e. use the new
server for SQL and Exchange, use the old one for file sharing and ...)
Or do I just sell the old one on ebay and hope for the best?

Lastly, what's the rule of thumb for server life? I'm not looking for
simply if it ain't broke don't fix it here. The speed of advances in
both hardware and software seem to suggest that I need to budget for
improvements. In desktops, it seems to take care of itself. Units
break in 3 to 5 years and the cost of repair outweighs the purchase of
a new one. No brainer. So far, I've solely based the decision to
replace (or reallocate) a server on whether it was getting the job
done. Any thoughts?

Thanks in advance for your replies,
DB



Relevant Pages

  • RE: Single Server Upgrade Exchange Question
    ... The Exchange Migration Wizard can migrate all user mailboxes. ... server and then import them to the destination server. ... Single Server Upgrade Exchange Question ...
    (microsoft.public.windows.server.sbs)
  • Re: Validation for 2000 to 2003 upgrade
    ... Concerning the Exchange attribute in schema that will get duplicate during ... I don't want to have to run the adprep from the exchange server cdrom before ... Inplace upgrade will work without problem from 2000 to 2003, ...
    (microsoft.public.windows.server.active_directory)
  • RE: NT4 to 2003 server upgrade including Exchange 5.5 to Exchange 2003
    ... my understanding of your current issue is totally ... related to Exchange 5.5 upgrade to Exchange 2000. ... Domain A includes the Exchange 5.5 server which B and C ...
    (microsoft.public.windows.server.migration)
  • Re: forestprep and domainprep on a Windows 2000/Exchange 2000 Dire
    ... You can not upgrade the schema until you change the names with the .ldf script. ... During the upgrade phase it will use the RFC compliant name versions, that are not existing, because Exchange 2000 use names that where not RFC compliant as stated in the document. ... OK with the Windows Server 2003 forestprep/domainprep? ...
    (microsoft.public.windows.server.active_directory)
  • Re: WinNT Domain to Win2K Active Directory? Help!!!
    ... ---domains can remain NT until those Admins feel like doing their upgrade? ... Microsoft Online Partner Support ... Also, we already have a Server 2000 running our DNS and WINS, do I need ... Perform an inplace upgrade to Exchange 2000. ...
    (microsoft.public.windows.server.migration)

Loading