Service Desk installation guide: IIS

There are two ways you can host Targetprocess Service Desk: using a Docker container, or as an application in IIS. This article describes installation using IIS on Windows servers.

Prerequisites

1. Install .NET Core 2.0 hosting bundle using this link: https://aka.ms/dotnetcore-2-windowshosting
   Important! Before 2018 Service Desk required .Net Core 1.1, so if you had it installed previously, you will need to update .Net Core to 2.0 
2. Restart IIS by running the “cmd” command prompt as an administrator and executing the iisreset command. If the .NET Core hosting bundle was already installed, you do not need this step.

Installation

• Download the latest Service Desk archive here and extract it somewhere on the server. For example, c:\inetpub\wwwroot\ServiceDesk\ There should be write permissions to "logs" and "data" folders for IIS_Users or the user specified in Application Pool settings (usually Network Service)
• Open IIS Management Studio and create a new application pool. Set .Net CLR versions to No Managed Code as shown below.
  
• Now you have two options:
  • Create an application within an existing site. It makes sense if your Targetprocess environment is already installed as virtual directory and can be accessed as http://localhost/Targetprocess . You can do that by right-clicking the folder under your site and using the “Convert to application” option in IIS Management Studio.
  • Create a new Site for Service Desk. You may want to do so if Targetprocess is installed to the root of another web site. Please note that in this case, you will have to manage bindings or use a different port.
    
    
    In both cases you need a newly created Application pool and Physical Path specifying where you extracted the archive. For example: c:\inetpub\wwwroot\ServiceDesk\ (the location of web.config). The authentication type should be just “Anonymous”
• Modify the data\config.json file and set the parameters to connect to Targetprocess:
  "tpUrl" - the path to your Targetprocess environment. For example: "http://localhost/Targetprocess". It has to be entered in the same way as your usual Targetprocess URL, including the http or https part of the link.
  "tpAuthToken" - the token that will be used by Service Desk to access Targetprocess. All actions, such as creating a new request, will appear in Targetprocess as if made by this user. We recommend using a System user in this case. You can get a token for System user by running the following query http://_your_targetprocess_path_/api/v1/authentication?login=System
  (Just be sure to replace _your_targetprocess_ path with the real link to your Targetprocess environment)

  Important: for security reasons, starting from Targetprocess version 3.10.4, you cannot use a System user token if the password was never changed. You can change it at Settings -> System User Credentials under General Settings. For more information, see https://targetprocess.com/guide/settings/users-roles-permissions/system-user/ .

Service Desk Configuration

For additional Service Desk settings (such as Private or Public mode, Custom Fields, company logo, and available projects) please go to the Settings Page after the basic parameters are specified:

Upgrading Service Desk

1. Download the latest version from https://targetprocess.com/downloads
2. Back up the content of “.../data” folder of your original installation (it contains settings and logo)
3. Replace the content of the Service Desk folder with the newly downloaded version
4. Replace the “data” folder with the one from the previous version