Client Management Suite

Hello,

I have found this thread, https://www-secure.symantec.com/connect/downloads/get-outlook-cache-mode-status-custom-inventory, however i am having trouble implementing this. I am wondering if there is an easier way to scan all machines and report back how many have and an OST, which will give us an accurate number to how many people we currently have in Outlook cache mode.

Thanks and let me know if you need clarification.

Are you using v6 or v7?

Version 6

This process should get what you want, otherwise you can pursue the custom inventory option, which is a bit heavy handed for what I think you are looking for.

Ok sounds like i would want to create a new ini with just *.ost to pick up just that file. would that work? Secondly, How do I edit the auditpls.ini USING AeXAuditPls.exe?

AeXAPedit.exe

just use the AexAPEdit.exe, which is located outside of the Inventory Solution, in the NSCAP\bin\win32\x86 directory to edit the existing auditpls.ini (which is in the same directory but one level deeper, in the Inventory Solution folder).

So runt he aexapedit.exe, and the use the 'file -> open' to select the correct file (the one listed above) and edit it as you need, meaning add the file mask *.ost, and make sure the 'include unknown' box is checked.

Looks like i am getting the hang of this. I edited the INI, updated distribution points on the package, then sent and updated config on my own machine to test and see if i'll be about to see it in the resource manager under Inventory, data classes...looking in the right place? Thanks for the help by the way. Slowly but surely learning the deeper, more important, parts of Altiris.

software audit dataclasses. Unfortunately, the procedure changes quite a bit for v7 and up (but it's still good practice).

Works great, i took exe out of file types but should probably put that back in as it is a software scan...thumbs up, great help.

Glad to help. I would definitely put the .exe back (so you get your regular software scans). You want to be careful as well in what file types you choose. For example, *.dll would probably kill most databases (and cause users to complain as well). If you're looking for a specific file you can customize that as well.