The Standalone Repository requires at least version 3.2.10 of MongoDB (or a later release in the
3.2.x series—MongoDB 2.x is no longer supported), which must be installed and running the MMAPv1 storage engine before
the Standalone Repository can be installed. The Standalone Repository does not support SSL connections to MongoDB, as the MongoDB instance is restricted to connections from the local host.
Note: We recommend putting MongoDB's data on a separate drive. The steps assume the
P:\ drive, but it can be any drive (aside from
D:\ on an Azure VM); just replace
P:\ with the drive you
Download MongoDB 3.2.x (x64) from https://www.mongodb.org/downloads.
Select "Community Server".
From the Version drop-down, select "Windows Server 2008 R2 64-bit and later, without SSL support x64".
Click the "All Version Binaries" link.
Search for and download the ZIP archive
win32/mongodb-win32-x86_64-2008plus-3.2.10.zip or that of a later version.
Extract the contents to the root folder, e.g.
C:\. You should have a folder named something similar to
Rename the folder to
Make a new folder for logs:
Make a new folder for the database:
Make a configuration file for mongod.exe in the
C:\mongodb folder. The configuration file is a text file (YAML format) named
mongod.cfg that should contain lines to configure the database to use the MMAPv1 storage engine,
set the logging and data locations, specify a slow operation threshold, and restrict access to the local host. For example:
Important Note: The YAML format of the configuration above does not allow Tab characters. Use spaces instead.
Install MongoDB as a Windows Service by running this command from an Administrator command prompt:
C:\mongodb\bin\mongod.exe --config C:\mongodb\mongod.cfg --install
Start the service from the command prompt using the following command:
net start MongoDB
If the service fails to start, check the log (
C:\mongodb\log\mongo.log) for errors. Note that the service won't start if the logpath in the configuration file is pointing to a non-existent folder, or if the server can't
access it. It may also fail to start if the configuration file is improperly formatted.
Verify connectivity by running
C:\mongodb\bin\mongo.exe which will display an error if it can’t connect to the MongoDB server. If the connection is successful, type the command
exit to close the client.
Per the MongoDB Production Notes, we recommend setting the Windows page file to the largest feasible multiple of