To resolve an issue for a client recently, I needed to connect into the TMG 2010 AD LDS instance manually to remove a duplicate Local Domain Table entry that was causing errors when viewing the LDT in the GUI, and also when exporting the configuration. The error was:
Forefront TMG cannot load the property page.
Error: 0xc004032a
The string is not valid Local Domain Table (LDT) domain name.
The error occurred on object ‘Internal’ of class ‘Network’ in the scope of array ‘Gateway’.
This issue is nothing new, but it did bite me when setting up a FIM 2010 RC1 portal under a custom URL, so I thought I would share. When accessing the FIM portal from another server or workstation, integrated authentication worked fine, but when accessing it from the FIM server itself, you were prompted for authentication 3 times, and then ultimately denied. With security auditing enabled, a logon failure was shown in the Event Log (see below). From there, I came across this blog post which discusses an IIS change introduced in Server 2003 SP2 (aka the IIS loopback issue). That post also mentions this KB article, which works for Server 2008 even if it doesn’t say so.
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 1/11/2010 12:17:00 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: computer.domain.loc
Description:
An account failed to log on.Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: username
Account Domain: domainFailure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc000006d
Sub Status: 0x0Process Information:
Caller Process ID: 0x0
Caller Process Name: -Network Information:
Workstation Name: COMPUTER
Source Network Address: 192.168.1.1
Source Port: 63846Detailed Authentication Information:
Logon Process:
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-a5ba-3e3b0328c30d}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2010-01-11T17:17:00.019Z" />
<EventRecordID>72842</EventRecordID>
<Correlation />
<Execution ProcessID="680" ThreadID="772" />
<Channel>Security</Channel>
<Computer>computer.domain.loc</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-0-0</Data>
<Data Name="SubjectUserName">-</Data>
<Data Name="SubjectDomainName">-</Data>
<Data Name="SubjectLogonId">0x0</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">username</Data>
<Data Name="TargetDomainName">domain</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2304</Data>
<Data Name="SubStatus">0x0</Data>
<Data Name="LogonType">3</Data>
<Data Name="LogonProcessName">
</Data>
<Data Name="AuthenticationPackageName">NTLM</Data>
<Data Name="WorkstationName">computer</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x0</Data>
<Data Name="ProcessName">-</Data>
<Data Name="IpAddress">192.168.1.1</Data>
<Data Name="IpPort">63846</Data>
</EventData>
</Event>
In my last post, I discussed an issue with creating the FIM Service MA when you are building an all-in-one demo environment. This is another one of those issues. My single VM is a Server 2008 machine, so in addition to FIM 2010 RC1, it has AD DS, Exchange 2007, SQL 2008, SharePoint Services, and Visual Studio 2008.
If you are unaware, Exchange 2007 creates a self-signed computer certificate during install and uses that for securing its connections by default. In my case, Exchange 2007 was installed prior to FIM so the certificate was there when I installed FIM. During the FIM install, it recognizes the certificate’s presence and uses it for the Security Token Service (though that’s not very clear).
The issue I ran into was during registration for Self Service Password Reset. The user was prompted to register, confirmed their identity by re-entering their password, and answered the gate questions. Immediately up submitting the answers, I received the following error:
An error was encountered. Please call helpdesk or your system administrator for further assistance.
After some digging on forums I discovered this post regarding the certificate. After copying the self-signed certificate to the “Trusted People” store, I was able to successfully register for SSPR.
I recently began building a FIM 2010 RC1 VM for testing/demo purposes. This is an all-in-one Server 2008 machine, so in addition to FIM 2010, it has AD DS, Exchange 2007, SQL 2008, SharePoint Services, and Visual Studio 2008.
FIM 2010 recommends three FIM related user accounts:
I created the accounts and set up the Sync service without issue. After installing the FIM portal and service, I went to set up the FIM Service Management Agent, but received the following error:
Failed to retrieve the schema.
Failed to connect to the specified database or Forefront Identity Manager Service. Please check the specified database location, service host address, and account information.
I double checked all of my information (and even re-installed the FIM Service to verify the settings I used when installing it), but nothing seemed to be wrong. I enabled all success and failure auditing on the DC, and found the following event when I retried the information:
Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 10/13/2009 11:19:43 AM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: FIM.lab.loc
Description:
An account failed to log on.Subject:
Security ID: LAB\FIM_sync
Account Name: FIM_sync
Account Domain: LAB
Logon ID: 0x130e4cLogon Type: 2
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: FIM_ma
Account Domain: LABFailure Information:
Failure Reason: The user has not been granted the requested logon type at this machine.
Status: 0xc000015b
Sub Status: 0x0Process Information:
Caller Process ID: 0x168c
Caller Process Name: C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\miiserver.exeNetwork Information:
Workstation Name: FIM
Source Network Address: -
Source Port: -Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
Note the “The user has not been granted the requested logon type at this machine” message. In my case, the server is a DC, so that account has no rights to log on. Once I put the account into the domain local Administrators group, the MA creation process proceeded just fine.
The long awaited RC1 for FIM 2010 was released yesterday. Microsoft has promised an upgrade path from RC1 to RTM. No upgrade path exists for any of the betas or RC0.
Get the bits at http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4bb3f16b-27f8-4c1d-922f-2c7b522d9ad6.
