Jorge's Quest For Knowledge!

All About Identity And Security On-Premises And In The Cloud – It's Just Like An Addiction, The More You Have, The More You Want To Have!

Archive for the ‘Microsoft Identity Manager (MIM)’ Category

(2017-05-11) Updating MIM 2016 With Patches After Fresh MIM 2016 (SP1) Install

Posted by Jorge on 2017-05-11


Somewhere in September 2016 Microsoft released MIM 2016 SP1 (see this blog post). That was MIM 2016 with SP1 included (build 4.4.1237.0) and which could be installed freshly. However, if you were running MIM 2016 RTM (4.3.1935.0) (with or without patches 4.3.2064.0, or 4.3.2195.0, or 4.3.2266.0) you could not apply this MIM 2016 SP1 (build 4.4.1237.0) as it was not an update package for RTM, but rather a new installation package. To still install MIM 2016 SP1 (build 4.4.1237.0) you had to first uninstall MIM 2016 RTM and then install MIM 2016 SP1 (build 4.4.1237.0) and reuse existing DBs. That procedure is explained here. In November 2016 I blogged about 2 different SP1 packages here. The build 4.4.1302.0 is explained here. Since then Microsoft released a newer build 4.4.1459.0 to replace the build 4.4.1302.0. The build 4.4.1459.0 is explained here.

If you are running MIM 2016, you will be able to install either build 4.4.1302.0 or build 4.4.1459.0.

However, if you are running MIM 2016 SP1, because you performed a fresh install you will NOT be able to install either build 4.4.1302.0 or build 4.4.1459.0.

If you want to install build 4.4.1302.0 and/or build 4.4.1459.0 you will have to perform the following actions:

  • Do NOT make any changes
  • Backup ALL FIM related databases in SQL Server
  • Create a backup copy of the contents of the folder “C:\Program Files\Microsoft Forefront Identity Manager\2010”
  • Uninstall the MIM 2016 SP1 server components
  • Install the MIM 2016 RTM (4.3.1935.0) and reuse the databases
  • DO NOT try to apply the patches 4.3.2064.0, or 4.3.2195.0, or 4.3.2266.0 as that will break your database. In that latter case you will need to restore the DB from backup
  • Apply the patch with build 4.4.1302.0 (this may be skipped if you want to install the newest patch mentioned next)
  • Apply the patch with build 4.4.1459.0
  • Check the different settings in the WEB.CONFIGs by comparing them with the backup copy. Apply any configuration differences you find
  • If applicable also check the mfasettings.xml
  • Done!

I do not when, but I think/hope Microsoft will create patches that can be applied to both SP1 packages.

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

Advertisements

Posted in Microsoft Identity Manager (MIM), Updates | Leave a Comment »

(2017-05-11) A Hotfix Rollup Package (Build 4.4.1459.0) Is Available for Microsoft Identity Manager 2016 SP1

Posted by Jorge on 2017-05-11


Microsoft released a new hotfix for MIM 2016 SP1 with build 4.4.1459.0. What it fixes can be found in this blog post. For additional or detailed info see MS-KBQ4012498. If you have installed build build 4.4.1237.0 you cannot install this package. Build 4.4.1237.0 was a fresh MIM 2016 SP1 install and this hotfix enables the upgrade to SP1 without the need to uninstall first and reinstall.

Download link

Issues that are fixed or improvements that are added in this update

MIM Service

Issue 1

Authentication workflow fails with "The semaphore time out period has expired" after custom client requests AuthN token.

After you install the update, the request will complete as expected, and a clear message about a communications error is thrown into the event log.

Issue 2

Under a heavy load, there may be race condition situation when two MIM Service instances try to process the same workflow at the same time. This may cause workflow processing to fail.

After you install this update, this problem no longer occurs.

Issue 3

Set partitioning may not work if a set criteria contains a sub-condition. After you install this update, set partitioning works correctly.

Issue 4

Over time, some processing data accumulates in the MIM Service database, which may cause performance issues. This causes a problem when many Object IDs are retained in the FIM.Objects table. The SQL Server Agent job runs stored procedure FIM_DeleteExpiredSystemObjectsJob and removes expired system objects by collecting all the requests and any object references, and puts their object IDs into the ExpiredObjectKeys table.

