Details of Errata

 

Here is what the text on page 183 should say (the italicized items are the new or changed bits of text)

Unattended Install of the FIM Client

This is the component that you will perhaps most desperately see the need for unattended install.

Use the following table to help you plan your install as well as to understand the relationship between the UI parameters, the Unattended parameters and where these items are persisted. These items can also be controlled through Group Policy templates that are shipped with the product.

These items are persisted in one of four spots in the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Forefront Identity Manager\2010\

Add-ins

Extensions

Extensions\Intranet

Errata and Updates to FIM Best Practices Volume 1

Thanks to several readers including Freek Berson, for catching a few errors I made while revising after my first round of reviewers.

Changes: in version 1.1 (Sept 28, 2010)

Chapter 1, updated the manager to director card, previously the word director was not visible (page 2)

Manager Director

Chapter 1 Fixed “Error Missing Reference” in Chapter 1 (page 4) to refer to Figure 1-2 Actual Photo of Smart Card

Fixed client unattended install in Chapter 7: deleted reference to config files and corrected registry references.

Updated bio

 

Here is the beauty of Print on Demand I have fixed the errors listed above and released a new version of FIM Best Practices Volume 1 through Lulu. As of now all new copies ordered will have the above corrections.

A lot of folks have asked about an e-book and I am looking into that. Others have asked about volume 2 and I am working on that. For now my target date for volume 2 is December

Extinguishing Cystic Fibrosis

Well, we are on our way towards our goal of $2000, but we need more help (please make a donation).

Refresher:

Every year Ensynch sponsor’s the Ensynch Stairclimb and Firefighter challenge. The purpose of the event is to raise money for research on Cystic Fibrosis. The event is this Saturday, in Phoenix at Arizona Center - 5th Street & Van Buren.  This year I am heading up the Stripes team, we have a goal of raising $2000 by this Saturday. Many of our team mates at Ensynch will be climbing stairs. If you live in Phoenix or will be here this Saturday you can participate too (you can climb or come and cheer as part of the no-sweat supporters). Alternatively, you can sponsor one, make a donation in our team’s name. The event also includes cheering on different firefighting teams as they perform their challenges!

 

Last year there was food and various family friendly activities. My kids had a blast!

Fighting Cystic Fibrosis

Every year Ensynch sponsor’s the Ensynch Stairclimb and Firefighter challenge. The purpose of the event is to raise money for research on Cystic Fibrosis. The event is this Saturday, in Phoenix at Arizona Center - 5th Street & Van Buren.  This year I am heading up the Stripes team, we have a goal of raising $2000 by this Saturday. Many of our team mates at Ensynch will be climbing stairs. If you live in Phoenix or will be here this Saturday you can participate too (you can climb or come and cheer as part of the no-sweat supporters). Alternatively, you can sponsor one, make a donation in our team’s name. The event also includes cheering on different firefighting teams as they perform their challenges!

 

Last year there was food and various family friendly activities. My kids had a blast!

 

Default GalSync Connector Filter

Using FIM 2010 RTM Update 1:

The default GalSync Connector Filter is to filter out user objects that are hidden from the addressbook, OR missing the legacyExchangeDN, OR missing both the msExchangeHomeServerName and targetAddress are missing, OR proxyAddresses are missing, OR if it is a Mailbox Plan, Arbitration Mailbox, or Discovery Mailbox.

Consequently, this answers the question are mail-enabled users filtered out by default?

No they are not, as a mail-enabled user will have the target address populated, and none of the other rules will filter it out.

When moving the FIM DB ensure FT Indexing enabled

I just found a very intriguing blog post from Thomas Vuylsteke, about a potential danger when moving your FIM Service Database from SQL Server to another: The case of the new attributes that didn’t want to be found

In short there is the potential that when you move the database that it might arrive on the new server with the Full Text Indexing disabled. The way Thomas tumbled to the problem was that he couldn’t search for a new attribute.

His post has a clever title and is well written, exposing a potential problem.

TEC Europe – Come hear me speak!

I will be presenting at TEC Europe in Dusseldorf Germany Oct 4-6. During my sessions I will give away a copy or two of my book FIM Best Practices Volume 1 .

FIM 2010 Performance Tuning (SQL and more)
Speaker: David Lundell

Learn how to tune FIM 2010 to make it scream. Take a look at the various architectures and what they buy you. Learn how crucial SQL is to FIM performance and what to do about it. You’ll also learn tips for workflows and the FIM web service and receive a crash course in the SQL Server Optimization.

Proper Care and Feeding of Your Databases: FIM, ILM, CLM, RMS, SharePoint and OCS
Speaker: David Lundell

Without proper care and feeding of your databases (FIM Meta Directory Services, FIM Certificate Services, FIM Web Service, RMS, SharePoint and OCS logging), chaos will result. Learn to conquer the chaos as David Lundell, SQL expert and ILM/FIM MVP, teaches you appropriate backup strategies, database and index maintenance tactics, and performance optimization tricks including guidance on fillfactor settings for SharePoint. You will also receive a crash course in the SQL Transaction Log, SQL Recovery Models, Database Maintenance Plans, Index Optimization, SQL Backups, and SQL Agent Jobs.