Deployment Solution

For some reason the Aclient keeps getting installed/reinstalled on Windows servers.
We only use Altris for desktop and laptop management so I'd like a way to block, restrict or filter so that only desktop and laptop computers get the AClient on them.
I cannot locate where on DS to specify which computers on our network get and do not get the DS client.

It's probably right in front of my face but at the moment I'm lost and under pressure to get this resolved quickly.

The server admins are on my back all the time as to why Altiris gets installed without their say-so and just this morning they're blaming Altiris for shutting down a bunch of virtual servers and PCs alike.

In any case my boss wants Altiris in a any way, shape or form off servers and to stay off.

I did check our NS server and can't find any job pushing the Aclient, so I don't believe it's coming from there.

Can someone steer me in the right direction?
I appreciate any assistance in this matter.

Thank you,
Brian

Under the Altiris Deployment Server Configuration Utility, Click on Options --> click Connections.
You can block individual IPs, subnet blocks, etc...

We use this at our locations because we share our wire with others.

HTH

Here is a quick thought: HP hardware comes with the agent bundled into the OS. There might be some sort of restore job that is bringing it back after you uninstall it.
Other possibilities will include an initial deployment job is finding your server every time you come online after uninstalling the client.

-Lee, STS Deployment Solution 6.9

Lets be clear here, do you mean the Aclient, or the Altiris Agent? The altiris agent can be auto pushed from the NS under the configuration tab. The aclient however isn't automatically installed unless:

- The Altiris Agent is already on the machine and a policy is using that agent to install the aclient
- If you are installing the aclient via a logon script
- Somehow your servers have a trial license of the aclient on them which is using multicasting to find your DS eventually.

Regardless, this should fix it (just edit the path to your aexagentutil.exe):

@echo off
Echo.
Echo Removing AClient . . .
Start /Wait "" "C:\program files\altiris\aclient\aclient.exe" /remove /silent
DEL /s /q "C:\AClient.cfg"
DEL /s /q "C:\WINDOWS\system32\drivers\AlKernel.sys"
DEL /s /q "C:\WINDOWS\Temp\alsmb.exe"
RD /s /q "C:\Program files\Altiris\AClient\"
REG DELETE HKLM\SYSTEM\CurrentControlSet\Services\AClient /f
REG DELETE HKLM\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_ACLIENT /f
REG DELETE HKLM\SYSTEM\ControlSet001\Enum\Root\LEGACY_ACLIENT /f
REG DELETE HKLM\SYSTEM\ControlSet001\Services\AClient /f
REG DELETE HKLM\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\AuthorizedApplications\List /f /v "C:\Program Files\Altiris\AClient\AClntUsr.EXE"
REG DELETE HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\AuthorizedApplications\List /f /v "C:\Program Files\Altiris\AClient\AClntUsr.EXE"
Echo done.
Echo.
Echo Removing Altiris Agent . . .
\\server\altiris\AeXAgentUtil.exe /UninstallAgents
\\server\altiris\AeXAgentUtil.exe /Clean
DEL /q "C:\Program Files\Altiris\Altiris Agent"
reg delete "HKLM\Software\Altiris\Altiris Agent" /f /va
reg delete "HKLM\Software\Classes\AppID\{5E038245-CF81-44BE-8018-9A2981B9DC9B}" /f /va
Echo done.

:END
exit