Re: licensing after running SBS 2003 transition pack

Yes, we do have a terminal server in the domain. It works fine after the
transition.
Also, we do have Veritas BackupExec.
Is there anything to do with these?

"Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa@xxxxxxxxxxx>
wrote in message news:%23Xd3AsuKGHA.1180@xxxxxxxxxxxxxxxxxxxxxxx
Can you add Terminal services?

And did you have any third party backup software loaded? and if so, what?

sbs transit wrote:
Hi there,
just ran the transition pack last weekend.
all looks fine except the licensing.

Before transition, the SBS server had 25 CALs in total and max usage was
19.
A transition pack was purchased which includes 5cals. Additional 20 CAL
transition pack was also purchased, which contains only a license
agreement.
So in theory, we should have 25 CALs in total after transition.

After running the transition pack, the following has been noticed:
1. the license logging service was disabled right after completed the
transition;
2. if manually enable and start the license logging service and then
click the "License" in "server management" which was the SBS tool, in the
right pane we see "Small Business Server Licensing" followed by an error
message:
"Cannot load a critical system file, C:\windows\system32\sbscrdll.dll.
......"
and this operation stops the licensing logging service.
3. start the license logging service again and from "administrative tool"
to start "Licensing". From here I was able to add 25 CALs for both
windows server and exchange 2003 server - which we are entitled to. I
also see there are 15 per server licenses and I guess that's because we
have 3 other windows 2003 servers in the domain. (right?)
4. Howerver, after a while, per server license usage went up while no CAL
client logged.
5. Not taking long, users started sufferring connection difficulties -
they could not create new connections to the shares and shared printers.
In the event log, event ID 201 was logged with message like this:
"No license was available for user domain\user using product SMB server
5.2. Use Licensing from the Administrative Tool folder to ensure that you
have sufficient licenses"
6. Stopping the license logging service, the problem disappeared.

Any ideas? Please help!




.

Relevant Pages

  • Re: SBS2003 - Transition Pack
    ... If you were under your current purchased CALs, ... If it still says it's SBS, ... Once the transition is complete, ... Server 2003 Standard Edition and Exchange Server 2003 Standard. ...
    (microsoft.public.windows.server.sbs)
  • Re: Mapped Network Drives
    ... The license logging service is ... buggy - stop & disable it on the server & keep track of your CALs manually. ... > received an error stating "No more connections can be made to this ...
    (microsoft.public.win2000.networking)
  • Re: licensing after running SBS 2003 transition pack
    ... The veritas BackupExec is working fine after the transition. ... And can you add TS to that former SBS 2k3 box? ... the SBS server had 25 CALs in total and max usage ... the license logging service was disabled right after completed the ...
    (microsoft.public.windows.server.sbs)
  • Re: Designing Server 2003 multisite Licensing setup, CALS
    ... FYI The license logging service does not work as expected. ... the server, just be able to prove you have them in case of an audit. ... Should I use Per User/Per Device mode or Per Server mode. ... I would like to buy say 150 device CALS and put the main server in "Per ...
    (microsoft.public.windows.server.general)
  • Re: Move SQL 2000 to new server questions
    ... Once you run the transition pack...NONE of your SBS cals are any good ... You wind up with 5 cals for each product. ... So you will have to CALS for the new Win2k3 Server and additional CALs ...
    (microsoft.public.windows.server.sbs)