Re: licensing after running SBS 2003 transition pack

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Was Veritas it installed on the system as it went through the transition pack?

And can you add TS to that former SBS 2k3 box?

sbs transit wrote:
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: Transition from SBS 2003 Standard SP2
    ... I understand that you have a non-R2 SBS server with SP2 ... You should buy Windows Small Business Server Standard 2003 English ... w/Service Pack 1 CD Transition Pack. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 to standard with Transition Pack: Really that easy?
    ... These most definitely include UN-INSTALLING Veritas BackupExec. ... Disconnect the server from the internet completely. ... Just make sure you have the matching TP version to your SBS ... Finally, just run the transition. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS Transition Pack Advice
    ... Ken - I ran this about a dozen times while I was writing our SBS 2003 R2 book (Microsoft Windows Small Business Server 2003 R2 Administrator's Companion from Microsoft Press) so that we could add an appendix covering it to the book. ... Before you run the Transition Pack there are a few steps you should take to ensure a smooth transition: ... If it isn't verified and tested, it isn't a backup, IMHO. ...
    (microsoft.public.windows.server.sbs)
  • 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: Join branch office SBS 2003 to heaquarters existing AD site
    ... transition pack?" ... to join the headquarters' domainX.local. ... add your server to domainX.local. ... I am pretty sure that this branch of 15 users held the only SBS 2003 box ...
    (microsoft.public.windows.server.sbs)