Installing FIM Portal and Service with a load balanced name

As a follow up to my previous post, How to setup a load balanced FIM Portal and service deployment, I wanted to walk through the configuration with an example. I’ll follow the steps of the previous post using the server names of a set of VMs.

Lab background

My lab is made up of three Windows Server 2008 R2 Servers (Virtual Machines):

Fully qualified domain name Lab roles/functions AD DS Domain Controller (
Exchange Server 2010 (basic setup, all common roles)
Enterprise Root CA (Certificate Services role, default setup) SQL Server 2008 R2 Enterprise
SQL Server 2008 R2 Cumulative Update #7 Windows SharePoint Services 3.0 x64 with SP2
FIM Synchronization Service (build 4.0.2592.0 –RTM)
FIM Service & Portal (build 4.0.2592.0 –RTM)
FIM Synchronization Service (build 4.0.3576.2 –latest CU)
FIM Service & Portal (build 4.0.3576.2 –latest CU)

FIM will be installed on TSAPP01 using the hostname IDWEB. Access will be via HTTPS, e.g. https://idweb/identitymanagement however under the covers the real portal name (from a Kerberos perspective) will be Note that I’ve dropped the CORP domain. I usually setup my lab environments with a child domain (from a DNS namespace perspective) and always utilise the “real” domain for intranet services. I like to think that adds a touch of realism to the environment.

Service accounts

The following service accounts have been created (I’m only focussing on the Service & Portal and WSS in this post, so I’ll omit everything not used in the installation).

Display Name Account Name
FIM Service & Portal Account CORP\svcfimsys
FIM Synchronization Service Account CORP\svcfimsync
WSS – IDWEB – Web Application Account CORP\svcwssidweb

Note. CORP\svcfimsys has an Exchange mailbox and an e-mail address of

Service Principal Names

We’ll register two SPNs for the FIM Service and two for SharePoint. We register the unqualified name and a fully qualified name. Note that the fully qualified name is not the true FQDN of the AD DS domain but rather is the DNS name, which omits the CORP domain.

From an elevated command prompt on any of the servers, the following commands are used.

setspn -s HTTP/idweb CORP\svcwssfimidweb 
setspn -s HTTP/idweb CORP\ 
setspn -s FIMService/idweb CORP\svcfimsys 
setspn -s FIMService/ CORP\ 

The -S switch registers the SPN if there isn’t a duplicate in the domain. You can make the uniqueness verification forest wide by including the -F switch.

Verification is achieved using the -L switch. The following is the output from running setspn -l CORP\svcfimsys & setspn -l CORP\svcfimwsssvc.

C:\>setspn -l CORP\svcfimsys & setspn -l CORP\svcfimwsssvc 
Registered ServicePrincipalNames for CN=FIM Service & Portal,OU=forefront-identi 
Registered ServicePrincipalNames for CN=FIM WSS Portal Account,OU=forefront-iden 

As stated earlier I’m not using the actual AD DS DNS name in either command. This is worth pointing out because the important part of Kerberos authentication is that the client “builds” the same SPN that is actually used by the server. With Internet explorer the SPN that it looks for is derived from the FQDN within the URL. What I do is implement a CNAME of IDWEB in the DNS domain. This CNAME points to Internet Explorer therefore constructs an SPN of HTTP/

Interestingly I utilise Alternate Access Mapping (AAM) within SharePoint so that the FQDN is hidden from the user, leaving a shorter and cleaner URL of https://idweb/identitymanagement.

Kerberos Constrained Delegation

Once the SPNs have been registered two delegations are required:

  1. The FIM Service & Portal account needs to be able to delegate credentials to itself. Or, specifically, the Portal needs to delegate credentials to the service.
  2. The SharePoint web application account needs to be able to delegate credentials to the FIM Service & Portal account.

The following figures illustrate the Delegation tab of both the SVCFIMWSSSVC and SVCFIMSYS service accounts. To expose the delegation tab you must have enabled “advanced view” (View | Advanced Features) in Active Directory Users & Computers (ADUC) and, the account in question must have an SPN.

Internet Information Services (IIS) configuration

The web site used by the default SharePoint web application must be configured to use the credentials of the application pool if we’re not turning off Kernel Mode authentication (a security feature that improves performance). On the SharePoint (FIM Service & Portal) server, tsapp01 in our case, we open an elevated NOTEPAD and then open the file %systemroot%\system32\inetsrv\config\applicationHost.config. We use “Find” (Ctrl + F) to locate location path=”SharePoint – 80. And then we modify <windowsAuthentication enabled=”true”> to become: <windowsAuthentication enabled=”true” useKernelMode=”true” useAppPoolCredentials=”true”>. Figure #3 shows a screenshot.

Underneath the <handlers> node is <security><authentication><windowsAuthentication>.

After making the described change save the file. Next we set the service account for the SharePoint web application.

Windows SharePoint Services (WSS) configuration

There are two configuration changes required within SharePoint Central Administration: the service account and the alternate access mappings.

Service Account

To change the service account open central administration and navigate to Operations| Security Configuration | Service Accounts. Select Windows SharePoint Services Web Application as the web service and SharePoint – 80 as the application pool. Enter the username and password and click OK.

Click OK when prompted with this dialog.

At this point the configuration is done. After an IISRESET everything will work, however before we do that we’re going to configure the alternate access mappings.

Alternate Access Mappings

Within the central administration tool we navigate to Operations | Global Configuration | Alternate access mappings. In the top right we select SharePoint – 80 from the Alternate Access Mapping Collection. Next we click Edit Public URLs and change the default to http://idweb or https://idweb (depending on whether or not you want to use HTTPS, in my case I’m using HTTPS) and click Save.

Next we click Add Internal URL and then enter an URL that can be used to access the site. We repeat this process for each name. In our case we add the following additional names:

The following screenshot (figure #7) depicts my configuration which defines both HTTP and HTTPS.

At this point it’s time to bounce IIS. From an elevated command prompt type IISRESET.

Wrap up

After the IISRESET all that’s left to do is install FIM Service & Portal. When installing FIM the public facing name is IDWEB, usually entered in lowercase.

You then access FIM using either https://idweb/identitymanagement or

If everything has been done correctly FIM will load as expected.

Going back to what I said in the beginning re. using non-standard names, because I use a CNAME that resolves to and I configured FIM with the unqualified name of idweb I’ll get a Kerberos service ticket for HTTP/ and FIMService/idweb, as depicted below (figure #9).

The above screenshot is a non-elevated command prompt. I’ve simply executed KLIST without any arguments, which is the same as running KLIST TICKETS. I stress the fact that I’m using a non-elevated shell here. The set of tickets is different in your elevated shell as EXPLORER is not running under elevated credentials.

Appendix: Certificates

You might notice that I happily interchange between https://idweb and Work is needed to block HTTP or redirect HTTP to HTTPS and encourage one name over the other, however the other important aspect that I’d like to point out is that there is no certificate error using either the unqualified or qualified name. The reason for this is SAN: Subject Alternate Name. I build my certificate request with a common name of CN=idweb. What I use here is irrelevant really as Windows ignores the CN when a SAN is specified. For completeness I specify three DNS SANs: idweb, and

Here’s a couple of screenshots of my enrolment wizard.

I select Web Server and click More information is required to enrol for this certificate. Click here to configure settings.

I enter the CN of the unqualified hostname into the Subject name field. I also add the unqualified hostname, as well as the fully qualified hostname of the AD DNS domain and the DNS domain-name into the Alternative name field, using a Type of DNS. Remember SChannel.dll ignores the CN when there’s a SAN so you have to make sure all names are in the SAN even if you have the name as the CN.

I provide a Friendly name and Description (these are optional but helpful) and click OK. The remainder of the defaults are fine for my purpose.

I then click Enroll.

Then Finish and I’m done. Here’s the certificate.

Now I create a binding on the IIS web site to use this certificate.


About Paul Williams

IT consultant working for Microsoft specialising in Identity Management and Directory Services.
This entry was posted in FIM, SharePoint and tagged , , , , , , , , , , , . Bookmark the permalink.

10 Responses to Installing FIM Portal and Service with a load balanced name

  1. Janae Gramc says:

    This is certainly a wonderful write-up. Many thanks for taking the time to summarize this all out for all of us. It really is a great guide!

  2. fimpassion says:

    Firstly, you explain very well, I tried what you said.
    I installed WSS as you discribe with adminfim (a domain account which is local admin too and therefore it is a sharePoint Site Collection administrator), I had my SharePoint Home page which displayed well (I logged me into the site thanks to adminfim), I continued the process, but before “Wrap Up”, I tried to access to my SharePoint Home page with always the same account, and I have the following error :
    Not Authorized
    HTTP Error 401. The requested resource requires user authentication.

    I don’t understand why.
    Do you have any idea ?

  3. fimpassion says:

    I have no longer the problem, but I have another whchi is the IE says to me that “Internet Explorer cannot display the webpage” when I try to reach http://fimweb (your idweb).
    Do you have any idea ?
    Thanks in advance.

  4. Hello fimpassion.

    We need to try two things to see where we’re at:
    1. Ensure that the WSS site collection root is accessible via Kerberos AuthN.
    2. Ensure /identitymanagement is available via NTLM.

    To ascertain whether or not Kerberos is working please take the following steps:
    1. Open a non-elevated command prompt.
    2. Execute “klist purge” without the quotes.
    3. Lock the machine (WinKey + L)
    4. Unlock the machine and load http://fimweb
    5. In the CMD window type “klist” without the quotes. Is there a service ticket for either HTTP/fimweb or HTTP/fimweb.domain-name.tld? Look at my screenshot in the wrap up section to compare.

    If there is a service ticket listed Keberos is working. If there isn’t, then Kerberos isn’t working and you’re using NTLM.

    To be sure the FIM portal is installed and working attempt to access it using localhost, i.e. http://localhost/identitymanagement (assuming you’re on the box) or the IP address, e.g.

    If Kerberos is working for the site collection, bounce IIS via an IISRESET from an elevated command prompt and re-check that you have both delegations in place. The WSS service account must delegate to FIMService/fimweb and the FIM Service account must also delegate to FIMService/fimweb.

    Also, please be aware that the FIM forum might be a better resource for troubleshooting this issue. Not because I don’t want to help or can’t help, but because it will inevitably be faster as I’m only able to check these comments and respond, if appropriate, in the evenings.

  5. fimpassion says:

    thank you for your quick answer. However, this morning, when I restarted my VMs, all worked fine. Perhaps, it needs to restart the server before the “Wrap up” section ?. For the future, I will folllow your advice.
    Again thank you and congratulations for your explanations

    • I have also encountered the race condition you mention. I’ve not looked into it properly, but there’s certainly a benefit in bouncing IIS right at the end and then going and making a coffee before coming back and testing everything. 🙂

      Anyway, I’m glad it’s all working and that the post was helpful. Thanks for following up.

  6. Pingback: How to setup a load balanced FIM Portal and service deployment | Yet another identity management blog

  7. Pingback: FIM Service Principal Names and Kerberos Delegation | Yet another identity management blog

  8. Hemant says:

    Thanks a lot for this detailed article.

  9. Pingback: How to configure (Hardware) Load Balancer for Microsoft Forefront Identity Manager | IDArchitect.NET

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s