Notification

Icon
Error

CMD - Uninstall TrendMicro IDF with rundll32 command

Posted: Thursday, March 31, 2016 8:28:19 PM(UTC)
Diego Tomazzoni

Diego Tomazzoni

Member Original PosterPosts: 14
0
Like
This issue has been solved! Click here to view the solution
Hi! Anxious
I need to remove TrendMicro IDF Client from all computers.
Manually I just run this command "rundll32 "C:\Program Files\Trend Micro\IDF Client\IdfClientAgent.dll",Uninstall" for 32-bit computers and this command "rundll32 "C:\Program Files (x86)\Trend Micro\IDF Client\IdfClientAgent.dll",Uninstall" for 64-bit computers.
I did a deploy package (attached here) but don't have success. When I try to deploy it's reached for timeout.
Is correct run this command directly?
Thanks.
CMD - Uninstall IDFDownload Package
DescriptionUninstall IDF
Final ActionNothing
Max. Duration5 min(s), 0 hour(s)
RescanYes
Steps
1. Check Architecture
TypeCondition
SuccessGo To Step 2
FailureGo To Step 3
Conditions
OS Architecture Is 32 Bit
2. Uninstall IDF 32 bits
TypeCommand
Return Codes 0,1641,3010
SuccessStop (Success)
FailureStop (Failure)
Command rundll32 "C:\Program Files\Trend Micro\IDF Client\IdfClientAgent.dll",Uninstall
3. Uninstall IDF 64 bits
TypeCommand
Return Codes 0,1641,3010
SuccessStop (Success)
FailureStop (Failure)
Command rundll32 "C:\Program Files (x86)\Trend Micro\IDF Client\IdfClientAgent.dll",Uninstall
Susan.A
#1Susan.A Member Administration Posts: 1,536  
posted: 4/10/2016 9:39:42 PM(UTC)
In general, a command that runs successfully in Command Prompt should run successfully in a deployment package as well. My first guess would be that this is a permissions issue and that you should try running the deployment package under a different account. (Available options are system account, scanning credential and currently logged on user.)

It's difficult to know the exact cause of the issue though. A timeout is a generic error that indicates your package did not finish within the time you defined as the Max Duration for the deployment package. This can happen because:
  • There was no Stop(Success) and no Stop(Failure) defined as the next action in the last step of the package. (That doesn't appear to be the issue here.)
  • The execution of the steps took longer than the Max Duration defined for the package. You can increase the Max Duration when you select the package under Deployment\Packages.
  • User interaction was required during the package execution, e.g. the user was required to confirm a dialog or close an application.
  • The computer froze or started rebooting before giving back a result for the last package step.
  • ...
Diego Tomazzoni
#2Diego Tomazzoni Member Original PosterPosts: 14  
posted: 4/11/2016 5:31:56 PM(UTC)
Thanks Susan, I'll try more options. If I find the reason I will post here.

Active Discussions

Lansweeper Laptop warranty include users from active directory filtered by OU
by  Iyad   Go to last post Go to first unread
Last post: Yesterday at 11:09:27 PM(UTC)
Lansweeper Exclude Search
by  pryan67  
Go to last post Go to first unread
Last post: Yesterday at 4:01:43 PM(UTC)
Lansweeper Report: All Apple Mac devices with Memory RAM asset
by  gabrielo   Go to last post Go to first unread
Last post: Yesterday at 3:17:24 PM(UTC)
Lansweeper Does technical support for LS really respond?
by  tosch  
Go to last post Go to first unread
Last post: Yesterday at 12:48:50 PM(UTC)
Lansweeper Deployment packages using lsagent
by  CyberCitizen   Go to last post Go to first unread
Last post: 6/15/2021 11:44:33 PM(UTC)
Lansweeper INFO DateTimeService time refresh
by  ZachO21  
Go to last post Go to first unread
Last post: 6/15/2021 4:23:15 PM(UTC)
Lansweeper Helpdesk tabs always regenarated
by  Carla   Go to last post Go to first unread
Last post: 6/14/2021 9:49:27 PM(UTC)
Lansweeper Importing with user relations
by  teddyh2o  
Go to last post Go to first unread
Last post: 6/14/2021 6:05:46 PM(UTC)