Navigation

Install MongoDB Enterprise Edition on Windows

Overview

Use this tutorial to install MongoDB 3.6 Enterprise Edition on Windows using the default installation wizard.

MongoDB Enterprise Edition is available on select platforms and contains support for several features related to security and monitoring.

MongoDB Version

This tutorial installs MongoDB 3.6 Enterprise Edition. To install a different version of MongoDB Enterprise, use the version drop-down menu in the upper-left corner of this page to select the documentation for that version.

Installation Method

This tutorial installs MongoDB on Windows using the default installation wizard. Alternatively, you may chose to install MongoDB on Windows in an unattended fashion, using msiexec.exe from the command line (cmd.exe). This is useful for system administrators who wish to deploy MongoDB using automation.

➤ See Install MongoDB Enterprise on Windows using msiexec.exe for instructions.

Considerations

Platform Support

MongoDB 3.6 Enterprise Edition supports the following 64-bit versions of Windows on x86_64 architecture:

  • Windows 8 / Windows Server 2012 R2 and later
  • Windows 7 / Windows Server 2008 R2

MongoDB only supports the 64-bit versions of these platforms.

See Supported Platforms for more information.

Production Notes

Before deploying MongoDB in a production environment, consider the Production Notes document which offers performance considerations and configuration recommendations for production MongoDB deployments.

Show All File Name Extensions

Make certain that you set Windows Explorer to show file name extensions for all file types. This can prevent issues where the file type displayed to the user differs from the actual file type.

Example

If Windows Explorer has known file extensions hidden, what may appear to be mongod.cfg is actually mongod.cfg.txt.

Use Command Interpreter, not Powershell

Every time this tutorial refers to the command line, you should use the Windows command interpreter (cmd.exe) with Administrative privileges. Not all commands work in Powershell.

To start cmd.exe with Administrative privileges:

  1. Open the Start menu.

    • Press the windows icon key.
    • Click on the Start windows icon icon at the left end of the taskbar.
  2. Type cmd.exe in the search box.

  3. Press Ctrl + Shift + Enter.

    This starts the Command Prompt as the Administrator user.

Remember the directory where you installed MongoDB

This tutorial uses the default MongoDB Enterprise Edition location of C:\Program Files\MongoDB\Server\3.6\.

If you have installed in an alternative directory, you must adjust the paths as appropriate.

Install MongoDB Enterprise Edition

Prerequisites

Windows 2012 Server and Windows 10 need KB2999226 to provide Universal C Runtime support for Windows.

Procedure

Follow these steps to install MongoDB Enterprise Edition using the Windows Installation wizard. The installation process installs both the MongoDB binaries as well as the default configuration file <install directory>\bin\mongod.cfg.

1

Download MongoDB Enterprise Edition.

  1. Open a web browser and visit the MongoDB Download Center.
  2. The Download Center should display MongoDB Enterprise Server tab. If not, select Server, then click the MongoDB Enterprise Server tab.
  3. In the Version dropdown, select the version that corresponds to MongoDB Server 3.6. The download center always displays the latest available point version. For older point releases, click Archived releases in the right hand navigation box.
  4. In the OS dropdown, verify that Windows 64-bit X64 is selected.
  5. In the Package drop down, verify that MSI is selected.
  6. Click Download.
2

Open Windows Explorer.

3
4

Double-click the .msi file.

5

Follow the MongoDB Enterprise Edition installation wizard.

If you choose the Custom installation option, you may specify an installation directory. MongoDB has no other system dependencies. You can install and run MongoDB from any directory.

Start MongoDB Enterprise Edition from the Command Interpreter

1

Create the database directory.

Create the data directory where MongoDB stores data. MongoDB’s default data directory path is the absolute path \data\db on the drive from which you start MongoDB.

From the Command Interpreter, create the data directory:

cd C:\
md "\data\db"
2

Start your MongoDB database.

To start MongoDB, invoke mongod.exe.

"C:\Program Files\MongoDB\Server\3.6\bin\mongod.exe" --dbpath="c:\data\db"

The --dbpath option points to your database directory.

If the MongoDB database server is running correctly, the Command Interpreter displays:

[initandlisten] waiting for connections

Important

