Here's my situation: I am cloning multiple Library configurations into an existing workspace configuration using the internal SOAP API (4.0). I already have everything working with LibraryCloneToWorkspace(), including a provision for if multiple machines are inserted with the same name (renaming them as they are added so that they are sure to have a unique name, like LM does internally), and using MachineResetMacAddress() to prevent conflicts with that.

The issue I run into (which is a common case for my application) is that two machines based on the same template are cloned into the same configuration; thus, they have the same name, MAC address, and internal IP. I have the name and MAC address issues sorted out, as I said... but I don't yet have a way to deal with the internal IP.

I intend to keep looking around for a solution, but I was wondering if anyone else has run into the same issue. My guess is that the answer is either in some obscure, yet-undocumented option in MachinePerformAction, or in some argument for a deployment method (i.e., the "Force Recustomization" checkbox). Any ideas?

On a related note, has anyone seen the 4.0 internal API docs floating around?