(2011-11-24) Forefront Identity Manager 2010 R2 Release Candidate Now Available

Mark Wahl writes on the Microsoft Server and Cloud Platform Blog about the release and availability of Forefront Identity Manager 2010 R2.

-

SOURCE: Forefront Identity Manager 2010 R2 Release Candidate Now Available

-

<QUOTE SOURCE=”Forefront Identity Manager 2010 R2 Release Candidate Now Available”>

Microsoft is pleased to announce the availability of Forefront Identity Manager 2010 R2 release candidate. It is available for download from Microsoft Connect, as described below.

This release candidate includes new and updated features for FIM 2010 R2:

• Historical reporting using integration to the System Center Service Manager data warehouse
• Web-based Self-Service Password Reset
• Scale and performance improvements
• Outlook® 2010 support for the FIM add-ins and extensions and SharePoint® 2010 support for the FIM Portal

In particular, this release candidate introduces numerous functional improvements, including:

• New authentication gates for self-service password reset
• Additional reports
• Extensible Connectivity Management Agent 2

For complete information, see the Release Notes and feature-specific documents.

If you have already joined the FIM 2010 Community Evaluation Program or downloaded the beta, you can obtain FIM 2010 R2 RC from the FIM 2010 Connect web site. The downloads link is in the left column.

To join the program and download the software, click here. Once you answer the survey questions, the Connect site will auto-approve your access.

Thanks,

Mark Wahl

Principal Program Manager

</QUOTE SOURCE=”Forefront Identity Manager 2010 R2 Release Candidate Now Available”>

-

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

(2011-10-25) Stripping Diacritics From String Values

I found the following posts about stripping diacritics from string values when using either the FIM Portal and/or the ILM/FIM Sync Engine:

• http://social.technet.microsoft.com/Forums/en-US/identitylifecyclemanager/thread/cbd42706-14c2-40ba-959e-c50aaa139daf
• http://blogs.msdn.com/b/michkap/archive/2005/02/19/376617.aspx
• http://blogs.msdn.com/b/michkap/archive/2007/05/14/2629747.aspx
• http://ahinea.com/en/tech/accented-translate.html
• http://msdn.microsoft.com/en-us/library/windows/desktop/ms697269(v=vs.85).aspx
• http://www.idmcrisis.com/post/2009/05/11/Normalizing-diacritic-characters.aspx

-

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

(2011-10-24) A Hotfix Rollup Package (Build 4.0.3594.2) Is Available For Forefront Identity Manager 2010

This hotfix rollup package both resolves issues and also introduces new features. I have not tried myself yet, but I’m particularly interested in “issue 2” mentioned in the “Fixed Issues In Sets And Query”

-

SOURCE: http://support.microsoft.com/kb/2520954

-

Fixed issues in Workflow Engine

* Issue 1

Assume that you perform an operation that accesses the SQL database when the Microsoft SQL Server connection pooling feature is enabled in the FIM server. For example, you run a query or a request. If the operation times out for any reason, a future operation on the same thread may fail until that thread is removed from the SQL connection pool. An error message that resembles the following is displayed in the FIM Service Application event log, in the RequestStatusDetails property for a request, or in the WorkflowStatusDetails property of a workflow instance:

Cannot enlist in the transaction because a local transaction is in progress on the connection.

Additionally, the time stamp is the same as the time when the operation fails.

-

Fixed issues in Sync Engine

* Issue 1

An ExpectedRulesEntry (ERE) object is associated to a child synchronization rule of a Metaverse object. If the ERE object has a Remove action, deprovisioning of the object is also being triggered. Then, the behavior causes the deletion of the Metaverse object.

-

* Issue 2

Fixes an access violation when a custom extension calls a COM+ object.

-

* Issue 3

An earlier hotfix introduced a special Extensible Connectivity Management Agent (ECMA) mode to keep unconfirmed exports in escrow instead of awaiting confirmation. An issue with that hotfix causes delta sync to add new items that are not merged with an escrowed export into a pending export. After you install the hotfix that is mentioned in this article, if the ECMAAlwaysExportUnconfirmed registry entry is set to 1, the escrowed and pending changes are merged.

-

* Issue 4

Fixes an SQL query construction issue that occurs during an import. This issue affects a DB2 database that uses a non-Unicode character set.

