**

Good Morning Stefan,

I followed your instructions, but 'Properties' is grayed out. Is there something else I need to activate in the User or Admin Tool?

Thanks for your posting.

Audrey Franklin

Senior Systems Analyst

ITS Administrative Computing

New York University

audrey.franklin@nyu.edu



----- Original Message -----

From: Stefan Spijkers

Date: Friday, September 6, 2002 7:08 am

Subject: Re: Floating Licenses

> **
>
> **Does Remedy have any utility out the shows the # of users
> logged in and the # of licenses used?
>
> Yes it does. When logged onto Remedy User with admin rights, just
> go to Tools -> Accounts , then right click on the Server Name and
> click properties.
>
>
>
> Stefan Spijkers
>
> Compass Group Nederland
>
>
> To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
> listserv@arslist.orgYou may also control your subscription
> options, including UNSUBSCRIBE, at www.ARSLIST.org
>

**
Audrey, In the Admin tool server window, select a server. Then on the File menu select License information. It will show you the information you want. If you select File > Server Information, there is a Licenses tab that shows you how many licenses you have licensed. Jim.

-----Original Message-----
From: Audrey Franklin [mailto:audrey.franklin@NYU.EDU]
Sent: Friday, September 06, 2002 8:04 AM
To: ARSLIST@LISTSERV.QMXS.COM
Subject: Re: Floating Licenses


**



Good Morning Stefan,

I followed your instructions, but 'Properties' is grayed out. Is there something else I need to activate in the User or Admin Tool?

Thanks for your posting.

Audrey Franklin

Senior Systems Analyst

ITS Administrative Computing

New York University

audrey.franklin@nyu.edu



----- Original Message -----



From: Stefan Spijkers



Date: Friday, September 6, 2002 7:08 am



Subject: Re: Floating Licenses





> **
>
> **Does Remedy have any utility out the shows the # of users
> logged in and the # of licenses used?
>
> Yes it does. When logged onto Remedy User with admin rights, just
> go to Tools -> Accounts , then right click on the Server Name and
> click properties.
>
>
>
> Stefan Spijkers
>
> Compass Group Nederland
>
>
> To UNSUBSCRIBE, email the message "unsubscribe arslist" to:
> listserv@arslist.orgYou may also control your subscription
> options, including UNSUBSCRIBE, at www.ARSLIST.org
>

**

Hi,

I would like to know how you guys manage licenses. We're using the Remedy's
recommendation of 1 floating license per 3 users. Still, our users are
constantly complaining they are unable to submit or modify tickets. Everyday
we track the number of licenses being used. Throughout the day we see that
all floating licenses are being used and 20-40 users are waiting for a
floating write license. Since Remedy has changed when a floating write token
is issued (i.e. anytime you query, submit, modify, a floating license is
taken) did you guys just buy more licenses or did you do something else?

Thanks in advance,
Lily


You may control your subscription options, including UNSUBSCRIBE,and ACCESS THE ARCHIVES at http://www.ARSLIST.org

**
Lily - part of it is an education / training issue - I told individuals with floating licenses to do what they have to do and then exit Remedy as others are waiting for licenses. I also set the server to drop their floating license after 1 hour of inactivity.

On another note just because they don't have a floating license does not stop them from working - they can still search, create new tickets, run reports, etc. the only thing they can't do without a license is "modify".

Ty


-----Original Message-----
From: Lam, Lily [mailto:Lily.Lam@CCRA-ADRC.GC.CA]
Sent: Tue 10/8/2002 1:21 PM
To: ARSLIST@LISTSERV.QMXS.COM
Cc:
Subject: floating licenses



**

Hi,

I would like to know how you guys manage licenses. We're using the Remedy's
recommendation of 1 floating license per 3 users. Still, our users are
constantly complaining they are unable to submit or modify tickets. Everyday
we track the number of licenses being used. Throughout the day we see that
all floating licenses are being used and 20-40 users are waiting for a
floating write license. Since Remedy has changed when a floating write token
is issued (i.e. anytime you query, submit, modify, a floating license is
taken) did you guys just buy more licenses or did you do something else?

Thanks in advance,
Lily


You may control your subscription options, including UNSUBSCRIBE,and ACCESS THE ARCHIVES at http://www.ARSLIST.org


