kschroeder

I'm using this script to work around a known issue between Inventory 6.1 and Virtual machines; all of our VMs were showing up duplicated due to some bug in IS changing the machine type. My only concern is exactly how this "merge" works...I don't want to lose the existing events, etc for my VMs when they are merged with a non-existent GUID imported by the AD Connector. Unfortunately I dont' have any free time to extensively beta test the new AD Connector beta to see if it will clear this up. Looking at the code for the script, I'm trying to figure out how it "knows" which machine is the "newest". I would prefer that it went by the last Configuration Request, but as far as I can tell it just used "ModifiedDate" column from ResourceUpdateSummary table; but I don't know what that ModifiedDate really refers to.

At this point I'm pretty much forced to run this script (I just set it as a scheduled report that runs ~30 minutes before my nightly AD update import) so that I can successfully import new machines from AD. If I don't do this, then the AD import fails due to some primary key conflict, which in turn causes my machines to not flow down into their OU-based collections, which causes my regional Admins to not see all of their actual machines in their collections, etc etc etc...ARGGGH!