-

* Issue 5

Fixes many "Export not reimported" errors that might occur because of errors in SQL.

-

* Issue 6

Improves the performance of all Sync Engine operations.

Note This change involves an extensive upgrade to the sync database. This upgrade can take lots of time, depending on your hardware. A progress bar is displayed during the database upgrade.

-

* Issue 7

A password reset that uses the ADMAEnforcePasswordPolicy registry setting fails when the user is in the Administrator group but is not an administrator.

-

* Feature 1

Adds an option to have FIM 2010 export the current time on the server to the HTTPPasswordChangeDate field during the password set operation. The time stamp is stored as a TimeDate data type.

To enable this behavior, set the following registry subkey to a nonzero DWORD Value: HKLM\

SYSTEM\CurrentControlSet\Services\FIMSynchronizationService\Parameters\NotesMAExportPwdTimestamp

-

* Feature 2

The FIM 2010 Active Directory Management Agent (AD MA) does not honor the preferred domain controller list when passwords are exported. This is an issue for customers who require password changes to flow to a specific set of domain controllers. This hotfix rollup package changes the AD MA to use the preferred domain controller list first. If the preferred domain controller list does not exist, the domain controller locator service will identify a domain controller for password export operations. Additionally, you can still force password operations to use the primary domain controller by setting the following registry subkey:

Subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\FIMSynchronizationService\Parameters\PerMAInstance\<MA_name>

Value: UsePDCForPasswordOperations (REG_DWORD, 1 = True, 0 = False)

This hotfix rollup package also updates the AD MA so that a trust relationship with the configured Active Directory forest is not required to export passwords to that forest.

-

* Feature 3

Adds the ability to filter objects before they are imported into the AD MA connector space.

-

* Feature 4

Adds new options to the Storechk.exe tool to enable it to remove orphaned rule fragments that are associated with an MA. To do this, you can run the tool by using the following command-line options:

Storechk.exe -sync –repair

-

Fixed issues in Sets and Query

* Issue 1

Fixes an issue that would sometimes cause incorrect Set calculations. This resulted in lots of set corrections. Also revised the Sets Correction job so that it does not change special sets that are maintained by another system maintenance job.

-

* Issue 2

Revised the FIM "Query and Sets" features to treat underscores and percent signs as literals instead of as SQL wildcard characters.

-

Fixed issues in Certificate Management

* Issue 1

Enables the random number generator in the server key generation function.

-

* Issue 2

Improves the performance when enrolling a smartcard that has not previously been used with FIM Certificate Management (CM).

-

Fixed issues in FIM Management Agent (MA)

* Issue 1

Fixes an issue in which the FIM synchronization service configuration for synchronization rules and codeless provisioning was not correctly written to the FIM Service database.

-

Fixed issues in FIM Service

* Issue 1

Fixes an issue with SQL Server deadlocks that might occur during periods of high concurrency of requests or approvals.

-

* Issue 2

Fixes an issue in which unexpected data in the FIM Service database could result in the FIM MA causing the Synchronization service to fail during import, and a stopped-server error occurred.

-

* Issue 3

Fixes an issue when you add or remove a value for a multivalued string attribute. If the request was subject to authorization such as request reevaluation, the request would fail after approval.

-

* Issue 4

Some ExpectedRuleEntry objects and DetectedRuleEntry objects in FIM 2010 can become "orphaned" over time. When a DetectedRuleEntry object is not referenced in the DetectedRulesList of any object in the system, that object is determined to be orphaned. Similarly, when an ExpectedRuleEntry object is not referenced in the ExpectedRulesList of any object in the system, that object is also determined to be orphaned.

These orphaned objects have no functional impact on FIM. However, over time, these orphaned objects can cause a decrease in performance for both FIM operations and Sync operations that are related to FIM, such as import or export by using the FIM MA.

A pruning stored procedure, [debug].[DeleteOrphanedRulesByType], was added to the [debug] namespace of the FimService database. This stored procedure must be run separately for the DetectedRuleEntry object and the ExpectedRuleEntry object. The stored procedure also has a "reportOnly" mode, and this mode can be used to determine the presence and number of orphaned DetectedRuleEntry and ExpectedRuleEntry objects in the system.

