not really... I've been having tons of issues with autodeploy in my labs... I have a 5.0 setup and a 5.1... I have only seen this problem in 5.1, not in my 5.0, but... saying that, I think 5.1 is more stable. Yes I get the compliance warning, but everything seems to work. My 5.0 lab just decides to blow up every so often... I'll reboot and all the port groups and adapters will have migrated from dvs to svs that it seems to create on the fly. I edit the profile and put a password in it and it doens't remember it, goes back to no password and various other things that keep happening. I've had to recofigure the reference host about 5 times now from nearly scratch... I'm using dvs for all my switches pretty much - it seems that is the bit that is makes it blowup. Right after I migrate the management portgroup and adapter from the svs it does it, all looks good and within 5 minutes, the host disconnects, I can reconnect if I add the host on the other management interface, and then the original vmkport comes back. I'd say I was doing something wrong, but, I have the exact same setup - networks, dvswitches, iscsi devices... everything in my 5.1 lab and that works perfectly. The only reason I have the 5.0 lab is for prepping for my VCAP DCA once I pass that, I'm going to use it as a test for upgrading a 5.0 vcenter to 5.1 as I need to do that in real life in our datacentre.. anyway, sorry, none of this is much help to you, all I can say is that the non-compliance doesn't seem to cause any problems other than the warning.
Bill