Windows Forum

Ask something
Discussion Locked

Win2k logon script and licensing

0 helpful
6 replies

by brianaaa12

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Greetings,

I have a new Win2k Server set up with 10 Win2k workstations attached. The first problem is that I keep getting messages at the server saying it's out of licenses. I have 15 licenses and only 10 workstations attached. It is set up for "per server". As a temporary fix I added licenses but would like to get to the bottom of it.

Second and more important problem: I used the User and Computer Manager (or whatever it's called) to set a default login script for the domain. The script is a batch file. The first thing it does is map network drives. That part works fine. After that it executes a command similar to this:

If %computername%==W1 GOTO 1
If %computername%==W2 GOTO 2
etc. through W10

then
:1
set WS=W1
:2
set WS=W2

:END

This is not verbatim, as I am doing it from memory. The point is, the batch file is not fully executing. If I browse to, and double-click on the batch file, it will map the network drives, but nothing else. If I copythe batch file to the local machine, then double-click on it, same thing. But If I copy the batch file to the local machine then run it from a command prompt, it does everything! Just as it should.

An additional problem: Early on, when I first set up these workstations, I had added system Environmental Variables using the advanced properties of My Computer. I have since then removed them. But every time I launch a command shell using Start|run|CMD then execute a Set command, the EV's are back! I have checked the Autoexec.nt and Config.nt and there is nothing in them.

Any help is greatly appreciated.

Brian

6 replies

by ntoz

If your using per server, your limited to 10 Connetions. Connections meaning EACH connection. If your mapping multiple network drives and the likes, this can cause a problem. Also since your running in Per Server mode, once you reach that magic per connection level, noting else can connect. Move to per seat mode and those issues go away. Per Server mode is only valuable if you have a system and you have a very small set of systems that might just use it to authenticate and perhaps use one mapped drive. Your going way past that stage from what Im reading about your doing in my opinion. Second as far as your logon script, Its hard to help you with out understanding what your trying to accomplish with this portion of the script. Could you give a little more on what your doing with this script and the exact syntax? Finaly when your putting in your EV's are you putting them in the global EV's or the user EV's? What are the variables as they might need permissions.

Pete

by brianaaa12

Thanks for replying, but I have to differ with you on the licensing. I DO NOT believe that each mapped network drive uses a license. That is ludicrous. That's why they are called CLIENT access licenses. Each connecting workstation represents a client, not each mapped drive. I anybody can back up OS/PETE, I am willing to listen.
As to the problem with the Environmental Variables, I thought I was pretty clear. I set variables in the logon script, but when I do "set" at a command prompt, they are not listed. That simple. But it's moot now. I figured it out.
Brian

by ntoz

Brian,
I?m sorry you disagree, but in the licensing model for Windows NT 4.0, taken from Chapter 12 - Licensing and License Manager it states the following:

The license agreements for certain Microsoft BackOffice server products (such as Windows NT Server, Microsoft Exchange Server, SQL Server, and SNA Server) also provide the flexibility of two client licensing modes: Per Server and Per Seat. With Per Server licensing, each Client Access License is assigned to a particular server andallows one connection to that server for the use of that product. With Per Seat licensing, a Client Access License is assigned to each specific computer that accesses the server. Once a computer is licensed in the Per Seat mode, it can access any network server running that BackOffice server product at no additional charge.

Note the part where it says ONE connection.

Yes the model pushes you to perseat, it was the fact with Windows NT 4.0 I have seen this a multiple clients of mine. A second well-known fact is the license manager was a buggy app and never worked right to begin with. In many cases, simply stopping the licensing server service was the answer. They have reworded and perhaps changed it in Windows 2000, but its basicallyprob the same. Bottom line, and since you are already out of the scope of your license agreement by adding more CALS then you really own as you stated in your message, if you simply convert to per server and turn off the license manager, it will never prompt you again for anything. You could have 10,000 clients access the server and it wouldn?t matter. I tell you this not to encourage you to violate your terms of use, its because the license manager stinks. Buy the CAL?s they are cheep. I hope this clarified my answer to that portion of the question, as far as your batch file, maybe you were clear and perhaps to others as well, but I simply asked a question and spent my t

by ntoz

Per Server Licensing

With Per Server licensing, each Client Access License is assigned to a particular service (product) on a particular server and allows one connection to that service, such as basic network services. For Windows NT Server, the basic network services include the following:
?File services ? sharing and managing files and/or disk storage
?Printing services ? sharing and managing printers
?Macintosh connectivity ? file sharing and printing services
?File and Print Services for NetWare connectivity ? file sharing and printing services for NetWare clients
?Remote access services ? accessing the server from a remote location through a communications link
Notice that a connection, in this case, is to a server and notjust to an individual share point or printer on that server. If you connect to \\Airedale\Apps and \\Airedale\Public, that is considered as only one connection for licensing purposes. However, if you connect in Per Server mode to a server from two different computers using the same username, that is considered two connections.
You must have at least as many Client Access Licenses dedicated to a service on that server as the maximum number of client computers that will connect to that server atany point in time. If you select the Per Server option, you must specify during Setup or upon purchasing new Client Access Licenses, the number of Client Access Licenses (which corresponds to the number of concurrent connections) that you have purchased for that server.
With Per Server licensing, once the specified limit for concurrent connections is reached, the server returns an error to the client?s computer and does not allow more computer connections to that server. Connections made by administrators are also considered as part of the total number of concurrent connections. When the limit is reached, though, administrators are still allowed to connect to manage the

This discussion is closed to new replies.