The following error is received when trying to perform resource updating on computers:
\\PC_NAME Install 53 Error The network path was not found.
This in most cases means that computer's name can not be resolved via DNS.
Quest Migration Manager relies on DNS but using short non-FQDN (fully qualified domain name) computer name. When this name resolution query passed to the DNS server, primary DNS suffix of the computer is appended to short unqualified names by default. The behaviour is described in more details here:
http://technet2.microsoft.com/windowsserver/en/library/5fe46cef-db12-4b78-94d2-2a0b62a282711033.mspx?mfr=true
If QMM console is installed in the target domain and using DNS server different than source environment, then all the DNS searches will be attempted in the context of target domain. To alternate this behaviour, please populate "Append these DNS suffixes (in order)" list under TCP/IP properties of console machine with DNS suffixes that would correspond to the missing FQDN of computers from the source domain.
Additional Information:
Configuring a DNS suffix search list
For DNS clients, you can configure a DNS domain suffix search list that extends or revises their DNS search capabilities. By adding additional suffixes to the list, you can search for short, unqualified computer names in more than one specified DNS domain. Then, if a DNS query fails, the DNS Client service can use this list to append other name suffix endings to your original name and repeat DNS queries to the DNS server for these alternate FQDNs.
For computers and servers, the following default DNS search behavior is predetermined and used when completing and resolving short, unqualified names.
When the suffix search list is empty or unspecified, the primary DNS suffix of the computer is appended to short unqualified names, and a DNS query is used to resolve the resultant FQDN. If this query fails, the computer can try additional queries for alternate FQDNs by appending any connection-specific DNS suffix configured for network connections.
If no connection-specific suffixes are configured or queries for these resultant connection-specific FQDNs fail, then the client can then begin to retry queries based on systematic reduction of the primary suffix (also known as devolution).
For example, if the primary suffix were "example.microsoft.com", the devolution process would be able to retry queries for the short name by searching for it in the "microsoft.com" and "com" domains.
When the suffix search list is not empty and has at least one DNS suffix specified, attempts to qualify and resolve short DNS names is limited to searching only those FQDNs made possible by the specified suffix list. If queries for all FQDNs formed as a result of appending and trying each suffix in the list are not resolved, the query process fails, producing a "name not found" result.
Notes If the domain suffix list is used, clients continue to send additional alternate queries based on different DNS domain names when a query is not answered or resolved. Once a name is resolved using an entry in the suffix list, unused list entries are not tried. For this reason, it is most efficient to order the list with the most used domain suffixes first. Domain name suffix searches are used only when a DNS name entry is not fully qualified. To fully qualify a DNS name, a trailing period is entered at the end of the name.
