# Burning a USB drive with VMware ISO file

**URL:** <https://forums.balena.io/t/burning-a-usb-drive-with-vmware-iso-file/5741>\
**Category:** balenaEtcher\
**Created:** [March 25, 2019, 4:34pm UTC](https://forums.balena.io/t/burning-a-usb-drive-with-vmware-iso-file/5741 "2019-03-25T16:34:03Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![ab77](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/ab77/32/2870_2.png) [@ab77](https://forums.balena.io/u/ab77)\
**Post date:** [July 12, 2021, 5:48pm UTC](https://forums.balena.io/t/burning-a-usb-drive-with-vmware-iso-file/5741/7 "2021-07-12T17:48:54Z")

</div>

@felices this is the method you should try:

- download and decompress **generic-x86-64** balenaOS for your application via balenaCloud
- unwrap the payload image from the flasher image using using [GitHub - balena-os/balena-image-flasher-unwrap: Tool for unwrapping balena-image from a balena-image-flasher](https://github.com/balena-os/balena-image-flasher-unwrap) into `output/`
- copy the image to your server rescue system
- from the rescue boot, run `dd if=output/balena.img of=/dev/{{disk}} bs=4M`
- reboot

Your server should appear in your balenaCloud app/dashboard shortly.

If it doesn’t, try doing to same with the development variant on balenaOS so you can SSH in and see what’s going on. If you can see the OS booting but are unable to get network connectivity (ping), it would suggest the NIC in the proliant isn’t part of the NICs supported by the packaged kernel modules, in which case you’ll need to build one manually and create a custom version of the OS. Some examples [here](https://github.com/balena-os/kernel-module-build).

---

_[View the full topic](https://forums.balena.io/t/burning-a-usb-drive-with-vmware-iso-file/5741)._