To install the Knowledge Center server, you must have administrator privileges to the computer on which you are installing it, or at least have necessary permissions to install software.

 

Before you install the Knowledge Center, you will need the following information. 


Setup Requirements for the Server

The server setup requires the IIS Admin and WorldWide Web Publishing services to be running. If they are not running, the setup program will attempt to start them; if they cannot be started, the installation will be aborted. An optional service used by Knowledge Center is the Indexing service for search. If it is not running, the setup program will prompt you and attempt to start it; if it cannot be started, installation will continue, but search may not work properly.

 

Before installing the server application files, the installer checks for IIS and Microsoft .NET Framework 3.5 SP1. If IIS is not installed, you will not be able to install the server application files. If the .NET framework is not installed or if the installer cannot determine whether it is installed, an informational message will be displayed. If you choose to continue, .NET 3.5 SP1 will automatically be installed; if you choose not to continue, the installation will be aborted.


Authentication Methods

The Knowledge Center can authenticate users in one of two different security modes:

Note: Changing security authentication methods after installation will result in technical issues.

 

Secure Web Site and SSL

If a secure web site is available, the installer defaults to that web site. While you can also install on a non-secure web site, using a secure web site and SSL is the recommended method of deployment for the web services, because SSL:

Change Protocols after Installation

You can install the Knowledge Center server on either a secure (SSL) or unsecure (non-SSL) server. If necessary, you can change the protocol after installation; for example, if you attach a certificate to web site, you can change the protocol for the Knowledge Center server.

 

To convert the Knowledge Center server from non-SSL to SSL:

  1. Install and run the Knowledge Center server on a non-SSL web site.
     
  2. Apply the certificate and HTTPS bindings to the web site on which the Knowledge Center server is installed.
     
  3. Log in to Knowledge Center as an administrative user under the HTTP binding.
     
  4. Click the Manager link.
     
  5. In Manager, point to the More option and choose Server.
     
  6. Change the value in the Server URL field to the URL of the web site to which the certificate has been applied.
     
  7. Click Save to save your changes.
     
  8. Point to the More option and choose Content Roots.
     
  9. From the list of content roots, click Edit for a content root on the affected web site.
     
  10. Change the value in the URL (http) field to the URL of the web site to which the certificate has been applied.
     
  11. Save the changes.
     
  12. Click the Back to List link.
     
  13. Repeat steps 9 - 12 for each affected content root.
     
  14. Log out of Knowledge Center.
     
  15. Navigate to the installation location and open the \Web Server\KCenter\web.config file in the editor of your choice.
     
  16. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "KPDATAURL".
     
  17. Change the value to the URL of the web site to which the certificate has been applied.
     
  18. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding where the "name" attribute is "BasicHttpBinding_GenericInformationWebServiceWCF".
     
  19. Locate the "security" key located within the key and change the "mode" attribute from "TransportCredentialOnly" to "Transport".
     
  20. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding where the "name" attribute is "BasicHttpBinding_SearchIndexServiceWCF".
     
  21. Locate the "security" key located within the key and change the "mode" attribute from "None" to "Transport".
     
  22. Save the changes and close the file.
     
  23. Navigate to the installation location and open the \Web Server\KData\web.config file in the editor of your choice.
     
  24. Locate the XML value for the node configuration/appSettings/add. There should be a list of the "add" keys.
     
  25. Add a new "add" node for a "key" attribute "K_SSL" with a "value" attribute "true", for example: <add key="K_SSL" value="true" />.
     
  26. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding. There should only be one "name" attribute.
     
  27. Locate the "security" key located within the key and change the "mode" attribute from "TransportCredentialOnly" to "Transport".
     
  28. Save the changes and close the file.

Note: If the content roots reside on the affected web site, continue with the following steps. If not, stop here.

  1. Navigate to the installation location of the content root and open the web.config file.
     
  2. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "KPDATAURL".
     
  3. Change that value to the URL of the web site to which the certificate has been applied.
     
  4. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "KPEndUser".
     
  5. Change that value to the URL of the web site to which the certificate has been applied.
     
  6. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding where the "name" attribute is "BasicHttpBinding_GenericInformationWebServiceWCF".
     
  7. Locate the "security" key located within the key and change the "mode" attribute from "TransportCredentialOnly" to "Transport".
     
  8. Save the changes and close the file.
     
  9. In the content root installation location, open the \ContentTools\web.config file.
     
  10. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "KPDATAURL".
      
  11. Change that value to the URL of the web site to which the certificate has been applied.
     
  12. Locate the XML value for the node configuration/appSettings/add. There should be a list of these "add" keys.
     
  13. Add a new "add" node for a "key" attribute "K_SSL" with a "value" attribute "true", for example: <add key="K_SSL" value="true" />.
     
  14. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding. There should only be one "name" attribute.
     
  15. Locate the "security" key located within the key and change the "mode" attribute from "TransportCredentialOnly" to "Transport".
     
  16. Save the changes and close the file.
     
  17. Repeat these steps for each affected content root
     
  18. Log in to Knowledge Center using the HTTPS binding and verify it works.

