<?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 Clone Windows LUN, Connect in VMWare in VMware Solutions Discussions</title>
    <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Clone-Windows-LUN-Connect-in-VMWare/m-p/46311#M4539</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We a windows LUN connected to a physical windows server.&amp;nbsp; We'd like to clone this volume/LUN and present the LUN to a virtual windows server.&amp;nbsp; I've cloned the LUN, split it from the parent and am trying to connect it using SnapDrive on the windows VM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the process runs fine until the final step when it fails with the following error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-------------------------&amp;nbsp; SnapDrive Operation Start ---------------------------------&lt;/P&gt;&lt;P&gt;Disk connect operation on server - XXXDEV2K3 failed for reason&lt;/P&gt;&lt;P&gt;Failed to create disk in virtual machine, Failed to Map virtual disk: Permission to perform this operation was denied..&lt;/P&gt;&lt;P&gt;--------------------- The complete operation list is shown as follows -------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;********************* Server Name: CCMTSDEV2K3*********************&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Checking input parameters&lt;/P&gt;&lt;P&gt;2. Checking access control&lt;/P&gt;&lt;P&gt;3. Checking policies&lt;/P&gt;&lt;P&gt;4. Turning on space reservation&lt;/P&gt;&lt;P&gt;5. Connecting to the LUN&lt;/P&gt;&lt;P&gt;6. Failed to create disk in virtual machine, Failed to Map virtual disk: Permission to perform this operation was denied.. &lt;/P&gt;&lt;P&gt;------------------------------------------ Operation Done ---------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas on how to resolve this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:02:27 GMT</pubDate>
    <dc:creator>msandona</dc:creator>
    <dc:date>2025-06-05T07:02:27Z</dc:date>
    <item>
      <title>Clone Windows LUN, Connect in VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Clone-Windows-LUN-Connect-in-VMWare/m-p/46311#M4539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We a windows LUN connected to a physical windows server.&amp;nbsp; We'd like to clone this volume/LUN and present the LUN to a virtual windows server.&amp;nbsp; I've cloned the LUN, split it from the parent and am trying to connect it using SnapDrive on the windows VM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the process runs fine until the final step when it fails with the following error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-------------------------&amp;nbsp; SnapDrive Operation Start ---------------------------------&lt;/P&gt;&lt;P&gt;Disk connect operation on server - XXXDEV2K3 failed for reason&lt;/P&gt;&lt;P&gt;Failed to create disk in virtual machine, Failed to Map virtual disk: Permission to perform this operation was denied..&lt;/P&gt;&lt;P&gt;--------------------- The complete operation list is shown as follows -------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;********************* Server Name: CCMTSDEV2K3*********************&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Checking input parameters&lt;/P&gt;&lt;P&gt;2. Checking access control&lt;/P&gt;&lt;P&gt;3. Checking policies&lt;/P&gt;&lt;P&gt;4. Turning on space reservation&lt;/P&gt;&lt;P&gt;5. Connecting to the LUN&lt;/P&gt;&lt;P&gt;6. Failed to create disk in virtual machine, Failed to Map virtual disk: Permission to perform this operation was denied.. &lt;/P&gt;&lt;P&gt;------------------------------------------ Operation Done ---------------------------------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas on how to resolve this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:02:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Clone-Windows-LUN-Connect-in-VMWare/m-p/46311#M4539</guid>
      <dc:creator>msandona</dc:creator>
      <dc:date>2025-06-05T07:02:27Z</dc:date>
    </item>
    <item>
      <title>Re: Clone Windows LUN, Connect in VMWare</title>
      <link>https://community.netapp.com/t5/VMware-Solutions-Discussions/Clone-Windows-LUN-Connect-in-VMWare/m-p/46315#M4541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What type of iSCSI connection are you using in the VM, RDM or MS iSCSI?&amp;nbsp; If using RDM and the ESX(i) software iSCSI initiator, you need to add whatever account is configured in the Snapdrive ESX logon settings to have the appropriate permission on the vCenter/ESX side.&amp;nbsp; Depending on whether you have a single ESX host or multiple hosts managed by vCenter. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assuming you have a vCenter server, as a test, in the vSphere client, go to the vCenter level (the top level), then click the permissions tab.&amp;nbsp; Make sure the user account you have configured in the Snapdrive settings is listed here with the correct permissions.&amp;nbsp; If the account is not there, add it as an administrator, just for testing, to see if this is your issue.&amp;nbsp; Then you can set the correct permissions once you know it works.&amp;nbsp; I don't have the Snapdrive/vCenter security settings in front of me otherwise I'd post them here.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Jan 2011 17:42:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/VMware-Solutions-Discussions/Clone-Windows-LUN-Connect-in-VMWare/m-p/46315#M4541</guid>
      <dc:creator>radnorsan</dc:creator>
      <dc:date>2011-01-21T17:42:04Z</dc:date>
    </item>
  </channel>
</rss>

