Remote Process Explorer

Remote Process Explorer is a powerful tool for managing, monitoring and analyzing processes on a local or remote computer.

To download and install Remote Process Explorer please visit our Download page.

The latest version of Remote Process Explorer supports the following Windows platforms:

Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012R2, Windows 10, Windows Server 2016, Windows Server 2019

To install and run Remote Process Explorer, your computer will need the following minimum requirements based on your operating system:

• Administrator privileges are required
• Super VGA 800 x 600 video adapter
• Internet access is required to register and receive product updates

No. To correctly install Remote Process Explorer you must have administrative privileges. If you are going to use Remote Process Explorer only on a local computer you must have local admin's privileges. If you are going to use Remote Process Explorer throughout your network you must have domain admin's privileges.

Well, there are no functional limitations for unregistered versions and you may use Remote Process Explorer (during the evaluation period) as a fully registered program but only on one computer in the network. In addition, unregistered versions of Remote Process Explorer display nag screens.

For every installation on a separate machine an additional license is required.

If you have lost your license code you may request a copy be sent to you.

Please fill out the registration information request form.

Please click on the header as shown below 

Yes. You may change the time range in Preferences window.

Please use 'Export to file' command from process list

or from Process menu in the Main menu

It is plain text file with one IP address or name per line.

Software doesn't work with Windows Home editions because remote administrating is disabled in these versions. Software works with XP, Vista, Windows Server 2003, Windows Server 2008, Windows Server 2008R2, Windows 7, 8, 8.1, 10.

You must have administrative privileges to connect to the remote computer.

If your current account is not administrative then you may specify administrative login and password in properties of the remote computer in computer list (right click on the remote computer→ Properties→Connect as)

1. Make sure the administrator account has a password. Blank password will NOT work. Go to Control Panel → User Accounts → Create a password for the admin user.
2. Make sure simple file sharing is disabled. - Go to Control Panel → Folder Options → View tab → Scroll right to the bottom at Advanced Settings → Uncheck Use simple file sharing.
3. Make sure file and printer sharing exception is allowed in the firewall or simply turn off the Windows Firewall. - Go to Start → Run → type netsh firewall set service type = FILEANDPRINT mode = ENABLE and click OK.
4. Start → Settings → Control Panel → Administrative Tools → Local Security Policy → Network access: Sharing and security model for local accounts option → set Classic: Local users authenticate as themselves.

As a rule these parameters are set by default in corporate network because it is impossible to provide remote administrating without these settings. Home user must set these parameters by himself.

You need to open 135-139 ports and all ports above 1024 for incoming and outgoing packets:

• Port 135 (TCP) - for Remote Procedure Call (RPC) Service
• Port 137 (UDP) - for NetBIOS Name Service
• Port 138 (UDP) - for NetBIOS Netlogon and Browsing
• Port 139 (TCP) - for NetBIOS session (NET USE)
• Ports above 1024 (TCP) - for RPC Communication.
• DCOM needs open UDP ports in the 1024-5000 range. How to configure DCOM to listen to a specific ports range

Remote Process Explorer works like any other standard Windows administrative tool (such as Event Viewer, Services, Computer Management, etc.) so, if these tools work then Remote Process Explorer will work, too.

You can find more information in the Microsoft's Knowledge Base http://msdn.microsoft.com/en-gb/library/aa389286.aspx

Remote Process Explorer uses WMI (Windows Management Instrumentation) through DCOM RPC. DCOM does not work through a NAT unless at least one of the NAT'd server machine's network addresses is visible from the client machine. The best way to get this to work is to somehow see that the name of the server is resolvable from the client machine.

Solution

We have to do a entry of the server in the host file of our system, so that it can access the information of the requested server.

You have to do the simple steps:

1. Open the host file in the path : C:\WINDOWS\system32\drivers\etc
2. Add your server's ip address and its non FQDN name (eg. a.b.c.d xxxx)
3. Save the file
4. Test results with WBEMTEST tool on Windows
   • Execute “WBEMTEST” on CMD
   • Click “Connect” and type server information.
   • If you don’t see any problem, then it means you solved the problem.
5. Run Remote Process Explorer again.

The user does not have remote access to the computer through DCOM.

Solution

Please, try the next on the problem PC:

• Click Start, click Run, type DCOMCNFG, and then click OK.
• In the Component Services dialog box, expand Component Services, expand Computers, and then expand My Computer.
• On the toolbar, click the Configure My Computer button. The My Computer dialog box appears.
• In the My Computer dialog box, click the COM Security tab.
• Under Launch and Activate Permissions, click Edit Limits.
• In the Launch Permission dialog box, follow these steps if your name or your group does not appear in the Groups or user names list: In the Launch Permission dialog box, click Add. In the Select Users, Computers, or Groups dialog box, add your name and the group in the Enter the object names to select box and then click OK.
• In the Launch Permission dialog box, select your user and group in the Group or user names box. In the Allow column under Permissions for User, select Remote Launch, and then click OK.

UAC blocks some (not all) WMI counters, resulting in error 80041003: The current user does not have permission to perform the action. You can add the following registry key to disable this feature of UAC.

To disable UAC remote restrictions, follow these steps:

• Click Start, click Run, type regedit, and then press ENTER.
• Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
• If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
  • On the Edit menu, point to New, and then click DWORD Value.
  • Type LocalAccountTokenFilterPolicy, and then press ENTER.
• Right-click LocalAccountTokenFilterPolicy, and then click Modify.
• In the Value data box, type 1, and then click OK.
• Exit Registry Editor.

Note: This disables some of the protection provided by UAC. Specifically, any remote access to the server using an administrator security token is automatically elevated with full administrator rights, including access to the root folder.

More information can be found here: http://support.microsoft.com/kb/951016

You should run the software as administrator for registration.

To run as administrator please right-click on the program's shortcut and and select Run as Administrator from the popup menu.Then please enter the registration information.

In case if you are still seeing this issue:

Please download the latest version of Remote Process Explorer from our site and install it.

After that please register Remote Process Explorer from command line.

Please use this command:

rpexplorer.exe   QUIETREGISTER   LICENSED_TO,LICENSE_KEY