Re: Licensing issues or something else?



Thanks Anna,
Yes this was a retail version of SBS 2003 Standard Retail Version purchased
from a retail store online.
As far as posting the IP info, I can't do that sorry.
Thanks for your reply.



"Anna Clark" wrote:

Hi Cosmin:

Are you asking about Small Business Server 2003, the product that ships with
5 CD's and Exchange Server and several other applications? If so, either
you did not complete the installation, or you have DNS (and maybe other)
issues.

Can you please post:

1. The MS SKU for the product you are asking about
2. The results of ipconfig /all > c:\serverip.txt
3. The results of ipconfig /all > c:\clientip.txt

For the last two, the command will create a text file that you can open with
notepad and cut and paste the results into your reply.

--
Regards:

Anna Clark
Please reply or post the solution to
your issue so that others may benefit.


"CosminTheMan" <CosminTheMan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE0EF453-A9AA-4282-8D88-2E9C72F9940A@xxxxxxxxxxxxxxxx
Hi there,
I have a client for which I installed Win 2003 SB Standard with 5 CALs
It was a retail purchase however I knew that teh office has 12 users.
Installed it as a DC and added all 12 computers just fine however I find
all
kids of restrictions on the workstations and users are complaining about
slow
connection to the server, Word and other programs hang when they try to
open
docs located on the server, Outlook acts the same way (.pst file is on the
server). Also it take a very long time for the user to login to the domain
from their workstations.
Looking at the Event Viewer the only significant error I see is the
Licensing Warning with event id 221 "License usage for product Windows
Server
is nearing the maximum number of per server licenses purchased. Consult
Licensing from the Administrative Tools folder for more information."
Looking at the licensing information I can see that are 5 installed and 12
in use.
I did not want to buy the additional licenses yet because I want it to see
how SMB works for them.
Are all the issues described related to licensing?. If we purchase
additional licenses it will solve these problems described? Also is there
a
limit on the number of liceses that can be installed? This is not the R2
version, is the retail Standard 2003 SB 5 CALs version. A fast answer will
be
really appreciated.
Thanks
Cosmin





.



Relevant Pages

  • Re: novice terminal services questions
    ... the PCs will all be XP Pro, and the server is windows 2003. ... only other thing at the two remote sites will be printers. ... he has purchased windows 2003 server with 10 licenses. ... purchase terminal services licenses, right? ...
    (microsoft.public.windows.terminal_services)
  • Re: Please see System Specs inside and comment. Thank You! :)
    ... You need a license for each user running the software concurrently. ... licenses are not per machine, they are per user on the machine. ... just use the server to store the data files from ... This server is being considered for purchase in an environment with 33 ...
    (comp.cad.cadence)
  • Re: licensing versions
    ... can purchase CD media to support the licenses they purchase. ... Retail copies of MS Office are in boxes (There haven't been ... any real 'manuals' from MS in the product boxes for some time). ... I am shopping for new Office licenses and see retailers ...
    (microsoft.public.office.misc)
  • Re: 2003 SBS Cals
    ... if it was a volume purchase then you can login to MS site ... for the licenses or call to MS to get the licenses. ... managed to move as much data from the old server to the new server and now ... not use the Backup/Restore CAL feature in licensing. ...
    (microsoft.public.windows.server.setup)
  • Re: Licensing issues or something else?
    ... CD's and Exchange Server and several other applications? ... you did not complete the installation, or you have DNS ... It was a retail purchase however I knew that teh office has 12 users. ... I did not want to buy the additional licenses yet because I want it to see ...
    (microsoft.public.windows.server.sbs)