Solved

Systems Management Server 2003 - SQL Licensing & Authentication Requirements

Posted on 2007-03-30
3
210 Views
Last Modified: 2013-11-21
Greetings world -

A colleague of mine recently setup an SMS 2003 environment in VMWare and was having issues launching the SMS Service Manager and seeing collections data and so forth (just hourglasses).  I decided to help him and blew away all the Virtual Machines and started over.

When I did so, I made only two changes to the configuration.  I set the authentication mode of SQL to Windows instead of Mixed Mode, and I set the SQL Server 2000 licensing to "Per Seat" rather than "Per Processor".

Everything works now!  My question is, does SMS 2003 have a technical restriction that requires Per Seat licensing on SQL 2000 rather than Per Processor?  Or was it my change to the authentication mode that made it work.  Or both?

Any information anyone has on their experiences with SMS 2003 and SQL 2000 would be appreciated.  I'm wondering if the licensing made a big difference or not.
0
Comment
Question by:amendala
  • 2
3 Comments
 
LVL 33

Expert Comment

by:NJComputerNetworks
Comment Utility
SQL 2000 license mode does not matter  (I use per seat)

Authentication mode does not matter.   (I use Mixed mode.)
0
 

Author Comment

by:amendala
Comment Utility
Interesting.

When I install using Per Processor licensing no SQL and Mixed mode authentication, my virtualized environment does not function properly... hmm.

However, when I reinstalled using Per Seat and Windows auth, it works fine.  I do believe you are correct that the authentication mode doesn't matter because I have a production environment SMS 2003 setup with SQL Server 2000 running using Mixed Mode auth. and it functions.  Still wondering about the licensing...

Any input from anyone else?
0
 
LVL 33

Accepted Solution

by:
NJComputerNetworks earned 500 total points
Comment Utility
This table shows that both SQL licensing types are supported:  

(easier to see in the link:  http://www.microsoft.com/technet/sms/2003/evaluate/faq/default.mspx#ECF
)

Q. When does SMS 2003 require a Microsoft SQL Server™ CAL?
A. The following table describes when SMS 2003 requires SQL Server CALs.

SMS license type SQL Server license type SQL Server CAL for SMS 2003 required
Standalone
 Standalone per processor
 No
 
Standalone
 Standalone server/CAL
 Yes. An SMS 2003 server and every device managed by SMS, including desktops, laptops, servers, secondary site servers, and hand-helds, require a SQL Server CAL license.
 
SMS 2003 with SQL Server 2000 Technology
 SMS 2003 with SQL Server 2000 Technology or MOM 2000 with SQL Server 2000 Technology
 No
 
 
0

Featured Post

Why spend so long doing email signature updates?

Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

Join & Write a Comment

If you need to start windows update installation remotely or as a scheduled task you will find this very helpful.
When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup". After a while, you have entered a loop for Auto repair which does not fix anything and you will be in a  panic as all your work w…
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now