Skip to content

Single Server Setup - Single Store

This guide describes steps required for installing zervicepoint on a single-server setup. This setup will use a "standard" setup and use a service account for frontend and one for backend.

Follow this guide from top to bottom, note that there are steps where you should save/remember the output. So be prepared to take some notes. (e.g Appid, secret)


It will not cover deployment and setup of AD, CA, MS SQL Server, ADFS/AzureAD, request/import web certificate or DNS.


Ensure you have the following available.

  • Application server (Where zervicepoint will be installed) is joined to active directory domain.
  • Microsoft SQL Server (SQL Express supported for non-production scenarios)
  • Azure AD Tenant (and permissions to register a new application)
  • DNS
  • Web Certificate


A DNS record should be created that matches the intended hostname for zervicepoint and should point to the server.

Type Name


A web certificate is required and must match the DNS entry for zervicepoint. Wildcard certificates are supported.


Service Accounts

This section explains the purpose of the service account for zervicepoint and as well the required permissions for a single-server/store setup.

Frontend Account

The frontend account runs the application pools for Zervicepoint.

  • User Web
  • Admin Web
  • Process System Web
  • Client Web Service
  • ZP Web Api

Frontend account permissions

Local Administrator or:

Backend Account

The backend account runs the following services for Zervicepoint.

  • ProcessSystem service
  • ProvisioningSystem service
  • ProvisioningSystemInventory service

Backend account permissions

Local Administrator or:

  • Member of the Workflow Manager Admin group (default set to BUILTIN\Administrators group)

Workflow Manager Account

Workflow Manager account that runs the Service Bus / Workflow Manager services.

Workflow Manager account permissions


This account should already be created as Service Bus/Workflow Manager should be installed prior to installing zervicepoint, but often the DB_owner permission will be missing unless the zervicepoint database is pre-created as an empty database.

Create Service Accounts

Create two service account for zervicepoint to run the application pool and services. Make sure you take note which account should be used as frontend or backend.

Import-Module ActiveDirectory
New-ADUser -Name '<username>' -SamAccountName '<username>' -Description "Workflow Manager Service Account" -PasswordNeverExpires:$true -AccountPassword (ConvertTo-SecureString -String "Passw0rd1" -AsPlainText -Force) -Enabled:$true

Service Account Permissions

  • Local Administrator on application server.
  • Assigned to db_owner role on Zervicepoint database.
  • ManageUser on Servicebus Zervicepoint namespace
# On Application Server
Add-LocalGroupMember -Group administrators -Member '<domain>\<backend account>'
Add-LocalGroupMember -Group administrators -Member '<domain>\<frontend account>'

Assign db_owner role on zervicepoint database

As the database is not yet created, you can either choose to pre-create the database and assign the permissions or apply them after the installation.


If permissions are not correctly assigned, zervicepoint will not function correctly and a common first-setup issue are permissions and that orders get stuck.


Update SBNamespace ManageUsers

# This command should be run on the WF/SB server.
Import-Module ServiceBus
Set-SBNamespace -Name Zervicepoint -ManageUsers @('<domain>\<workflow manager account>','<domain>\<backend account>','<domain>\<frontend account>') -Verbose

Install Windows Features

