The vcbVmName command indicates that the VM is named what I think it's named. Where would the logfile go and what might it be named?

VcbMounter works, although I note what may be a problem: using name based access, the VM name is upper case, but Networker forces its client names to lower case, and the command is case-sensitive. If I use the ipaddr search directive with the VM hostname, that works fine, so it's clearly possible to mount the VM.

Right--as far as I can tell, VCB is configured correctly to use the ipaddr directive, which is why I'm thinking it's a matter of how the Networker module is talking to VMWare.

Has EMC gotten back to you at all? I've been working with them to try to sort this out, but with no luck so far. The only thing I can think of is that VMWare is now using an SSL certificate in VC 2.5, which may make Networker unhappy.

Well, that was certainly part of it. Thank you very much for the info! I've moved on to the following output:

savegrp: suppressed 55 lines of output.

• A certificate in the host's chain is based on an untrusted root.

2008-08-01 15:59:42.460 'BaseLibs' 520 warning SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled. LastError = 0
2008-08-01 15:59:42.460 'BaseLibs' 520 warning SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will proceed despite the error
2008-08-01 15:59:44.038 'vcbMounter' 520 error Error: Other error encountered: vim.fault.NoPermission
2008-08-01 15:59:44.038 'vcbMounter' 520 error An error occurred, cleaning up...
Deleted directory D:\vcb\mnt\<hostname>
External command failed. See error above.
Exit Code: 1

I'm going to guess that this is related to permissions for the VCB service account, which currently has the VCB Proxy User role assigned to it for the entire data center. Are there other permissions I should be looking at?

Newest error is:

Version mismatch:
Exit Code: 10

Guessing that the solution is to remove VCB and/or the Notworker integration module and reinstall.