Next, all values in the ObjectValue* tables are removed for each ID number in the ExpiredObjectKeys table. Finally, if the values in the ObjectValue* tables have indeed all been deleted, the matching row in the ExpiredObjectKeys table is also deleted. However, the object ID itself is never deleted from the fim.Objects table.

After you install the update, a new stored procedure in the debug namespace is added to clean up the database of these objects.

Stored Procedure Name: debug.DeleteObjectRemainders
Syntax: exec debug.DeleteObjectRemainders

Issue 5

After MIM SP1 clean installation, MIM Reporting or MIM Service Partitioning may not work correctly. After you install this update, both MIM Service reporting and partitioning are installed and function correctly.

Issue 6

If the FIMService database compatibility level is set to 120, SQL deadlocks may occur. After you install this update, these deadlocks no longer occur.

Improvement 1

Verbose trace logging in the MIM Service can now be enabled without forcing a restart of the service.

One new section is added to the Microsoft.ResourceManagement.Service.exe.config file to support this functionality. After you install this update, this new section is now present.

<dynamicLogging mode="true" loggingLevel="Critical" />

Logging can be set to any level between Critical and Verbose.

Two output files will be written to the installation folder for the MIM Service. It is important for the MIM Service account to have write permissions to this folder.

Folder location:

%programfiles%\Microsoft Forefront Identity Manager\2010\Service

Files written:

Microsoft.ResourceManagement.Service_tracelog.svclog

Microsoft.ResourceManagement.Service_tracelog.txt

Improvement 2

Support for System Center 2016 Service Manager and Data Warehouse is added for MIM Service Reporting.

Before this update, MIM Reporting could not install and perform with System Center 2016 Service Manager Console.

After you install this update, MIM Reporting can be installed and perform without a need to pre-install SCSM console, for any supported version of SCSM.

Synchronization Service

Issue 1

If the FIM Service management agent exports an object deletion but does not receive a confirmation of the deletion, that same object may be partly recreated in the FIMService.

After you install this update, an error will be displayed in the error list of the export run, and the recreation does not occur.

Issue 2

When the DN of an object is also the anchor, it cannot be renamed. Instead, you receive the following exception:

Unexpected-error

“The dimage has a different anchor or primary object class from what is on the hologram.”

After you install this update, the rename is processed as expected.

Issue 3

The Encryption Key Management Key (miiskmu.exe) tool may not abandon keys because of a time-out caused by a database lock.

After you install this update, the keys are processed without encountering the time-out.

Issue 4

When you run a synchronization profile step, periodic performance issues are encountered.

A fix was made to the mms_getprojected_csrefguids_noorder stored procedure to help improve performance.

Issue 5

Under certain circumstances, filter-based sync rules are applied even when they should not be.

After you install this update, the sync rule is applied only if it should be.

Issue 6

On Export for the Generic LDAP Connector, if the creation of an Audit Log file has been configured, the export run profile stops without posting a BAIL error.

After you install this update, an Export run profile step will run properly on the Generic LDAP Connector when the Audit Log File creation option is enabled.

MIM Password Reset Portal

Issue 1

When you reset a password by using the SMS authentication gate, an incorrect message is displayed to the user:

You need to click Next once you completed this call" and in next line "Call Verified:

After you install this update, the incorrect string, “Call Verified:” is removed from that dialog box.

MIM Identity Management Portal

Issue 1

Drag-and-drop users into the Remove box to delete or remove a member for group membership does not work in all circumstances.

After you install this fix, users can drag-and-drop users into the Remove box when you manage manual group memberships.

Issue 2

Local Date/Time settings being ignored for English (Australia).

After you install this update, the local date/time format settings are applied.

Issue 3

Custom controls are not initialized if we have custom event parameters in the Resource Control Display Configuration (RCDC).

After you install this fix, the custom controls are initialized as expected.

Issue 4

Error handling in the Resource Control Display Configuration is sometimes unclear.

In this update, error notifications are customized to describe the error more clearly.

Issue 5

When you use a copied link to a custom object in the Identity Management Portal, the object does not display as expected.

After you install this update, the custom object displays as expected from the copied link.

Issue 6

When you try to install the Identity Management Portal on SharePoint 2016 after you uninstall or during an update, the Portal is not installed. Additionally, you receive the following exception:

