Server upgrade and license question.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Our current machine is SBS 2003 Premium on a Dell PowerEdge 700 - Pentium 4
HT 3.4 GHz, 2 GB RAM, an extremely slow 40 GB SATA drive (2 MB cache), and
a slightly faster 120 GB SATA drive (8 MB cache).
Machine was bought in 2004 when there was only 8 clients, all running
Windows 98.
Machine was sold from Dell with SBS Basic, and then upgraded on-site to
Premium.

Now I have 14 client computers all running Windows XP, 16 total users, and
the server is struggling to keep up.

Question is really how big a server should be looking for to upgrade? We
may add 2-3 more client computers in the coming years, but the number of
physical users shouldn't increase (we're a hotel, limited how much
management you really need).
And if we do replace the server, can we use the same server license to
install on the new machine? And what do we do about the 3 extra CALs we've
purchased?

The odd part about this whole thing is: The sticker on the machine has the
key for SBS Basic, and the install itself reports one key, but the one on
our install media is different. Though going through the paperwork from
previous employees, something SBS 2003 was purchased at some point, that by
the description doesn't sound like a CAL, and my boss says they bought what
they thought was another CAL, but the key didn't work. And looking at what
they got, it looks like they bought another 2003 Premium install, instead
of an actual CAL.
Paper trail is rather messy, at best, so certain things I have quotes for,
but not final receipts, so not entirely sure what was bought over the
years, and what wasn't.

To help with the server dimension question: This is the only server on the
network. It does everything except for firewall/proxy. We don't use the web
services (no HTTP or FTP). We do use Exchange, but only for email. No other
Exchange features are used, which I know means that Exchange is actually
overkill. We run ICS2000 (PMS system) engines on it, Genesis phone
accounting (on MS SQL server), Simply Accounting data center (on MySQL
server) for 3 users, and it acts as file server too.

We will be upgrading the PMS to InnControl II when it becomes available,
but other than that all server apps should remain the same.
With upgrading the server, I was considering using the old box for a Linux
SAMBA, and just replace the harddrives with some slightly better
proportioned ones.
.

Relevant Pages

  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Confused about CALs
    ... You mention that the 5 CALs that come with the server do not ... Terminal Services client connection. ... License Server must be activated within 120 days of using the ...
    (microsoft.public.windows.terminal_services)
  • Re: Multiple Threads and Licensing
    ... you have one client program (where it executes ... and then that one client saves data in SQL Server. ... (and had the intelligence to use that connection) they would ... CALs instead of the version that is licensed based on processors due to ...
    (microsoft.public.sqlserver.connect)
  • Re: MSAS Licensing Part II
    ... There is only a SQL Server Client ... SQL Server CALs come in two flavors: ...
    (microsoft.public.sqlserver.olap)
  • Re: Upgrade to SBS2003 from 2000 question
    ... I understand that as long as I am using xp as the client os I am covered as ... SBS2000/2003 covered the terminal server cal and the clients are covered ... or do I need to go ahead and purchase some user cals for the terminal server ... >> move from SBS 2000 to SBS 2003. ...
    (microsoft.public.windows.server.sbs)