diff --git a/docs/doxygen-user/images/credentialManager.PNG b/docs/doxygen-user/images/credentialManager.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..21acb8779b41c9b47156b8378db3dd7de434ba26
Binary files /dev/null and b/docs/doxygen-user/images/credentialManager.PNG differ
diff --git a/docs/doxygen-user/images/credentialsWithDomain.PNG b/docs/doxygen-user/images/credentialsWithDomain.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..4127a9497f452ab0e4aca9a81e6da5f0c2e1a249
Binary files /dev/null and b/docs/doxygen-user/images/credentialsWithDomain.PNG differ
diff --git a/docs/doxygen-user/images/dataDir.PNG b/docs/doxygen-user/images/dataDir.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..b4b6eb0693a297095d0742d6a1115731144c545e
Binary files /dev/null and b/docs/doxygen-user/images/dataDir.PNG differ
diff --git a/docs/doxygen-user/images/getHostname.PNG b/docs/doxygen-user/images/getHostname.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..330c6555890608e2b6d14c86be363e43e55d6589
Binary files /dev/null and b/docs/doxygen-user/images/getHostname.PNG differ
diff --git a/docs/doxygen-user/images/hostname.PNG b/docs/doxygen-user/images/hostname.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..d97f78ae427d8f2059d1296d0b994d041c4798b4
Binary files /dev/null and b/docs/doxygen-user/images/hostname.PNG differ
diff --git a/docs/doxygen-user/images/log4j.PNG b/docs/doxygen-user/images/log4j.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..15a4ba1113a58b9238159fc06356e33de4b3e223
Binary files /dev/null and b/docs/doxygen-user/images/log4j.PNG differ
diff --git a/docs/doxygen-user/images/maxConnections.PNG b/docs/doxygen-user/images/maxConnections.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..13734ce42009972204255e179bb780bc73faec15
Binary files /dev/null and b/docs/doxygen-user/images/maxConnections.PNG differ
diff --git a/docs/doxygen-user/images/newLoginRole.PNG b/docs/doxygen-user/images/newLoginRole.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..2ceaf5305f827cfee55f6fdb65fb8add28b91849
Binary files /dev/null and b/docs/doxygen-user/images/newLoginRole.PNG differ
diff --git a/docs/doxygen-user/images/newPassword.PNG b/docs/doxygen-user/images/newPassword.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..aeaa67fb3178beca1affc229304291340e3aa5cb
Binary files /dev/null and b/docs/doxygen-user/images/newPassword.PNG differ
diff --git a/docs/doxygen-user/images/newRights.PNG b/docs/doxygen-user/images/newRights.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..548519c7571b184088655c740ffb5428f30100d3
Binary files /dev/null and b/docs/doxygen-user/images/newRights.PNG differ
diff --git a/docs/doxygen-user/images/newUserAndPassword.PNG b/docs/doxygen-user/images/newUserAndPassword.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..39f90ab846c516bd0940f33493014d65bb8111ba
Binary files /dev/null and b/docs/doxygen-user/images/newUserAndPassword.PNG differ
diff --git a/docs/doxygen-user/images/pgAdmin.PNG b/docs/doxygen-user/images/pgAdmin.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..cca4988335036219049308c2a1f38cb29198aa81
Binary files /dev/null and b/docs/doxygen-user/images/pgAdmin.PNG differ
diff --git a/docs/doxygen-user/images/postgresqlinstall2.PNG b/docs/doxygen-user/images/postgresqlinstall2.PNG
old mode 100644
new mode 100755
index ac73b9ca4addf4dce89dd64d3d456e82f8b68433..7a417966cafbc3f71de1da073d7dffce8e99e2e2
Binary files a/docs/doxygen-user/images/postgresqlinstall2.PNG and b/docs/doxygen-user/images/postgresqlinstall2.PNG differ
diff --git a/docs/doxygen-user/images/tickTime.PNG b/docs/doxygen-user/images/tickTime.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..554c0b62d9fa9f6530e71aeb7501ac10aa01d618
Binary files /dev/null and b/docs/doxygen-user/images/tickTime.PNG differ
diff --git a/docs/doxygen-user/images/toConnect.PNG b/docs/doxygen-user/images/toConnect.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..4bfecbc4b62cdd65babb58f8e80e1f5969940a34
Binary files /dev/null and b/docs/doxygen-user/images/toConnect.PNG differ
diff --git a/docs/doxygen-user/images/updatedServiceInstall.PNG b/docs/doxygen-user/images/updatedServiceInstall.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..7be7fb50747f0bab9a98b7b026c7b4576506af91
Binary files /dev/null and b/docs/doxygen-user/images/updatedServiceInstall.PNG differ
diff --git a/docs/doxygen-user/images/urlInAddressbar.PNG b/docs/doxygen-user/images/urlInAddressbar.PNG
new file mode 100755
index 0000000000000000000000000000000000000000..2577a554509c8dc80f944967af8fbad78789da8c
Binary files /dev/null and b/docs/doxygen-user/images/urlInAddressbar.PNG differ
diff --git a/docs/doxygen-user/installation.dox b/docs/doxygen-user/installation.dox
index ccd03defb76c9000265bc9488ecd8628d29c5c6b..68f6387d5fc17c49cd5c4c46f742c98be631e77a 100755
--- a/docs/doxygen-user/installation.dox
+++ b/docs/doxygen-user/installation.dox
@@ -77,54 +77,54 @@ To install ActiveMQ, perform the following steps:
<br>
6. Move the <i>apache-activemq-5.11.1</i> folder to a location of your choice, bearing in mind that the files should be in a location that the running process will have write permissions to the folder. A typical folder choice is <i>C:\\Program Files\\apache-activemq-5.11.1</i>. Typically, it will ask for administrator permission to move the folder. Allow it if required.
7. Install ActiveMQ as a service by navigating to the folder <i>apache-activemq-5.11.1-bin\\apache-activemq-5.11.1\\bin\\win64</i>, right-clicking _InstallService.bat_, clicking _Run as administrator_, then click _Yes_.
-8. Start the ActiveMQ service by going pressing _Start_, type _services.msc_, and press _Enter_. Find _ActiveMQ_ in the list and press the _Start the service_ link.
-9. ActiveMQ should now be fully installed.
-10. You can access the admin pages in your web browser using something via a URL like this (set your host): http://localhost:8161/admin. The default username is _admin_ and the default password is _admin_. If you can see a page that looks like the following, it is ready to function.
+8. Start the ActiveMQ service by pressing _Start_, type _services.msc_, and press _Enter_. Find _ActiveMQ_ in the list and press the _Start the service_ link.
+9. ActiveMQ should now be fully installed and configured. You can access the admin pages in your web browser via a URL like this (set your host): http://localhost:8161/admin. The default username is _admin_ and the default password is _admin_. If you can see a page that looks like the following, it is ready to function.
<br><br>
\image html activemq.PNG
<br>
-11. If you do not see a screen like the above screenshot and you have double checked that the ActiveMQ service is running, contact your network administrator. For the ActiveMQ service to be accessible by network clients you may need to configure your Windows firewall (and any other 3rd party firewall in use) to allow communication.
-
+<br>
+ If you do not see a screen like the above screenshot and you have double checked that the ActiveMQ service is running, contact your network administrator. For the ActiveMQ service to be accessible by network clients you may need to configure your Windows firewall (and any other 3rd party firewall in use) to allow communication.
<br><br>
\subsection solr_install Bitnami Solr Installation
-To install Solr, perform the following steps:
-1. Download the Apache Solr 4.10.3-0 installation package from https://bitnami.com/stack/solr/installer. By default, the Bitnami installation process will configure Solr to run in a 32-bit Java runtime as a Windows Service under the Local System account. The following steps will configure Solr to run in a 64-bit Java runtime using an account that will have access to the network storage.
+A central Solr server is needed to store keyword indexes. To install Solr, perform the following steps:
+1. Download the Apache Solr 4.10.3-0 installation package from https://bitnami.com/stack/solr/installer. By default, the Bitnami installation process will configure Solr to run in a 32-bit Java runtime as a Windows Service under the Local System account. The following steps will configure Solr to run in a 64-bit Java runtime using an account that will have access to the network storage.
2. Test if you have a 64-bit version of the Java Runtime Environment already installed by double clicking _test_version.bat_. If you do not see "You have a 64-bit JRE installed", proceed to step 3. If you see "You have a 64-bit JRE installed", proceed to step 4.
3. Install a 64-bit version of the JRE. Download it from: http://www.oracle.com/technetwork/java/javase/downloads/jre8-downloads-2133155.html. Be sure to select a package that has "x64" in the name. Follow the installation prompts to install the JRE, then when the install has completed, re-run _test_version.bat_. It should say "You have a 64-bit JRE installed".
-
4. Run the Bitnami installer, <i>bitnami-solr-4.10.3-0-windows-installer.exe</i>
-
5. If Windows prompts with User Account Control, click _Yes_
-
6. Follow the prompts through to completion. You do not need to "Learn more about Bitnami cloud hosting" so you can clear the check box.
-
7. If you see an error dialog like the following, you may safely ignore it.
<br><br>
\image html apachebadmessage.PNG
<br>
8. When the installation completes, clear the "Launch Bitnami Apache Solr Stack Now?" checkbox and click _Finish_.
9. Stop _solrApache_ and _solrJetty_ services by pressing _Start_, typing _services.msc_, pressing _Enter_, and locating the _solrApache_ and _solrJetty_ Windows services. Select the services one at a time, and press _Stop the service_ once for each of them. If the service is already stopped and there is no _Stop the service_ available, this is okay.
-
10. Right click on <i>C:\\Bitnami\\solr-4.10.3-0\\apache-solr\\scripts\\serviceinstall.bat</i> and click on _Run as administrator_, selecting _Yes_ if prompted by User Account Control.
-
-11. Edit the <i>C:\\Bitnami\\solr-4.10.3-0\\apache-solr\\scripts\\serviceinstall.bat</i> script and replace the path to _JavaHome_ with the path to your 64-bit version of the JRE, e.g. something like: <i>--JavaHome="C:\Program Files\Java\jre1.8.0_45"</i> Note you need administrator permission to change this file. The easiest way around this is to save a copy on the Desktop, edit the Desktop version, and copy the new one back over the top of the old. Windows will ask for permission to overwrite the old file; allow it.
-<br><br>
-If you have a 64-bit JRE installed, the correct path can be obtained by running the command _where java_ from the Windows command line. A correct example is shown below in yellow:
-<br>
-\image html wherejava.PNG
-<br>
-Do not include the "bin" folder in the path you place into the _JavaHome_ variable.
-<br><br>
-Note that if you get something like the following, it is a symbolic link to the Java installation and you need to trace it to the proper folder as explained below.
-<br>
-\image html symlinkjava.PNG
-<br>
-Use Windows Explorer to navigate to the path shown (<i>C:\\ProgramData\\Oracle\\Java\\javapath</i> for the example above), then right click on _java.exe_ and go to _Properties_. You will see the path you should use in the _Target_ field, shown in the screenshot below. Do not include the "bin" folder in the path you place into the _JavaHome_ variable.
-<br>
-\image html javaproperties.PNG
-<br>
-12. Edit <i>C:\\Bitnami\\solr-4.10.3-0\\apache-solr\\solr\\solr.xml</i> to set the _transientCacheSize_ to the maximum number of cases expected to be open concurrently. If you expect ten concurrent cases, the text to add is
+11. Edit the <i>C:\\Bitnami\\solr-4.10.3-0\\apache-solr\\scripts\\serviceinstall.bat</i> script. You need administrator permission to change this file. The easiest way around this is to save a copy on the Desktop, edit the Desktop version, and copy the new one back over the top of the old. Windows will ask for permission to overwrite the old file; allow it. You should make the following changes to this file:
+ <br>
+ <br>
+ - Add the following options in the _JvmOptions_ section of the line that begins with <i>"C:\Bitnami\solr-4.10.3-0/apache-solr\scripts\prunsrv.exe"</i> :
+ + <i>++JvmOptions=-DzkRun</i>
+ + <i>++JvmOptions=-Dcollection.configName=AutopsyConfig</i>
+ + <i>++JvmOptions=-Dbootstrap_confdir="C:\Bitnami\solr-4.10.3-0\apache-solr\solr\configsets\AutopsyConfig\conf"</i>
+ - Replace the path to <i>JavaHome</i> with the path to your 64-bit version of the JRE. If you do not know the path, the correct _JavaHome_ path can be obtained by running the command <i>"where java"</i> from the Windows command line. An example is shown below. The text in yellow is what we are interested in, so do not include the <i>"bin"</i> folder in the path you place into the _JavaHome_ variable. A correct example of the final result will look something like this: <i>--JavaHome="C:\Program Files\Java\jre1.8.0_45"</i>
+ <br><br>
+ \image html wherejava.PNG
+ <br><br>
+ Note that if you get something like the following when running the <i>"where java"</i> command, it is a symbolic link to the Java installation and you need to trace it to the proper folder as explained below.
+ <br><br>
+ \image html symlinkjava.PNG
+ <br><br>
+ To trace a symbolic link to the proper folder, use Windows Explorer to navigate to the path shown (<i>C:\\ProgramData\\Oracle\\Java\\javapath</i> for the example above), then right click on _java.exe_ and Click on _Properties_. You will see the path you should use in the _Target_ field, shown in the screenshot below. Do not include the <i>"bin"</i> folder in the path you place into the _JavaHome_ variable.
+ <br><br>
+ \image html javaproperties.PNG
+ <br><br>
+ A fully updated _serviceinstall.bat_ is shown below, with the changes marked in yellow.
+ <br><br>
+ \image html updatedServiceInstall.PNG
+ <br><br>
+12. Edit <i>"C:\Bitnami\solr-4.10.3-0\apache-solr\solr\solr.xml"</i> to set the _transientCacheSize_ to the maximum number of cases expected to be open concurrently. If you expect ten concurrent cases, the text to add is
<i>\<int name="transientCacheSize">10\</int></i>
<br><br>
The added part is highlighted in yellow below. Ensure that it is inside the <i>\<solr></i> tag as follows:
@@ -133,23 +133,43 @@ The added part is highlighted in yellow below. Ensure that it is inside the <i>\
<br>
Again you may have trouble saving to the file in the current location. If so, just save it out to the desktop and copy the desktop file back over the top of the original.
<br><br>
-Also, be very careful. Do not cut and paste this from this document, as some programs will change quotes to characters that look like quotes but are not.
+**Do not cut and paste this from this document**, as some programs will change quotes to characters that look like quotes but are not.
+<br><br>
+13. Edit <i>"C:\Bitnami\solr-4.10.3-0\apache-solr\resources/log4j.properties"</i> to configure Solr log settings:
+ - Increase the log rotation size threshold (_log4j\.appender\.file\.MaxFileSize_) from 4MB to 100MB.
+ - Remove the _CONSOLE_ appender from the _log4j\.rootLogger_ line.
+<br><br>
+The log file should end up looking like this (modified lines are highlighted in yellow):
+<br><br>
+\image html log4j.PNG
+<br><br>
+14. Edit the file <i>"C:\Bitnami\solr-4.10.3-0\apache-solr\solr\zoo.cfg"</i> to increase the _tickTime_ value to 15000 as shown in the screenshot below.
<br><br>
-13. Copy the folders _configsets_ and _lib_ from the installation disk to <i>C:\\Bitnami\\solr-4.10.3-0\\apache-solr\\solr</i>
+\image html tickTime.PNG
+<br><br>
+15. Edit the file <i>"C:\Bitnami\solr-4.10.3-0\apache-solr\solr\zoo.cfg"</i> to set the value <i>dataDir=C:/Bitnami/zookeeper</i> as shown in the screenshot below.
+<br><br>
+\image html dataDir.PNG
+<br><br>
+16. Right-click on the file <i>"C:\Bitnami\solr-4.10.3-0\apache-solr\scripts\serviceinstall.bat"</i> and click "Run As Administrator".
-14. Start a Windows command prompt as administrator by pressing _Start_, typing _command_, right clicking on _Command Prompt_, and clicking on _Run as administrator_. Then run the following command to install the _solrJetty_ service (very likely it will say "The solrJetty service could not be started." This is okay.): <i>cmd /c C:\\Bitnami\\solr-4.10.3-0\\apache-solr\\scripts\\serviceinstall.bat INSTALL</i>
- <br><br>
-Your command prompt should look like the screenshot below. Note the use of <i>cmd /c</i> to prevent the script from closing your command prompt.
+ If there is no "Run as administrator" option when you right-click the _serviceinstall.bat_ file, start a Windows command prompt as administrator by pressing _Start_, typing _command_, right clicking on _Command Prompt_, and clicking on _Run as administrator_. Then run the following command to install the _solrJetty_ service:
+ <br><br>
+ <i>cmd /c C:\\Bitnami\\solr-4.10.3-0\\apache-solr\\scripts\\serviceinstall.bat INSTALL</i>
+ <br><br>
+ Your command prompt should look like the screenshot below. Very likely it will say "The solrJetty service could not be started." This is okay.
<br><br>
\image html solrinstall1.PNG
<br><br>
-15. Press _Start_, type _services.msc_, and press _Enter_. Find _solrJetty_. If the service is running, press _Stop the service_, then double click it, and switch to the _Log On_ tab to change the logon credentials to a user who will have access to read and write the primary shared drive. If the machine is on a domain, the Account Name will be in the form of _DOMAINNAME\\username_ as shown in the example below. Note that in the screenshot below, the domain name is _DOMAIN_ and the user name is _username_. These are just examples, not real values.
+17. Copy the folder _configsets_ from the installation disk to <i>C:\\Bitnami\\solr-4.10.3-0\\apache-solr\\solr</i>
+18. Copy the folder _lib_ from the installation disk to <i>C:\\Bitnami\\solr-4.10.3-0\\apache-solr\\solr</i>
+19. Press _Start_, type _services.msc_, and press _Enter_. Find _solrJetty_. If the service is running, press _Stop the service_, then double click it, and switch to the _Log On_ tab to change the logon credentials to a user who will have access to read and write the primary shared drive. If the machine is on a domain, the Account Name will be in the form of _DOMAINNAME\\username_ as shown in the example below. Note that in the screenshot below, the domain name is _DOMAIN_ and the user name is _username_. These are just examples, not real values.
<br><br>
\image html solrinstall2.PNG
<br>
-If the machine is on a domain, **make sure** to select the domain with the mouse by going to the _Log On_ tab, clicking _Browse_, then clicking _Locations_ and selecting the domain of interest. Then enter the user name desired and press _Check Names_. When that completes, press _OK_, type in the password (once for each box) and press _OK_. You may see "The user has been granted the log on as a service right."
+If the machine is on a domain, **make sure** to select the domain with the mouse by going to the _Log On_ tab, clicking _Browse_, then clicking _Locations_ and selecting the domain of interest. Then enter the user name desired and press _Check Names_. When that completes, press _OK_, type in the password once for each box and press _OK_. You may see "The user has been granted the log on as a service right."
-16. You should be able to see the Solr service in a web browser via the URL <i>http://localhost:8983/solr/#/</i> as shown in the screenshot below.
+20. You should be able to see the Solr service in a web browser via the URL <i>http://localhost:8983/solr/#/</i> as shown in the screenshot below.
<br><br>
\image html solrinstall3.PNG
<br>
@@ -160,18 +180,46 @@ If the service is appropriately started and you are unable to see the screenshot
To install PostgreSQL, perform the following steps:
1. Download a 64-bit PostgreSQL version 9.4.1 installer from http://www.enterprisedb.com/products-services-training/pgdownload#windows Choose the one that says _Win X86-64_.
+
2. Run _postgresql-9.4.4-1-windows-x64.exe_
+
3. You may accept defaults for all items except for the password as you work through the wizard. Do not lose the password you enter in. This is the PostgreSQL administrator login password.
+
4. You do not need to launch the StackBuilder nor acquire any more software from it. Uncheck the option to use StackBuilder and press _Finish_.
-5. Using the PostgreSQL administrator login and the _psql_ tool, create a regular user account to use while running Autopsy. Note you can also do this with the graphical tool _pgAdminIII_, but this guide only covers _psql_. To start _psql_, press _Start_, type _psql_, and press _Enter_ a few times until it prompts you for a password. Type in the password you gave it when installing PostgreSQL. You should see a prompt that looks like the screenshot below.
-<br>
+
+5. Create a regular user account to use while running Autopsy. You can do this with either of two methods, graphically, or command line. We cover graphically first.
+
+ - Graphically:
+ - Using the PostgreSQL administrator login and the pgAdmin III tool, create a regular user account to use while running Autopsy.
+ - Right click on <i>"Login Roles"</i> and select <i>"New Login Role..."</i> as shown below:
+<br><br>
+\image html pgAdmin.PNG
+<br><br>
+ - Enter the user name you would like to use in the <i>"Role name"</i> field.
+<br><br>
+\image html newLoginRole.PNG
+<br><br>
+ - Enter the password on the <i>"Definition"</i> tab.
+<br><br>
+\image html newPassword.PNG
+<br><br>
+ - Check <i>"Can create databases"</i> on the <i>"Role Privileges"</i> tab.
+<br><br>
+\image html newRights.PNG
+<br><br>
+ - Click <i>"OK"</i>.
+<br><br>
+ - Command line:
+ <br>
+ Use the _psql_ tool. To start _psql_, press _Start_, type _psql_, and press _Enter_ a few times until it prompts you for a password. Type in the password you gave it when installing PostgreSQL. You should see a prompt that looks like the screenshot below.
+<br><br>
\image html postgresqlinstall1.PNG
-<br>
+<br><br>
If you want your user account name to be <i>"Autopsy"</i> and your password to be <i>"myPassword"</i>, use the following command to create a new user, noting that the password is enclosed in single quotes, __not backticks nor double quotes__. Also note that it is important to type this command in from the keyboard directly, as copying and pasting can sometimes yield different characters for single quotes that can confuse _psql_.
<br><br>
The command is:
<br>
-> CREATE USER Autopsy WITH PASSWORD 'myPassword' CREATEDB;
+> CREATE USER Autopsy WITH PASSWORD 'myPassword' CREATEDB;
<br>
When you see the _CREATE ROLE_ output as shown in the screenshot below, the new user has been created. You can close the _psql_ window now.
<br>
@@ -187,44 +235,96 @@ First, find your machine's IPv4 address and Subnet Mask (Press _Start_, type _cm
<br>
The following is an example rule that allows all clients on the 10.10.192.x subnet to connect using md5 authentication.
<br>
-> host all all 10.10.192.0/24 md5
+> host all all 10.10.192.0/24 md5
<br>
-__Rules of thumb:__
-If your Subnet Mask is 255.255.0.0, your rule should look like this: A.B.0.0/16, where A is the first octet in your IP address and B is the second octet.
+__Subnet Mask Rules of thumb:__
+ - If your Subnet Mask is 255.255.0.0, your rule should look like this: A.B.0.0/16, where A is the first octet in your IP address and B is the second octet.
+<br>
+ - If your Subnet Mask is 255.255.255.0, your rule should look like this: A.B.C.0/24, where A is the first octet in your IP address, B is the second octet, and C is the third octet.
<br><br>
-If your Subnet Mask is 255.255.255.0, your rule should look like this: A.B.C.0/24, where A is the first octet in your IP address, B is the second octet, and C is the third octet. Add the line highlighted in yellow below, formatted with spaces between the entries, adjusting the IP address to an appropriate value as described above.
+Add the line highlighted in yellow below, formatted with spaces between the entries, adjusting the IP address to an appropriate value as described above.
<br><br>
\image html postgresqlinstall4.PNG
<br>
<br><br>
If you intend to use PostgreSQL from machines on a different subnet, you need an entry in the _pg_hba.conf_ file for each subnet.
<br><br>
-Uncomment the following values in the configuration file located at <i>C:\\Program Files\\PostgreSQL\\9.4\\data\\postgresql.conf</i> and change the value to those shown below:
+
+7. Uncomment the following entires in the configuration file located at <i>C:\\Program Files\\PostgreSQL\\9.4\\data\\postgresql.conf</i> by removing the leading "#", and change their values <i>"off"</i> as shown below.
<br>
> fsync = off<br>
> synchronous_commit = off<br>
> full_page_writes = off<br>
<br>
Pictorially, change the following, from this:
-<br>
+<br><br>
\image html postgresqlinstall5.PNG
-<br>
+<br><br>
To this:
<br><br>
\image html postgresqlinstall6.PNG
-<br>
+<br><br>
Note the removal of the leading number symbol-this uncomments that entry.
+<br><br>
+
+8. Still in <i>"C:\Program Files\PostgreSQL\9.4\data\postgresql.conf"</i>, find the entry named _max_connections_ and set it to the number of suggested connections for your configuration. A rule of thumb is add 100 connections for each Automated Ingest Node and 100 connections for each Reviewer node you plan to have in the network. More information is available at 5.1.1. See the screenshot below.
+<br><br>
+\image html maxConnections.PNG
+<br><br>
-7. Press _Start_, type _services.msc_, and press _Enter_. Select _postgresql-x64-9.4 PostgreSQL Server 9.4_ in the services list and click the link that says _Stop the service_ then click the link that says _Start the service_ as shown in the screenshot below.
+9. Press _Start_, type _services.msc_, and press _Enter_. Select _postgresql-x64-9.4 PostgreSQL Server 9.4_ in the services list and click the link that says _Stop the service_ then click the link that says _Start the service_ as shown in the screenshot below.
<br><br>
\image html postgresqlinstall7.PNG
-<br>
-PostgreSQL should now be up and running. You can verify this with the PSQL tool used earlier in this document.
+<br><br>
+PostgreSQL should now be up and running. You can verify by using either the _pgAdmin_ tool or the _psql_ tool to connect to the database server from another machine on the network .
+<br><br><br>
+
+\section shared_network_drive Shared Network Drive
+To use Multi-user cases, there needs to be a large network storage available to all participating computers.
+<br><br>
+To authenticate with Windows and allow access to a shared drive, you will need a username and a password, a domain name if you are on a domain, the IP address of the machine hosting the shared drive, and the hostname of the machine hosting the shared drive. Using Windows Explorer, enter two slashes "\\" followed by the storage machine's IP address and press enter. An example is shown below with the text "\\10.10.152.211" entered.
+<br><br>
+\image html urlInAddressbar.PNG
+<br><br>
+
+You will see a dialog similar to the following, asking for your credentials.
+
+<br><br>
+\image html credentialsWithDomain.PNG
+<br><br>
+
+If you have a domain name, add it in the top box before the "\". Follow it with your username. If you have no domain name, just use your username. Add your password in the next box down and place a check mark in <i>"Remember my credentials"</i>, then press <i>"OK"</i>.
+
+Next, we will do the same with the hostname of the machine. This is necessary to authenticate with both IP address access and hostname access. If you do not know the hostname, you may find it by pinging the IP address with the <i>"-a"</i> flag set. It will look something like the screenshot below, where we find the hostname associated with the IP address <i>10.10.142.56</i> is <i>win-kmort-4863.basistech.net</i>.
+
+<br><br>
+\image html getHostname.PNG
+<br><br>
+
+In Windows Explorer, use this hostname preceded by two slashes, "\\", in the address bar as shown below and press enter.
+
+<br><br>
+\image html hostname.PNG
+<br><br>
+
+You will see a screen similar to the screenshot below.
+
+<br><br>
+\image html toConnect.PNG
+<br><br>
+
+
+If you are familiar with the Windows Credential Manager, you may use this tool to manage credentials. These credentials can also be managed from the command line using the "net use" command. To get to Credential Manager click on to <i>Start</i>, and typing <i>"Credential Manager"</i> and pressing enter. A screenshot of the Windows Credential Manager is shown below.
+
+<br><br>
+\image html credentialManager.PNG
+<br><br>
+
+Note that authentication and access can be an issue when passwords change. When passwords change, for every computer using a credential that is no longer valid, you will need to redo the above steps. One indicator this is a problem is seeing the text: <i>"The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you."</i> Do not forget to re-authenticate with both the IP address and the hostname.
<br><br><br>
\section optimizing_performance Optimizing Performance
After installing Autopsy, there are several hardware-based things that we suggest you do to optimize performance:
-
1. Change the number of parallel pipelines used at run time. The default is two pipelines, but this can be increased if you are running on a system with several cores. To do this:
- Run Autopsy from the Start Menu or desktop
- When presented with the case creation splash screen, cancel/close the window