New commit detected on ManageIQ/manageiq/darga:
https://github.com/ManageIQ/manageiq/commit/e66c3824aec855dc5b74f3652796f746657a8319

commit e66c3824aec855dc5b74f3652796f746657a8319
Author:     Greg McCullough <gmccullo@redhat.com>
AuthorDate: Fri Sep 9 10:39:58 2016 -0400
Commit:     Oleg Barenboim <chessbyte@gmail.com>
CommitDate: Tue Oct 11 09:14:43 2016 -0400

    Merge pull request #11135 from syncrou/remove_discovered_virtual_machine
    
    No longer select 'Discovered virtual machine' as a default folder
    (cherry picked from commit 7ac58a9eddd6068e141a166de578834f59bd4441)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1383470

 .../vmware/infra_manager/provision/cloning.rb          |  5 ++---
 .../providers/vmware/infra_manager/provision_spec.rb   | 18 +-----------------
 2 files changed, 3 insertions(+), 20 deletions(-)

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2839.html

Hi Leo,  Sorry I missed this.  No - auto placement used to be pre defined to provision to the 'Discovered Virtual Machine' folder. From time to time this caused confusion as to where it was actually provisioned.  

This change simply pre defines auto placement to go to the root folder instead.  

Automate provisioning methods can be used to change this location - but that was always the case even before this change.

Is that what you were asking?

Yes. That what I was asking.