To convert the Knowledge Center server from SSL to non-SSL:

  1. Install and run the Knowledge Center server on an SSL web site.
      
  2. Log in to Knowledge Center as an administrative user under the HTTPS binding.
     
  3. Click the Manager link.
     
  4. In Manager, point to the More option and choose Server.
     
  5. Change the value in the Server URL field to the URL of the web site from which the certificate will be removed.
     
  6. Click Save to save your changes.
     
  7. Point to the More option and choose Content Roots.
     
  8. From the list of content roots, click Edit for a content root on the affected web site.
     
  9. Change the value in the URL (http) field to the URL of the web site from which the certificate will be removed.
     
  10. Save the changes.
     
  11. Click the Back to List link.
     
  12. Repeat steps 7 - 11 for each affected content root.
     
  13. Log out of Knowledge Center.
     
  14. Navigate to the installation location and open the \Web Server\KCenter\web.config file in the editor of your choice.
     
  15. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "KPDATAURL".
     
  16. Change the value to the URL of the web site from which the certificate will be removed.
     
  17. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding where the "name" attribute is "BasicHttpBinding_GenericInformationWebServiceWCF".
     
  18. Locate the “security” key located within the key and change the "mode" attribute from "Transport" to "TransportCredentialOnly".
     
  19. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding where the "name" attribute is "BasicHttpBinding_SearchIndexServiceWCF".
     
  20. Locate the "security" key located within the key and change the "mode" attribute from "Transport" to "None".
     
  21. Save the changes and close the file.
     
  22. Navigate to the installation location and open the \Web Server\KData\web.config file in the editor of your choice.
     
  23. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "K_SSL" and delete this key. Be careful not to delete the closing tag "</appSettings>", as it may be on the same line.
     
  24. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding. There should only be one "name" attribute.
     
  25. Locate the "security" key located within the key and change the "mode" attribute from "Transport" to "TransportCredentialOnly".
     
  26. Save the changes and close the file.

Note: If the content roots reside on the affected web site, continue with the following steps. Otherwise, skip to step 17.

  1. Navigate to the installation location of the content root and open the web.config file.
     
  2. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "KPDATAURL".
     
  3. Change that value to the URL of the web site from which the certificate will be removed.
     
  4. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "KPEndUser".
     
  5. Change that value to the URL of the web site from which the certificate will be removed.
     
  6. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding where the "name" attribute is "BasicHttpBinding_GenericInformationWebServiceWCF".
     
  7. Locate the "security" key located within the key and change the "mode" attribute from "Transport" to "TransportCredentialOnly".
     
  8. Save the changes and close the file.
     
  9. In the content root installation location, open the \ContentTools\web.config file.
     
  10. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "KPDATAURL".
      
  11. Change that value to the URL of the web site from which the certificate will be removed.
     
  12. Locate the XML value for the node configuration/appSettings/add where the "key" attribute is "K_SSL" and delete this key. Be careful not to delete the closing tag "</appSettings>", as it may be on the same line.
       
  13. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding. There should only be one "name" attribute.
     
  14. Locate the "security" key located within the key and change the "mode" attribute from "Transport" to "TransportCredentialOnly".
     
  15. Save the changes and close the file.
     
  16. Repeat these steps for each affected content root.
     
  17. Remove the certificate and HTTPS bindings from the web site.
     
  18. Ensure the HTTP binding is allowed on the web site where you removed the certificate.
     
  19. Log in to Knowledge Center using the HTTP binding and verify it works.

Content Root Folder
The Content Root is where user content is stored. The ContentTools folder of the Content Root does all the work for Knowledge Center content. It needs to copy files and folders, so it needs to be accessed by a Windows user with the necessary privileges to perform these tasks. This user can be created by the installer, or can be an existing user on the system.


Folder Permissions