Timeout expired and error in Sharepoint log: Package name does not exist in the solution store.

Installing this update, setup will restart the SharePoint timer service to retry the failed SharePoint jobs, so setup can now complete.

Issue 7

The Approval View RCDC has incorrect symbols and displays an error.

After you install this fix, the approval view RCDC is displayed as expected, and does not throw an exception.

Issue 8

The membership buttons if custom group objects do not work correctly.

After you install this fix, the group membership buttons work as expected.

Issue 9

When you view the MIM Identity Management Portal by using the Firefox browser, object list-views, such as Users and Distribution Groups, do not display properly.

After you install this update, object list-views display as expected when you use the Firefox browser.

Issue 10

When you view the MIM Identity Management Portal by using the Internet Explorer browser, object list-views headings may not be left-aligned in the column.

After you install this update, object list-view headings display left aligned as expected.

Issue 11

When you run the MIM Portal in SharePoint 2016, the Join, Leave, Add Member, and Remove Member buttons do not work as expected on custom group object types.

After you install this update, these buttons work as expected against custom group object types.

Improvement 1

To address the fact that the default value of a Group Scope cannot be set, two optional properties were added to the UoCDropDownList and the UocRadioButtonList.

  • DefaultValue
    • This is an optional property. Use this property to define a default value for the control if the control is used to create new data

For example:

   <my:Control my:Name="My UocDropDownList" my:TypeName="UocDropDownList"
        …
         <my:Properties>
          ...
           <my:Property my:Name="DefaultValue" my:Value="MyDefault" />
  • Condition
    • Condition is optional attribute in property and it is used to specify the condition when the property is applied. The control can have several properties that use the same name but disjoint conditions
    • The syntax for condition is as follows:
      • my:Condition="[left part] [condition] [right part]
    • Notes
      • [left part] has the following options:
        • Binding Source and path
        • Simple value
      • [condition] has the following options:
        • ==
        • !=
      • [right part] has the following options:
        • Binding Source and path
        • Simple value

Example of creation different defaults for different types of group:

<my:Control my:Name="My UocDropDownList" my:TypeName="UocDropDownList"
        …
         <my:Properties>
          ...
           <my:Property my:Name="DefaultValue" my:Value=" MyDefautltForDistributionGroups" my:Condition="{Binding Source=object, Path=Type} == Distribution" />
          <my:Property my:Name="DefaultValue" my:Value=" MyDefautltForSecurityGroups " my:Condition="{Binding Source=object, Path=Type} == Security" />
-

Improvement 2

The name for all activity types that you created through Portal is authenticationGateActivity. After you install this update, all new ActivityType objects that are created, will have the following activity name values, according to type:

  • Authentication: authenticationActivity1… authenticationActivityN
  • Authorization: authorizationActivity1… authorizationActivityN
  • Action: actionActivity1… actionActivityN

Improvement 3

Requestor or Approver has no means to provide Justification upon creating the request or Approving/Rejecting pending request.

