Jump to content

Malwarebytes endpoint deployment tool fails


ABL

Recommended Posts

when trying to deploy to computers on local network via endpoint "discovery and deployment tool vs 1.1.0.380, get failures:

ErrorMessage:System.IO.IOException: The trust relationship between this workstation and the primary domain failed.

In text for failure, getting System.Exception: Unable to establish remote SSH connection ---> SBSimpleSftp.EElSimpleSFTPClientError: Connection error 10060

What do I need to do to get this to deploy (have about 100 computers, some connecting over VPN, most local to office)

thanks!

Link to post
Share on other sites

  • Root Admin

Hello @ABL

This is a Windows security issue that you need to resolve for any that have the issue.

Please see the following link. (please ignore any Ads and do not download any software)

https://www.partitionwizard.com/partitionmanager/trust-relationship-failed.html

 

Link to post
Share on other sites

The computers are on the domain and do not have any issues logging into domain.  

I can install malwarebytes directly to any computer, and see it in the malwarebytes admin web page. I would rather use the deployment tool as there are over 100 computers.

I get the "ErrorMessage:System.IO.IOException: The trust relationship between this workstation and the primary domain failed."  when trying any computer on my domain.  If there really was a bad trust relationship, the users computers would not be able to login.

Any other ideas?  No one has received this error before when using the deployment tool?
Thanks,
Warren

Edited by AdvancedSetup
Corrected font issue
Link to post
Share on other sites

Whilst your service ticket starts, a few additional tips.

If the Deployment Tool fails one authentication technique, it progressively tries others.  SSH is a final technique, often used with Macs.
Look back from start of log, for the first technique attempted, it is more likely to indicate cause of problem.
The tool uses two main techniques:
* WMI and/or
* File copy and remote Service-Controller SC

Pre-requisites are: File and Print Sharing Enabled, network reachability for MSRPC (135), SMB (445), optionally NETBIOS etc.

Try mounting Folder   \\endpoint\Administrator$   -- this indicates credentials are working
Or something like this older style command 
NET USE Y: \\endpoint\Administrator /USER:domain\user *
NET USE Y: /DELETE
Generally, if you can mount the drive it is going to work.

Alternatively consider using ActiveDirectory/GPO to deploy the MSI, with a RunOnce style task.  (It doesn't hurt to rerun, MSI installer will detect we are already installed)
 

Link to post
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.