You may also control your subscription options, including UNSUBSCRIBE, at http://www.ARSLIST.org This posting was submitted via the Web interface

**
Dee:

The reset of floating licenses does not work if they are using autorefresh. Also logging out and in is NOT an option where I am at. I suggest approaching management with the suggestion of moving some folks to fixed licenses, especially the frontline engineers and analysts that are constantly updating actions. This is 'cheaper' than buying 20 to 30 more floating licenses.

James Mckenzie

-----Original Message-----
From: Dee, Tyrone [mailto:tdee@KNOWSYSINC.COM]
Sent: Tuesday, October 08, 2002 10:44 AM
To: ARSLIST@LISTSERV.QMXS.COM
Subject: Re: floating licenses
Sensitivity: Confidential


**
Lily - part of it is an education / training issue - I told individuals with floating licenses to do what they have to do and then exit Remedy as others are waiting for licenses. I also set the server to drop their floating license after 1 hour of inactivity.

On another note just because they don't have a floating license does not stop them from working - they can still search, create new tickets, run reports, etc. the only thing they can't do without a license is "modify".

Ty


-----Original Message-----
From: Lam, Lily [mailto:Lily.Lam@CCRA-ADRC.GC.CA]
Sent: Tue 10/8/2002 1:21 PM
To: ARSLIST@LISTSERV.QMXS.COM
Cc:
Subject: floating licenses



**

Hi,

I would like to know how you guys manage licenses. We're using the Remedy's
recommendation of 1 floating license per 3 users. Still, our users are
constantly complaining they are unable to submit or modify tickets. Everyday
we track the number of licenses being used. Throughout the day we see that
all floating licenses are being used and 20-40 users are waiting for a
floating write license. Since Remedy has changed when a floating write token
is issued (i.e. anytime you query, submit, modify, a floating license is
taken) did you guys just buy more licenses or did you do something else?

Thanks in advance,
Lily


You may control your subscription options, including UNSUBSCRIBE,and ACCESS THE ARCHIVES at http://www.ARSLIST.org


You may also control your subscription options, including UNSUBSCRIBE, at http://www.ARSLIST.org This posting was submitted via the Web interface

You may also control your subscription options, including UNSUBSCRIBE, at http://www.ARSLIST.org This posting was submitted via the Web interface

**

You have to look at how the people are using the product. If people get
in ARS and stay in ARS all the time it is cheaper to purchase fixed
licenses about 3 to 1. If a floating license is waiting to time out it
can take anywhere from 1 to 2 hours, if you use the minimum setting for
time out. Floating licenses work best where the person gets in ARS does
their thing and then gets out of ARS.

Mike J.

>>> Lily.Lam@CCRA-ADRC.GC.CA 10/08/02 01:21PM >>>
**

Hi,

I would like to know how you guys manage licenses. We're using the
Remedy's
recommendation of 1 floating license per 3 users. Still, our users are
constantly complaining they are unable to submit or modify tickets.
Everyday
we track the number of licenses being used. Throughout the day we see
that
all floating licenses are being used and 20-40 users are waiting for a
floating write license. Since Remedy has changed when a floating write
token
is issued (i.e. anytime you query, submit, modify, a floating license
is
taken) did you guys just buy more licenses or did you do something
else?

Thanks in advance,
Lily


You may control your subscription options, including UNSUBSCRIBE,and
ACCESS THE ARCHIVES at http://www.ARSLIST.org


You may control your subscription options, including UNSUBSCRIBE,and ACCESS THE ARCHIVES at http://www.ARSLIST.org

**

Lily,

This is a subject for constant discussion on the list.
The issue with floating licenses is always going to be the
release time. Suggest you look at your users and seriously
consider adding dedicated fixed licenses for those users that
may be in Remedy for extended periods of time and MUST have
unrestricted R/W capabilities. There is no hard and fast
formula for Fixed vs. Floating licenses that work in all
situations.

Yes, you need to purchase more licenses, sorry.

Regards...Gidd

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@LISTSERV.QMXS.COM]On Behalf Of Lam, Lily
Sent: Tuesday, October 08, 2002 10:22 AM
To: ARSLIST@LISTSERV.QMXS.COM
Subject: floating licenses
Sensitivity: Confidential


**

Hi,

