Re: Automatic LogOff

Ok thanks for the help.

Bryan



"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:eVR3%239umGHA.5052@xxxxxxxxxxxxxxxxxxxxxxx
You're looking for a "formal tracking method" that doesn't exist. It's a
pretty "loose" manual tracking system. You simply write down the names of
the assignees on the CAL paperwork you get from your vendor or MS (or keep
track of it in a spread***). Then put it in a safe place in case the MS
legal beagles come calling.

If a user permanently leaves the company or is on long-term leave, you go
to your paperwork and re-assign the CAL to his replacement or note that
this is a re-assignment to temporary worker "xxx xxxxxx" until the
original user returns.

You cannot "see" (in the SBS 2003 software) which specific CAL is being
used by a specific user. There is no CAL tracking mechanism in SBS 2003.

--
Merv Porter [SBS MVP]
===================================
"Bryan Krossley" <krossley@xxxxxxxxxxxxxx> wrote in message
news:ePA6%230umGHA.4100@xxxxxxxxxxxxxxxxxxxxxxx
How do you see which cal is being used by which user. How do you track it
all. What do you write down when you get your 5 cal user code.

Bryan Krossley
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:eeSlLEjmGHA.1912@xxxxxxxxxxxxxxxxxxxxxxx
Ahh... OK I see the problem now Bryan: just a couple CALs shy of
"enough".
That's a real pain because, as you probably know, you have to buy a full
5-CAL pack just to satisfy those two extra users. :(

There was talk of a SBS 2003 single CAL pack but I haven't found it
anywhere
yet.

You can't assign the CALs within the server software (no CAL assignment
tracking module in SBS 2003). This must be done manually (paper).
Normally, you would write down the CAL assignees on the CAL paperwork you
get from your vendor (or MS). (Not very high tech, is it?) Or you could
create a spread*** to track CAL assignments.

--
Merv Porter [SBS MVP]
===================================
"Bryan Krossley" <krossley@xxxxxxxxxxxxxx> wrote in message
news:OtQ3fgimGHA.856@xxxxxxxxxxxxxxxxxxxxxxx
Hey dont get me wrong. We dont have 20 users. I was only using that as
an
example. We only have 12 but not all user are here at the same time.
Where
do you assign each user a Cal?

Bryan
"Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23%23WZFIimGHA.4772@xxxxxxxxxxxxxxxxxxxxxxx
Again, SBS 2003 (Windows 2003) has User CALs and Devices CALs, not
concurrent usage CALs (like SBS 4.5 and 2000). From a "legal"
perspective,
each user or device MUST have a CAL purchased and assigned to it. The
algorithm that checks CAL usage on the server is not precise.
Sometimes
it
will bark about being "out of licenses" when you hit the maximum number
of
CALs installed. Other times it may let you slide 1 or 2 CALs before it
starts to growl.

In any case, if you have 20 users and only 10 CALs installed on the SBS
2003
server, you need to purchase more CALs.

--
Merv Porter [SBS MVP]
===================================

"Bryan Krossley" <krossley@xxxxxxxxxxxxxx> wrote in message
news:%230t3YfemGHA.4700@xxxxxxxxxxxxxxxxxxxxxxx
> What you are describing does not seem to be what I have been doing.
When
> we bought SBS 2003 Std. we received 5 user cals out of the box. We
then
> bought 5 more open user cals to give us a total of ten. We have
never
> assigned them to a certain user. We start getting a warning message
if
> there is more than 10 people logged onto the server.
>
> Bryan Krossley
>
>
>
>
> "Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in message
> news:uKyp9DZmGHA.3468@xxxxxxxxxxxxxxxxxxxxxxx
>> No, not with the new Windows 2003 licensing model of per User or per
>> Device. What you're describing is the previous model of "concurrent
>> licensing" where you buy a set of client licenses (CALs) and then
anyone
>> can dip into the "pool" of these licenses to authenticate to the
server.
>>
>> While SBS 2003 may treat the 10 licenses you have now have installed
>> somewhat as "concurrent" licenses (because SBS 2003 doesn't have an
>> internal tracking mechanism), legally you need to buy a separate CAL
for
>> each user or device that authenticates to the SBS 2003 domain
server.
>> You then physically write down which user or device is assigned to
each
>> CAL that you buy. This is a permanent assignment with some
provisions
>> for altering it if an employee terminates or is on "temporary
leave".
If
>> you buy Software Assurance (SA) with the CALs, there are additional
>> provisions for changing CAL assignments.
>>
>> So basically, make up 10 Post-It notes and stick each one to a
user's
>> forehead. Now write down (on the CAL paperwork you received) the
name
of
>> the user and the fact that a User CAL was assigned to him on
xx/xx/xx
>> date. The Post-It note should remain attached to the user's forehead
>> until he/she permanently leaves the company. You've then met the
legal
>> requirements for your SBS 2003 CALs tracking. ;-)
>>
>> --
>> Merv Porter [SBS MVP]
>> ===================================
>>
>> "Bryan Krossley" <krossley@xxxxxxxxxxxxxx> wrote in message
>> news:uQOdofYmGHA.1912@xxxxxxxxxxxxxxxxxxxxxxx
>>> We are using a User Cal. Question. Say you have twenty users that
can
>>> log on to the server at any given time. But you only have 10
license
>>> installed. As long as no more than 10 of the 20 Users log on at
the
>>> same time is this not ok?
>>>
>>> Bryan Krossley
>>>
>>>
>>>
>>>
>>> "Merv Porter [SBS-MVP]" <mwport@xxxxxxxxxxxxxxxxxxx> wrote in
message
>>> news:eofpw4VmGHA.3600@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Hi Brian,
>>>>
>>>> SBS 2003 licensing is not concurrent, rather it's per user or per
>>>> device. There isn't a general "pool" of licenses to dip into when
you
>>>> authenticate. So, each user or each device must have a specific
CAL
>>>> assigned to it. While logging off current users will free up the
device
>>>> for another authentication to it, it will not increase the
availability
>>>> of licenses.
>>>>
>>>> This isn't obvious because SBS 2003 has no way of tracking license
>>>> usage at the server software level. It must all be done by the
network
>>>> administrator by manually keeping track of which CAL is assigned
to
>>>> which device or user (writing it down on paper). It can also be
>>>> confusing because SBS 2003 can sometimes throw "out of licenses"
errors
>>>> making you think that there must be a tracked pool of licenses
>>>> somewhere. SBS does have some kind of internal mechanism for
tallying
>>>> "maximum" license usage at any point in time, but the algorithm
appears
>>>> not to be very precise and should not be used as an indication of
>>>> "available" licenses.
>>>>
>>>> Do you have a CAL for each Device or User on your SBS 2003
network?
>>>>
>>>> --
>>>> Merv Porter [SBS MVP]
>>>> ===================================
>>>>
>>>> "Bryan Krossley" <krossley@xxxxxxxxxxxxxx> wrote in message
>>>> news:%23SFD5fVmGHA.4164@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Hello Group,
>>>> Is there a way you can automatically logoff a user if they are
>>>> inactive for a certain period of time. Some of our users forget
to
>>>> logoff when they leave the office. I want to free up any
available
>>>> licenses for other clients.
>>>>
>>>> Bryan Krossley
>>>> SBS 2003 Std. Ed.
>>>>
>>>
>>>
>>
>>
>
>






.

Loading