Re: Licensing issues or something else?
- From: CosminTheMan <CosminTheMan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 22 Apr 2007 22:28:00 -0700
"Lanwench [MVP - Exchange]" wrote:
CosminTheMan <CosminTheMan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
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.
Given that, why did you not buy more CALs?
Because they are upgrading from an NT server also using some old software
programs like Act and such and we were not sure if 2003 is a big step or
should we do it gradualy to 2000 first and then 2003 knowing all the bugs in
2003.
Installed it as a DC
You have to do that; there is no other option. Did you run the setup from
the wizards, and the to do list? Every single one?
What do you mean there is no other option? Could be a network simply without
a domain. But yes I did run everything from the list.
and added all 12 computers just fine however I
find all kids of restrictions on the workstations
Such as?
Such as, could not add domain users as local admins on the workstation from
the workstation for example. Later I would find unresolved SIDs.
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,
I suspect you may have DNS problems....
Outlook acts the same way (.pst file is on the server).
Well,
a) you really ought to be using Exchange, and no PSTs, but more importantly,
b) accessing a PST file across a LAN/WAN connection is entirely unsupported,
and leads to performance problems and likely data corruption. Avoid this.
They had access the pst file accross the local network for years with no
issues.
Also it take
a very long time for the user to login to the domain from their
workstations.
Again, this indicates a DNS problem. If you set up SBS to run DHCP services
for the network during install, it would have configured itself properly -
to dish out the DNS suffix (mycompany.local), the WINS server IP and node
type, the router IP, and most importantly, the SBS server's LAN IP for DNS.
No public DNS servers should show up in an ipconfig /all on a client or the
server itself. AD requires properly configured DNS.
I will look at these settings one more time however I configured properly
from the very beginning.
There is no such a thing as lab env. in a small company that has nothing to
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.
That's not what the product is for. You could have used a trial version in a
lab environment so they could test it - you don't buy a production OS and
then not fully license it.
do with IT or related field.
Interesting because on the box it says clearly that 15 licenses max can beAre all the issues described related to licensing?. If we purchase
additional licenses it will solve these problems described?
It will get you legal, and you need to do it, but I suspect you have larger
configuration problems.
Also is
there a limit on the number of liceses that can be installed?
You can have up to 75 users in SBS. User does not necessarily = CAL, if
you're using 'per device' CALs - I suggest you call MS directly with any/all
licensing questions, as nobody in a newsgroup is officially sanctioned to
provide answers to licensing questions.
added.
Thanks for your replyThis is
not the R2 version, is the retail Standard 2003 SB 5 CALs version. A
fast answer will be really appreciated.
Thanks
Cosmin
Cosmin
.
- References:
- Re: Licensing issues or something else?
- From: Lanwench [MVP - Exchange]
- Re: Licensing issues or something else?
- Prev by Date: RE: Unable to Establish Telnet Connection on Ports 22 or 23
- Next by Date: Re: Can't Install SBS R2 package as final step in Converting to R2
- Previous by thread: Re: Licensing issues or something else?
- Next by thread: Re: Licensing issues or something else?
- Index(es):
Relevant Pages
|
Loading