The updated file did the trick, and I did catch that as well, but it took me a while to figure out what was wrong, becuase I am getting weird results from one of my main test machine. That is a whole different subject but the summary is it does not process the .nsi files properly every time it runs an inventory. It often leaves the .nsi and .bak files in the express\inventory folder, for no reason I have been able to detect yet.
So in order to test this I created a new inventory job (instead of using the hardware inventory), and ran it against a group of 5 or so machines and they all worked perfectly the first time. That would have saved me about 3 hours had I used more than one test machine!
This is the custom inventory file, AeXCompCustInv.ini:
wscript.exe //B GetADDescription.vbs
aexcustinv.exe /in .\AeXADCompDesc.xml
aexnsinvcollector.exe /hidden /nsctransport /v default /useguid
And I created a new inventory job with the command line:
AeXInvSoln.exe /hidden /s AeXCompCustInv.ini
In case anyone else wants to give it a shot.
BTW, you can also test this from a batch file to verify it works before running it in Altiris. The contents of the batch file would look exactly like the contents of the ini file above. Just make sure you have a copy of AeXCustInv.exe and AeXNSInvCollector.exe in your test folder, along with the script and XML file.
Thanks for sticking with it, Kyle-
-Rob