The installer will check the folders listed below for the following permissions, and apply permissions where necessary.

  • C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319
       
    Windows Authentication
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    Standard Authentication
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
     
  • C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files
     
    Windows Authentication
    <ContentTools User> - Read & Execute, Write
     
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    Standard Authentication
    <ContentTools User> - Read & Execute, Write
     
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
     
  • C:\WINDOWS\Temp (Special permissions)
     
    Windows Authentication
    <ContentTools User> - Modify
     
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    Standard Authentication
     
    <ContentTools User> - Modify
     
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
     
  • Install Directory (C:\Program Files...\KData and C:\Program Files...\KCenter) or any local drive (D:\...\KData and D:\...\KCenter)
     
    Windows Authentication
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    Standard Authentication
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
     
  • <Oracle folder>
     
    Windows Authentication
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    Standard Authentication
    ASPNET (Windows XP only) or NETWORK SERVICE (all other operating systems) - Read & Execute, List Folder Contents, Read
     
    IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute, List Folder Contents, Read
     
  • <Content Root> Directory
     
    Windows Authentication
    <ContentTools User> - Read, Write, List Folder Contents, Modify
     
    Standard Authentication
    <ContentTools User> - Read, Write, List Folder Contents, Modify
     
    IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute Only
     
  • <Content Root>\ContentTools
     
    Windows Authentication
    ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute Only
     
    Standard Authentication
    ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute Only
     
    IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute Only
     
  • <Content Root>\Tools
     
    Windows Authentication
    <ContentTools User> - Read & Execute Only
     
    ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute Only
     
    Standard Authentication
    <ContentTools User> - Read & Execute Only
     
    ASPNET (Windows XP Only) or NETWORK SERVICE (All other OS) - Read & Execute Only
     
    IUSR_<machinename> (Windows XP or Windows 2003) or IUSR (Windows Vista, Windows 2008 or Windows 7 only) or IIS Anonymous Account - Read & Execute Only
     
  • <Content Root>\bin
     
    Windows Authentication
    <ContentTools User> - Read & Execute Only
     
    Standard Authentication
    <ContentTools User> - Read & Execute Only
     
  • <Content Root>\web.config
     
    Windows Authentication
    <ContentTools User> - Read & Execute Only
     
    Standard Authentication
    <ContentTools User> - Read & Execute Only

Database Access

If you choose to install the database at the same time as you install the application files on the server, you will be prompted for two sets of credentials for the database. The first set is for an account that the installer can use to create the database. You must use an existing account for this set of credentials, and the account must have permissions to create databases and logins.


Note: A Microsoft SQL database server must be configured with mixed mode authentication.


The second set of credentials is used for the Web Services access for the Developer to read from and write to the database. This can be a pre-existing login, for which you must supply the correct login name and password, or you can specify a new login name and password. The installer grants this account access to the database and adds it to the appropriate roles.


