Related Questions:

1. What is the x86 folder under Altiris\Altiris Agent found on x64 systems?
   1. Should we expect to see an x64 folder on 32bit clients?
2. Why is there an x86 version of the Client Task Agent (CTA) on systems?
3. What 32bit plugins and/or tasks/jobs/policies are still present in SMP 7.1 now that everything should support 64bit?
4. What is the AexAgentSrvHost service?
5. What is causeing AexAgentSrvHost to start running?

Answers:

1)
The x86 Folder is for holding an/all 32bit required processes / code on 64bit computers.  For instance, on the NS, you need to have a 32bit task agent for running some of the processes (i.e. inventory as of SMP 7.1 SP1) that have not yet converted to 64bit fully.  This keeps the code and files separate from the rest of the code until all processes can be fully migrated to 64bit.  You will not see an equivalent x64 folder on 32bit agent installations.

2)
The CTA has to install both a 32bit and 64bit version on 64bit clients due to some of the task processes not yet being fully 64bit compatible.  For instance, task will trigger inventory which is still 32bit, so we have to have access to the 32bit version of the CTA.

3)
Though we've made a concerted effort to get everything moved to x64 in the CMS/SMP 7.1 SP1 release, some things didn't quite make it.  For instance, inventory, mentioned above, is not yet fully converted.

4)
The AexAgentSrvHost service is the 32bit host engine for anything that requires 32bit processes on a 64 bit platform.  It points to exe's in the root of the x86 folder.

5)
It is launched automatically by any subsystem that requires a 32bit process.  So, for instance, during an inventory run you might see it running.