AnsweredAssumed Answered

vrf Font Setup

Question asked by VRFuser on Jun 5, 2002
Latest reply on Jun 5, 2002 by VRFuser
I need to add more fuel to this fire:

I see this new policy as being analogous to the ownership of an automobile.
If you happen to own several and you are the only driver for any of those
vehicles, then you must pay the license and insurance fees on each vehicle.
This gives you the priviledge of driving any of them on a public highway but
only one at a time.  And these fees recur annually.

I discussed this issue with a very experienced Agilent sales rep on Monday
and he was unaware of this new policy for the VEE product.  But he did talk
about two other Agilent products which use the same licensing principle.  So
it appears that the policy for Agilent products is evolving, but the field
sales force may not have been notified.  That might suggest that quality
sales force feedback for this policy never reached Loveland marketing.

I  hope that Agilent has a solution for secure government/aerospace
facilities that have an intranet but no internet where they can connect to
Agilent for downloading VEE 6.1 bits.  The computers don't ever come out of
those facilities after they first enter; they are crushed and the hard
drives crushed and burned.  This would appear to prohibit any form of
flexibility at those facilities.  There are several of those facilities
around Denver and certainly many more throughout the USA.  This definitely
seals the fate of VEE for potentially a large number of customers.

I discussed this problem with one of my customers on Tuesday and their IT
personnel were very displeased with the support issue.  They insist on
maintaining their control over the computers in the facility and
independently managing licenses.  They are not planning to order VEE 6.1 but
are staying in VEE 5.x and 6.01 until they decide which path is best for
future systems.  We may eventually move from VEE because of this policy.

Agilent:  I'm sure you have been listening to the discussion but I suspect
that marketing has your hands tied.  This is disappointing.

Best Regards,
George Tyrrell
TestDynamics LLC


----- Original Message -----
From: "SHERRILL,DAVID S (A-hsgAndover,ex1)" <david_sherrill@hsgmed.com>
To: "'Reiner Schlieker'" <REINERS@milltronics.com>; <vrf@lvld.agilent.com>;
<robert@wscw.com>
Sent: June 06, 2002 7:47 AM
Subject: RE: vrf Licensing of VEE