The @ruleType parameter expects one of the following well-known values:

N’Detected’ for DetectedRuleEntry objects

N’Expected’ for ExpectedRuleEntry objects

-

To determine the number of orphaned objects in the system, run the stored procedure in "reportOnly" mode as follows.

DECLARE
  @deletedRulesFound  BIT;
  EXEC [debug].[DeleteOrphanedRulesByType] @ruleType=N'CHANGE_ME', @reportOnly=1, @deletedRulesFound=@deletedRulesFound OUTPUT;

-

To loop through and actually delete orphaned objects in the system, run the stored procedure as follows. @deletionLimit=1000 instructs the procedure to stop when it has deleted 1,000 objects. If there are more than 1,000 orphaned objects in the system, either run the procedure multiple times (recommended) or increase the deletionLimit value.

DECLARE 
  @deletedRulesFound  BIT,
  @startDateTime      DATETIME,
  @endDateTime        DATETIME;
  SELECT @deletedRulesFound = -1;         
    WHILE @deletedRulesFound <> 0
    BEGIN
      SELECT @startDateTime  = CURRENT_TIMESTAMP;
      EXEC [debug].[DeleteOrphanedRulesByType] @ruleType=N'CHANGE_ME', @deletionLimit=1000, @reportOnly=0, @deletedRulesFound=@deletedRulesFound OUTPUT;
      SELECT @endDateTime    = CURRENT_TIMESTAMP;
      SELECT @startDateTime AS [StartTime], @endDateTime AS [EndTime], @deletedRulesFound AS [WereDeletedRulesFound];
    END

-

Cheers,

Jorge

———————————————————————————————

* This posting is provided "AS IS" with no warranties and confers no rights!

* Always evaluate/test yourself before using/implementing this!

* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/

———————————————————————————————

############### Jorge’s Quest For Knowledge #############

######### http://JorgeQuestForKnowledge.wordpress.com/ ########

———————————————————————————————

 

(2011-09-14) FIM 2010 R2 Beta Documentation

Through the following link you will find all kinds of evaluation guides for FIM 2010 R2:

• Forefront Identity Manager 2010 R2 Beta

-

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

(2011-02-18) Latest Rollup Hotfix Available For FIM 2010 (build 4.0.3573.2)

A few weeks ago Microsoft released a new KB article MS-KBQ2417774 which included FIM 2010 build 4.0.03561.2. The first days of february that KB article was updated to release a new revision (revision 4) of that build. However it did get a new build number being build 4.0.03573.2. About a week ago, the KB article was updated again to release a newer revision (revision 5) of the latter build (build 4.0.03573.2). So we got an update for the update! .

When you compare the revision 4 build with the revision 5 build, the revision 5 build does not include updates for FIM CM and FIM PCNS. Weird, because revision 4 is not available anymore, only revision 5 build.

In my opinion the most interesting updates in this new build are:

• AD MA now fully supports AD Recycle Bin;
  
• Approval operations can be processed by any FIM instance;
  
• Improved FIM MA performance (multi-threaded), especially during initial loads
  

For more details see, the link to the KB article is: A hotfix rollup package (build 4.0.3573.2) is available for Forefront Identity Manager 2010 (REV5)

On my FIM 2010 test environment I already had deployed revision 4 and last night I updated it with revision 5 without any issues. I still need to test if everything I configured is still working. If something breaks, I’ll post it here.

Ohhh, and to do too much at the same time I also decide to update my FIM 2010 test environment, based upon W2K8R2 and Win7, to SP1 which was released a few days ago.

 

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

(2011-01-23) Searching For Objects When Populating Reference Attributes In FIM – Available Options (Part 3)

This post explains the option to search for objects when using the " UsageKeyword Linking To A Search Scope ". Part 2 can be found here.

[Ad.2] "UsageKeyword Linking To A Search Scope"

In the screen below you see the "Computer Used By" attribute with the UocIdentityPicker control in the RCDC. You can also see that it’s value is pointing to another person object.

With this attribute, and of course any other similar attribute, you may want to make sure that only certain person objects (for example in specific location) are referenced. The next thing you need to think about is how are you going to mark an object so that you can define your filter? However, in this case any PERSON object was eligeable to be selected and it was not as important as with option 1 to be very precise. You should also be able to specify different search criteria (filters).

