<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Limitations</title><link>https://sourceforge.net/p/esxiimaging/wiki/Limitations/</link><description>Recent changes to Limitations</description><atom:link href="https://sourceforge.net/p/esxiimaging/wiki/Limitations/feed" rel="self"/><language>en</language><lastBuildDate>Mon, 29 Oct 2012 02:37:44 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/esxiimaging/wiki/Limitations/feed" rel="self" type="application/rss+xml"/><item><title>WikiPage Limitations modified by Matt</title><link>https://sourceforge.net/p/esxiimaging/wiki/Limitations/</link><description>Unfortunately, we did not have access to any type of Storage Area Network (SAN) or iSCSI network which is commonly found in an enterprise VMware environment to allow for high available through features such as vMotion. Using a SAN or iSCSI would mean virtual machines are stored not on the ESXi server, but on some type of network storage. 

Because we did not have access to these technologies, we are unable to test how out script would work if these types of storage were used. With that being said, we can only support that this script works for imaging virtual machines off of storage local to the ESXi server. Meaning the virtual machines are stored on hard drives directly attached to the ESXi server. 
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matt</dc:creator><pubDate>Mon, 29 Oct 2012 02:37:44 -0000</pubDate><guid>https://sourceforge.net3941649f2d6eca6d9e7de087adf960dbf17b5c99</guid></item></channel></rss>