A complete web-based remote monitoring and management web site. Once setup you can install agents and perform remote desktop session to devices on the local network or over the Internet.
Go to file
2019-11-28 20:57:34 -08:00
agents Enabled all next-gen agent features in the server. 2019-11-28 12:34:45 -08:00
amt A working serverside AMT API via 3 different 2019-09-20 17:21:58 -07:00
docs Added docs folder with word documents. 2019-10-18 20:08:53 -07:00
public Updated to next generation MeshAgent. 2019-11-28 12:27:44 -08:00
translate Randomized Intel AMT Env Detection. 2019-11-15 14:36:41 -08:00
views Enabled all next-gen agent features in the server. 2019-11-28 12:34:45 -08:00
.gitignore Removed package-lock.json 2019-06-06 14:16:38 -07:00
amt-ider.js First server with working hard-coded server-side IDER support. 2019-04-24 11:38:28 -07:00
amtevents.js Changed copyrights headers for 2019. 2019-01-03 16:22:15 -08:00
amtscanner.js Removed clonings. 2019-10-11 11:16:36 -07:00
amtscript.js Changed copyrights headers for 2019. 2019-01-03 16:22:15 -08:00
apfserver.js Update apfserver node search to fix authentication issue 2019-11-26 15:38:03 -07:00
certoperations.js Added automatic key usage fix for root cert 2019-11-14 16:10:16 -08:00
common.js Improved support for reverse-proxy certificate loading. 2019-10-29 16:17:29 -07:00
CreateSourcePackage.bat Initial main commit 2017-08-28 09:27:45 -07:00
db.js Plugin system improvements. 2019-11-25 14:12:43 -08:00
exeHandler.js Fixed how the Windows MeshAgent's are downloaded from the server. 2019-10-23 13:12:30 -07:00
interceptor.js Changed copyrights headers for 2019. 2019-01-03 16:22:15 -08:00
letsEncrypt.js Added extra checking for Let's Encrypt NodeJS version. 2019-11-19 11:18:08 -08:00
LICENSE Changed copyrights headers for 2019. 2019-01-03 16:22:15 -08:00
meshaccelerator.js Added server process cleanup. 2019-07-17 15:57:42 -07:00
meshagent.js Merge branch 'master' into plugin-admin 2019-11-01 16:50:42 -04:00
meshcentral.js Implemented optional 2nd factor skip for some IP addresses 2019-11-28 20:57:34 -08:00
MeshCentral.sln Initial main commit 2017-08-28 09:27:45 -07:00
MeshCentralServer.njsproj Updated to next generation MeshAgent. 2019-11-28 12:27:44 -08:00
meshctrl.js Added config command to MeshCtrl. 2019-11-22 16:17:29 -08:00
meshmail.js Added SMTP connection options. 2019-09-16 10:49:35 -07:00
meshrelay.js Fixed mesh router relay. 2019-10-17 10:09:16 -07:00
meshscanner.js Reverse proxy fixes. 2019-08-31 19:40:50 -07:00
meshuser.js Added server warnings in MyServer tab. 2019-11-26 14:11:09 -08:00
mpsserver.js Removed clonings. 2019-10-11 11:16:36 -07:00
mqttbroker.js Added manual device events, fixed MQTT publish filter. 2019-10-16 14:46:41 -07:00
multiserver.js More MQTT improvements. 2019-10-07 18:11:15 -07:00
package.json Added server warnings in MyServer tab. 2019-11-26 14:11:09 -08:00
pass.js Added batch account addition. 2019-05-14 14:39:26 -07:00
plugin_development.md Doc update 2019-11-23 15:23:44 -05:00
pluginHandler.js Fix MeshCentral version comparisons. (Breaking for versions -a through -c) 2019-11-27 13:18:18 -05:00
readme.md Fixed agent invite link when UserAllowedIP is used. 2019-10-11 15:39:15 -07:00
redirserver.js Moved to GreenLock v3 2019-11-13 22:47:17 -08:00
reinstall-modules.bat Module dependency cleanup. 2019-03-25 11:32:16 -07:00
sample-config.json Implemented optional 2nd factor skip for some IP addresses 2019-11-28 20:57:34 -08:00
SourceFileList.txt Improved MeshAgent and MeshCmd. 2018-01-25 16:12:53 -08:00
swarmserver.js Added server tracing dialog in web app. 2019-08-22 15:31:39 -07:00
webauthn.js Fixed webauthn.js file name 2019-07-11 15:00:38 -07:00
webserver.js Implemented optional 2nd factor skip for some IP addresses 2019-11-28 20:57:34 -08:00
winservice.js Small fix to winservice.js 2019-08-08 13:02:49 -07:00

MeshCentral

For more information, visit MeshCommander.com/MeshCentral2. Discussion forum on Reddit.

Download the full PDF user's guide with more information on configuring and running MeshCentral2. In addition, the installation guide can help get MeshCentral installed on Amazon AWS, Microsoft Azure, Ubuntu or Raspberry Pi.