To install the server with an Oracle database, launch the Setup.exe file located in the root folder in the software installation files. If a Security Warning appears, click Run. You are then prompted to choose the language for the Installer, and the Install Wizard appears. During installation, you will proceed through these screens in the Install Wizard.

  • License Key: Depending on the product you are installing, this screen may appear. If it does, click Browse to navigate to the location of the license key file (usually license.xml).
     
  • Welcome: From this screen, you can access the Installation and Upgrade manuals in Adobe Acrobat format.
     
  • Setup Type: From the Configuration list, select Knowledge Center.
     
  • Setup Requirements: Specific services are required for installation. If the services are not running, this screen appears notifying you which services are needed. You can choose to start or enable the services and continue. Depending on the service, the installation may be aborted if it is not started.
      
    Professional Edition only: The Indexing service is optional for the Professional Edition of Knowledge Center; however, if it is not installed and started, the Search functionality will not function properly. During the installation of Professional Edition, the installer will detect the state of the Indexing service. If the service is installed but stopped, the installer presents you with the option to start it. If the service is not installed or disabled, and you want Search to function properly, you must manually install or enable the service before proceeding with the installation.
     
  • Choose Destination Location: You can accept the default target location, or click Change to specify a different one.
     
  • Usage Tracking Installation: Select the No, this is a new installation option.
     
  • Choose Web Site: The Available websites list contains the list of all web sites available to the user, allowing you to choose the most appropriate one. Preference is given to secure web sites. In the Application (virtual directory) name box, you can enter the name you want to use for the virtual directory, or accept the default. You also select the mode to use to authenticate the users, either Windows or Standard. Later, when you supply the credentials for the initial Profile, you must choose the same authentication mode.
     
    Note: The web server and the database server must be in the same local network.
     
  • Web Site Options: This screen appears if there is no secure web site available or if you did not select a secure web site on the Choose Web Site screen. It allows you to ignore the recommendation and continue with the installation, or create a secure web site manually and retry the installation.
     
  • Database System: Choose Oracle Database.
     
  • Oracle .NET Data Provider: A specific version of the Oracle .NET Data Provider must be installed for the Developer to work correctly. This screen appears if the correct version is not present. In the Path field, enter the physical location to which you want to install the software. In the Name field, enter the name of the Oracle Home.
     
  • SQL Script Options: If you have already run the scripts to create the database, click the Yes, the scripts have already been run for this version option. If you want the installer to create the database, click the No, the scripts have not been run, let the installer run them option.
     
  • Internet Information Services Option: During installation, the Internet Information Services will need to be stopped and restarted. You can choose to continue with the installation or cancel it and install at a later time.
     
  • Oracle Database Login: If the scripts have not been run, enter a valid system account name, password, and host string to connect to the Oracle Database server. This account must have permissions to create the schema and the tablespace. If the scripts have already been run to create the database, enter a user name, password and host string that has access to the user schema created to run the application. If the scripts have already been run, the Profile Credentials screen appears next.
     
    Note: Host String represents the name you assign for TNS connectivity in the tnsnames.ora file. This typically identifies the machine, port number and SID of the Oracle database. If you need to connect to a remote Oracle database you will need to supply the host:port/service_name; for example, "myservername:1521/orcl". In some environments a tnsname.ora might not be present. If you are not sure, it is highly recommended that you supply the host/service_name or host:port/service_name (if remote).
     
  • Choose Schema: Specify a tablespace name, user name, and password and confirm the password. The user name is limited to 20 characters. The tablespace name is the name of the tablespace that will be created or used during the installation; the user name is the user name that will be created or associated with the schema.
     
  • Content Root Information: The content root name is the name of the virtual directory to be created for the content root. The content root location is the actual location (path and folder name) for the content root. You can also choose to use anonymous tracking, which means that all usage and tracking information is gathered under an anonymous name. Individual users scores and tracking data will not be available.
     
  • Application Pool User: The ContentTools folder within the content root performs all the processing activities for Knowledge Center content. It needs to copy files and folders, so it needs to be accessed by a user with the necessary privileges to perform these tasks. The virtual directory for the ContentTools needs to be assigned to an application pool that runs under the identity of this user.
     
    If the ContentTools application pool has already been created (usually by the Knowledge Center installation), the application pool identity will already be set. If not, a user account to be used as this application pool identity must be created or selected. If you create a new Windows account user, enter the user name and a password. If you use an existing account, specify the user name, including the domain, and the existing password for the account.
     
  • Profile Credentials: If you chose to install the server with standard authentication, enter a user name and password for the default administrator user, and confirm the password. If you chose to install with Microsoft Windows authentication, allow the system to use the current Microsoft Windows account or specify another valid Microsoft Windows user account and password. You must also enter a first and last name for the profile. The Middle initial and E-mail address are optional.
     
  • Folder permission: The Knowledge Center needs certain permissions to complete the installation. If the installer detects any missing permission(s) it displays this screen, which lists the name of the folder, the user name, and the permission it needs before the installer can continue. If you are installing a Content root to the same server as the Knowledge Center, the permission must be applied to the specific folders for the Content root as well. The user account needed is used by the Content root Application Pool in IIS.
     
    Click Yes, grant permission to the folders to automatically grant the permissions to the folders. If the permissions cannot be applied, this screen reappears. This option is highly recommended. Click No, ignore permission and attempt to continue installation to ignore the permission check and try to continue the installation. If the permissions are not set properly, the installation may fail. Use this option if you know that the permissions are already applied. Click Retry to recheck the folders without applying any permissions. The permissions must be applied manually.
     
  • Ready to Install: The Installation Wizard is ready to install the software. Click Back to review or modify any settings.
     
  • Setup Status: This screen appears while the files are being installed, the schema and virtual directory are being created, and IIS is being configured.
     
  • Installshield Wizard Complete: During the installation a file might be in use by the operating system on the computer; this will require a reboot to complete the installation. Also, make sure to run Windows update to get the latest patches from Microsoft.