The only correct way to do this is by using the "UsageKeyword Linking To A Search Scope". Its configuration can be seen below.

First let’s explain the yellow marked options.

• Attribute Name: "computerUsedBy"
  
• Control Type: "UocIdentityPicker" –> enables you to select other objects to be specified as a value for the attribute;
  
• ColumnsToDisplay: "DisplayName,AccountName,Department " –> this is a list of attributes (specified by systemName) separated by a comma (,) that are shown when browsing for objects (after clicking the Browse button). However, this would only apply when using the "Filter Property" method and it is not used in this case;
  
• AttributesToSearch: "DisplayName,AccountName" –> this is a list of attributes (specified by systemName) separated by a comma (,) that are searched with the value that was specified by you (after clicking the Validate And Resolve button);
  
• UsageKeywords: "AllUsers,AllEmployees,AllContractors" –> this is a list of UsageKeywords separated by a comma (,) that are used in specific Search Scopes. In this case three Search Scopes exist and each have one of the UsageKeywords defined so that it is linked to this Identity Picker (also see picture below);
  
• ObjectTypes: "Person" –> when just specifying a value in the Identity Picker and resolving it, it would only be resolved against PERSON objects. This can be a list of objectTypes to search against and those are separated by a comma (,);
  
• Mode: "SingleResult" –> at all times the attribute can only have one single value. To be able to specify multiple value it should have had the value MultipleResult;
  
• ResultObjectType: "Person" –> The resource type is used to render objects matching the filter in the pop-up dialog-box list.
  

REMARK: In addition, additional filtering might be in effect because of configured permissions. For example, if you have people in Amsterdam and Seattle and you are only allowed to view person objects in the Seattle, then in your case as the person performing the query will be only to match PERSON objects in Seattle.

Advantages:

• When clicking the Browse button it does not return results right away (as shown in the picture below). If the list of quite large, it enables you to search based upon the selected Search Scope
  

Disadvantages:

• The only filters here are the objectType defined and the permissions to be able to query (view) the objects of the same objectType. If this option is used in the previous scenario you are able to select objects that should not be specified.
  

More information about controls in RCDCs: Resource Control Display Configuration XML Reference

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

(2011-01-23) Searching For Objects When Populating Reference Attributes In FIM – Available Options (Part 2)

This post explains the option to search for objects when using the "Filter Property". Part 1 can be found here.

 

[Ad.1] "Filter Property"

In the screen below you see the "manager" attribute with the UocIdentityPicker control in the RCDC. You can also see that it’s value is pointing to another person object.

With this attribute, and of course any other similar attribute like the "Assistant" attribute, you want to make sure that only person objects are referenced that represent people that are managers. The next thing you need to think about is how are you going to mark an object as belonging to a manager? In this simple example, a person being a manager, independent of department, location or project would have the "JobTitle" attribute configured with the word "Manager". Anyone else that’s not a manager must not be specified here, even by mistaken.

The only correct way to do this is by using the "Filter Property". Its configuration can be seen below.

First let’s explain the yellow marked options.

• Attribute Name: "Manager"
  
• Control Type: "UocIdentityPicker" –> enables you to select other objects to be specified as a value for the attribute;
  
• Mode: "SingleResult" –> at all times the attribute can only have one single value. To be able to specify multiple value it should have had the value MultipleResult;
  
• ObjectTypes: "Person" –> when just specifying a value in the Identity Picker and resolving it, it would only be resolved against PERSON objects. This can be a list of objectTypes to search against and those are separated by a comma (,);
  
• ColumnsToDisplay: "DisplayName,AccountName,EmployeeType,EmployeeStatus,JobTitle,Department,OfficeLocation" –> this is a list of attributes (specified by systemName) separated by a comma (,) that are shown when browsing for objects (after clicking the Browse button);
  
• AttributesToSearch: "DisplayName,AccountName,Department" –> this is a list of attributes (specified by systemName) separated by a comma (,) that are searched with the value that was specified by you (after clicking the Validate And Resolve button);
  
• Filter: "/Person[JobTitle = 'Manager']" –> Instead of searching against all PERSON objects, the search will only be carried out against all PERSON objects matching the filter;
  
