Unfortunately I don't think there is any way around losing the ip info. As far as Windows goes it is a new adaptor and it must change its drivers. Personally(I am dealing with the same problem....x14000) I am writing an app that will drop itself on the server, grab the IP info, wait for the change, and then re-apply it. Email me and when its done (in the next few days) I'll send you a copy.
Now for my real feelings on how VmWare is handling this and how it has cost them or is costing them many customers...maybe/probably me included. Hyper-v is free with Windows now and works well. WHY do you not care to fix this bug. You are NOT the tiny company anymore. Your clients/customers rely on this critically. How dare you just make a statement that you know of the bug and tell us to change the adaptor. Do you have any idea how much of a problem it is to have your entire prod environment crash every other week only for the vendor causing it to tell you to basically deal with it.
Well I will tell you that if I have to touch 14k servers, I might as well touch them all the way over to hyper-v. The manner in which this is being handled is down right irresponsible.....especially since I work for a company that provides critical infrastructure services to the entire world!
So...when are you going to fix this VERY problematic bug? Can we at least get an ETA? Are you working on it? Tell me something other than change every adaptor in my organization or deal with purple screens several times a month! E1000 is the DEFUALT STILL. When you created a guest you get an e1000 nic (for win at least) so your default is basically setting everyone up for failure.