Not for Resale VMware License Information

Products

• Support Portal
• Global Customer Assistance

Issue/Introduction

This article defines the Broadcom partner Not for Resale (NFR) license program for VMware by Broadcom products, including partner responsibility, partner eligibility criteria, acceptable use cases, and the request process.

Important notes:

• NFR Licenses (NFRs) may be requested by Broadcom Advantage Partner (BAP) program partners:
• With a current Pinnacle, Premier, or Select-level Reseller Agreement
• The Reseller Agreement is with a VMware (software) Division
• NFR requests are submitted, on their partners’ behalf, by Broadcom employees in Partner Business Manager or Partner Account Director roles.
• Customers are ineligible to request, receive, or view NFRs.
• NFRs are subject to all terms, conditions, and limitations of the Broadcom End User Agreement, transaction documents, and Specific Product Documentation.
• Product availability is limited to the VMware by Broadcom price book published on the date of request.
• Approved requests are fulfilled with current-version VMware products.
• License duration is 1 year.
• Quantity is determined based upon the requesting partner’s use case, BAP tier, and alignment to VMware by Broadcom strategy.
• NFRs may be used for partner test, demo, training, and development purposes only, as authorized by BAP program guidelines and agreements. See below for a sampling of acceptable use cases.
• Use of NFRs in any production environment is strictly prohibited. NFRs may not be used to manipulate, test, transmit, or host protected / private customer or partner data.
• Under no circumstances will issued-to partners share or otherwise expose NFRs to other parties. If keys are or were exposed, Broadcom reserves the right to take legal and / or programmatic action against the originally requesting partner.
• NFRs are ineligible for Broadcom Software Maintenance (support).
• Broadcom reserves the right to collect NFR consumption and utilization statistics to demonstrate the effectiveness of the solutions provided. Collected data may be used to support a Partner’s business plan metric requirements.
• NFR keys may be re-used if the issued-to partner has multiple demo environments, i.e., in different cities or within a Holodeck VMware Cloud Foundation (VCF) architecture. Re-use scenarios and multi-deployed locations must be clearly identified and described in each NFR request.
• Within 30 days of expiration, as-is NFR license renewal may be requested as long as recipient BAP partners continue fulfilling all terms identified above, and applicable business plans include the focus products requested.

Allowed Use Examples 

• The requesting partner is developing a VMware by Broadcom consulting services offering, so applies NFRs to a test / validation environment.
• The partner operates an internal-facing enablement lab used to train their own employees on VMware by Broadcom solutions.
• A pre-sales environment is used to demonstrate and promote VMware by Broadcom solutions to internal parties, other BAP partners, or customers.

Prohibited Use Examples 

• Use of NFRs in any customer-hosted environment.
• Developing an adjacent offering like backup. This and similar use cases are addressed by the Broadcom Technology Alliance Partner (TAP) program (https://tap.broadcom.com/web/tap/home).
• Any partner or customer production / revenue-generating purpose, to include training.
• Customer Proofs of Concept (POCs). Partners may request Customer POC licenses via a partner-initiated request process.
• Temporary license expansion for overage during migration, acquisition, consolidation or conversion.
• License bridging of any type or purpose. For example: 
  • Support renewal gaps for production licenses
  • POC license expiration prior to purchase fulfillment
  • Trial license expiration prior to purchase fulfillment

Resolution

Not for Resale (NFR) license requests are neither auto-generated nor auto-renewed. Rather, Broadcom employees in direct partner management roles initiate requests on their partners’ behalf. BAP partners who don’t know their manager may contact [e-mail]. All requests are manually reviewed and validated based on the criteria mentioned in this Article.

Table of Contents

• Request Process
• Delivery Process

Request Process

1. A partner’s business owner notifies their Broadcom business contact (hereafter referred to as “contact”) to initiate a request for NFRs.
   
   
2. The contact submits an internal-to-Broadcom form, which initiates the quote process. Each NFR request submittal requires:
   • Partner name, ERP Account Number, and deployment region(s)
   • Multi-region details must be input in submission form’s Notes field
   • Partner Account Director or Partner Business Manager contact information
   • BAP VMware resale tier (must be Pinnacle, Premier, or Select)
   • Partner’s Sold-To Account Name & Address
   • Partner’s Bill-To Account Name & Address
   • Partner’s Ship-To Account Name & Address
   • Requested products and quantities from the then-current Partner price book
   • Partner’s license POC name & Email address (the destination for new Key issued communication)
   • Email aliases are not permitted
   • POCs are recommended to be existing Product Administrators in the Broadcom Customer Support Portal with access to the Site ID associated with the Ship-To Address.
   • Detailed use case descriptions
   • Notes to fully support unique requests or exceptions to policy
     
     
3. For each NFR request, the contact will confirm:
   • They have reviewed, with their partner, acceptable and unacceptable use criteria.
   • Their partner understands and agrees to NFR terms.
   • Each request addresses an acceptable business-focused use case.
   • The requesting partner’s business plan includes the Focus Area(s) identified in the request
   • Capacity required by the partner within the next year is met by the request
   • Non-technical contacts may consult with partner-supporting technical teams on variance from standard request quantities.

Delivery Process

1. Approved requests are processed as a special quote, then delivered as a special entitlement to the Broadcom Support Portal.
2. NFRs are delivered to the Support Portal Site ID associated with the requested partner’s Ship-To email address identified in the NFR request.
3. The individual identified in the request’s Ship-To receives email notification of the new entitlement.
4. Support Portal Product Administrators can, after keys are delivered, perform License Key Management functions on the delivered NFRs.
   
   

Tips for Successful Notification

• Contacts are encouraged to advise Ship-To email recipients to check SPAM folders and, if necessary, to whitelist the address [e-mail].
• Contacts should ensure all provided partner email addresses are associated with currently employed individuals.
• Fulfillment email messages are sent from [e-mail], with the subject “Broadcom Software Final Fulfillment Notification for Contract #####.” In this example, “####” is a placeholder.
• Lost, missed, or misrouted delivery notifications caused by incorrectly entered information are the responsibility of the contact.