<div>
why not use VMware Converter directly?
</div>


<div>
covnerter direct is not an option - mobo is dead, so I had to pull the disk and cold image it from a temporary mobo.<br />
<br />
Does Covnerter not read a &quot;bare&quot; v2i file?
</div>


covnerter direct is not an option - mobo is dead, so I had to pull the disk and cold image it from a temporary mobo.

Does Covnerter not read a "bare" v2i file?

<div>
that is correct, converter will not read a v2i file. &nbsp;It will only ready sv2i file which is the index for the for the image and doesn't actually contain drive data.
</div>


that is correct, converter will not read a v2i file.  It will only ready sv2i file which is the index for the for the image and doesn't actually contain drive data.

<div>
Symantec's MO lately, provide 95% of a good solution with the missing 5% being the MOST IMPORTANT!!!
</div>


Symantec's MO lately, provide 95% of a good solution with the missing 5% being the MOST IMPORTANT!!!

<div>
VMware Converter could do with an update! (it's quite outdated!)
</div>


VMware Converter could do with an update! (it's quite outdated!)

<div>
another option worth a try is to use BESR converter to convert to a windows version of vmdk. &nbsp;Afterwards create a VM using vmware server or workstation. &nbsp;Attach vmdk and run. &nbsp;If it works you can use vmware converter to convert to an ESXi VM.
</div>


another option worth a try is to use BESR converter to convert to a windows version of vmdk.  Afterwards create a VM using vmware server or workstation.  Attach vmdk and run.  If it works you can use vmware converter to convert to an ESXi VM.

<div>
<div class="content wysiwyg-content">
I did a cold image using BESR 2010 of a Windows 2003 disk. I have a single disk.v2i file.<br />
<br />
Now, vmware converter 4.3 only shows sv2i files for Symantec images. &nbsp;If I rename the v2i file to sv2i, vmware converter does not like it.<br />
<br />
How do I get a cold image from the source disk in a format vmware converter likes?
</div>
</div>


I did a cold image using BESR 2010 of a Windows 2003 disk. I have a single disk.v2i file.

Now, vmware converter 4.3 only shows sv2i files for Symantec images.  If I rename the v2i file to sv2i, vmware converter does not like it.

How do I get a cold image from the source disk in a format vmware converter likes?

Symantec BESR cold image --&gt; vmware converter. no sv2i file!

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.

VMware

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Symantec BESR cold image --&gt; vmware converter. no sv2i file!

Symantec BESR cold image --> vmware converter. no sv2i file!