Microsoft Internet Information Services (IIS)

IIS does not easily support network drive mappings. Conquest III requires full UNC paths to be defined for access to files attached to Conquest Objects and for Icons used in the Standard Objects of the Knowledge Base. This needs to be done before migrating from Conquest II to III.

The following images are from Windows Server 2012 R2 - IIS8.

When creating the Web Server Role for IIS, make sure that it is configured with ASP.NET and with Web Management Services as follows:

Having installed the Web Server Role and configured it, install the Microsoft .NET Framework:

      Microsoft .NET Framework version 4.5.1 or later
Note: Conquest III versions earlier than 3.0300 will run on 4.0 (Client and Extended) or later

      If the Windows IIS Role is configured after the .NET Framework is installed, you must register .NET by running “aspnet_regiis.exe -iru”. This is an undocumented tool provided by Microsoft for exactly this situation and is located in:

      32 bit machines - C:\Windows\Microsoft.NET\Framework\v4.0.30319

      64 bit machines - C:\Windows\Microsoft.NET\Framework64\v4.0.30319

      The Conquest III Application Pool is preset to use ADO.Net 4.0 Integrated mode

      The Conquest III Application Pool uses a Specific Time to Recycle, which frees up resources. It is recommended that the Recycling Interval is set to a Specific Time outside of normal office hours

Note: Conquest III on the Web Server relies on a single UNC path definition for the location of general files attached to Conquest Objects such as Assets and Defects. However, Conquest II allowed multiple locations, although this is not recommended. In the event that such documents are stored in multiple locations, they will need to be consolidated to the Documents Folder location and their path information in the Conquest database updated accordingly.