Add-WindowsFeature -Name @(


Depending on whether you will use Azure AD or ADFS for Zervicepoint.


To login with Azure AD we'll need to create a Azure Application in Azure. This can be done in either the azure web portal or by using their command line tools/APIs.

  1. Login to azure portal ( and login with an administrative account that have create a azure application.
  2. > Azure Active Directory > App Registrations


New Azure Application

  1. Click New Registration to create a new azure application.
  2. Enter displayname (i.e zervicepoint).
  3. Enter Redirect URI. This should be matching the hostname of zervicepoint. (i.e
  4. Click register.

RegisterApp RegisterApp

ApplicationId and TenantId

  1. After registration, take note of the Tenant Id and Application Id as you will use them later in this guide.


Update Redirect URIs

  1. Go to the Authentication page of the created application and add an additional Redirect URL.
Type RedirectURI


Update Implicit grant setting

  1. Go to the Authentication page and check the checkbox ID Tokens


Generate Azure App Secret

  1. Go to the Certificates & Secrets page.
  2. Click New client secret.
  3. Choose how long this secret will be enabled and add a description. (i.e 'zervicepoint')


Azure Permissions

  1. Go to the API Permissions page.
  2. Click Add a permission > Select an API (Select Microsoft Graph)
  3. Click Delegated permissions > User.Read.All > Add Permission
  4. Click Add a permission > Select an API (Select Microsoft Graph)
  5. Click Application permissions > Directory.Read.All > Add Permission
  6. Click "Grant admin consent for organization name" in order to allow zervicepoint to read the necessary Azure AD info to login to Zervicepoint.


Update Manifest

Update the following two properties in the manifest.

Property Value
acceptMappedClaims true
groupMemershipClaims All
  1. Click Manifest
  2. Update manifest. Ensure you don't make any typos.
  3. Click save.



Zervicepoint needs the following information from your ADFS environment

  • ADFS hostname (
  • ADFS thumbprint

How to find ADFS thumbprint?

If you plan to use ADFS you will need to create a relying party in your ADFS environment.

ADFS relying party trust

Active Directory Federation Service should run atleast version 2.0 or later

Relying party trust

WS-Federation Passive Endpoint


Required claims (LDAP)

Attribute Claim
SAM-Account-Name Name ID
E-mail-Addresses E-Mail
Display-Name Name
Token-Groups Unqualified names Group

Create ADFS Relying Party Trust using PowerShell


Replace "" with your Zervicepoint hostname

# Must be run on ADFS Server
Import-Module ADFS

$Name = "Zervicepoint"
$Identifier = @(
$IssuanceTransformRule = '@RuleTemplate = "LdapClaims"
    @RuleName = "LDAP"
    c:[Type == "", Issuer =="AD AUTHORITY"]
        => issue(store = "Active Directory", types = ("", "",
        "", "",
        ""), query = ";mail,displayName,sAMAccountName,displayName,tokenGroups;{0}", param = c.Value);'

$WSFedEndpoint = ""
$AdditionalWSFedEndpoint = ""
$AccessControlPolicyName = "Permit everyone"

Add-AdfsRelyingPartyTrust -Name $Name -Identifier $Identifier -IssuanceTransformRules $IssuanceTransformRule -WSFedEndpoint $WSFedEndpoint -AdditionalWSFedEndpoint $AdditionalWSFedEndpoint  -AccessControlPolicyName $AccessControlPolicyName

Start ZervicePointSetup

Download zervicepoint media



Select and install the following features. The setup wizard will provide explanation on the settings to configure.

  • Database
  • Workflow Manager Extensions
  • Administration Web
  • Process system service
  • User Web
  • Provisioning System
  • Process System Web
  • Client Webservice
  • API Web
  • Powershell maintenance module


Enter database settings for zervicepoint.

Authentication Settings

Select Azure or ADFS as Identity provider. depending on your choice earlier.

If you haven't created a Azure application for zervicepoint, check the following links

Register Azure Application for Zervicepoint

Where can I find tenant id

Web site settings

Key Value
Application Pool Account domain\frontendaccount
Website certificate
ServiceBus server If WF/SB is installed on the same server as zervicepoint, use the FQDN of the server.

process system

Key Value
Services account domain\backendaccount
Workflow Manager hostname If WF/SB is installed on the same server as zervicepoint, use the FQDN of the server.
ServiceBus server If WF/SB is installed on the same server as zervicepoint, use the FQDN of the server.

Provisioning and API

Key Value
Store Store
Client webservice hostname
Client webservice port 8443
Services account domain\backendaccount
Worker authentication Key
Credential name ZervicepointProvisioning
API authentication Key

Powershell module

Key Value


Verify permissions

Ensure permissions are set for the service accounts.

Frontend account | Backend account | Workflow manager account


The community module dbatools is great for sql server administration. It can be used to easily validate that the permissions are set.

Find-Module dbatools | Install-Module
Import-Module dbatools
Get-DbaDbRoleMember -SqlInstance localhost\zervicepoint -Database zervicepoint -Role db_owner

Restart ServiceBus and Workflow Manager

If the Service Bus Farm and Workflow Manager is running, ensure that both services are restarted before starting Zervicepoint


It can take a few minutes for the services to stop/start sometimes. You must run with an account that is member of the WF/SB admin group and in a elevated powershell prompt.


Add AzureAppSecret to frontend account

Create a credential called AzureAppSecret as the frontend account. This can either be done via powershell or using "Windows Credentials" tool. The azure app secret is the secret that was created during registration of an app.

start-process powershell -Credential (Get-Credential -UserName "<domain>\<username>" -Message "Enter password for frontend account")
# In the new powershell window running in the context of the frontend account
Import-Module "C:\Program Files\Zipper\ZervicePoint\Powershell\ZervicePoint.WebApi.PowerShell"
Set-ZPKeyCredential -Name "AzureAppSecret" -Key "<azure app secret>"

Run powershell as a different user

Login to zervicepoint

Login to zervicepoint portal.(e.g '')

During the first login to zervicepoint using Azure AD, it may take a minute or so before you're redirected to the Azure login page. If the azure application has not yet been granted consent. You will be prompted to grant it.


The account logging in for the first time should be a global administrator of the azure tenant used as tenant id. You will not be prompted for this again unless the azure application permissions are modified.

Accept permission request

If you've logged in with a global administrator account, you'll see the following prompt.


Common issues

Oops something went wrong

If you login to zervicepoint portal the first time after creating a azure app. If you login with an account that does not have global administrator permissions in the tenant or application administrator. You may see a 'something went wrong' error.


  1. Go to the azure portal > Azure Active Directory > Enterprise applications > search for application using displayname or appid
  2. Go to Permissions page and click 'Grant admin consent for organization'




Configure ProvisioningSystem service

After we've verified that we can logon to the zervicepoint portal, login with the account that has a email address that matches the storeadministrator email used during the install.

Go to admin page > Edit Store > Worker Authentication

  1. Generate a WorkerKey - Save this key as it will be used in a later step
  2. Generate a token signing certificate - use the same certificate for both token and data signing. Save the thumbprint as it will be used in a later step.
  3. Click save.


Update ClientWebService config with generated certificate thumbprint

notepad 'C:\Program Files\Zipper\ZervicePoint\Web\ClientWebService\Web.config'

Update the TokenCertThumbPrint and DataSignCertThumbPrint keys with the generated certificate.

        <add key="TokenCertThumbPrint" value="C30F3A5F15E2BA0630B6BC6638051DA67CECBCF0"/>
        <add key="TokenCertFile" value=""/>
        <add key="DataSignCertThumbPrint" value="C30F3A5F15E2BA0630B6BC6638051DA67CECBCF0"/>
        <add key="TokenAudience" value="whiteowlwebservice"/>
        <add key="providerSettings" value="C:\Program Files\Zipper\ZervicePoint\ClientWebService\providers.xml"/>
        <add key="providerPath" value="C:\Program Files\Zipper\ZervicePoint\Web\ClientWebService\"/>
# Restart the website
Get-Website -Name "ZervicePoint ClientWebService" | Stop-Website
Get-Website -Name "ZervicePoint ClientWebService" | Start-Website

Update ProvisioningKey

start-process powershell -Credential (Get-Credential -UserName "<domain>\<username>" -Message "Enter password for backend account")
# In the new powershell window running in the context of the backend account
Import-Module "C:\Program Files\Zipper\ZervicePoint\Powershell\ZervicePoint.WebApi.PowerShell"
Set-ZPKeyCredential -Name "WorkerKey" -Key "<worker key>"

Create a test activity and data source

You should complete the following in order to create a sample data source and activity that can be found by the inventory.

Restart Provisioning System

Restart-Service ProvisioningSystem,ProvisioningSystemInventory
  • The provider Get-DayOfWeek should now be listed in Admin Page > Providers
  • The data source DropDown.GetDays should now be listed in Admin Page > Data sources

Start Zervicepoint Process System

Now we're ready to start the processsystem service.

Start-Service -Name ProcessSystem


You could start all zervicepoint services, but note that provisioningsystem and provisioningsysteminventory may generate errors as they have not been configured yet in the administration portal.

Create test service

You should create a test service which will use the data source and activity and verify the following.

  • You can receive data from a dynamic dropdown using the DropDown.GetDays activity
  • You can receive todays day from the activity Get-DayOfWeek by adding the activity and a state activity bound to variable DayOfWeek