**
Also some of us smaller but not that small houses look at the Total Cost of Ownership how much have we spent on this product say since 1999 in initial cost, training cost, license cost, support cost. Does the product save us that much or more are we breaking even or losing in the long run. Also consulting time, upgrade time and downtime. Also like said earlier we would rather pay a site license and support fee based on a sliding scale on our user base say $100.00 a seat for 100 seats which includes license and support for one year of course that is a very small number right now we pay closer to $250.00 a seat per year in support which added to TCO makes this a very expensive product...that does not make us money.

W. Kevin Colwell
Help Desk Administrator
CDPHP
1223 Washington Avenue
Albany, New York 12206
e-mail: kcolwell@cdphp.com

CONFIDENTIALITY NOTICE: This e-mail, including attachments, is for the sole use of the individual to whom it is addressed, and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you have received this e-mail in error, please notify the sender by reply e-mail and destroy this message and its attachments.

>>> baltimore-1@MEDCTR.OSU.EDU 12/18/03 06:49AM >>>
**
Amen brother! Testify!

Warren

>>> R.Phillips@LATROBE.EDU.AU 12/17/2003 8:39:49 PM >>>

**

Comments on your issues are below each bullet.

-James

Quoting Rick Parry :
>
> 1) We run Crystal Enterprise for reporting. With this system we have it
> configured so when a report request is made it looks to see what report
> server is available to run the report. It then passes the report to that
> server. All the servers are setup with the Remedy ODBC driver. The same
> user id and password is used for each report server. If I roll out
> Remedy 6 I now have to configure each report server with there own login
> id and password. This add's more work to our already busy schedule. One
> of the strengths of Remedy has been the small team size needed to
> administer the servers and applications. With changes like these more
> staff will be needed. Not good. Not good at all.

If you are using a login to access only reports, then you really should not be
using a Fixed or Floating license anyway. Fixed and Floating licenses should
only be used when data needs to be modified in Remedy by users or applications
integrated with the Remedy application. Whether you stay with 5.x or upgrade,
you might want to consider switching to a Read (or Restricted Read for 6.x)
license. You will still be able to submit your report requests, but will not
be burning a fixed or floating license on a login designed to only access
reports.

> 2) Now lets talk web submits. We create web pages that use the same
> user id and password for creating records. One reason we take this
> approach is that all the records are created in the same form for those
> pages. This allows us to tailor the submit form to the end user.

According to Remedy, the Read license is not going to be affected by the one
login per IP address restrictin. The Read license will continue to function in
the same manner it functions on 5.x and 4.x.

> 3) We have developers that have multiple computers in there office.
> They like to login and keep the client up and running on each computer.
> Now logically you could look at that and say "They don't need to do
> that." but they do. They may be running through some sort of debug on
> one computer and making notes in Remedy on the other. Then it would
> switch. They are running debug code on the first computer and making
> notes in Remedy on the second. The reality is that this is how your
> users use the system. I know you are trying to stop a group of people
> from sharing a license but you are making life more difficult for those
> of us that don't.

According to Remedy, users who are part of the Administrator group are not going
to be affected by the one login per IP restriction. So your developers will
still be able to login to a test box while still logged in to another computer.

> At this point I can not recommend going the Remedy 6. Your not making
> my life easier your giving me more work.
>
> Well that is my two cents on this item.
>
> Take care,
>
> Rick Parry
>
> Rick Parry
> Remedy Team Lead
> Novell, Inc., the leading provider of information solutions
> http://www.novell.com
>
>

Rick,

Let me try to answer these concerns....

1) That is a very interesting condition that you have. Multiple Report
servers. Some companies do not even have one separate reporting servers.
However, I wonder, what is the license on the account that is used to get
the data for the report server? Is it a "Read" license? Why would a
"Restricted Read" license not work in this case? (Reporting is "Read
only". So change the license for that user and move on. No need to change
anything else.)

