- Install MongoDB >
- Install MongoDB Enterprise >
- Install MongoDB Enterprise Edition on Windows >
- Install MongoDB Enterprise on Windows using
msiexec.exe
Install MongoDB Enterprise on Windows using msiexec.exe¶
On this page
- Overview
- Considerations
- Install MongoDB Enterprise Edition
- Start MongoDB Enterprise Edition from the Command Interpreter
- Start MongoDB Enterprise Edition as a Windows Service
- Stop MongoDB Enterprise Edition as a Windows Service
- Remove MongoDB Enterprise Edition as a Windows Service
- Additional Considerations
Overview¶
Use this tutorial to install MongoDB 3.6 Enterprise Edition on
Windows in an unattended fashion using msiexec.exe from the command
line. This is useful for system administrators who wish to
deploy MongoDB using automation.
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 command-line tool
msiexec.exe. To install MongoDB using the graphical MSI Installer
instead, see Install MongoDB using the MSI Installer.
Considerations¶
Platform Support¶
MongoDB 3.6 Enterprise Edition supports the following 64-bit versions of Windows on x86_64 architecture:
- Windows 10 / Windows Server 2016
- Windows 8.1 / Windows Server 2012 R2
- Windows 8 / Windows Server 2012
- 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:
-
- Press the windows icon key.
- Click on the Start windows icon icon at the left end of the taskbar.
Type
cmd.exein the search box.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¶
Users on Windows versions previous to Windows 10 must install the following update before installing MongoDB:
➤ Update for Universal C Runtime for Windows
Users on Windows 10, Server 2016 and Server 2019 do not need this update.
Procedure¶
Follow these steps to install MongoDB Enterprise Edition unattended on
Windows from the Windows command prompt/interpreter (cmd.exe) using msiexec.exe.
Download MongoDB Enterprise Edition.¶
- Open a web browser and visit the MongoDB Download Center.
- The Download Center should display MongoDB Enterprise Server tab. If not, select Server, then click the MongoDB Enterprise Server tab.
- 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.
- In the OS dropdown, verify that
Windows 64-bit X64is selected. - In the Package drop down, verify that
MSIis selected. - Click Download.
Run the Windows Installer from the Windows Command Interpreter.¶
Change to the directory containing the .msi installation binary
and invoke:
To specify a different installation location for the executables,
add the INSTALLLOCATION value.
By default, this method installs all MongoDB binaries. To install
specific MongoDB component sets, you can specify them in the
ADDLOCAL argument using a comma-separated list including one or
more of the following component sets:
| Component Set | Binaries |
|---|---|
Server |
mongod.exe |
Router |
mongos.exe |
Client |
mongo.exe |
MonitoringTools |
mongostat.exe, mongotop.exe |
ImportExportTools |
mongodump.exe, mongorestore.exe, mongoexport.exe, mongoimport.exe |
MiscellaneousTools |
bsondump.exe, mongofiles.exe, mongoperf.exe |
Example
To install only the MongoDB utilities, invoke:
If you do not wish to install
MongoDB Compass
at this time, include the SHOULD_INSTALL_COMPASS="0" argument.
Start MongoDB Enterprise Edition from the Command Interpreter¶
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:
Start your MongoDB database.¶
To start MongoDB, invoke mongod.exe.
The --dbpath option points to your
database directory.
If the MongoDB database server is running correctly, the Command Interpreter displays:
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:
- Click Private Networks, such as my home or work network.
- Click Allow access.
To learn more about security and MongoDB, see the Security Documentation.
Connect to MongoDB.¶
To connect a
mongo.exe shell to the MongoDB instance, open another
Command Interpreter with Administrative privileges and run:
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.
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:
Create a MongoDB configuration file.¶
Create a MongoDB configuration file:
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:
Create the MongoDB service.¶
Invoke the following command in the Command Interpreter to create the service:
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:
Start the MongoDB service.¶
Close all other command prompts, then invoke the following command:
Verify that MongoDB has started successfully.¶
Check your MongoDB log file for the following line:
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.
Stop MongoDB Enterprise Edition as a Windows Service¶
To stop the MongoDB service, invoke the following command:
Remove MongoDB Enterprise Edition as a Windows Service¶
To remove the MongoDB service, first stop the service and then run the following command:
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:
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), the
.msi automatically upgrades within the same 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.