• ResultObjectType: "Person" –> The resource type is used to render objects matching the filter in the pop-up dialog-box list.
  

REMARK: In addition to the Filter Property, additional filtering might be in effect because of configured permissions. For example, if you have managers in Amsterdam and Seattle and you are only allowed to view person objects in the Seattle, then in your case as the person performing the query will be only to match PERSON objects in Seattle for which the JobTitle equals Manager.

Advantages:

• Only objects matching the filter will be searched against. Therefore, objects not matching the filter will never be selected
  

Disadvantages:

• When clicking the Browse button you cannot search for objects and it returns the results right away (as shown in the picture below). If the list of quite large, it may take some time before you will find the required object.
  

Part 3 can be found here.

More information about controls in RCDCs: Resource Control Display Configuration XML Reference

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

(2011-01-23) Searching For Objects When Populating Reference Attributes In FIM – Available Options (Part 1)

Within FIM you search for and select objects be specified in another object’s reference attribute. Examples of this are:

• A person being specified as someone’s manager;
  
• A person being specified as someone’s assistant;
  
• A person being specified as the owner of something;
  
• One or more persons being specified as the member(s) of a certain group.
  

In all cases, you of course want to select the correct objects to be specified in the other object’s reference attribute (e.g. manager, assistant, owner, member).

Within FIM you have two options to choose from that you can use in RCDCs when configuring the UocIdentityPicker control. Both options of course have their advantages and disadvantages.

• Option 1: Through a Filter Property
  
• Option 2: Through a UsageKeyword Linking To A Search Scope
  

REMARK: You can only use one of the options at a time. Unfortunately it is not possible to use both at the same time and therefore combine their powers (advantages).

The best way to go through this is by using examples to make sure it is best understood. I will explain this in the next two posts.

Part 2 can be found here.

More information about controls in RCDCs: Resource Control Display Configuration XML Reference

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

(2011-01-22) Checking Uniqueness Of An Attribute In FIM 2010 During The EDIT process

In this post I explained how to check for uniqueness of an attributevalue that was entered manually in the RCDC during the CREATE process. At that point in time it only worked for the CREATE process and it did not work in the EDIT process. Starting with some FIM build number it also started working for the EDIT process. A colleague (kudos!) of mine needed this, tried it and it surprisingly worked! For my own fun I tested this with FIM build 4.0.3561.2. So I know for sure it works in that build and later, but probably also a few builds earlier.

For the CREATE process the XPATH Validation filter (/Person[AccountName='%VALUE%']) looks like:

(when using NOTEPAD)

(when using XML NOTEPAD)

Although when using the same XPATH validation filter, it might appear to work correctly, except for one scenario. Let’s analyse this.

When creating a new object, that object of course does not exist yet and with that XPATH validation filter you are querying the DB for all PERSON objects that have the value you entered for, in this case, the AccountName attribute. Because the object does not yet exist, it is not important to take the non-existent object into account.

However, using the same XPATH validation filter in the EDIT process would work rather against you then help you. This is why. When editing an existing object and with that XPATH validation filter you querying the DB for all PERSON objects (including the object you are editing at the moment!) that have the value already specified for, in this case, the AccountName attribute. You would not be able to edit the existing object anymore because it would keep telling you another object exists with the same value for the same attribute. Because the object being editted does already exist, it is important to take the object into account.

For the EDIT process the XPATH Validation filter (/Person[(AccountName='%VALUE%') and not(ObjectID='%ObjectID%')]) should look like:

(when using NOTEPAD)

(when using XML NOTEPAD)

So, with this XPATH validation filter in the EDIT process you are querying the DB for all PERSON objects, excluding the object you are editing at the moment, that have the value you entered or was already specified for, in this case, the AccountName attribute.

Using this XPATH validation filter in the CREATED process would also work.

 

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————

(2010-09-24) Security Questions For The FIM QA Gate

One of the coolest features in the current version of FIM 2010 is the ability to reset your own password without even contacting the service desk (helpdesk). The feature is called Self-Service Password Reset (SSPR). However, being able to reset your own password you must authenticate yourself. You can’t do it the regular way (username and password) because you just forgot your password. The way FIM authenticates you before you are able to reset your own password, is by letting you answer certain questions with regards to your own person. For FIM to be able to check you have answered those questions correctly, you need to register the answers to those questions. So, with SSPR the user is authenticated by first providing the domain and username and then answering the questions that are shown and for which the answers have been registered.

