<?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>topic vLCM &amp;amp; Auto Deploy - Stateful Install to Remote / SAN Disk in VMware vSphere™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vLCM-amp-Auto-Deploy-Stateful-Install-to-Remote-SAN-Disk/m-p/2869485#M40326</link>
    <description>&lt;P&gt;I'm trying to use auto deploy to perform stateful installs on diskless ESXi hosts to an FC SAN disk on our Flasharray (using the 'remote' disk argument).&lt;/P&gt;&lt;P&gt;This works fine unless I configure auto deploy to build the host into a vLCM enabled cluster (which annoyingly is what I want...)&lt;/P&gt;&lt;P&gt;When using a vLCM cluster, auto deploy always fails with 'install --firstdisk specified, but no suitable disk is found' during install.&amp;nbsp; It seems that regardless of what disk arguments you set in the host profile associated with the vLCM cluster, auto deploy insists on using 'firstdisk' - when I want it to use 'remote'.&lt;/P&gt;&lt;P&gt;It works fine if I deploy the host outside the cluster - so, I guess I have a workaround (I could just move the hosts into the cluster after they are deployed), but it feels like this is an undocumented feature / limitation of vLCM and auto deploy, unless I'm missing something.&lt;/P&gt;&lt;P&gt;Anyone with similar experiences?&lt;/P&gt;</description>
    <pubDate>Thu, 30 Sep 2021 09:22:05 GMT</pubDate>
    <dc:creator>mrstorey303</dc:creator>
    <dc:date>2021-09-30T09:22:05Z</dc:date>
    <item>
      <title>vLCM &amp; Auto Deploy - Stateful Install to Remote / SAN Disk</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vLCM-amp-Auto-Deploy-Stateful-Install-to-Remote-SAN-Disk/m-p/2869485#M40326</link>
      <description>&lt;P&gt;I'm trying to use auto deploy to perform stateful installs on diskless ESXi hosts to an FC SAN disk on our Flasharray (using the 'remote' disk argument).&lt;/P&gt;&lt;P&gt;This works fine unless I configure auto deploy to build the host into a vLCM enabled cluster (which annoyingly is what I want...)&lt;/P&gt;&lt;P&gt;When using a vLCM cluster, auto deploy always fails with 'install --firstdisk specified, but no suitable disk is found' during install.&amp;nbsp; It seems that regardless of what disk arguments you set in the host profile associated with the vLCM cluster, auto deploy insists on using 'firstdisk' - when I want it to use 'remote'.&lt;/P&gt;&lt;P&gt;It works fine if I deploy the host outside the cluster - so, I guess I have a workaround (I could just move the hosts into the cluster after they are deployed), but it feels like this is an undocumented feature / limitation of vLCM and auto deploy, unless I'm missing something.&lt;/P&gt;&lt;P&gt;Anyone with similar experiences?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Sep 2021 09:22:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/vLCM-amp-Auto-Deploy-Stateful-Install-to-Remote-SAN-Disk/m-p/2869485#M40326</guid>
      <dc:creator>mrstorey303</dc:creator>
      <dc:date>2021-09-30T09:22:05Z</dc:date>
    </item>
  </channel>
</rss>

