scurvylion
asked on
problem creating vm from winxp for ESXi using standalone converter
Hi,
I have been having a lot of difficulty creating a vm from a powered on machine running winxp pro. I'm using VMware vCenter Converter Standalone client version: 4.3.0. I have used this app to migrate other vm's over to the new host and also to restore one from an image; however, when I try to create a vm from the aforementioned powered on machine I get an error.
The process I have been following is the following:
1) Open the application and select convert machine and then source type as Powered-on machine
2) specify remote machine and add ip address and user name and password and select windows as OS famly
3) Click next
it then says that it is connecting to the machine and then another window opens
VMware vCenter Converter Standalone Agent Deployment
it states that is needs to temporarily install the agent on the remote machine
I then check
Automatically uninstall the files when impoprt succeeds
and click yes
It says that it is deploying agent and then I get the error message
"Unable to complete vCenter Converter agent installation on ---.---.--.--- Error code 1,154"
I checked the error code on the web and found this:
Error Code 1154
System error code 1154 means "One of the library files needed to run this application is damaged."
The machine that I am trying to convert is pretty old - it is an old MS Windows NT workstation that is running WinXP pro now. Could this be part of the problem?
How do I fix this situation?
I have been having a lot of difficulty creating a vm from a powered on machine running winxp pro. I'm using VMware vCenter Converter Standalone client version: 4.3.0. I have used this app to migrate other vm's over to the new host and also to restore one from an image; however, when I try to create a vm from the aforementioned powered on machine I get an error.
The process I have been following is the following:
1) Open the application and select convert machine and then source type as Powered-on machine
2) specify remote machine and add ip address and user name and password and select windows as OS famly
3) Click next
it then says that it is connecting to the machine and then another window opens
VMware vCenter Converter Standalone Agent Deployment
it states that is needs to temporarily install the agent on the remote machine
I then check
Automatically uninstall the files when impoprt succeeds
and click yes
It says that it is deploying agent and then I get the error message
"Unable to complete vCenter Converter agent installation on ---.---.--.--- Error code 1,154"
I checked the error code on the web and found this:
Error Code 1154
System error code 1154 means "One of the library files needed to run this application is damaged."
The machine that I am trying to convert is pretty old - it is an old MS Windows NT workstation that is running WinXP pro now. Could this be part of the problem?
How do I fix this situation?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry to take so long to get back to you. I read the article that you referenced in your post and did some more research on the internet. Initially, when I tried your methodology, I had the same result as previous attempts so I was unsure of how to proceed.
However, after reviewing all of the settings on the remote machine, I found that the WinXP Pro OS only had SP1 installed so I updated the OS to include SP2 and then when I followed your procedure again I managed to successfully convert the machine.
Thanks for your help.
scurvylion
However, after reviewing all of the settings on the remote machine, I found that the WinXP Pro OS only had SP1 installed so I updated the OS to include SP2 and then when I followed your procedure again I managed to successfully convert the machine.
Thanks for your help.
scurvylion
ASKER
Thanks for the info. Much appreciated!
Hi
Glade to help
Jail
Glade to help
Jail
ASKER