Looking at the availability of social networks on the internet (LinkedIn, Facebook, Hyves, etc.), it is almost not possible to not find the smallest information about anyone. So the real difficulty for the FIM QA Gate is by finding string questions that in general can only be answered by the individual that also registered those questions.

The following site has an interesting list of GOOD, FAIR and BAD questions that could be used in the FIM QA Gate, or any other product that uses a similar authentication mechanism.

SOURCE: http://www.goodsecurityquestions.com/examples.htm

 

GOOD

What was your childhood nickname?

In what city did you meet your spouse/significant other?

What is the name of your favorite childhood friend?

What street did you live on in third grade?

What is your oldest sibling’s birthday month and year? (e.g., January 1900)

What is the middle name of your youngest child?

What is your oldest sibling’s middle name?

What school did you attend for sixth grade?

What was your childhood phone number including area code? (e.g., 000-000-0000)

What is your oldest cousin’s first and last name?

What was the name of your first stuffed animal?

In what city or town did your mother and father meet?

Where were you when you had your first kiss?

What is the first name of the boy or girl that you first kissed?

What was the last name of your third grade teacher?

In what city does your nearest sibling live?

What is your youngest brother’s birthday month and year? (e.g., January 1900)

What is your maternal grandmother’s maiden name?

In what city or town was your first job?

What is the name of the place your wedding reception was held?

What is the name of a college you applied to but didn’t attend?

Where were you when you first heard about 9/11?

 

FAIR

What was the name of your elementary / primary school?

What is the name of the company of your first job?

What was your favorite place to visit as a child?

What is your spouse’s mother’s maiden name?

What is the country of your ultimate dream vacation?

What is the name of your favorite childhood teacher?

To what city did you go on your honeymoon?

What time of the day were you born?

What was your dream job as a child?

What is the street number of the house you grew up in?

What is the license plate (registration) of your dad’s first car?

Who was your childhood hero?

What was the first concert you attended?

What are the last 5 digits of your credit card?

What are the last 5 of your Social Security number?

What is your current car registration number?

What are the last 5 digits of your driver’s license number?

What month and day is your anniversary? (e.g., January 2)

What is your grandmother’s first name?

What is your mother’s middle name?

What is the last name of your favorite high school teacher?

What was the make and model of your first car?

Where did you vacation last year?

What is the name of your grandmother’s dog?

What is the name, breed, and color of current pet?

What is your preferred musical genre?

In what city and country do you want to retire?

What is the name of the first undergraduate college you attended?

What was your high school mascot?

What year did you graduate from High School?

What is the name of the first school you attended?

 

POOR

What was your favorite sport in high school?

What is the name of the High School you graduated from?

What is your pet’s name?

In what year was your father born?

In what year was your mother born?

What is your mother’s (father’s) first name?

What is your mother’s maiden name?

What was the color of your first car?

What is your father’s middle name?

In what county where you born?

How many bones have you broken?

What is the first and last name of your favorite college professor?

On which wrist do you wear your watch?

What is the color of your eyes?

What is the title and artist of your favorite song?

What is the title and author of your favorite book?

What is the name, breed, and color of your favorite pet?

What is your favorite animal?

What was the last name of your favorite teacher?

What is your favorite team?

What is your favorite movie?

What is your favorite teacher’s nickname?

What is your favorite TV program?

What is your least favorite nickname?

What is your favorite sport?

What is the name of your hometown?

What is the color of your father’s eyes?

What is the color of your mother’s eyes?

What was the name of your first pet?

What sports team do you love to see lose?

In what city were you born?

What is the city, state/province, and year of your birth?

What is the name of your hometown newspaper?

What is your favorite color?

What was your hair color as a child?

What is your work address?

What is the street name your work or office is located on?

What is your address, phone number?

Make sure to also read: http://www.goodsecurityquestions.com/index.htm#insecure

 

Cheers,
Jorge
———————————————————————————————
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: http://jorgequestforknowledge.wordpress.com/disclaimer/
———————————————————————————————
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########
———————————————————————————————