If I were in your shoes I would simply run a job on each system to uninstall the aclient, it can be done with a simple batch job, Altiris script job, or manually of course from a command line. Is there a reason this wouldn't work for your environment?

Shannon DuBey CNA, MCP, A+

CMS/SMS 6.x - 7.1

Patch Management & Inventory Expert

I agree with Sdubey.  You could disable the Dagent/Aclient service on the clients in the event you thought you might move back to DS.  But if not, I would simply do an uninstall of the agent using the -remove -silent switches. 

Thanks for your quick feedback.

DaveDurkee wrote, "You could disable the Dagent/Aclient service on the clients in the event you thought you might move back to DS."

If this was the preferred method--keeping our foot in the Altiris Deployment door so-to-speak--what is the most efficient way of disabling the DAgent/AClient and corresponding policies?

Thanks.

For DS I wouldn't bother doing anything, it shouldn't interfere with SCCM any more than it interferes with NS. I've been in lots of places where DS is used to upgrade NS agents from 6 to 7, for example. The AClient/DAgent don't really have policies as such. If you want to disable the agent without removing it then Group Policy is a good option.

If you do have NS you could maybe "pause NS activities" although events will build up on the clients until the Altiris Agent is removed. Otherwise you could just disable all agent, inventory and software delivery polices on the NS.