Depending on the Windows Defender Firewall settings on your Windows host, Windows may display a Security Alert dialog box about blocking “some features” of C:\Program Files\MongoDB\Server\3.6\bin\mongod.exe from communicating on networks. To remedy this issue:

  1. Click Private Networks, such as my home or work network.
  2. Click Allow access.

To learn more about security and MongoDB, see the Security Documentation.

3

Connect to MongoDB.

To connect a mongo.exe shell to the MongoDB instance, open another Command Interpreter with Administrative privileges and run:

"C:\Program Files\MongoDB\Server\3.6\bin\mongo.exe"

For more information on connecting a mongo.exe shell, such as to connect to a MongoDB instance running on a different host and/or port, see The mongo Shell. For information on CRUD (Create,Read,Update,Delete) operations, see MongoDB CRUD Operations.

To help you start using MongoDB, MongoDB provides Getting Started Guides in various driver editions. See Getting Started for the available editions.

Start MongoDB Enterprise Edition as a Windows Service

You can set up the MongoDB server as a Windows Service that starts automatically at boot time.

1

Create the database and log directories.

If you have not created the data and log directories for your MongoDB server, you must create them before running MongoDB Enterprise Edition as a Windows service.

From the Command Interpreter, create the following directories:

cd C:\
md "\data\db" "\data\log"
2

Create a MongoDB configuration file.

Create a MongoDB configuration file:

C:\Program Files\MongoDB\Server\3.6\mongod.cfg

Note

MongoDB configuration files use the YAML file format. Per the YAML 1.2 specification, all indents must use spaces to maintain portability. To ensure no parsing errors, enclose all values in double quotation marks (") and escape any backslash characters (\).

Set the storage.dbPath and systemLog.path. Include additional configuration options as needed:

systemLog:
  destination: "file"
  path: "c:\\data\\log\\mongod.log"
storage:
  dbPath: "c:\\data\\db"
3

Create the MongoDB service.

Invoke the following command in the Command Interpreter to create the service:

sc.exe create MongoDB binPath= "\"C:\Program Files\MongoDB\Server\3.6\bin\mongod.exe\" ^
  --service --config=\"C:\Program Files\MongoDB\Server\3.6\mongod.cfg\"" DisplayName= "MongoDB" start= auto

Note

sc.exe requires a space between “= ” and the configuration values (i.e. binPath= `` ) as well as using `` "\" and \"" to escape a double-quoted string.

If successfully created, the following message is written to the log:

 [SC] CreateService SUCCESS
4

Start the MongoDB service.

Close all other command prompts, then invoke the following command:

net start MongoDB
5

Verify that MongoDB has started successfully.

Check your MongoDB log file for the following line:

[initandlisten] waiting for connections on port 27017

You may see non-critical warnings in the process output. As long as you see this message in the MongoDB log, you can safely ignore these warnings during your initial evaluation of MongoDB.

6

Connect to the MongoDB server.

To connect to MongoDB through the mongo.exe shell, open another Command Interpreter.

"C:\Program Files\MongoDB\Server\3.6\bin\mongo.exe"

Stop MongoDB Enterprise Edition as a Windows Service

To stop the MongoDB service, invoke the following command:

net stop MongoDB

Remove MongoDB Enterprise Edition as a Windows Service

To remove the MongoDB service, first stop the service and then run the following command:

sc.exe delete MongoDB

Additional Considerations

Localhost Binding by Default

By default, MongoDB launches with bindIp set to 127.0.0.1, which binds to the localhost network interface. This means that the mongod.exe can only accept connections from clients that are running on the same machine. Remote clients will not be able to connect to the mongod.exe, and the mongod.exe will not be able to initialize a replica set unless this value is set to a valid network interface.

This value can be configured either:

  • in the MongoDB configuration file with bindIp, or
  • via the command-line argument --bind_ip

Warning

Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist. At minimum, consider enabling authentication and hardening network infrastructure.

For more information on configuring bindIp, see MongoDB Configuration Hardening.

Point Releases and .msi

If you installed MongoDB with the Windows installer (.msi), that .msi automatically upgrades within its release series (e.g. 3.6.1 to 3.6.2).

Upgrading a full release series (e.g. 3.6 to 4.0) requires a new installation.

Add MongoDB binaries to the System PATH

All command-line examples in this tutorial are provided as absolute paths to the MongoDB binaries. You can add C:\Program Files\MongoDB\Server\3.6\bin to your System PATH and then omit the full path to the MongoDB binaries.