2) I also do not see a problem here. (Or do you have multiple web servers
to deal with? Well that is still not a problem.) Use a "Restricted Read"
license and your done. On the other hand you could also give these people
ARS Read license and give them a "custom" view based on some 'Login Name'
to "Preferred View" logic too. (So no need to use "outside website"
building either. Just a thought.)

3) Are these users part of the ARS Administrator group? (or are they
developing other tools/code?)
If part of the ARS Admin group, then they will not be subject to the
"from only one IP address" rule. Sorry that was something that I left out
in my previous post.)
If they are non-ARS Admin users, then they need to get a life. Ok,
that is a bit harsh, but really, why do they need to have multiple
instances of the user tool connected at the same time? Because one CPU is
busy and they don't want to wait? If boxes are cheep enough for these
"users" to have multiple, then give them one more. (If they can use 3 at
the same time then they could use 4 too. They likely already have a hub
setting on their desk and a power strip with an spare plug too.) Make it a
very low end pc and let them run their email and Remedy from it. Keep those
things away from their "debug/compile type work. It really does not take
much to run ARS's client.


Then again, maybe there is more to these conditions than I understand. Let
me know if that is the case.

--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.



"Rick Parry"
M> cc:
Sent by: "Action Subject: Re: What's Coming in Version 6? Here it is ...
Request System
discussion
list(ARSList)"
ORG>


12/18/2003 02:23
PM
Please respond to
arslist






**
Hello Everyone,

I must say number nine does not make me very happy. I will give a few
examples for the Remedy people to take back to management.

1) We run Crystal Enterprise for reporting. With this system we have it
configured so when a report request is made it looks to see what report
server is available to run the report. It then passes the report to that
server. All the servers are setup with the Remedy ODBC driver. The same
user id and password is used for each report server. If I roll out Remedy 6
I now have to configure each report server with there own login id and
password. This add's more work to our already busy schedule. One of the
strengths of Remedy has been the small team size needed to administer the
servers and applications. With changes like these more staff will be
needed. Not good. Not good at all.

2) Now lets talk web submits. We create web pages that use the same user id
and password for creating records. One reason we take this approach is that
all the records are created in the same form for those pages. This allows
us to tailor the submit form to the end user.

3) We have developers that have multiple computers in there office. They
like to login and keep the client up and running on each computer. Now
logically you could look at that and say "They don't need to do that." but
they do. They may be running through some sort of debug on one computer and
making notes in Remedy on the other. Then it would switch. They are running
debug code on the first computer and making notes in Remedy on the second.
The reality is that this is how your users use the system. I know you are
trying to stop a group of people from sharing a license but you are making
life more difficult for those of us that don't.

At this point I can not recommend going the Remedy 6. Your not making my
life easier your giving me more work.

Well that is my two cents on this item.

Take care,

Rick Parry

Rick Parry
Remedy Team Lead
Novell, Inc., the leading provider of information solutions
http://www.novell.com

I would just like to say in all good spirits and humor for number 3, what a
challenge to have to get your users to stop using Remedy so much.
I'm happy when I get my users using Remedy on one pc....

:)
Janie



-----Original Message-----
From: Carey Matthew Black [mailto:matt.black@VERIZON.COM]
Sent: Thursday, December 18, 2003 12:59 PM
To: ARSLIST@ARSLIST.ORG
Subject: Re: What's Coming in Version 6? Here it is ...


Rick,

Let me try to answer these concerns....

1) That is a very interesting condition that you have. Multiple Report
servers. Some companies do not even have one separate reporting servers.
However, I wonder, what is the license on the account that is used to get
the data for the report server? Is it a "Read" license? Why would a
"Restricted Read" license not work in this case? (Reporting is "Read
only". So change the license for that user and move on. No need to change
anything else.)

2) I also do not see a problem here. (Or do you have multiple web servers
to deal with? Well that is still not a problem.) Use a "Restricted Read"
license and your done. On the other hand you could also give these people
ARS Read license and give them a "custom" view based on some 'Login Name'
to "Preferred View" logic too. (So no need to use "outside website"
building either. Just a thought.)