This is a full computer management web site. With MeshCentral, you can run your own web server to remotely manage and control computers on a local network or anywhere on the internet. Once you get the server started, create a mesh (a group of computers) and then download and install a mesh agent on each computer you want to manage. A minute later, the new computer will show up on the web site and you can take control of it. MeshCentral includes full web-based remote desktop, terminal and file management capability.

To test this server, feel free to try MeshCentral.com.

Installation

Make sure you have NodeJS and npm installed. If you are behind a proxy, setup npm to use the proxy:

	npm config set proxy http://proxy.com:88
	npm config set https-proxy http://proxy.com:88

Then, install MeshCentral by creating an empty folder and using npm to download the module:

	mkdir meshcentral
	cd meshcentral
	npm install meshcentral

To run MeshCentral you may need to use nodejs instead of node on Linux.

	cd ./node_modules/meshcentral
	node meshcentral [arguments]

You can launch MeshCentral with no arguments to start it in LAN mode. In LAN mode only devices on the local network can be managed. To setup a more secure server, use --cert to specify an IP address or name that resolves to your server. This name will be used by mesh agents to connect back to the server. So, make sure you set a name that will resolve back to your server. MeshCentral will not register this name for you. You must make sure to setup the DNS name yourself first, or use the right IP address. If you are just taking a quick look at MeshCentral, you can skip this step and do it at later time.

	node meshcentral --cert servername.domain.com
	node meshcentral --cert 1.2.3.4

On Windows, you can install MeshCentral to run as a background service, just run it using --install. Once running, open a browser and enter the server url. By default, a TLS self-signed certificate is created so you will need to ignore the security warning given by your browser. A link to the root certificate that can be loaded into your browser is provided on the website so you can make the warnings go away. You can run without TLS security using --notls, but this is not recommended.

Update and uninstall

Uninstalling MeshCentral is super easy, just use npm as usual. For updating, just install over the previous version by installing again, data files will not be changed. From the parent folder of node_module, enter ether:

	npm install meshcentral
	npm uninstall meshcentral

Command Line

Command line arguments on Windows only:

Arguments Description
--install Install MeshCentral as a background service.
--uninstall Uninstall MeshCentral background service.
--start Start MeshCentral as a background service.
--stop Stop MeshCentral background service.

Command line arguments on any platform:

Arguments Description
--notls Use HTTP instead of HTTPS for the main web server.
--user [username] Always login as [username] if the account exists.
--port [number] Web server port number (default is 443).
--mpsport [number] Intel AMT server port number (default is 4433).
--redirport [number] Redirection web server, redirects users to the HTTPS server (default to 80).
--exactports Server must run with correct ports or exit.
--cert [name], (country), (org) Create a web server certificate with a server name. Country and organization can optionaly be set.

Configuration File

As an alternative to using command line arguments, you can create a ./node-module/meshcentral-data/config.json file, for example:

	{
		"settings": {
			"port": 8080,
			"redirport": 81
		},
		"domains": {
			"": {
				"title": "MyServer",
				"title2": "Servername",
				"userQuota": 1048576,
				"meshQuota": 248576,
				"newAccounts" : 1
			},
			"Customer1": {
				"title": "Customer1",
				"title2": "Extra String",
				"newAccounts" : 0
			},
			"Customer2": {
				"title": "Customer2",
				"title2": "Other String"
			}
		}
	}

The settings part are for command line arguments. For example, instead of running with --port 8080, you can put "port": 8080 in the settings portion of the config.json file. In addition, you can use the config.json file to create multi-tenancy servers. In the domains section, you can set options for the default domain ("") in addition to creating new domains.

For the configuration above, the root domain and two other domains will be accessible like this:

	https://servername:8080/
	https://servername:8080/customer1
	https://servername:8080/customer2

When you setup many domains, the server considers each domain separately. Each domain has separate user accounts, administrators, etc. Within each domain, you can put a title and title2 as strings that will show up at the top of the web site. userQuota indicates the default maximum amount of data a user can have in it's "My Files" folder. meshQuota is the maximum total size of files in each mesh folder. newAccounts indicates if new accounts can be created from the login page, 0 if not allowed, 1 if allowed. Note that if a web site has no accounts, the new account option will be available until an account is created and the first account will be the site administrator.

Other Notes

For Windows users, if you install MeshCentral globally using npm install meshcentral -g, it will not be able to run correctly as a Windows Service. It will immediately stop each time you start it.

For more information on MeshCentral or other tools, visit MeshCommander.com.

Tutorials

How to install MeshCentral2 in a few minutes.
MeshCentral2 - Installation

Demonstration of MeshCentral2 usages and more tips & tricks.
MeshCentral2 - Usages

How to setup Intel® AMT client initiated remote access (CIRA) to connect to MeshCentral2.
MeshCentral2 - Intel AMT CIRA

License

This software is licensed under Apache 2.0.