By default, MediaMonkey's .ini file is configured for single user access to a locally stored database. However, it is possible to change these settings so that multiple users can share a database stored to a common location.
Note that MediaMonkey uses sqlite as the backend database, and it isn't designed as a multi-user/networked database, so test this approach in your local environment carefully before deploying.
To set up such a shared environment:
- On a machine that has MediaMonkey installed, scan a network location that will contain your music by pasting it into the Scan Folders dialog. It is preferable to scan a UNC path rather than a mapped drive. e.g.
\\ip _address\path (almost always works)
\\computer_name\path (often works)
J: (mapped network drive often fails)
- Close MediaMonkey (so that it doesn't overwrite any of the changes)
- Back up the .ini file. If you're not sure where to find it, see:
- To ensure that all users on the local machine have access, move the MediaMonkey.ini file to the Program Files/MediaMonkey directory. This will cause all users to have the same MediaMonkey settings, however, you must make sure that all users have permission to read/write to this directory.
- Save the MediaMonkey database to a shared folder e.g.
c:\MM Shared library\mm.db or \\ip _address\path\mm.db (\\computer_name\path\mm.db)
- Edit MediaMonkey.ini file in Program Files/MediaMonkey directory and add this line to [system] section depending on where the DB is stored:
a) DBName=c:\MM Shared library\mm.db
b) DBName=\\ip _address\path\mm.db
- For each machine that is accessing the database, modify the location of the database to a shared location as described at:
- Start MediaMonkey to ensure that your MediaMonkey database file has correctly set permissions so that all users can read/write to the database.
Note: If the tracks are greyed out on one of the machines, see:
More about sqlite in a networked/multi-user environment: