Comments on: Forefront, Etrust & SCCM http://www.buttonclicker.com/2009/08/14/forefront-etrust-sccm/ Techno Button Master Thu, 02 Feb 2012 21:30:53 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jason http://www.buttonclicker.com/2009/08/14/forefront-etrust-sccm/comment-page-1/#comment-27 Jason Sun, 17 Jan 2010 11:48:22 +0000 http://www.buttonclicker.com/?p=137#comment-27 If anyone's interested, I created an expanded version of the script posted here for removing CA ITM. This one also has the uninstalls for the 64-bit versions of the ITM agent and iGateway. Just substitute in your server name and create a share called rmitm. I used psexec to push this out to all my systems, worked great and I have it generating lots of logs in case anything goes wrong. Hope it helps someone! rem stop services net stop ITMRTSVC >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err net stop InoRT >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err net stop InoTask >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err net stop InoRPC >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err net stop igateway >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err rem rename Spin.conf so iTechnology iGateway can be uninstalled move "C:\Program Files\CA\SharedComponents\iTechnology\Spin.conf" "C:\Program Files\CA\SharedComponents\iTechnology\Spin.conf.old" >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err rem CA eTrustITM Agent 32-bit MsiExec.exe /qn /X{85F88F9C-6EB2-426B-88AB-28DA4A3526B9} >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err echo CA eTrustITM Agent 32-bit: %errorlevel% >> \\[server name here]\rmitm\logs\%computername%.errorlevel rem CA eTrustITM Agent 64-bit MsiExec.exe /qn /X{E6BECFFB-D60F-464A-9F7C-89C2D6E84465} >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err echo CA eTrustITM Agent 64-bit: %errorlevel% >> \\[server name here]\rmitm\logs\%computername%.errorlevel rem CA iTechnology iGateway (4.2.0.2): MsiExec.exe /qn /X{847501DF-07C0-4691-B04A-893929F108AE} >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err echo CA iTechnology iGateway (4.2.0.2): %errorlevel% >> \\[server name here]\rmitm\logs\%computername%.errorlevel rem CA iTechnology iGateway [x64]: MsiExec.exe /qn /X{ACB0696B-AB1F-4A40-831A-65A2E5BA54B0} >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err echo CA iTechnology iGateway [x64]: %errorlevel% >> \\[server name here]\rmitm\logs\%computername%.errorlevel If anyone’s interested, I created an expanded version of the script posted here for removing CA ITM. This one also has the uninstalls for the 64-bit versions of the ITM agent and iGateway.

Just substitute in your server name and create a share called rmitm. I used psexec to push this out to all my systems, worked great and I have it generating lots of logs in case anything goes wrong.

Hope it helps someone!

rem stop services
net stop ITMRTSVC >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err
net stop InoRT >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err
net stop InoTask >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err
net stop InoRPC >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err
net stop igateway >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err

rem rename Spin.conf so iTechnology iGateway can be uninstalled
move “C:\Program Files\CA\SharedComponents\iTechnology\Spin.conf” “C:\Program Files\CA\SharedComponents\iTechnology\Spin.conf.old” >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err

rem CA eTrustITM Agent 32-bit
MsiExec.exe /qn /X{85F88F9C-6EB2-426B-88AB-28DA4A3526B9} >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err
echo CA eTrustITM Agent 32-bit: %errorlevel% >> \\[server name here]\rmitm\logs\%computername%.errorlevel

rem CA eTrustITM Agent 64-bit
MsiExec.exe /qn /X{E6BECFFB-D60F-464A-9F7C-89C2D6E84465} >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err
echo CA eTrustITM Agent 64-bit: %errorlevel% >> \\[server name here]\rmitm\logs\%computername%.errorlevel

rem CA iTechnology iGateway (4.2.0.2):
MsiExec.exe /qn /X{847501DF-07C0-4691-B04A-893929F108AE} >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err
echo CA iTechnology iGateway (4.2.0.2): %errorlevel% >> \\[server name here]\rmitm\logs\%computername%.errorlevel

rem CA iTechnology iGateway [x64]:
MsiExec.exe /qn /X{ACB0696B-AB1F-4A40-831A-65A2E5BA54B0} >> \\[server name here]\rmitm\logs\%computername%.out 2>> \\[server name here]\rmitm\logs\%computername%.err
echo CA iTechnology iGateway [x64]: %errorlevel% >> \\[server name here]\rmitm\logs\%computername%.errorlevel

]]> By: J http://www.buttonclicker.com/2009/08/14/forefront-etrust-sccm/comment-page-1/#comment-15 J Wed, 09 Sep 2009 12:17:37 +0000 http://www.buttonclicker.com/?p=137#comment-15 Sounds good, I have had no issues so far in the deployment, it was harder to remove etrust than deploy FCS, one thing I do miss is the “scan file” context menu, it seems its very much dumbed down.. but it did find a few viruses on the network (inside zips) that for some reason or not etrust did not.. good luck! Sounds good, I have had no issues so far in the deployment, it was harder to remove etrust than deploy FCS, one thing I do miss is the “scan file” context menu, it seems its very much dumbed down.. but it did find a few viruses on the network (inside zips) that for some reason or not etrust did not..

good luck!

]]> By: Dilip http://www.buttonclicker.com/2009/08/14/forefront-etrust-sccm/comment-page-1/#comment-13 Dilip Tue, 08 Sep 2009 17:34:30 +0000 http://www.buttonclicker.com/?p=137#comment-13 Great, thanks, this is what I have to do in probably in few months time. Have SCCM Server, FCS and WSUS in place on Windows 2008 Servers. Need to install SCCM Clients and then convert Symantec to Forefront... Part of the company has e-trust... Great, thanks, this is what I have to do in probably in few months time. Have SCCM Server, FCS and WSUS in place on Windows 2008 Servers. Need to install SCCM Clients and then convert Symantec to Forefront… Part of the company has e-trust…

]]> By: Msiexec | All Days Long http://www.buttonclicker.com/2009/08/14/forefront-etrust-sccm/comment-page-1/#comment-7 Msiexec | All Days Long Fri, 14 Aug 2009 18:54:57 +0000 http://www.buttonclicker.com/?p=137#comment-7 [...] Forefront, Etrust & SCCM | Button-c-licker By J Etrust remover.bat was basically just a msiexec that called for it to be removed. I had some issues with clients not completly removing the AV software/services, So I made the removal.bat actually Install CA, then STOP Services, … Button-c-licker – http://www.buttonclicker.com/ [...] [...] Forefront, Etrust & SCCM | Button-c-licker By J Etrust remover.bat was basically just a msiexec that called for it to be removed. I had some issues with clients not completly removing the AV software/services, So I made the removal.bat actually Install CA, then STOP Services, … Button-c-licker – http://www.buttonclicker.com/ [...]

]]>