I suspect yes.
Internally the VDS is identified with it's Id.
When you import the config, the new VDS will get a new Id
The VM still points to the old Id, hence the invalid backing messageBlog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz
We have already registered around 300 vms in the environement. Anything that can be done now to rectify it other than adding the network labels via powercli ?
Yes, that seems the best way to me.
Connect all these VMs to the correct portgroup with a PowerCLI scriptBlog: http://lucd.info | Twitter: @LucD22 | PowerCLI Reference co-author: http://tinyurl.com/hkn4glz