3) Are these users part of the ARS Administrator group? (or are they
developing other tools/code?)
If part of the ARS Admin group, then they will not be subject to the
"from only one IP address" rule. Sorry that was something that I left out
in my previous post.)
If they are non-ARS Admin users, then they need to get a life. Ok,
that is a bit harsh, but really, why do they need to have multiple
instances of the user tool connected at the same time? Because one CPU is
busy and they don't want to wait? If boxes are cheep enough for these
"users" to have multiple, then give them one more. (If they can use 3 at
the same time then they could use 4 too. They likely already have a hub
setting on their desk and a power strip with an spare plug too.) Make it a
very low end pc and let them run their email and Remedy from it. Keep those
things away from their "debug/compile type work. It really does not take
much to run ARS's client.


Then again, maybe there is more to these conditions than I understand. Let
me know if that is the case.

--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.



"Rick Parry"
M> cc:
Sent by: "Action Subject: Re: What's Coming
in Version 6? Here it is ...
Request System
discussion
list(ARSList)"
ORG>


12/18/2003 02:23
PM
Please respond to
arslist






**
Hello Everyone,

I must say number nine does not make me very happy. I will give a few
examples for the Remedy people to take back to management.

1) We run Crystal Enterprise for reporting. With this system we have it
configured so when a report request is made it looks to see what report
server is available to run the report. It then passes the report to that
server. All the servers are setup with the Remedy ODBC driver. The same
user id and password is used for each report server. If I roll out Remedy 6
I now have to configure each report server with there own login id and
password. This add's more work to our already busy schedule. One of the
strengths of Remedy has been the small team size needed to administer the
servers and applications. With changes like these more staff will be
needed. Not good. Not good at all.

2) Now lets talk web submits. We create web pages that use the same user id
and password for creating records. One reason we take this approach is that
all the records are created in the same form for those pages. This allows
us to tailor the submit form to the end user.

3) We have developers that have multiple computers in there office. They
like to login and keep the client up and running on each computer. Now
logically you could look at that and say "They don't need to do that." but
they do. They may be running through some sort of debug on one computer and
making notes in Remedy on the other. Then it would switch. They are running
debug code on the first computer and making notes in Remedy on the second.
The reality is that this is how your users use the system. I know you are
trying to stop a group of people from sharing a license but you are making
life more difficult for those of us that don't.

At this point I can not recommend going the Remedy 6. Your not making my
life easier your giving me more work.

Well that is my two cents on this item.

Take care,

Rick Parry

Rick Parry
Remedy Team Lead
Novell, Inc., the leading provider of information solutions
http://www.novell.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com



IMPORTANT NOTICE: This communication, including any attachment, contains
information that may be confidential or privileged, and is intended solely
for the entity or individual to whom it is addressed. If you are not the
intended recipient, you should contact the sender and delete the message.
Any unauthorized disclosure, copying, or distribution of this message is
strictly prohibited. Nothing in this email, including any attachment, is
intended to be a legally binding signature.

No - not quite right. When developing, you often don't want to run tests
with an Admin log on (because of the different access privileges). You
want to log on as a regular user.

Now, not only does it improve the development process to be able to run
several tests simultaneously, under certain circumstances you may want
to run the same tests under several 'different' test account
configurations. (Especially if you are using change groups)

Which means restrictions on swapping licenses around can also affect
your development process - in an admittedly small, but still seriously
annoying way. When the heat is on, 20 minutes here, 15 minutes there all
adds up to serious headaches.

If Remedy want to keep building technical solutions to problems created
by their ownership philosophy - they could build special NIC-bound user
licenses for development that bypass the usual controls so long as the
client resides on say 3 - 6 specific machines. And if they were smart
they wouldn't charge anything for them.

Yes there would be the odd site that would run a small 'freebie' shop -
but seriously, how many places are going to fork out all the back-end
costs for a six-user implementation?