I would like to know how you guys manage licenses. We're using the Remedy's
recommendation of 1 floating license per 3 users. Still, our users are
constantly complaining they are unable to submit or modify tickets. Everyday
we track the number of licenses being used. Throughout the day we see that
all floating licenses are being used and 20-40 users are waiting for a
floating write license. Since Remedy has changed when a floating write token
is issued (i.e. anytime you query, submit, modify, a floating license is
taken) did you guys just buy more licenses or did you do something else?

Thanks in advance,
Lily



You may control your subscription options, including UNSUBSCRIBE,and ACCESS
THE ARCHIVES at http://www.ARSLIST.org


You may control your subscription options, including UNSUBSCRIBE,and ACCESS THE ARCHIVES at http://www.ARSLIST.org

**

Or... Instead of purchasing more license... Make your separation of your
users functions greater.

A "Read" license (no cost) can "Submit", "Search", and (if Submitter
mode is = locked) can update data they created.

"Float" and "Fixed" license are only needed when the user will be
modify "other users" data. So give the "Self service" people "Read" license.
Have them call the "Central support personnel" if they need to "update" data
that is not theirs. (The "Central support personnel" get the "Float" or
"Fixed" license.)

If you can convince your management that 80-90% of the work can be
done with "Self service" and the other 10-20% needs to be "managed anyway",
then this model works very well. You train your "Central" people to help the
users with the "Self-Help" and to know where "Self-Help" crosses the line
into "Things they have to do for the end users".

AKA:
"I need to reset my password." Vs. "I need to reset Bob's password."
Both are password resets, but the later case requires the requestor to be
"authorized to alter Bob's account." and most likely needs to be tracked
(managed) much more closely.


Just my two cents.

--
Carey Matthew Black

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.


You may control your subscription options, including UNSUBSCRIBE,and ACCESS THE ARCHIVES at http://www.ARSLIST.org

**

We're getting along with a ratio of about 6 to 1 right now. There are
several things that are a factor in getting a ratio that high.

1. Many of our staff are very infrequent users, so one license goes a
long way.

2. Most of the above use ARS via a web interface that logs in and out
for each browser submit. When Logout is done explicitly, the license
goes right back into the pool.

3. Use a more recent version of ARS. 4.5 was (I think) the first version
that delayed the assignment of a floating license until it was actually
needed for a modify operation. 5.x adds the ability to group licenses
in pools, so you can define the ratio you need to support, say, a 2.5-1
ratio for a critical group.

4. Matt's suggestions below are excellent, aside from the concern I have
that he might have worn all the paint off his "quote" key! You definitely
need to know your user mix. License pools will help.

"Black, Matt" wrote:
>
> **
>
> Or... Instead of purchasing more license... Make your separation of your
> users functions greater.
>
> A "Read" license (no cost) can "Submit", "Search", and (if Submitter
> mode is = locked) can update data they created.
>
> "Float" and "Fixed" license are only needed when the user will be
> modify "other users" data. So give the "Self service" people "Read" license.
> Have them call the "Central support personnel" if they need to "update" data
> that is not theirs. (The "Central support personnel" get the "Float" or
> "Fixed" license.)
>
> If you can convince your management that 80-90% of the work can be
> done with "Self service" and the other 10-20% needs to be "managed anyway",
> then this model works very well. You train your "Central" people to help the
> users with the "Self-Help" and to know where "Self-Help" crosses the line
> into "Things they have to do for the end users".
>
> AKA:
> "I need to reset my password." Vs. "I need to reset Bob's password."
> Both are password resets, but the later case requires the requestor to be
> "authorized to alter Bob's account." and most likely needs to be tracked
> (managed) much more closely.
>
> Just my two cents.
>
> --
> Carey Matthew Black
>
> Solution = People + Process + Tools
> Fast, Accurate, Cheap.... Pick two.
>
>
> You may control your subscription options, including UNSUBSCRIBE,and ACCESS THE ARCHIVES at http://www.ARSLIST.org

--
G. David Frye gdf@uiuc.edu
CCSO - Systems and Operations - ARS Development (217) 333-7439
University of Illinois at Urbana-Champaign


You may control your subscription options, including UNSUBSCRIBE,and ACCESS THE ARCHIVES at http://www.ARSLIST.org