XP Managed Client

[kev]

I'm trying to install a namaged client on an old win XP box.

It fails when I try to deploy fromthe management console, saying windows installer 4.0 is missing. Installing windows installer 4.0 doesn't change anything.

I can export an installation package which installs ok but doesn't seem to update from either the MWB server or the internet.

Has anyone had any success with XP and managed clients?

[IT_Guy]

I've never been able to get the cloud to deploy anything to any operating system, XP 7 or 10.

 

For my XP machines I had to get the Windows XP installer off the management console and manually install it on the XP machine. After it installs the .net framework you will need to reboot to get MBEP to start working. You won't have an icon in the system tray but you will see it in the cloud console.

[djacobson]

@kev On the client go to C:\Program Files (x86)\Malwarebytes' Managed Client and run the tool CollectClientLog.exe as local admin. Attach the folder it generates.
 

@IT_Guy wrong product.

Edited November 21, 2017 by djacobson

[IT_Guy]

3 minutes ago, djacobson said:

@kev On the client go to C:\Program Files (x86)\Malwarebytes' Managed Client and run the tool CollectClientLog.exe as local admin. Attach the folder it generates.
 

@IT_Guy wrong product.

Did this post just get moved? I don't browse the other forums on here and I swear this was posted under Endpoint Protection.

[djacobson]

@IT_Guy I did move it, the OP opened it under the incorrect topic header, which is common because of our naming scheme's redundancy. The keywords in this post are; "management console", "managed client", "export an installation package" and "update from either the MWB server or the internet". These are the on-prem product's pieces and behavior.

[IT_Guy]

My bad!

To be fair it got moved after I commented though and his problem did seem to be the same as my experience installing the software on Windows XP.

[djacobson]

@IT_Guy problems with the D&D tool for the cloud product and its deployment attempts are much easier to diagnose, the logging is better and that tool also uses more deployment functions than just Netbios, RPC and WMI.

XP (and other OS) deployment failures on both product versions usually revolves around account permissions due to some lockdown of RPC, WMI and/or DCOM. Even domain admin accounts can fail to have the needed permissions, that is something a lot of folks have trouble with understanding and is just the nature of Windows and its changes since the full admin access of Win 2k and below days.

Some settings that can change these pieces can get really obscure and it can become a major hassle, needle/haystack situation, to go through every single aspect of someone's domain policy to find out what setting it could be, especially when all the major typical ones have been modified in preparation to deploy. It is usually a better practice in that case to temporarily enable the local admin account (if it is not already enabled), give it a password (blank passwords are not accepted), then use that as the credential for pushing over using using domain creds of any kind.

If local admin fails, then you are looking at;

• a machine with a home consumer free/trial install already in place, preventing the install since it is already "installed". This is more typical for MBMC product deployments since that product version's installer has no ability to perform a cleanup of pre-existing MB installs.
• a pre-existing infection preventing installation of security programs (not just us, you'll have infections like this targeting many vendors).
• a broken Windows installation itself, an sfc /scannow can help but sometimes, that's gonna be a reinstall/reimage.
• a failing hard drive.
• network level issues with the ports and protocol required.

[IT_Guy]

Yeah our work computer environment is an IT nightmare. I won't go into details for obvious security reasons, but we have multiple OS's, no domain server, inconsistent credentials and permissions etc. etc. Absolutely nothing deploys properly on our network so I wasn't overly surprised this didn't either.