vmware converter is stupid

i think i’ve mentioned before that i manage a blackberry enterprise server at work. in the nearly two years we’ve been using it, it’s been running on the free vmware server. we first purchased vmware infrastructure last summer and moving the bes v.m. over to esx has never really been a huge priority.

a few days ago, it was decided that we’d go ahead and move it over. a co-worker handles most of the vmware management but i volunteered to take care of this for a few different reasons (which aren’t really relevant).

so this morning, at 2am, i start working to import the bes v.m. off of the vmware server and onto esx. i spent an hour and a half having nothing but problems. i eventually figured out a way to make it work and, as i write this, it’s at 87% completion.

in order to get the import to work, i had to:

  • use vmware converter starter edition (not enterprise edition),
  • import directly to a specific esx server (as opposed to a cluster), and
  • use the credentials for my local account on the esx server (not the credentials i use to access the virtualcenter server — which is tied into active directory).

isn’t that fuckin’ retarded?

it just finished successfully, so it’s time to fire up the “new” v.m. and see how it went. *crosses fingers*

Share and Enjoy:
  • StumbleUpon
  • Digg
  • Reddit
  • Facebook
  • del.icio.us

Related Posts:
  • VMware Converter 4.0 Standalone Beta
  • unity on vmware workstation 6.5
  • vmware server on gentoo linux
  • fedora core 6 and vmware workstation
  • password aging on vmware esx

  • Leave a comment