To install the server with a Microsoft SQL database, launch the Setup.exe file located in the root folder in the software installation files. If a Security Warning appears, click Run. You are then prompted to choose the language for the Installer, and the Install Wizard appears. During installation, you will proceed through these screens in the Install Wizard.

  • License Key: Depending on the product you are installing, this screen may appear. If it does, click Browse to navigate to the location of the license key file (usually license.xml).
     
  • Welcome: From this screen, you can access the Installation and Upgrade manuals in Adobe Acrobat format.
     
  • Setup Type: From the Configuration list, select Knowledge Center.
       
  • Setup Requirements: Specific services are required for installation. If the services are not running, this screen appears notifying you which services are needed. You can choose to start or enable the services and continue. Depending on the service, the installation may be aborted if it is not started.
      
    Professional Edition only: The Indexing service is optional for the Professional Edition of Knowledge Center; however, if it is not installed and started, the Search functionality will not function properly. During the installation of Professional Edition, the installer will detect the state of the Indexing service. If the service is installed but stopped, the installer presents you with the option to start it. If the service is not installed or disabled, and you want Search to function properly, you must manually install or enable the service before proceeding with the installation.
     
  • Choose Destination Location: You can accept the default target location, or click Change to specify a different one.
     
  • Usage Tracking Installation: Select the No, this is a new installation option.
     
  • Choose Web Site: The Available websites list contains the list of all web sites available to the user, allowing you to choose the most appropriate one. Preference is given to secure web sites. In the Application (virtual directory) name box, you can enter the name you want to use for the virtual directory, or accept the default. You also select the mode to use to authenticate the users, either Windows or Standard. Later, when you supply the credentials for the initial Profile, you must choose the same authentication mode.
     
    Note: The web server and the database server must be in the same local network.
     
  • Web Site Options: This screen appears if there is no secure web site available or if you did not select a secure web site on the Choose Web Site screen. It allows you to ignore the recommendation and continue with the installation, or create a secure web site manually and retry the installation.
     
  • Database System: Choose Microsoft SQL Server.
     
  • SQL Script Options: If you have already run the scripts to create the database, click the Yes, the scripts have already been run for this version option. If you want the installer to create the database, click the No, the scripts have not been run, let the installer run them option.
     
  • Internet Information Services Option: During installation, the Internet Information Services will need to be stopped and restarted. You can choose to continue with the installation or cancel it and install at a later time.
     
  • Microsoft SQL Server Login: From the Database server list, select the desired Microsoft SQL server. If the scripts have not been run, select Windows Authentication or SQL Server Authentication to connect to the database. If you select Microsoft SQL Server authentication, enter an existing login name and password that has database administrator access to the server.
     
  • Choose Database: Accept the default name for the database or enter a custom name. If you have already run the scripts, you must use the name of the database you created. Specify an existing database user ID and password and confirm the password, if necessary, or, if you have not run the scripts, you can also specify a new database user ID and password. The installer will create the login, if necessary, grant the login access to the database, and give it the appropriate permissions. If you ran the scripts to create the database, you must use the login you created.
     
  • Content Root Information: The content root name is the name of the virtual directory to be created for the content root. The content root location is the actual location (path and folder name) for the content root. You can also choose to use anonymous tracking, which means that all usage and tracking information is gathered under an anonymous name. Individual users scores and tracking data will not be available.
     
  • Application Pool User: The ContentTools folder within the content Root performs all the processing activities for Knowledge Center content. It needs to copy files and folders, so it needs to be accessed by a user with the necessary privileges to perform these tasks. The virtual directory for the ContentTools needs to be assigned to an application pool that runs under the identity of this user.
     
    If the ContentTools application pool has already been created (usually by the Knowledge Center installation), the application pool identity will already be set. If not, a user account to be used as this application pool identity must be created or selected. If you create a new Windows account user, enter the user name and a password. If you use an existing account, specify the user name, including the domain, and the existing password for the account.
     
  • Profile Credentials: If you chose to install the server with standard authentication, enter a user name and password for the default administrator user, and confirm the password. If you chose to install with Microsoft Windows authentication, allow the system to use the current Microsoft Windows account or specify another valid Microsoft Windows user account and password.
     
  • Folder permission: The Knowledge Center needs certain permissions to complete the installation. If the installer detects any missing permission(s) it displays this screen, which lists the name of the folder, the user name, and the permission it needs before the installer can continue. If you are installing a content root to the same server as the Knowledge Center, the permission must be applied to the specific folders for the content root as well. The user account needed is used by the content root application pool in IIS.
     
    Click Yes, grant permission to the folders to automatically grant the permissions to the folders. If the permissions cannot be applied, this screen reappears. This option is highly recommended. Click No, ignore permission and attempt to continue installation to ignore the permission check and try to continue the installation. If the permissions are not set properly, the installation may fail. Use this option if you know that the permissions are already applied. Click Retry to recheck the folders without applying any permissions. The permissions must be applied manually.
     
  • Ready to Install: The Installation Wizard is ready to install the software. Click Back to review or modify any settings.
     
  • Setup Status: This screen appears while the files are being installed, the database and virtual directory are being created, and IIS is being configured.
     
  • Installshield Wizard Complete: During the installation a file might be in use by the operating system on the computer; this will require a reboot to complete the installation. Also, make sure to run Windows update to get the latest patches from Microsoft.

Table of Contents