How to stop McAfee Client Proxy (mcpservice.exe)

McAfee Client Proxy (mcpservice.exe) Version 2.3.0.0 no longer has its own service, so when you try to stop the process, even as SYSTEM, it’ll fail with an Access Denied error.

mcafee-client-proxy_mcpservice.exe_2.3.0.0_unable-to-terminate_access-denied

So, how to stop McAfee Client Proxy (mcpservice.exe)? Well, with the help of Process Hacker (Process Explorer should also do). Before continuing, let me say that you’ve got to be extra careful and that you’ll be responsible should anything go wrong (these are easy steps though..).

Download link for Process Hacker: http://processhacker.sourceforge.net/

Once I ran Process Hacker, I noticed that the McAfee Client Proxy had a parent process called mfemms.exe that starts from a service called McAfee Service Controller. So that means we’re still going to be able to try and stop this process by working on the parent’s.

mcafee-client-proxy_mcpservice.exe_2.3.0.0_process-hacker-properties

Note: If you’re running an old version of McAfee Client Proxy Service, that has its own service, you may follow the steps below that I will action against mfemms.exe and then stop the process.

So, back in Process Hacker (remember to run it as an administrator!):

  • Go to the Services Tab.
  • Go to mfemms’s properties.
    • mcafee-client-proxy_mcpservice.exe_2.3.0.0_process-hacker-mfemms-properties
  • Under the tab Security, click Advanced and change the owner to Administrators. Click Ok twice, until mfemms’  properties window closes. You must run this step in order to run next’s!
    • mcafee-client-proxy_mcpservice.exe_2.3.0.0_process-hacker-mfemms-properties-security-advanced
    • mcafee-client-proxy_mcpservice.exe_2.3.0.0_process-hacker-mfemms-properties-security-owner
  • Now assign Full Control to Authenticated Users and Administrators (just Administrators didn’t work for me). Do the same for SYSTEM if you’re running as SYSTEM.
    • mcafee-client-proxy_mcpservice.exe_2.3.0.0_process-hacker-mfemms-properties-security-permissions
  • You can finally stop the service.
    • mcafee-client-proxy_mcpservice.exe_2.3.0.0_process-hacker-stop-mfemms
    • mcafee-client-proxy_mcpservice.exe_2.3.0.0_process-hacker-mfemms-stopped
  • Now that the parent service is stoppped, go back to the Processes Tab and kill mcpservice.exe.
    • mcafee-client-proxy_mcpservice.exe_2.3.0.0_process-hacker-terminate
  • After a reboot, the process will start again. You may disable mfemms service to prevent it from starting again (not suggested as this service may be controlling other important processes/services).

Read More

Received too large SFTP packet. Max supported packet size is 1024000 B

Received too large SFTP packet. Max supported packet size is 1024000 B, when connecting to a VMware Platform Services Controller (PSC) with WinSCP. This is an error you get due to the way the user specified is connecting via SSH. In fact, by default, you are connected with the “appliancesh”, so WinSCP isn’t able to connect correctly.

winscp_received-too-large-sftp-packet_Max-supported-packet-size-is-1024000-B

Here’s what to do (it can be rolled back to restore the previous settings) to access the Platform Services Controller via WinSCP:

  • SSH onto the Platform Services Controller and login
  • Run the following two commands to enable the shell on the current connection
    • vmware_platform-services-controller_psc_shell-enabled
  • Now run the following command. This will enable bash at login for the user you specify. In my case, I’m happy to do it for root.
      • vmware_platform-services-controller_psc_bash-enabled-for-root
  • You are now able to connect with WinSCP.

 

In order to roll back, run the following against the user you enabled bash for:

vmware_platform-services-controller_psc_appliancesh-enabled-for-root

Read More

Enable Wake on LAN in Windows

The title Enable Wake on LAN in Windows is a bit generic on purpose as this article is targeting any system. Specifically, the screenshots are take from a DELL Optiplex Micro 3040 system, but applies to any other vendor as well (screenshots will differ). The reason why I’m specifically writing this article is because I struggled a bit more than usual with a Micro 3040 model running Windows 10 and I had the 3020 working with no issues. Again, these steps apply to any system running Windows!

Also note that normally, you do not have to set all of the below up (like Firewall etc).

Let’s go in steps, starting with the basics BIOS settings.

  • Make sure the BIOS is up to date.
  • Go in the BIOS by starting the computer up and by pressing F2.
  • On a DELL system, go to Power Management and Disable Deep Sleep Control. If you’re not configuring a DELL, find the option (if it exists) to prevent the system from fully shutting down or hibernating.
    • dell_optiplex_3040_wake_on_lan_disable_deep_sleep
  • Enable Wake on Lan (or Wan or both).
    • dell_optiplex_3040_wake_on_lan_enabled

In order to fully Enable Wake on Lan in Windows, there are a few settings to be changed at the OS level. This process covers Windows 10’s settings, if you’re on Windows 7 or earlier, you may need to skip a setting or two as not present in these versions of Windows.

  • Upgrade the network interface card (NIC) drivers to the latest available.
  • Open the Network Card’s hardware settings and, under Adavanced:
    • Make sure Speed&Duplex is set to Auto Negotiation.
      • nic_advanced_speedAndDuplex_auto-negotiation
    • Enable Wake on Magic Packet.
      • nic_advanced_wakeonlan_wake-on-magic-packet-enabled
  • Go to the NIC’s Power Management tab and select Allow this device to wake the computer.
    • nic_power-management_allow-this-device-to-wake-the-computer
  • In Windows 10, go to the Power Options under Control Panel.
    • On the left hand of the window, click Choose what the power buttons do.
      • power-options_choose-what-the-power-buttons-do
    • Disable the option Turn on fast startup (recommended).
      • power-options_turn-on-fast-startup_disabled
      • Note that this option might get reset after running Windows Update. I have not encountered this problem myself yet.
  • Go to Control Panel > Windows FirewallAdvanced Settings.
    • windows-firewall_advanced-settings
    • Right click on Inbound Rules and select New Rule.
      • windows-firewall_new-rule
    • In the New Rule Wizard, select Port and click Next.
      • windows-firewall_new-rule_port
    • Under Protocol and Ports, select UDP and Specific local ports and type 9.
      • windows-firewall_new-rule_UDP_Port-9
    • See the screenshots for the rest of the steps:
      • windows-firewall_new-rule_Action
      • windows-firewall_new-rule_Profile
      • windows-firewall_new-rule_Name

This should be enough for you to get Wake On Lan configured on the machine you want.

Read More