VCS to VCSA Fling Experience

We’ve been discussing using the VCS to VCVA fling converter appliance.  We spent a few days installing the lab and re-installing due to not reading all the requirements for the VMware Migration Fling. I built the test vCenter server with Windows 2012 Server which has specifically been shown to be buggy and does not work.  I shouldn’t have done that anyway since our production vCenter servers are Windows 2008 R2.

After spending time re-reading all the caveats and known issues with the fling at William Lam’s virtuallyGhetto it was time to test and get comfortable with how the fling works. We scheduled some conference room time and went through the deployment of the migration appliance and just followed the instructions.

Troubleshooting

The only issue that we experienced is that the converter appliance would not accept my domain credentials to access the existing vCenter server. Our default administrator account on all of our Windows servers is renamed in our domain.  It appeared that the converter appliance would only try the vCenter local account called Administrator. After several tries with domain\username, username, localusername, etc. we created a local account on the vCenter server called Administrator. Once that was done the conversion continued on smoothly.  After looking around I didn’t see anyone else having this issue but I thought I’d mention it in case someone else experiences this issue as well.

We were very happy with the result in the lab and will be scheduling the conversion of one of our production vCenter servers to the VCSA soon.

Advertisements