Many outfits are starting to buy more Macs, because the Intel chips in them make running Windows feasible. However, there's no solution for running Windows applications directly in OSX, so until then your options are:

1. Dual boot with Windows XP (using Boot Camp Beta).
   
2. Run virtualized Windows XP as an application under Mac OSX (using Parallels or VMWare Workstation 6 Beta).

So, how best to use LANDesk to manage these two scenarios? Your first question needs to be, "how am I going to be licensed?" I Am Not A Lawyer, but the word on the street seems to be that concurrent use is more likely to cause license impact than non-concurrent use. In other words, dual booting on one piece of hardware is less likely to require separate licensing for all the cross-platform applications which are installed in both OSes, whereas running two OSes simultaneously does require dual licensing.

If that is true, then the best way to manage scenario two is the easiest way: install a LANDesk agent into the virtual copy of XP and call it a day. You get two devices in your inventory with two different IDs, you get to send them different policies and do different scans, and you can see them both in the console at the same time (handy when they're both active at the same time). To save resources, it makes sense to leave Remote Control out of the XP agent, and you may also want to skip other components based on how that XP agent is configured... for instance, if it uses host-only networking and never contacts the wire directly, why bother with antivirus, firewall, security scanning, &c &c.

Scenario one takes a bit more thought... but if you're able to meet your licensing obligations with a dual boot "flip-flop", you can easily set up LANDesk to use a single license and a single computer record for the dual-booting machine. To do this, you just need to set the UUID to the same value in both OS'es. In OS X, this is done at /Library/Preferences/com.landesk.uuid.plist -- in XP, it's done in two places, HKLM/Software/Intel/LANDesk/CommonAPI and HKLM/Software/LANDesk/CommonAPI. Set these three values to the same string and you'll see the one computer record update to XP or OS X depending on what the user is running.

If you want to go down that path, be aware that your software inventory and SLM usage database tables will take something of a thrashing from all the delta changes. If you're doing this with a few dozen machines, it's probably no big deal, but if you're doing it with a few thousand, you might want to test thoroughly.