> Keep in mind that a NIC only costs $10.  Surely none of us has a budget so
> tightly controlled that a VEE upgrade is OK but adding $10 kills the deal.
>
> If security issues prevent someone from adding a NIC to a system, one can
> surgically remove the LAN cable connector before installing the NIC.
>
> That leaves users who's systems physically cannot accept a NIC
(rack-mounted
> single-board computers come to mind).  I would hope that Agilent can make
> some accommodation for these users.
>
> On another approach, is there any sort of Windows registry mischief -- I
> mean magic -- that would induce Windows to report a LAN connection and MAC
> address even in the absence of a NIC?  Perhaps not, as this would
completely
> subvert this rather common license locking strategy.
>
>    ...david
>
> David Sherrill
> Philips Medical Systems
> Andover, Massachusetts
> USA
>
>
>    ...david
>
> -----Original Message-----
> From: Reiner Schlieker [mailto:REINERS@milltronics.com]
> Sent: Thursday, June 06, 2002 9:25 AM
> To: vrf@lvld.agilent.com; robert@wscw.com
> Subject: vrf Re: Vrf Licensing of VEE
>
>
> I've recently spoken directly with Nicole and Scott at Agilent, and as the
> question was a concern to many of us, I put the question to them.  They
> assured me that there will be a process in place to be able to register
your
> current software on a new machine if necessary - how quickly this can be
> achieved remains to be seen.  (This information is to be revealed soon on
> the website, I'm told)  As for myself, this doesn't help me, as most of my
> test systems do not have a NIC in them.  And, you DEFINITELY need an NIC
to
> use VEE 6.1, there is no other way around it.  As a result, it would seem
I
> will be unable to ever upgrade again, except at great expense. This annoys
> greatly as I happen to like VEE very much, and would have appreciated
being
> able to stay current with the program.
>
> I have a question for the VEE users out there:  Nicole and Scott feel my
> situation is unusual in that I troubleshoot the testers on the production
> floor, using the development version of VEE.  As I'm the only user of VEE
> here, I felt justified in installing it on all my testers, as I can only
use
> one at a time anyway.  This new licensing would force me to install a NIC
in
> each tester, and buy a license for each machine.  My question is, does
> everybody else troubleshoot their test systems on a separate development
> only platform?  I cannot believe this is the case, especially if looking
for
> a faulty instrument!
>
> Any responses would be appreciated, and hopefully Agilent is listening...
>
>
>
> Reiner Schlieker
> Test Equipment Designer
> Siemens Milltronics Process Instruments Inc.
> Phone: (705) 740-7553
> Fax:      (705) 740-7692
> e-mail: reiners@milltronics.com
>
>
> >>> "Robert Reavis" <robert@wscw.com> 06/05/02 09:58PM >>>
> Regarding the recent flurry of messages about the NIC as a licensing
tool...
> I liked the response from Jeff Davis (repeated at the end).
>
> That is not as far fetched as you think.  Last week my laptop released an
> unusual aroma.  Electronic developers know it well.  When I took it to the
> repair shop, the answer was, "It needs to go back to the factory for
> repairs."  We removed my hard drive and put it into a new chassis.
> Everything(!) is different (NIC too) except the software.
>
> My two cents worth...
> We went through this hassle twenty years ago when the PC industry was new.
> Those of us who lived through this remember all the techniques that were
> tried and abandoned as simply too much trouble.  Companies that continued
> the practice simply lost markets to other companies that stopped the
> practice.
>
> There were dongles that were forgotten about when the software's prime
user
> changed assignments and moved, the replacement who had his own computer
and
> knew nothing about the dongle and spent days or weeks looking for it.
>
> There were encrypted sectors on a floppy that transferred a "key" to the
> hard drive during the installation proccess.  Then the hard drive crashed
> and you tried to re-install the software on the new drive and found out
the
> key was missing.
>
> There were activation keys available only from the manufacturer for a
price
> and only worked once.
>
> Now it is the NIC.  New item, same problems.
>
> The essential point is trust.  Does Agilent trust its customers or not?  I
> think we are getting signals now.
>
> Robert Reavis
> Warm Springs Computer Works
> Fremont, California
>
> ______________________________________________________________
>
>
> > What about this one Mike...
> >
> > Saturday evening...EMERGENCY troubleshooting session on a High-Rel job
> that
> > has a MAJOR deadline...Your development machine cooks off for some
reason,
> > and WILL NOT boot; could be an OS problem, could be a hardware problem,
it
> > doesn't matter since you cannot get your development machine to boot.
> >
> > You decide to install VEE on a backup machine just to get you through
the
> > troubleshooting session.
> >
> > WRONG !!!
> >
> > During the installation, you are prompted by VEE that your license ID is
> > invalid. You decide AHH HAA!  I will swap the NIC's from the unbootable
> > machine to the backup machine.
> >
> >
> > WRONG!!!
> >
> > Your company does not allow its users to have ADMIN rights on the client
> > machines, you are shut down until you can get an IT guy to come in and
> swap
> > the card. You lose valuable development time waiting for the IT guy to
> show
> > up, IF you can even get one to respond to your emergency pages.
Rearrange
> > this scenario to happen on a LAPTOP with integrated NIC, and now you
> cannot
> > even SWAP the NIC's to get you through the emergency troubleshooting
> > session.
> >
> > I know it seems like a stretch, but is it really that far off ? I am not
> > trying to hammer on Agilent, I just do not like the idea that they are
> > adding this security feature without providing details on it on their
> > website ~
> >
>
>
> ---------------------------------------------------------------------
> This is the "vrf" maillist, managed by Majordomo.  To send messages to
> this maillist, just email to "vrf@lvld.agilent.com".  Subscriptions and
> unsubscriptions are done through the address
"vrf-request@lvld.agilent.com".
> If you need details, just send a message containing the text "help"
> to "vrf-request@lvld.agilent.com".
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> This is the "vrf" maillist, managed by Majordomo.  To send messages to
> this maillist, just email to "vrf@lvld.agilent.com".  Subscriptions and
> unsubscriptions are done through the address
"vrf-request@lvld.agilent.com".
> If you need details, just send a message containing the text "help"
> to "vrf-request@lvld.agilent.com".
> ---------------------------------------------------------------------
> ---------------------------------------------------------------------
> This is the "vrf" maillist, managed by Majordomo.  To send messages to
> this maillist, just email to "vrf@lvld.agilent.com".  Subscriptions and
> unsubscriptions are done through the address
"vrf-request@lvld.agilent.com".
> If you need details, just send a message containing the text "help"
> to "vrf-request@lvld.agilent.com".
> ---------------------------------------------------------------------


---------------------------------------------------------------------
This is the "vrf" maillist, managed by Majordomo.  To send messages to
this maillist, just email to "vrf@lvld.agilent.com".  Subscriptions and
unsubscriptions are done through the address "vrf-request@lvld.agilent.com".
If you need details, just send a message containing the text "help"
to "vrf-request@lvld.agilent.com".
---------------------------------------------------------------------

Outcomes