First off, have a read through this article - Explanation of how to use the "Devices" and "Duplicate ID's" option for Inventory, and how they work. - that gives you an understanding of "what's there" & what's doable.
Now - having thought a bit on your situation, I do think you'll be better off keeping / having 2 records (one for MAC / one for Windows).
- You need to be able to manage the Windows APP-stack separate from the MAC app-stack.
- You need to be able to manage the OS / application patching sides separately.
- You may well need to keep the software licensing information separate (one license of "software X" may permit the use on dual boot systems, but "software Y" would require one for MAC, one for Windows).
- Different policies / packages will only work on their relevant target OS (not going to get far targeting a Windows package on a MAC OS).
I understand the desire in wanting to have "one record" for this - but there's many arguments counter to that (the above items are purely the first to come to me). Theoretically it WOULD be doable (you can crowbar the device ID's to be consistent across the OS'es), but your inventory & vulnerability data would be a singular mess.
So ... "doable - yes" ... but it'd be a very bad idea to do so. As tempting as it may seem, the realities of it will cause many more problems.
Hope this helps .
Thanks for the quick reply phoffmann, I appreciate your input. I read through that document a few weeks back to get a better idea on how those tools work.
Just to clarify, our goal is to keep both Mac and Windows entries for the dual boot Macs, but we need to make sure that the duplicate PCs are removed from LANDesk. Is there a way to accomplish this?
This is exactly what we do - we have one record for the OS X side and one for Windows, and for exactly the reasons mentioned. They really are two distinct clients, and are treated this way. Our AD naming convention is AAAAXXXXXX (A = letters for our department, X = decimals for the asset tag). We add "BC" for "BootCamp" for the Windows side. This distinguishes them by name.
In order for the Mac/Win side to NOT clobber one another when a new inventory is collected, we add "Type" to the criteria used to determine duplicate devices (see linked article above). For OS X, this is "MAC" and for Windows it's "Workstation" or something. As long as the Mac side differs from the Win side, you'll get two distinct devices.
I have a page on our wiki that's all about "Special Considerations for Dual-Boot Macs." I'll see if I can't get a PDF of it and post it...
In addition to the above (since I don't know the complexities & intricacies of your environment) - there's an alternative method as well.
Assuming you've got the relevant skills, you can use a SQL script to help you identify the list of devices that you do vs do NOT need to get deleted, and then use the MBSDK to loop through what you do want to have deleted. I've recently scribbled up something to that end (how to use the MBSDK & included example scripts) that may give you a leg up.
See the article here -- Getting Started with the MBSDK (Example Scripts Included) -- that may offer you more options.
But yes - ultimately it comes down to "the need for uniqueness" and that is something that I've highlighted in the "Explanation of Device IDs..." article as well - it's not a simple thing. Especially across OS'es (as concept X that exists on Windows, doesn't exist on MAC/NIX).
A potential additional "out" here, would be a custom data field. Something to the effect of "Dual Boot = Yes" or so - that way you could control
... and here's the custom data for MAC article I've been looking to link here - Macintosh Agent Custom Data White Paper - voila.
That should give you a few options on how you want to handle this I hope .