Again - when either the impact of revenue protection measures or the
simple cost of the product start to exceed the cost of developing
workarounds that do not violate the law, people either stop buying or
start building those workarounds.

Ric Phillips
La Trobe University
Melbourne

-----Original Message-----
From: James Van Sickle [mailto:gothbert@SPAMCOP.NET]
Sent: Friday, 19 December 2003 8:52 AM
To: ARSLIST@ARSLIST.ORG
Subject: Re: What's Coming in Version 6? Here it is ...

Comments on your issues are below each bullet.

-James


According to Remedy, users who are part of the Administrator group are
not going
to be affected by the one login per IP restriction. So your developers
will
still be able to login to a test box while still logged in to another
computer.


UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com

**
Janie, you crack me up. :) I wish I could say all my users use Remedy that much but I too live in the real world. We have some users just like yours.

Take care,

Rick

>>> JSprenge@LHS.ORG 12/18/2003 2:31:21 PM >>>

This posting was submitted via the Web interface
I would just like to say in all good spirits and humor for number 3, what a
challenge to have to get your users to stop using Remedy so much.
I'm happy when I get my users using Remedy on one pc....

:)
Janie



-----Original Message-----
From: Carey Matthew Black [ mailto:matt.black@VERIZON.COM]
Sent: Thursday, December 18, 2003 12:59 PM
To: ARSLIST@ARSLIST.ORG
Subject: Re: What's Coming in Version 6? Here it is ...


Rick,

Let me try to answer these concerns....

1) That is a very interesting condition that you have. Multiple Report
servers. Some companies do not even have one separate reporting servers.
However, I wonder, what is the license on the account that is used to get
the data for the report server? Is it a "Read" license? Why would a
"Restricted Read" license not work in t! his case? (Reporting is "Read
only". So change the license for that user and move on. No need to change
anything else.)

2) I also do not see a problem here. (Or do you have multiple web servers
to deal with? Well that is still not a problem.) Use a "Restricted Read"
license and your done. On the other hand you could also give these people
ARS Read license and give them a "custom" view based on some 'Login Name'
to "Preferred View" logic too. (So no need to use "outside website"
building either. Just a thought.)

3) Are these users part of the ARS Administrator group? (or are they
developing other tools/code?)
If part of the ARS Admin group, then they will not be subject to the
"from only one IP address" rule. Sorry that was something that I left out
in my previous post.)
If they are non-ARS Admin users, then they need to get a life. Ok,
that is a bit! harsh, but really, why do they need to have multiple
ins! tances o f the user tool connected at the same time? Because one CPU is
busy and they don't want to wait? If boxes are cheep enough for these
"users" to have multiple, then give them one more. (If they can use 3 at
the same time then they could use 4 too. They likely already have a hub
setting on their desk and a power strip with an spare plug too.) Make it a
very low end pc and let them run their email and Remedy from it. Keep those
things away from their "debug/compile type work. It really does not take
much to run ARS's client.


Then again, maybe there is more to these conditions than I understand. Let
me know if that is the case.

--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.



! "Rick Parry"
M> cc:
Sent by: "Action Subject: Re: What's Coming
in Version 6? Here it is ...
! Request System
&! nbsp;&nb sp; discussion
list(ARSList)"
ORG>


12/18/2003 02:23
PM
Please r! espond to
arslist






**
Hello Everyone,

I must say number nine does not make me very happy. I will give a few
examples for the Remedy people to take back to management.

1) We run Crystal Enterprise for reporting. With this system we have it
configured so when a report request is made it looks to see what report
server is available to run the report. It then passes the report to that
server. All the servers are setup with the Remedy ODBC driver. The same
user id and password is used for each report server. If I roll out Remedy 6
I now have to configure each report server with there own login id and
password. This add's more work to our already busy schedule. One of the
strengths of Remedy has been the small team size needed to administer the
servers and applications. With changes ! like these more staff will be
needed. Not good. Not good at! all.

