Revisiting an old topic: licensing/titlement and "redistribution"



Hi everyone, this topic has been brought up from time to time, but
generally I've seen conflicting answers (and have just received one
from my RH sales rep).

To avoid getting too overcomplicated by describing my specific
situation, I'm trying to determine if a copy of RHEL was purchased
(entitlement and support for one year say), are we then allowed to take
the installation media and reinstall it to X number of machines and
just _not_ take advantage of support or updates for those machines?

This was my initial understanding of things, but reading over the
Enterprise Agreement and EULA it seems that this may not be the case.

However I am confused because I understand that you can get a 30-day
trial of RHEL and continue using it legally even after the trial is
completed. I'm not sure what the "real" difference is between simply
reinstalling from media to many machines and downloading 50 trial
copies and doing the same.

In addition, you can continue to use a paid-for installation of RHEL
after the entitlement has run out.

My ultimate goal here is not to fleece RH out of any $$ they are owed,
but to get a handle on what we should and should not be paying for, and
perhaps get a tighter rein on what is and isn't installed around here.
:)

The vast majority of our RHEL installs are point-release specific -- ie
RHEL4 U4, and are not really production machines but just done to
reproduce a problem or verify compatibility. It would be nice in these
situations to just slap a copy of RHEL on a machine for a few weeks and
not need to worry about tracking down whether or not we have a valid
entitlement, etc, etc, or even worse trying to reconcile it all at the
end of the year when subscriptions expire :)

Thanks in advance for any thoughts.
Ray

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



Relevant Pages

  • Re: Linux clients in network - experiences?
    ... as you're bound to buy more machines, deal with hardware failures, etc. ... can deal with installation, tough you may want to hack it so that most ... you'll need a secure channel to the install server (we use a dedicated ssh ... the Packages.gz lists that apt-get uses on "normal" ...
    (Debian-User)
  • Re: Software Update - Distribution Status; How is this reported back to SMS?
    ... For all new machines that are added to the network, ... office2003 sp2 pre-installed with SP2 before the advanced client is ... installed via Client Push Installation. ... The compliance reports indicate ...
    (microsoft.public.sms.admin)
  • Re: Licenses for 10.2?
    ... md5sum to produce a checksum for both the burnt image and the ISO. ... 'firstboot' option in YaST setup that completes the installation. ... much machines as you bandwith can handle. ...
    (alt.os.linux.suse)
  • Re: Problems with Email, cusmapi
    ... VFP ships with MAPI controls, ... Does MAPI get installed during the automatic installation of Outlook? ... line of code fails on the machine where the program fails and ... WOULD fail on those machines as well. ...
    (microsoft.public.fox.helpwanted)
  • Re: SMS 2k3 Advanced Client not installing...
    ... Can you run a command session as local sytem and try to do a net stop on the ... > may try on one client to remove BITS then re-install the advanced client. ... >>> Have you configured your Push Installation account? ... I can't tell you SP level on>> all machines, is there a minimum I might be missing? ...
    (microsoft.public.sms.setup)