1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Issues Deploying Trend Micro Worry Free Business Security Services Client

Avatar
fsaccone

I just got our MSI for the Trend Micro Security Agent, and I am attempting to build a working package to deploy to a bunch of Lenovo E485's and a couple dozen custom built desktops. All running 64 bit Windows 10.

After a little googling, I found the easiest way to accomplish this silently and with no restart. I tested on my desktop, which I had fully removed our previous AV client from. It took a few minutes, but it finished with no issue. I assumed I was good to go, so I attempted to deploy this to one of the laptops. I removed the previous AV, and pushed the same package, only this time, it failed and outputted a long-winded log about what went wrong. I tried to do this again, on another desktop, and it installed successfully. So, back to the laptop, and got the same failure. I tried on a couple more laptops, to no avail.

Worst part is now, that when I attempt to just manually install the client from a local file on the laptops, it errors out telling me that it needs to finish install and needs to restart, over and over after many restarts. After some more googling, I found a couple tools that are supposed to fully clean a computer of any and all things Trend Micro. That didn't work. I opened a ticket with Trend Micro, who gave me an updated uninstaller to remove any remnants, and again it errors out. So, now I can't even remove or install anything on those laptops.

Before I move on, I'd like to see if anyone has successfully accomplished a deployment if this software, and talk about the package. I see a couple very short threads, but nothing of real value for my specific issue. Any help would be appreciated. Thanks in advance.

0

Comments

3 comments
Date Votes
  • Avatar
    Ryan Joachim

    The errors saying a restart is required are going based off of one or more registry entries (usually) - if you have PDQ Inventory, they have a collection that shows machines "pending restart". If your test machine is in that collection, then the reboot is in the registry.

    You could dive in that way and remove the entry as part of your testing.

    0
  • Avatar
    Ron P. Gallimore

    Were you able to resolve this? I am trying to push it out and it keeps failing.
    Would you mind sharing the command used for the deployment?

    0
  • Avatar
    Neil Lubke

    I was able to host it on a network share and script it like this. I added the step as "command" instead of pointing to the MSI file directly and adding options.

    msiexec /i "\

    0