2) Now lets talk web submits. We create web pages that use the same user id
and password for creating records. One reason we take this approach is that
all the records are created in the same form for those pages. This allows
us to tailor the submit form to the end user.

3) We have developers that have multiple computers in there office. They
like to login and keep the client up and running on each computer. Now
logically you could look at that and say "They don't need to do that." but
they do. They may be running through some sort of debug on one computer and
making notes in Remedy on the other. Then it would switch. They are running
debug code on the first computer and making notes in Remedy on the second.
The reality is that this is how your users use the system. I know you are
trying to stop a group of people from sharing a license but you are making
life more difficult for those of us that don't.

At this point I can no! t recommend going the Remedy 6. Your not making my
life easier your giving me more work.

Well that is my two cents on this item.

Take care,

Rick Parry

Rick Parry
Remedy Team Lead
Novell, Inc., the leading provider of information solutions
http://www.novell.com



UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
www.QMXS.com



IMPORTANT NOTICE: This communication, including any attachment, contains
information that may be confidential or privileged, and is intended solely
for the entity or individual to whom it is addressed. If you are not the
intended recipient,! you should contact the sender and delete the message.
Any ! unauthor ized disclosure, copying, or distribution of this message is
strictly prohibited. Nothing in this email, including any attachment, is
intended to be a legally binding signature.

This may not be the final word on the licensing topic, but I'd like to say:

1. In most cases, switching from READ to READ RESTRICTED will solve the
problem.
2. If a WEB server uses a common USERID for multiple people, they will all
have the
same IP address (of the web server), which is OK, because you can have
several
instances of one Userid on ONE IP address. ARS 6 prevents the same userid
from
DIFFERENT IP addresses at the same time.
3. You CAN log on to multiple AR Servers from one IP address.
4. You CAN NOT log on to one server, with one userid, from multiple IP
addresses.
5. You CAN log on with multiple userids from one IP address (think citrix).

For the most part, Remedy/BMC is simply trying to enforce the rule "one
person per userid".


ALSO,
I suggested using an update form, but I've been reminded that this is a
violation
of the Remedy End User License And Maintenance Agreement Article 2.3g, which
states at the end:

"Licensee may not bypass, in any way, the use of a Fixed and Floating
license to manage an
update (including, without limitation, submitting a ticket to a parallel
form and then using
workflow to perform the update without a license)."

To be clear, I do not advocate violating Remedy's (or any other company's)
license agreement.
I strongly recommend that license agreements and the governing laws be
obeyed. To quote that
famous cricket, "let your conscience be your guide"

HTH,
Joel

QMX Support Services, Inc.
Joel D. Sender,
Director of Western Operations
JSender@QMXS.com www.QMXS.com


-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@ARSLIST.ORG]On Behalf Of Rick Parry
Sent: Thursday, December 18, 2003 3:32 PM
To: ARSLIST@ARSLIST.ORG
Subject: Re: What's Coming in Version 6? Here it is ...


**
Janie, you crack me up. :) I wish I could say all my users use Remedy that
much but I too live in the real world. We have some users just like yours.


Take care,

Rick

>>> JSprenge@LHS.ORG 12/18/2003 2:31:21 PM >>>


UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
(Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
SERVICES at www.QMXS.com This posting was submitted via the Web interface

**
I received an e-mail from Doug Mueller yesterday, seems we all have it kind of wrong.

Read license: Still exists as it always has. Functionality still same. CHANGE: Can only be used from one IP at a time.

Restricted Read license: Can be used from many different IP's at once. Capable of submitting. CANNOT MODIFY.

I am going to try and speak with Doug today. I'm very concerned about this switch.

Warren

Warren R. Baltimore II
Senior Systems Analyst
Information Systems
The Ohio State University Medical Center
1375 Perry St.
Battelle 13-1-125
Columbus, OH 43201
614-293-2315
baltimore-1@medctr.osu.edu

>>> gothbert@SPAMCOP.NET 12/18/2003 9:40:08 AM >>>

No, the Read license still exists in the same form and fashion that we all know
from 4.x and 5.x. The new one login per IP restriction only exists for Fixed
and Floating licenses according to what the Remedy tech emailed me. The Read
licenses can still submit requests and modify their submitted requests if ARS
is in Submitter Locked mode. Restricted Read is just a Read license without
the ability to submit or modify tickets.

You might want to check the list archives. I posted a reply from Remedy I got
yesterday about the new licensing changes.

-James

Quoting Warren Baltimore :

> I've been reading this thread with much interest (and an equal amount of
> confusion). If I understand what has been said, Remedy is making a mid
> course change that may very well cost them this customer!
>
> I want to lay out my understanding, and if I'm wrong, please correct me (I
> don't want to panic...yet).
>
> Remedy has always allowed the use of a Read License to submit tkts to the
> system (when submitter locked is chosen). This has allowed for the
> development of global guest licenses that could be automatically triggered to
> get customers into the site to submit requests. If I understand what is
> being said, that is no longer possible? Am I correct in understanding that
> there are now 2 Read license types, one will allow for submissions (but has
> to be single threaded) and one can be multi threaded but does not allow for
> interaction with ticket?
>
> If that is true, I may have to reccomend to my admin staff to stop
> considering Remedy for future development. That will suck! Cause I'll be
> out of a job then....
>
> Warren
>
>
> Warren R. Baltimore II
> Senior Systems Analyst
> Information Systems
> The Ohio State University Medical Center
> 1375 Perry St.
> Battelle 13-1-125
> Columbus, OH 43201
> 614-293-2315
> baltimore-1@medctr.osu.edu
>
> >>> Patrick.Zandi@RL.AF.MIL 12/17/2003 11:10:03 AM >>>
>
> Jarl, Axton, Thanks..
> A Couple of Additional thoughts here.. I think this was out once.. Some of
> it..
> I just had a few additions..
>
> If a User logs into a User tool, and then log's into mid-ter (one IP) like
> stated below, then you cannot log in ?
> Or what if I have a JAVA front end, or a ARSPERL front end. the IP is the
> SAME, or is there now going to be a change to the Login API, passing the IP
> value into the script?
>
> So Remedy now is going to limit what customers can or cannot do, based on
> the system they choose to login with{IP}.
> I suppose the only way around this is a NAT'd ::Virtual MAC or Virtual Linux
> or Virtual PC on the box you are one, then you can have multiple instances.
>
> What is the timeout Value set to ? 15 Mintues ??? If you are on the
> usertool, and log out or just X or Blowup. You now have to Wait ?
> CASE in Point::
>
> What about the Technicians who log into their boxes at their desk, and then
> use the Mid-tier to check their tickets?
> They have to go BACK and log out before they go to another persons Station..
> ?? And if on Mid-Tier, does that mean they go to another Workstation, they
> have to Wait 15 minutes to Log in again to check tickets or Update them ???
>
>
> What about Technicians installing Remedy, I usually Test the installation
> with a login and then have them log in.. This is now out the window too.
>
> I am totally Rebellious to this sort of thinking Guys..
> You Either Paid for the USAGE of a Product or you DID NOT !!! I did and
> would like FULL usage !!! Not with 15 Minute Interruptions.
>
> This TOTALLY STINKS --- It Looks like the possibility of Dropping Support
> has Finally come. I might have to stay on 5X for life.
>
> I sure hope this is not the CASE... =8 -/
>
>
> -----Original Message-----
> From: Axton Grams [ mailto:agrams@REMEDY.ACS.UNT.EDU]
> Sent: Wednesday, December 17, 2003 9:52 AM
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: What's Coming in Version 6? Here it is ...
>
>
> I believe it will prompt whether to end the other session, and will transfer
> ownership of the license token between sessions. I think there is also a
> wait period before it can be transferred again, something link 15 minutes.
>
> If the session is ended before the server is accessed from the same user,
> this enforcement does not apply.
>
> Axton
>
> -----Original Message-----
> From: Jarl Groneng [ mailto:jarl.groneng@TELENOR.COM]
> Sent: Wednesday, December 17, 2003 8:46 AM
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: What's Coming in Version 6? Here it is ...
>
> #9 applies to all users.
>
> --
> Jarl
>
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [ mailto:ARSLIST@ARSLIST.ORG]On Behalf Of Mougis, Phil
> Sent: 17. desember 2003 15:08
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: What's Coming in Version 6? Here it is ...
>
>
> **
> I have to tell you #9 is the one I am most concerned about..... Does this
> apply to Client only... or Mid Tier users as well?
>
> I have a process which allows un-named users (actually users click a
> hyperlink which logs them onto a generic account & password) to update a
> custom table we created.. the account used is VERY low security and doesn't
> touch Help or Asset forms...but does relate to Asset information... I have
> 50 fixed Asset licenses... but chose to not use these for this group of
> people (since I didn't want to have to administer the logins....) in fact..
> we use this feature to acknowledge receipt of delivery of assets which have
> been purchased (via a custom module we deployed).. the main concern I have
> had with the web is that users who do not log out (FYI - I have a logout
> button on EVERY web form I have)....
>
> Phil
>
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList)
> [ mailto:ARSLIST@ARSLIST.ORG]On Behalf Of Zandi Patrick S TSgt AFRL/IFOSS
> Sent: Wednesday, December 17, 2003 8:43 AM
> To: ARSLIST@ARSLIST.ORG
> Subject: Re: What's Coming in Version 6? Here it is ...
>
>
> **
> Joel,
> I would like a little more info on # 9, and a little more info on #13
>
> 9 Concerns me, as we have multiple boxes per person here.. I have 3 alone..
> (I know I am Admin) I have people who have a mac and 2 PC's doing
> Development, who use Remedy on different boxes as the SAME time.. I work in
> a Development Shop // Testing // Rebuild // Testing again... With Everything
> you have not seen yet .. This would Stink, having to give more two license
> to one person just because they use it on multiple machines as the same
> time..
>
> 13 I just don't get this..
> -----Original Message-----
> From: Joel Sender [ mailto:arslist@EARTHLINK.NET]
> Sent: Tuesday, December 16, 2003 6:12 PM
> To: ARSLIST@ARSLIST.ORG
> Subject: What's Coming in Version 6? Here it is ...
>
>
> **
> Hi Folks,
> I just took the ARS 6.0 Delta class, and, as usual, Doug & his team have
> taken another giant step forward. Here's a summary of the features that were
> covered in the class:
>
> Expect the 'First Customer Shipment' (FCS) in January. No official date was
> announced.
> SNMP integration is built-in
> Unicode is supported - just select it during install
> We loaded two ARS servers on one PC with one Oracle instance (different ORA
> tables)
> Mid-Tier installed & worked on the first try. Really
> Licensing is different. You send Remedy support your 'Remedy.lic' file and
> they'll send you the same licenses in the new format.
> The license tool is now included in the Admin tool, no longer a separate
> program.
> There's a new license type: "Read Restricted". It's the same as the old
> "Read" except that you can't change ANY DATA, regardless of the "Submitter
> Locked" setting.
> You can only log on a Userid from ONE IP address. Except Admins running the
> Admin tool or "Read Restricted" users.
> You can only change a Fixed License entry in User 3 times in a WEEK. The 4th
> change locks the userid for 3 DAYS.
> AR Server groups allow different functions to reside on different servers
> (sharing a DB instance). Server groups CAN have separate machines for
> Assignment, DSO, Email, Escalations, Flashboards and FTS.
> Server groups can be configured for 'fail-over'. If a server fails, it's
> dedicated function can be automatically picked-up by another server.
> Licenses are shared across the server group.
> AR workflow can be 'bundled' in 'Deployable Applications' This is different
> from Mid-Tier deployment. A form can only reside in one D.Application.
> D.Applications can be exported WITH DATA. You specify the import tool
> options when you add the data to the D.Application.
> Data Archiving has been automated. Open a form in the Admin tool and specify
> how you want it archived (move or copy, based upon a qualification). The
> Archive form is automatically generated, with additional fields for the
> 'Original Entry ID'
> You can export a D.Application and LOCK it in 'Read-Only' or "Hidden" mode.
> There are lots of performance logging options for AR System forms.
> Security groups can be CALCULATED form existing groups. For example, a
> calculated group could include "Support Managers", "Development Managers"
> but NOT 'Education Managers". The group numbers are NEGATIVE
> Dynamic groups are numbered from 60000 to 60999 and extend 'row level'
> access 'a thousand times'
> D.Applications don't have security groups, they have "ROLES", which are
> mapped to local Groups. an application Role can be mapped on each local
> server to which it is deployed.
> Any form can be designated as a 'Home Page'. Click the Home Page button and
> it opens that form. When you logon to AR User, the Home Page opens. Home
> Pages can have a new field type: "Application List". It will list the
> Application 'Entry Points" to which the user has access.
> Entry points can be defined for applications, with security access control.
> Fields in forms can be 'automatically' laid out. You turn this on & off as
> needed.
> View fields are 'filled' in the admin tool to confirm they are correct. Once
> filled, they are not active.
> Char fields can be 'masked' with asterisks when typed in. The data remains
> in clear text for workflow.
> Char fields can be non-editable' so only menu choices can be entered. You
> can not type in the field. Automates the $MENU$ function.
> There's a GUID field that always generates a unique ID across servers.
> The new Windows Global Field remains the same when changing entries.
> Active links can execute on "Events" to synchronize multiple open windows.
> You can define 'events'
> Server-side tables allow filters to perform table operations. Reduces
> network overhead.
> In filters and active links, the IF & ELSE actions can point to different
> Servers and Forms, based on workflow. If you have one form for customers and
> another for employees, you can set the FORM name in a field and the FORM
> specification would have the field name.
> There are new keywords for multiple open windows, i.e. $CURRENTWINID$
> Remedy will work with developers to license their Deployable Applications.
> Flashboards is included. you can have 6 FB's with the ARS license. More that
> that requires an FB license
> Mid-tier 6.0 supports BEA Weblogic 8.1 and Apache 1.3.28 and 2.0.43 &
> Mozilla (Sun 1.2.1, HP. Widows & IBM 1.4)
> Mid-tier no longer requires a license, it's included with AR System.
> Mid-tier tracks the last time an app was deployed, so it won't re-deploy
> when not needed.
> Mid-tier an automatically 'deploy' an app when a user requests it.
> Custom Style Sheets (CSS) is supported.
> There's more, and the details go on & on. It was three intense days of class
> & labs, and a fourth for the "Exam" in order to be RAC certified for ARS
> 6.0. The labs and test are MUCH better than the ARS 5.0 materials - Remedy
> Educational (and everyone else) is clearly out from under Peregrim.
>
> HTH,
> Joel
>
> Joel Sender
> (ARSLIST Backup Admin)
> www.QMXS.com
> JSender@QMXS.com
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
> SERVICES at www.QMXS.com This posting was submitted via the Web interface
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
> SERVICES at www.QMXS.com This posting was submitted via the Web interface
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
> SERVICES at www.QMXS.com This posting was submitted via the Web interface
>
>
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org
> (Support: mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT
> SERVICES at www.QMXS.com
>
>
>
> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
> mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
> www.QMXS.com
>
>

> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
> mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
> www.QMXS.com
>
>
>
>
>

> UNSUBSCRIBE or access ARSList Archives at http://www.ARSLIST.org (Support:
> mailto:support@arslist.org ) ARSList is hosted by QMX SUPPORT SERVICES at
> www.QMXS.com
>





This posting was submitted via the Web interface