With vConverter 4.1 GA (4.1.252.0) there is a known issue with RCC (remote cold clone) migration due to DNS errors.
vConverter 4.1 always tries to resolve names to IP addresses, to avoid any possible IP address conflict/mix-up in networks which use dynamic IP addressing via DHCP. However, when a host obtains the VistaPE name (as when is it rebooted during RCC), and DNS doesn’t reflect this change properly across the network, vConverter fails and doesn’t continue the conversion task.
Applied to the system where vConverter is installed, this fix excludes a DNS checking mechanism for the rebooted host (under VistaPE) and forces vConverter to use the IP address from the received TCP notification packet instead.
INSTRUCTIONS:
1.Exit from vConverter
2.Open C:\Program Files\Vizioncore\vConverter\Bin or the custom location containing vcclient.exe
3.Rename current vcclient.exe to vcclient.old
4.Rename current SharedCore.dll to SharedCore.old
5.Downloadhttp://store.vizioncore.com/downloads/path.do?id=4.1RCC-FIX
6.Extract the files to C:\Program Files\Vizioncore\vConverter\Bin or the custom location containing vcclient.exe
7.Run vConverter 4.1 as normal.
Additional Information:
The migration procedure is started, source host is restarted and booted under Vista PE, but vConverter doesn’t see this host after it is restarted and when the timeout expires, the migration fails. This is despite the VistaPE host having a valid IP address.
In the conversion logs you will discover text like:
System.Net.Sockets.SocketException: The requested name is valid, but no data of the requested type was found.
-OR-
[2009-02-18 15:05:52,998] [5] [INFO ] Rebooted with Vista PE machine found.
[2009-02-18 15:06:53,013] [5] [INFO ] New Vista PE found name:MININT-9LP2P8U Id:3EF49F7BDA314C35A79ACBD11A89B8D9 ip:162.123.118.125
[2009-02-18 15:06:53,013] [5] [INFO ] Comparing. Task Id:3ef49f7bda314c35a79acbd11a89b8d9 VistaPE Id:3EF49F7BDA314C35A79ACBD11A89B8D9 Ip:10.10.1.125 Name:MININT-9LP2P8U[
Also other DNS related errors may occur.
