VMware Converter 6.2 failed after 3% with error FAILED: An error occurred during the conversion: ‘BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[60-2A-FF-68-00-00-10-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338)’

1 physical server to virtual with VMware Converter 6.2 failed after 3% with error. FAILED: An error occurred during the conversion: 'BlockLevelVolumeCloneMgr::CloneVolume: Detected a write error during the cloning of volume \WindowsBitmapDriverVolumeId=[60-2A-FF-68-00-00-10-00-00-00-00-00]. Error: 37409 (type: 1, code: 2338)' Source machine had Teaming configured and I just pulled out the cabels and put new one in... Continue Reading →

Migrate to Virtual Center 6.7 when the Virtual Center is Virtulized on providers Virtual Center. Migrated Virtual Center has no ip connectivity to local ESXi host. Add extra nic to VirtualCenter is the soloution!

You need ip connectivity from the temp VC to the ESXi host that the upgraded VC is hosted. We want to upgrade VC-CUST (192.168.1.1), in this case migrate to 6.7 from 6.5. This CirtualCenter resides in hosted VirtualCenter VC-Provider. VC-Provider has NO ip connectivity to customer. VC-CUST has no IP connectivity to ESXI host (172.16.1.2)... Continue Reading →

CONFIGURING PURE1 VM ANALYTICS With Proxy settings

Please follow this great guide from Cody! https://www.codyhosterman.com/2018/10/configuring-pure1-vm-analytics-detailed-guide/ When you come to the point when you shall install or update something stop! Now it is time for proxy stuff. Apt proxy settings sudo vi /etc/apt/apt.conf.d/proxy.conf Acquire { HTTP::proxy "http://proxy.invid.se:8080"; HTTPS::proxy "http://proxy.invid.se:8080"; } Linux For other Linux stuff you want to add this in root users... Continue Reading →

Blog at WordPress.com.

Up ↑