Installing Directory Search


Quick Installation of Prerequisites

You can quickly install all of the roles and features necessary using the PowerShell's Server Manager module. This allows you to specify all the roles and features required.

Windows Server 2008 R2
1.  Open a PowerShell command prompt as an administrator 
2.  Type Import-Module ServerManager and press Enter
3.  Type Add-WindowsFeature Web-Server, Web-Basic-Auth, Web-Windows-Auth, Web-ASP-NET, Web-Net-Ext, AS-Web-Support and press Enter
4.  Reboot if prompted.
          
Windows Server 2012 / Windows Server 2012 R2
1.  Open a PowerShell command prompt as an administrator  
2.  Type Import-Module ServerManager and press Enter
3.  Type Add-WindowsFeature Web-Server, Web-Basic-Auth, Web-Windows-Auth, NET-FRAMEWORK-45-Core, NET-FRAMEWORK-45-ASPNET, Web-HTTP-Logging, Web-NET-Ext45, Web-ASP-Net45 and press Enter
4.  Reboot if prompted.
          
Windows Server 2016
1.  Open a PowerShell command prompt as an administrator 
2.  Type Import-Module ServerManager and press Enter
3.  Type Add-WindowsFeature Web-Server, Web-Mgmt-Console, Web-Scripting-Tools, Web-Basic-Auth, Web-Windows-Auth, NET-FRAMEWORK-45-Core, NET-FRAMEWORK-45-ASPNET, Web-HTTP-Logging, Web-NET-Ext45, Web-ASP-Net45 and press Enter
4.  Reboot if prompted.
          

Installation of Directory Search

Directory Search is simple to install as long as the prerequisites all installed. Download the latest version from our Web site and unzip the DirectorySearch.msi file. Place the MSI file on the server’s local hard drive, such as in the c:\temp folder.

You can usually just double-click on the MSI file to launch the installer, but on Windows Server 2008/2012, the User Account Control security settings may be set so tightly that you have to launch the installer from the command line (don’t forget to “Run As Administrator”) like so:

msiexec.exe /i c:\temp\DirectorySearch.msi
  1. On the installation wizard welcome screen, Click Next

  2. On the License Agreement screen, click “I Agree” and then click Next

  3. On the Select Installation Address, most installations use the defaults. From this screen, you can select a different web site and virtual directory name . When you have made your selection, click Next.

    Directory Search - Installation Address

  4. On the Destination Folder screen, select the location for the Directory Search files (usually c:\inetpub\wwwroot\DirectorySearch\) and click Next

  5. On the Directory Settings screen, enter the host name of the domain controller, then DNS domain name of your Active Directory domain, the service/proxy account (in domain\username format), and the proxy account password. A common configuration problem is entering the FQDN name of the domain controller in the Domain Controller text box; this text box is for the host (short) name of the domain controller. Click the “Test Directory Settings” button and then click Next.

    Directory Search - Specifying domain and service account information

  6. On the Licensing Information Screen, copy and paste the organization name and license key that you were provided after you purchased the software. If you select the Evaluation checkbox, the software is fully functional in Evaluation mode for 10 days and you can run the configuration wizard later to provide the licensing information. Click Next when finished.

    Directory Search - Licensing information

  7. On the Ready To Install Directory Search screen, click the Install button. The installation takes between 15 and 30 seconds. When complete, click the Finish button to exit the installer.

  8. Immediately test the installation by using a Web browser to visit http://localhost/DirectorySearch (the default URL if you are checking from the console of the server) or http://yourservername.yourcorp.local/DirectorySearch (if you are checking from elsewhere on your network.)

You can now proceed to customizing the application.


Installation Checklist

  1. Test the default installation (with no customizations)

  2. Edit the DirectorySettings.XML file to configure the fields that you want to use (visibility, required, dropdown versus text, validation formats, etc…)

  3. Edit the AppSettings.XML file to customize the help text