With this update, a justification field is added to the Create Request view, and new justification request/workflow data can be used. The following attributes are added [//Request/Justification] and [//WorkflowData/Reason] parameters.

Certificate Management

Issue 1

When enrolling for a virtual smart card, entering a pin with fewer than 8 characters returns a misleading error.

After you install this update, a relevant error is returned to the user.

Issue 2

When renewing a smartcard, a user can be caught in an infinite renew loop.

The following steps will cause this issue:

  1. The current smartcard profiles enter the renew window:
    • User receives an email from FIM CM Service asking him to complete a renew request
  2. User successfully executes the renew request and retrieves all certs renewed.
  3. Several hours later, user receives a second email from FIM CM Service.
    • This is not expected as the profile has already been renewed.
  4. The user will end in an infinite renew loop if he executes all the requests FIM CM Service creates.

After you install this update, only the correct requests are created, and there is no infinite loop.

Issue 3

If the Delta CRLs are disabled on a Certification Authority used by MIM Certificate Management, the exception ERROR_FILE_NOT_FOUND will be thrown by MIM CM.

After you install this update, no exception is thrown.

Issue 4

MIM CM does not support NonAdmin mode when you work with virtual cards. Virtual smart card could be only created by the MIM CM Client during enrollment. It is also required to have local admin rights to create a virtual smart card. So, only local admins can enroll for a new virtual smart card through MIM CM Portal.

After you install this hotfix, a new registry key will configure the MIM CM client to run in non-admin mode. Notice that the virtual smart card must be pre-created before the user can enroll their virtual smart card under the non-Admin mode settings.

To enable NonAdmin mode, change or create DWORD value NonAdmin=1 under the following registry key on a client computer:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CLM\v1.0\SmartCardClient

Issue 5

When you use the MIM CM REST API to change the smart card status to “Disabled”, an Error 501 (NotImplemented) is returned.

After you install this update, this same code will successfully disable the smart card.

PUT …/api/v1.0/requests/{reqID}/smartcards/{smartcardID}
{
   “status” : “Disabled”
}

For more information, see the Update Smartcard Status topic on the Microsoft website.

Issue 6

MIM CM Server version 4.3.1999.0 or a later version (until current hotfix) cannot work with older version of CM Clients (FIM 2010R2 and MIM).

After you install this update, MIM CM Server will work with older MIM and FIM 2010R2 CM Clients (FIM 2010R2 Clients version 4.1.3508.0 and later versions were tested).

Issue 7

"OfflineUnblock" request could not be created by using the following call from the MIM CM REST API:

https://docs.microsoft.com/en-us/microsoft-identity-manager/reference/create-request

After you install this update, this same code will successfully submit the OfflineUnblock request.

Issue 8

There is no possibility to use smart card id as a parameter when you create a "Disable"(or any other type) request by using the following call from MIM CM REST API:

https://docs.microsoft.com/en-us/microsoft-identity-manager/reference/create-request

Only the "profile" parameter is available.

For example:

POST api/v1.0/requests
    {
        "target":"e5008CDD9E614F9BBEDC45EEEE6776F0",
        "comment":"any comment",
        "type":"Disable",
        "profiletemplateuuid":"7860DEBB-771D-464E-AAC5-2F093282CE66",
        "datacollection":[],
        "priority":"1",
        "smartcard":"49BFE09C-5590-4CC4-8A21-FB4289F4F6C8"  
     }

After you install this update, you can use the smart card id as a parameter.

Notice that the smart card id is not the same as that of the smart card serial number. Smart card id is created by the MIM CM for each active smart card.

Issue 9

MIM CM Client tracing does not log datetime. After you install this update, the date time data will be included in the client trace log.

Issue 10

Cancelling a user in the existing virtual smart cards modal dialog box can lead to an unusal and confusing error message instead of simply cancelling the operation.

After you install this update, the operation cancels the user.

Issue 11

Retire flow stops responding for TPM virtual smart cards when the NonAdmin option is set in the registry.

Issue 12

Duplicate Revocation Settings under Replace policy does not apply to a duplicated profile. After you install this update, the flow works as expected. The revocation delay is successfully copied to the duplicated profile.

Issue 13

MIM Certificate Management does not log web service exception data. After you install this update, CM now logs all web service exception data.

Improvement 1

Before this update, the only options for PIN rules in the MIM CM Modern App is MinimumPinLength.

After you install this update, the following validation settings are now available:

  • Digits
  • LowercaseLetters
  • MaxLength
  • MinLength
  • SpecialCharacters
  • UppercaseCharacters

MIM Add-in for Outlook

Issue 1

The 32-bit MIM Add-in dlls (for example, OfficeintegrationShim2010.dll) are unsigned after you apply the MIM SP1 MSP update (4.4.1302.0 build).

In this update, all files are signed as expected.

Cheers,

Jorge

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

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

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

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

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

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

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

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

Posted in Forefront Identity Manager (FIM) bHold, Forefront Identity Manager (FIM) Certificate Management, Forefront Identity Manager (FIM) PCNS, Forefront Identity Manager (FIM) Portal, Forefront Identity Manager (FIM) Sync, Microsoft Identity Manager (MIM), Updates, Updates, Updates, Updates, Updates, Updates | 1 Comment »

(2016-12-23) New Password Change Notification Service (PCNS) Package Has Been Released

Posted by Jorge on 2016-12-23


If you have installed the MIM 2016 version with SP1 integrated, you will have PCNS version 4.4.1237.0 on your writable DCs if you are using PCNS at all

image

Figure 1: PCNS Version/Build 4.41237.0 Installed On A Writable DC

However as soon as you try to start the “Password Change Notification Service” service, it stops immediately. When you look in the Application event log, you will see:

image

Figure 2: PCNS Error About An Untrusted Root Certificate That Is Part Of A Certificate Chain Used To Sign The Binaries

The Password Change Notification service executable "C:\Program Files\Microsoft Password Change Notification\pcnssvc.exe" failed while verifying the file signature. The service will not be started and password notifications will not be sent.
pcnsfltapi.cpp (525): A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

To solve this issue, Microsoft has released a new version of the PCNS package, which can be downloaded from here.

Funny enough the new PCNS package carries the same version/build as MIM 2016 after applying the SP1 update package, but it does not mention MIM 2016 (with SP1) in the release notes. It does also not state it can run on Windows Server 2016 writable DCs.

Well I did install it on a Windows Server 2016 writable DC and it actually works also works with MIM 2016 SP1! Smile

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

Posted in Microsoft Identity Manager (MIM), PCNS | Leave a Comment »

(2016-11-27) Issues With Popup Screens In IE On The MIM Portal Server After Installing/Applying SP1

Posted by Jorge on 2016-11-27


After installing MIM 2016 with SP1 or applying the SP1 update package you may experience issues with popup windows in the MIM Portal. An example is when you for example get a popup window because you click on an MPR object.

-hen doing this remotely on another server, other than the server with the MIM Portal, you may experience the following, which is expected when using any browser.50

image

Figure 1: MIM Portal On A Remote Server With A Working Popup Window

However, doing exactly the same on the server running the MIM Portal, you may experience the following when using IE, which is NOT expected! It keeps loading, and loading, and loading….

image

Figure 2: MIM Portal On The MIM Portal Server With A Non-Working Popup Window

The solution for this problem is quite easy!

On the MIM Portal server, open Internet Explorer and then open its internet options. On the “General” tab click the “Settings” button. Then click the “View Files” button.

image

Figure 3: MIM Portal On The MIM Portal Server With A Non-Working Popup Window

After clicking the “View Files” button, a Windows Explorer window opens. Click in the files section somewhere, press {CTRL]+[A] and then press [DEL]. Close all the windows by either closing them or clicking [OK].

After doing this, popup windows with IE on the MIM Portal server should work OK again as expected!

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

Posted in Microsoft Identity Manager (MIM), Portal, Updates | Leave a Comment »

(2016-11-23) Microsoft Identity Manager (MIM) 2016 Service Pack 1 Packages

Posted by Jorge on 2016-11-23


Somewhere in September Microsoft released SP1 for MIM  2016 as you can read here. The first package was MIM 2016 with SP1 already included. If you wanted to install SP1 on your current deployment you had to uninstall first and reinstall with MIM 2016 with SP1 included where you would reuse all DBs. This procedure is described here. However, for some customers uninstalling everything and reinstalling it is a little bit too much. The impact and downtime is not acceptable. Because of that Microsoft has also released a SP1 update package that can be deployed on existing MIM 2016 deployments.

There is a subtle different of which you must be aware:

  • MIM 2016 with SP1: build 4.4.1237.0
  • SP1 update package: 4.4.1302.0

As you can see the builds are different! Please be aware you cannot apply the SP1 update package to a deployment already running MIM 2016 with SP1. You can only apply it when running MIM 2016 RTM.

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

Posted in Forefront Identity Manager (FIM) bHold, Forefront Identity Manager (FIM) Certificate Management, Forefront Identity Manager (FIM) PCNS, Forefront Identity Manager (FIM) Portal, Forefront Identity Manager (FIM) Sync, Microsoft Identity Manager (MIM), Updates, Updates, Updates, Updates, Updates, Updates | 1 Comment »

(2016-09-26) Upgrading To MIM 2016 SP1

Posted by Jorge on 2016-09-26


Microsoft has released Microsoft Identity Manager (MIM) 2016 Service Pack 1 (build 4.4.1237.0).

You are running FIM 2010 (R2) or MIM 2016 and you want to upgrade to MIM 2016 SP1? Then read all about it here!

First check if you can simply upgrade to the newer version. If you cannot upgrade, you will see the message as displayed in figure 1. If you see that message you will have to uninstall the current version before installing the newer version. However, before uninstalling create a backup using the scripts mentioned in this blog post to create a backup FIRST!!!!

After having created the backup, you can uninstall all components one by one and reinstall the new version. For the required values use the values in the backups/exports if you do not know them anymore.

image

Figure 1: Message To Uninstall The Current Version First

Upgrading to MIM PCNS

This must be executed on a per writable DC basis!

First uninstall PCNS through Programs and Features

Then install PCNS by executing the MSI (attend) or using the command line with all the options defined (unattended)

Upgrading to MIM SYNC

This must be executed on a per FIM/MIM Sync Server basis!

First uninstall MIM Sync through Programs and Features

Then install MIM Sync by executing the MSI (attend) or using the command line with all the options defined (unattended)

image

Figure 2: Welcome Screen

image

Figure 3: License Agreement

image

Figure 4: Component Selection

image

Figure 5: Specifying SQL Server And SQL Instance

image

Figure 6: Specifying FIM/MIM Sync Service Account Credentials

image

Figure 7: Specifying FIM/MIM Sync Service Security Groups

image

Figure 8: Enabling Firewall Rules For RPC Connections

image

Figure 9: Last Screen Before The Actual Installation

image

Figure 10: Message About Finding The Existing Database And The It Will Be Upgraded

image

Figure 11: Installation Completed

image

Figure 12: The Build Of The FIM/MIM Sync Service

Now after installing the product:

  • Check and compare the config files and reconfigure as needed;
  • Check and compare the registry settings and reconfigure as needed;
  • Recompile any code you have (e.g. Rules Extensions) to use it in the new version;

Upgrading to MIM Service And Portal

REMARK: In my case as you can see below I had the MIM Service, the MIM Portal, the MIM Password Registration Portal and the MIM Password Reset Portal on one server running. If you have distributed the components amongst multiple servers, use the following order:

  • MIM Service
  • MIM Portal
  • MIM Password Registration Portal
  • MIM Password Reset Portal

This must be executed on a per FIM/MIM Server basis that hosts a specific component!

First uninstall MIM Service and Portal through Programs and Features

Then install MIM Service and Portal by executing the MSI (attend) or using the command line with all the options defined (unattended)

image

Figure 13: Welcome Screen

image

Figure 14: License Agreement

image

Figure 15: Joining CEIP

image

Figure 16: Component Selection

image

Figure 17: Specifying The SQL Server, The Database Name And Whether Or Not You Want To Reuse The Database

image

Figure 18: Warning About creating A Backup Before Continuing With The Upgrade

image

Figure 18: Specifying The Mail Server And Other Related Settings

REMARK: Have you noticed the option “Use Exchange Online”? As soon as you check that all the other options are greyed out.

image

Figure 19: Configuring The Service Certificate

image

Figure 20: Configuring The FIM/MIM Service Service Account Credentials And Mail Address

image

Figure 21: Specifying The FIM/MIM Sync Server And The Account For The FIM/MIM MA

image

Figure 22: Warning About Not Being Able To Contact The FIM/MIM Sync Service

image

Figure 23: Specifying The FIM/MIM Service FQDN

image

Figure 24: Specifying The Sharepoint Collection URL To Install The Portal In

image

Figure 25: Specifying The Password Registration Portal URL

image

Figure 26: Enabling Firewall Rules And Configuring Permissions

image

Figure 27: Specifying The Credentials, The Hostname And The Port For The Password Registration Portal

image

Figure 28: Warning About Not Using SSL Due To Custom Port

REMARK: SSL will be configured afterwards

image

Figure 29: Specifying The FIM/MIM Service FQDN And The Accessibility Of The Password Registration Portal

image

Figure 30: Specifying The Credentials, The Hostname And The Port For The Password Registration Portal

image

Figure 31: Warning About Not Using SSL Due To Custom Port

REMARK: SSL will be configured afterwards

image

Figure 32: Specifying The FIM/MIM Service FQDN And The Accessibility Of The Password Reset Portal

image

Figure 33: Last Screen Before The Actual Installation

image

Figure 34: Installation Completed

Now after installing the product:

  • Check and compare the IIS configuration and reconfigure as needed;
  • Check and compare the config files and reconfigure as needed;
  • Check our customizations for the Password Registration and Reset Portal still exist;
  • Check and compare the registry settings and reconfigure as needed;
  • Recompile any code you have (e.g. Rules Extensions) to use it in the new version;

Upgrading to MIM Add-In Extensions

This must be executed on every client running the FIM/MIM Add-In Extensions!

First uninstall MIM Add-In Extensions through Programs and Features

Then install MIM Add-In Extensions by executing the MSI (attend) or using the command line with all the options defined (unattended)

image

Figure 35: Welcome Screen

image

Figure 36: License Agreement

image

Figure 37: Joining CEIP

image

Figure 38: Component Selection

image

Figure 39: Specifying The MIM Portal Server Address And The MIM Service E-mail Address

REMARK: The MIM Portal Server Address should be entered as <FQDN> or <FQDN>:<PORT> when in the last case the port is a custom port. The screenshot shows the MIM Portal URL but that is not correct

image

Figure 40: Specifying The FIM/MIM Service FQDN

image

Figure 41: Specifying The Password Registration URL

image

Figure 42: Last Screen Before The Actual Installation

image

Figure 43: Installation Completed

Now after installing the product:

  • Check and compare the registry settings and reconfigure as needed;

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

Posted in Microsoft Identity Manager (MIM) | 2 Comments »

(2016-09-26) Microsoft Identity Manager (MIM) 2016 Service Pack 1 Has Been Released

Posted by Jorge on 2016-09-26


Microsoft has released Microsoft Identity Manager (MIM) 2016 Service Pack 1 (build 4.4.1237.0)!

What does it bring you?

  • In addition to Internet Explorer, it now also supports Edge, Chrome, FireFox, and Safari;
  • The MIM service now supports a mailbox in Exchange Online for approvals and notifications;
  • Image file format validation on upload;
  • PowerShell deployment scripts for Privileged Access Management (PAM) infrastructure components;
  • Privileged Access Management (PAM) Just-In-Time (JIT) administration also works for the privileged AD forest in addition to the corporate AD forest;
  • MIM now also supports Windows Server 2016 and SQL Server 2016 (Supported platforms for MIM 2016);
  • PAM deployment automatically uses PowerShell to create and configure Authentication Policies and Authentication Policy Silos to harden security;
  • … and a few fixes

Read more about it:

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

Posted in Microsoft Identity Manager (MIM), Updates | 2 Comments »

(2016-09-25) FIM/MIM Configuration Export Scripts

Posted by Jorge on 2016-09-25


When upgrading FIM or MIM to a newer version, you may need to uninstall the previous version first before installing the newer version. During the installation of the new version you need to reenter all the required information. But where do you get that data from? Either you have some installation/configuration guide or you make sure you make a copy (copy, export, backup) of the previous configuration so that you can look it up easily.

Making a copy of the previous configuration manually can take quite some time to finish and if unlucky you might even forget something!

Yes, you guessed it, PowerShell to the rescue! Smile

With the upcoming SP1 for MIM 2016 you may need this script.

Please provide feedback through the comments section OR you the contact page

DISCLAIMER (READ THIS!):

  • I wrote this script, therefore I own it. Anyone asking money for it, should NOT be doing that and is basically ripping you off!
  • The script is freeware, you are free to use it and distribute it, but always refer to this website (https://jorgequestforknowledge.wordpress.com/) as the location where you got it.
  • This script is furnished "AS IS". No warranty is expressed or implied!
  • I have NOT tested it in every scenario nor have I tested it against every Windows and/or AD version and/or FIM/MIM version and/or SQL version
  • Always test first in lab environment to see if it meets your needs!
  • Use this script at your own risk!
  • I do not warrant this script to be fit for any purpose, use or environment!
  • I have tried to check everything that needed to be checked, but I do not guarantee the script does not have bugs!
  • I do not guarantee the script will not damage or destroy your system(s), environment or whatever!
  • I do not accept liability in any way if you screw up, use the script wrong or in any other way where damage is caused to your environment/systems!
  • If you do not accept these terms do not use the script in any way and delete it immediately!

SYNTAX:

<PoSH Script File> [-allConfig] [-mainConfig] [-fimSyncConfig] [-fimSvcConfig] [-fimPortalConfig] [-fimPwdRegPortalConfig] [-fimPwdResetPortalConfig] [-backupDBs] [-mainBackupFolder <Folder To Backup/Export To>]

This PoSH script exports FIM/MIM configuration as a quick backup method. If applicabel, the following configuration components are exported:

  • FIM/MIM Main Configuration;
  • FIM/MIM Sync Configuration;
  • FIM/MIM Service Configuration;
  • FIM/MIM Portal Configuration;
  • FIM/MIM Registration Portal Configuration;
  • FIM/MIM Reset Portal Configuration;
  • SQL Server Database

I have NOT added support for:

  • FIM/MIM PCNS Configuration;
  • FIM/MIM CM Configuration;
  • FIM/MIM Reporting Configuration

Currently there is no import script. You will have to do it manually

Get the export script from HERE

When upgrading, you only need to the [-mainConfig option on every FIM server and the [-backupDBs] option on the SQL server! For example:

  • Everything on one server (incl. SQL server)? –> <PoSH Script File> -mainConfig -backupDBs -mainBackupFolder <Folder To Backup/Export To>
  • FIM/MIM servers without SQL –> <PoSH Script File> -mainConfig -mainBackupFolder <Folder To Backup/Export To>
  • SQL server without FIM/SQL –> <PoSH Script File> –backupDBs -mainBackupFolder <Folder To Backup/Export To>

REMARK: the installation of a newer version against an existing database WILL upgrade the database. Make sure to have a backup of your FIM/MIM DBs!!!

PARAMETER allConfig

Exports All The Configuration Of FIM/MIM. This is basically all the options combined.

PARAMETER mainConfig

Exports Only The Main Configuration Of FIM/MIM. This should be the option to use when upgrading FIM/MIM.

PARAMETER fimSyncConfig

Exports Only The FIM Sync Specific Configuration

PARAMETER fimSvcConfig

Exports Only The FIM Service Specific Configuration

WARNING: This export might take some considerabel amount of time!!!

PARAMETER fimPortalConfig

Exports Only The FIM Portal Specific Configuration

PARAMETER fimPwdRegPortalConfig

Exports Only The FIM Password Registration Portal Specific Configuration

PARAMETER fimPwdResetPortalConfig

Exports Only The FIM Password Reset Portal Specific Configuration

PARAMETER backupDBs

Backup Only The Databases In Use By FIM

PARAMETER mainBackupFolder

Main Backup Folder To Store The Backup

image

Figure 1: Exporting The FIM/MIM Configuration Before The Upgrade

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

Posted in Backup/Export, Backup/Export, Forefront Identity Manager (FIM) Portal, Forefront Identity Manager (FIM) Sync, Microsoft Identity Manager (MIM) | 1 Comment »

(2015-08-05) MIM 2016 Has Hit The Market Shelves And Is Now Available

Posted by Jorge on 2015-08-05


Microsoft has released the successor of Forefront Identity Manager 2010 R2 (FIM 2010 R2), Microsoft Identity Manager 2016 (MIM 2016).

MIM 2016 offers the same capabilities as FIM 2010 R2, with in addition:

  • Strong focus on hybrid identity (on premises and in the cloud)
  • Support for hybrid reporting from MIM included in Azure AD reports
  • In addition to Self-Service Password Reset, Self-Service Account Unlock is also supported
  • The Self Service Password Reset portal supports Azure multi-factor authentication (MFA) in the authentication gate
  • Privileged Identity Management controls and manages administrative access by providing temporary, task-based access to sensitive resources eliminating the carte blanche administrative access coveted by cyber attackers. In addition, Privileged Identity Management extracts and isolates administrative accounts from existing Active Directory forests.
  • Support in Certificate Management for REST API access
  • Certificate Management has support for multi-forest topologies, a Windows store app for virtual smartcard and certificate lifecycle management, updated events and troubleshooting capabilities
  • Support for:
    • Windows 8.1 with Internet Explorer 8 and higher
    • Windows Server 2012 R2
    • SQL 2014
    • Outlook 2013
    • System Center Service Manager 2012 and 2012 R2
  • The deprecated features are still deprecated, but are still available in MIM 2016 as mentioned by David Lundell

More information:

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

Posted in Microsoft Identity Manager (MIM) | 1 Comment »

 
%d bloggers like this: