<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: VMware vSphere / vCenter Subscription Licensing &amp;amp; Reconciliation Behaviour in SAM Pro in SAM forum</title>
    <link>https://www.servicenow.com/community/sam-forum/vmware-vsphere-vcenter-subscription-licensing-amp-reconciliation/m-p/3476260#M20170</link>
    <description>&lt;P&gt;For vSphere (stand-alone) entitlements, please confirm that you have it set up as follows:&lt;/P&gt;&lt;P&gt;Agreement Type = Enterprise Agreement&lt;/P&gt;&lt;P&gt;License Type = Subscription&lt;/P&gt;&lt;P&gt;License Metric = Per Core, Per Application Instance, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For VCF, you may need to go into the software model and change the metric attribute so that Minimum cores per processor = 16.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The license metric drives license compliance calculations. If you want to include/exclude on-prem, then you would need to set up a sw install condition - typically I use the DNS domain as the filter.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Jan 2026 00:28:35 GMT</pubDate>
    <dc:creator>MikeW0609686430</dc:creator>
    <dc:date>2026-01-28T00:28:35Z</dc:date>
    <item>
      <title>VMware vSphere / vCenter Subscription Licensing &amp; Reconciliation Behaviour in SAM Pro</title>
      <link>https://www.servicenow.com/community/sam-forum/vmware-vsphere-vcenter-subscription-licensing-amp-reconciliation/m-p/3475871#M20161</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;In SAM Pro, how are VMware subscription products handled during reconciliation?&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;For &lt;STRONG&gt;vSphere per-core subscription entitlements&lt;/STRONG&gt;, downgrade rights exist (e.g., vSphere 8 → vSphere 7), but downgraded usage is not reconciled and instead shows under &lt;EM&gt;Install Requires Action – No applicable entitlement&lt;/EM&gt;. Is this expected for subscription license types?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;For &lt;STRONG&gt;vSphere Foundation bundled subscriptions&lt;/STRONG&gt;, only one ESXi host is considered during reconciliation even when usage exists on multiple normalized hosts, leading to non-compliance. Is this due to parent–child bundle roll-up logic or a known limitation?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;When a valid entitlement exists but cannot be reconciled due to bundle or metric qualification, why is usage shown under &lt;EM&gt;Install Requires Action&lt;/EM&gt; instead of &lt;EM&gt;Unlicensed Installs&lt;/EM&gt;?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;For &lt;STRONG&gt;vCenter Server&lt;/STRONG&gt;, entitlements with &lt;EM&gt;Per Application Instance&lt;/EM&gt; metric show a health warning indicating &lt;EM&gt;SaaS – User Subscription License metric&lt;/EM&gt;. Is this a content-level metric classification issue for VMware subscription products?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Finally, can ServiceNow confirm whether &lt;STRONG&gt;vSphere and vCenter Server are classified as on-prem products&lt;/STRONG&gt;, and whether SaaS/subscription tagging in SAM Pro is related only to licensing models rather than deployment type?&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thanks in Advance!!&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 12:51:08 GMT</pubDate>
      <guid>https://www.servicenow.com/community/sam-forum/vmware-vsphere-vcenter-subscription-licensing-amp-reconciliation/m-p/3475871#M20161</guid>
      <dc:creator>Sujithra Govind</dc:creator>
      <dc:date>2026-01-27T12:51:08Z</dc:date>
    </item>
    <item>
      <title>Re: VMware vSphere / vCenter Subscription Licensing &amp; Reconciliation Behaviour in SAM Pro</title>
      <link>https://www.servicenow.com/community/sam-forum/vmware-vsphere-vcenter-subscription-licensing-amp-reconciliation/m-p/3476260#M20170</link>
      <description>&lt;P&gt;For vSphere (stand-alone) entitlements, please confirm that you have it set up as follows:&lt;/P&gt;&lt;P&gt;Agreement Type = Enterprise Agreement&lt;/P&gt;&lt;P&gt;License Type = Subscription&lt;/P&gt;&lt;P&gt;License Metric = Per Core, Per Application Instance, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For VCF, you may need to go into the software model and change the metric attribute so that Minimum cores per processor = 16.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The license metric drives license compliance calculations. If you want to include/exclude on-prem, then you would need to set up a sw install condition - typically I use the DNS domain as the filter.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 00:28:35 GMT</pubDate>
      <guid>https://www.servicenow.com/community/sam-forum/vmware-vsphere-vcenter-subscription-licensing-amp-reconciliation/m-p/3476260#M20170</guid>
      <dc:creator>MikeW0609686430</dc:creator>
      <dc:date>2026-01-28T00:28:35Z</dc:date>
    </item>
  </channel>
</rss>

