<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>Solve your Identity crisis without therapy</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/ms-identity-support/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/feed.xml</link>
    <description>This blog is designed to cover information that the Security Identity Support Team encounteres and is able to share.</description>
    <lastBuildDate>Tue, 16 Apr 2019 05:20:49 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>FAQ for FIM 2010 to support SHA2, KSP/CNG and v3 certificate templates for issuing user and agent certificates and MIM 2016 upgrade</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/faq-for-fim-2010-to-support-sha2-kspcng-and-v3-certificate-templates-for-issuing-user-and-agent-certificates-and-mim-2016-upgrade</link>
      <pubDate>Thu, 14 Jul 2016 14:52:30 GMT</pubDate>
      <dc:creator><![CDATA[Tim Macaulay]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/?p=2255</guid>
      <description><![CDATA[~ Milan Milosavljevic | Senior Escalation Engineer

Hi everyone, Milan Milosavljevic here from the...]]></description>
      <content:encoded><![CDATA[<strong>~ <em>Milan Milosavljevic | Senior Escalation Engineer</em></strong>

Hi everyone, Milan Milosavljevic here from the Microsoft Platform AD Identity support team. I’d like to take a minute to clarify a couple common questions we get regarding upgrade support for Microsoft Identity Manager 2016 (MIM 2016). This includes how to handle the deprecation of the Forefront Identity Manager 2010 Certificate Management (FIM CM) management agents as well as SHA2 support.

<strong>Question</strong>: Does FIM CM 2010 R2 SP1/MIM CM 2016 support user certificates signed using SHA2?

<strong>Answer</strong>: Yes. SHA2 support is provided by configuring the issuing CA to issue SHA2 certificates. No additional action is required on FIM CM 2010 or MIM 2016. It means that FIM CM 2010 R2 SP1/MIM CM 2016 can work with SHA2 PKIs.

=====

<strong>Question</strong>: Does FIM CM 2010 R2 SP1/MIM CM 2016 support CM agent certificates (cmagent, cmenrollmentagent and cmrecoveryagent) signed using SHA2?

<strong>Answer</strong>: Yes. This means that FIM CM 2010 R2 SP1/MIM CM 2016 can work with SHA2 PKIs. Please note however that if you want to change hash algorithms for the agents after the upgrade, you will need to replace or renew the certificates. For more information see <a href="https://technet.microsoft.com/en-us/library/hh149034(v=ws.10).aspx">https://technet.microsoft.com/en-us/library/hh149034(v=ws.10).aspx</a>.

=====

<strong>Question</strong>: Does FIM CM 2010 R2 SP1/MIM CM 2016 support user certificates issued with KSP/CNG keys and v3 (and newer) certificate templates?

<strong>Answer</strong>: Partially. User certificates can use KSP, but only with RSA. This means the corresponding certificate template (v3 or newer) in its Cryptography tab can be configured with “Provider Category = Key Storage Provider” but “Algorithm Name” must be “RSA”. Selecting any of ECDH algorithms (ECDH_P256, ECDH_P384, ECDH_P521) as “Algorithm Name” is not supported.

The same support statement applies to FIM CM 2010 R2 SP1 and to MIM CM 2016.

The same support statement (RSA only) applies to 3rd Party software and hardware KSPs.

The reason why other algorithms (ECDH and ECDSA) are not supported are different for the smartcard and software profiles:
<ul>
	<li>For smartcard profiles, CM client uses CryptoAPI which doesn’t support elliptic curves.</li>
	<li>For software profiles, JavaScript client side code uses RSA only.</li>
</ul>
<strong>=====</strong>

<strong>Question</strong>: Does FIM CM 2010 R2 SP1/MIM CM 2016 support CM agent certificates (cmagent, cmenrollmentagent and cmrecoveryagent) issued with KSP/CNG keys and v3 (and newer) certificate templates?

<strong>Answer</strong>: KSP/CNG is not supported with CM agent certificates. This limitation exists because the .NET Framework X509Certificate2 class does not support certificates associated with a CNG private key provider. V3 (or newer) certificate templates can be used but the Cryptography tab in “Provider Category” must reference “Legacy Cryptographic Service Provider”.

=====

<strong>Question</strong>: Is an in place upgrade from FIM CM 2010 R2 Service Pack 1 to MIM CM 2016 possible?

<strong>Answer</strong>: Yes, assuming you’re on the latest build of FIM CM 2010 R2 SP1. You only need run the CM installation and make sure to check the migration checkbox in the setup wizard and FIM CM 2010 will be migrated to MIM CM 2016. Prior to performing the upgrade, please make sure that your FIM CM backup is current and complete, including the FIM CM database, agent accounts and certificates/keys, as well as the FIM CM configuration files.

=====

<strong>Question</strong>: What is the official recommendation for replacement of FIM CM management agents?

<strong>Answer</strong>: FIM CM management agents (MAs) have been deprecated in MIM 2016. As an alternative, you can create similar functionality using the FIM CM Provision API (<a href="https://msdn.microsoft.com/en-us/library/windows/desktop/bb468091(v=vs.100).aspx">https://msdn.microsoft.com/en-us/library/windows/desktop/bb468091(v=vs.100).aspx</a>) or the FIM CM SQL API (<a href="https://msdn.microsoft.com/en-us/library/windows/desktop/bb468093(v=vs.100).aspx">https://msdn.microsoft.com/en-us/library/windows/desktop/bb468093(v=vs.100).aspx</a>).

&nbsp;

<em><b>Milan Milosavljevic | Senior Escalation Engineer | Microsoft</b></em>]]></content:encoded>
    </item>
    <item>
      <title>FAQ for FIM 2010 to MIM 2016 upgrade and SHA2 support</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/fimcm-info-faq-for-fim-2010-to-mim-2016-upgrade-and-sha2-support</link>
      <pubDate>Mon, 11 Jan 2016 13:02:00 GMT</pubDate>
      <dc:creator><![CDATA[J.C. Hornbeck]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/2016/01/11/fimcm-info-faq-for-fim-2010-to-mim-2016-upgrade-and-sha2-support/</guid>
      <description><![CDATA[~ Milan Milosavljevic | Microsoft Senior Escalation Engineer 

UPDATED 7/14/2016: A newer version...]]></description>
      <content:encoded><![CDATA[<em>~ <strong>Milan Milosavljevic | Microsoft Senior Escalation Engineer </strong></em>

<strong>UPDATED 7/14/2016</strong>: <em>A newer version of this article is available here: <a href="https://blogs.msdn.microsoft.com/ms-identity-support/2016/07/14/faq-for-fim-2010-to-support-sha2-kspcng-and-v3-certificate-templates-for-issuing-user-and-agent-certificates-and-mim-2016-upgrade/">https://blogs.msdn.microsoft.com/ms-identity-support/2016/07/14/faq-for-fim-2010-to-support-sha2-kspcng-and-v3-certificate-templates-for-issuing-user-and-agent-certificates-and-mim-2016-upgrade/</a></em>

=====

Hi everyone, Milan Milosavljevic here from the Microsoft Platform AD Identity support team. I’d like to take a minute to clarify a couple of common questions we get regarding upgrade support for Microsoft Identity Manager 2016 (MIM 2016). This includes how to handle the deprecation of the Forefront Identity Manager 2010 Certificate Management (FIM CM) management agents as well as SHA2 support.

<span style="text-decoration: underline">Q1</span>: Is an in place upgrade from FIM CM 2010 R2 Service Pack 1 to MIM CM 2016 possible?

<span style="text-decoration: underline">Answer</span>: Yes, assuming you’re on the latest build of FIM CM 2010 R2 SP1. You only need run the CM installation and make sure to check the migration checkbox in the setup wizard and FIM CM 2010 will be migrated to MIM CM 2016. Prior to performing the upgrade, please make sure that your FIM CM backup is current and complete, including the FIM CM database, agent accounts and certificates/keys, as well as the FIM CM configuration files.

<span style="text-decoration: underline">Q2</span>: What is the official recommendation for replacement of FIM CM management agents?

Answer: FIM CM management agents (MAs) have been deprecated in MIM 2016. As an alternative, you can create similar functionality using the FIM CM Provision API (<a href="https://msdn.microsoft.com/en-us/library/windows/desktop/bb468091(v=vs.100).aspx">https://msdn.microsoft.com/en-us/library/windows/desktop/bb468091(v=vs.100).aspx</a>) or the FIM CM SQL API (<a href="https://msdn.microsoft.com/en-us/library/windows/desktop/bb468093(v=vs.100).aspx">https://msdn.microsoft.com/en-us/library/windows/desktop/bb468093(v=vs.100).aspx</a>).

<span style="text-decoration: underline">Q3</span>: Does FIM CM 2010 R2 SP1 support user certificates signed using SHA2?

Answer: Yes. SHA2 support is provided by configuring the issuing CA to issue SHA2 certificates - no additional action is required on FIM CM 2010 or MIM 2016.

<span style="text-decoration: underline">Q4</span>: Does FIM CM support FIM CM agent certificates (fimcmagent, fimcmenrollmentagent and fimcmrecoveryagent) signed using SHA2?

Answer: Yes. Please note however that if you want to change hash algorithms for the agents after the upgrade, you will need to replace or renew the certificates. For more information see <a href="https://technet.microsoft.com/en-us/library/hh149034(v=ws.10).aspx">https://technet.microsoft.com/en-us/library/hh149034(v=ws.10).aspx</a>.

<span style="text-decoration: underline">Q5</span>: Does MIM CM support user certificates signed using SHA2?

Answer: Yes, the same way as in FIM CM 2010 R2 SP1.

<span style="text-decoration: underline">Q6</span>: Does MIM CM support FIM CM agent certificates (fimcmagent, fimcmenrollmentagent and fimcmrecoveryagent) signed using SHA2?

Answer: Yes, in the same way as FIM CM 2010 R2 SP1.

<strong><em>Milan Milosavljevic | Senior Escalation Engineer | Microsoft</em></strong>

<a href="https://www.facebook.com/Microsoft-System-Center-Support-111513322193410/" target="_blank"><img title="fb" src="https://msdnshared.blob.core.windows.net/media/2016/01/fb2.jpg" alt="fb" width="98" height="68" border="0" /></a><a href="https://twitter.com/MS_SystemCenter" target="_blank"><img title="TwitterPic" src="https://msdnshared.blob.core.windows.net/media/2016/01/TwitterPic2.jpg" alt="TwitterPic" width="99" height="67" border="0" /></a>

<strong>Our Blogs</strong>
<ul>
	<li>Configuration Manager: <a href="https://blogs.technet.com/configurationmgr/" target="_blank">https://blogs.technet.com/configurationmgr/</a></li>
	<li>Data Protection Manager: <a href="https://blogs.technet.com/dpm/" target="_blank">https://blogs.technet.com/dpm/</a></li>
	<li>Orchestrator: <a href="https://blogs.technet.com/b/orchestrator/" target="_blank">https://blogs.technet.com/b/orchestrator/</a></li>
	<li>Operations Manager: <a href="https://blogs.technet.com/momteam/" target="_blank">https://blogs.technet.com/momteam/</a></li>
	<li>Operations Management Suite: <a href="https://blogs.technet.microsoft.com/omsblog/" target="_blank">https://blogs.technet.microsoft.com/omsblog/</a></li>
	<li>Service Manager: <a href="https://blogs.technet.com/b/servicemanager" target="_blank">https://blogs.technet.com/b/servicemanager</a></li>
	<li>Virtual Machine Manager: <a href="https://blogs.technet.com/scvmm" target="_blank">https://blogs.technet.com/scvmm</a></li>
	<li>Microsoft Intune: <a href="https://blogs.technet.microsoft.com/intunesupport/" target="_blank">https://blogs.technet.microsoft.com/intunesupport/</a></li>
	<li>WSUS: <a href="https://blogs.technet.com/sus/" target="_blank">https://blogs.technet.com/sus/</a></li>
	<li>AD and Azure RMS: <a href="https://blogs.technet.com/b/rms/" target="_blank">https://blogs.technet.com/b/rms/</a></li>
	<li>Application Virtualization: <a href="https://blogs.technet.com/appv/" target="_blank">https://blogs.technet.com/appv/</a></li>
	<li>MED-V: <a href="https://blogs.technet.com/medv/" target="_blank">https://blogs.technet.com/medv/</a></li>
	<li>Application Proxy: <a href="https://blogs.technet.com/b/applicationproxyblog/" target="_blank">https://blogs.technet.com/b/applicationproxyblog/</a></li>
	<li>Forefront Endpoint Protection: <a href="https://blogs.technet.com/b/clientsecurity/" target="_blank">https://blogs.technet.com/b/clientsecurity/</a></li>
	<li>Forefront Identity Manager: <a href="https://blogs.msdn.com/b/ms-identity-support/" target="_blank">https://blogs.msdn.com/b/ms-identity-support/</a></li>
	<li>Forefront TMG: <a href="https://blogs.technet.com/b/isablog/" target="_blank">https://blogs.technet.com/b/isablog/</a></li>
	<li>Forefront UAG: <a href="https://blogs.technet.com/b/edgeaccessblog/" target="_blank">https://blogs.technet.com/b/edgeaccessblog/</a></li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>KB: Microsoft Azure AD Management Agent hangs during Full Import or Delta Import</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/kb-microsoft-azure-ad-management-agent-hangs-during-full-import-or-delta-import</link>
      <pubDate>Thu, 01 Oct 2015 13:06:46 GMT</pubDate>
      <dc:creator><![CDATA[Tim Macaulay]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/2015/10/01/kb-microsoft-azure-ad-management-agent-hangs-during-full-import-or-delta-import/</guid>
      <description><![CDATA[When you run a Full Import or a Delta Import on the Microsoft Azure Active Directory (Azure AD)...]]></description>
      <content:encoded><![CDATA[<a href="https://support.microsoft.com/en-us/kb/3096482" target="_blank"><img style="float: left;padding-top: 0px;padding-left: 0px;padding-right: 0px;border-width: 0px" title="KB7334333232" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/metablogapi/7144.KB7334333232_4913B19C.jpg" alt="KB7334333232" width="100" height="115" align="left" border="0" /></a>

When you run a Full Import or a Delta Import on the Microsoft Azure Active Directory (Azure AD) Connector, one of the following actions occur:

1. The following error is logged in the Application Event Log:

<em><span style="color: #004080">FIMSynchronizationService Event 6801
The extensible extension returned an unsupported error.
The stack trace is:
“System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at System.Collections.ObjectModel.KeyedCollection`2.get_Item(TKey key)
at Microsoft.Azure.ActiveDirectory.Connector.Connector.GetConnectorSpaceEntryChange(SyncObject syncObject)
at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
at Microsoft.Azure.ActiveDirectory.Connector.Connector.GetImportEntriesCore()
at Microsoft.Azure.ActiveDirectory.Connector.Connector.GetImportEntries(GetImportEntriesRunStep getImportEntriesRunStep)</span></em>

2. You receive the following error message:

<em><span style="color: #004080">DirectorySynchronization Event 109:
Failure while importing entries from Windows Azure Active Directory. Exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at System.Collections.ObjectModel.KeyedCollection`2.get_Item(TKey key)
at Microsoft.Azure.ActiveDirectory.Connector.Connector.GetConnectorSpaceEntryChange(SyncObject syncObject)
at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
at Microsoft.Azure.ActiveDirectory.Connector.Connector.GetImportEntriesCore()
at Microsoft.Azure.ActiveDirectory.Connector.Connector.GetImportEntries(GetImportEntriesRunStep getImportEntriesRunStep).</span></em>

For complete details as well as a resolution, please see the following:

<a href="https://support.microsoft.com/en-us/kb/3096482" target="_blank">KB3096482</a> - <em>"System.Collections.Generic.KeyNotFoundException" error and Azure AD Management Agent hangs during Full Import or Delta Import</em> (<a title="https://support.microsoft.com/en-us/kb/3096482" href="https://support.microsoft.com/en-us/kb/3096482">https://support.microsoft.com/en-us/kb/3096482</a>)

<b>J.C. Hornbeck</b> <strong>| Solution Asset PM | Microsoft GBS Management and Security Division</strong>

<b><span style="color: #c0504d">Get the latest System Center news on</span> </b><a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><b>Facebook</b></a><b> <span style="color: #c0504d">and</span> </b><a href="https://twitter.com/#!/MS_SystemCenter"><b>Twitter</b></a><b>:</b>

<a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><img title="clip_image001" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image001_64a4101d-1898-43ad-8493-b15123a8f037.gif" alt="clip_image001" width="89" height="21" border="0" /></a> <a href="https://www.twitter.com/MS_SystemCenter"><img title="clip_image002" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image002_e463ef66-6372-4614-ad1b-a2e20e16de5f.gif" alt="clip_image002" width="89" height="21" border="0" /></a>

Main System Center blog: <a href="https://blogs.technet.com/b/systemcenter/">https://blogs.technet.com/b/systemcenter/</a>

Configuration Manager Support Team blog: <a href="https://blogs.technet.com/configurationmgr/">https://blogs.technet.com/configurationmgr/</a>
Data Protection Manager Team blog: <a href="https://blogs.technet.com/dpm/">https://blogs.technet.com/dpm/</a>
Orchestrator Team blog: <a href="https://blogs.technet.com/b/orchestrator/">https://blogs.technet.com/b/orchestrator/</a>
Operations Manager Team blog: <a href="https://blogs.technet.com/momteam/">https://blogs.technet.com/momteam/</a>
Service Manager Team blog: <a href="https://blogs.technet.com/b/servicemanager">https://blogs.technet.com/b/servicemanager</a>
Virtual Machine Manager Team blog: <a href="https://blogs.technet.com/scvmm">https://blogs.technet.com/scvmm</a>

Microsoft Intune: <a href="https://blogs.technet.com/b/microsoftintune">https://blogs.technet.com/b/microsoftintune/</a>
WSUS Support Team blog: <a href="https://blogs.technet.com/sus/">https://blogs.technet.com/sus/</a>
RMS blog: <a href="https://blogs.technet.com/b/rms/">https://blogs.technet.com/b/rms/</a>
App-V Team blog: <a href="https://blogs.technet.com/appv/">https://blogs.technet.com/appv/</a>
MED-V Team blog: <a href="https://blogs.technet.com/medv/">https://blogs.technet.com/medv/</a>
Server App-V Team blog: <a href="https://blogs.technet.com/b/serverappv">https://blogs.technet.com/b/serverappv</a>

Forefront Endpoint Protection blog: <a href="https://blogs.technet.com/b/clientsecurity/">https://blogs.technet.com/b/clientsecurity/</a>
Forefront Identity Manager blog: <a href="https://blogs.msdn.com/b/ms-identity-support/">https://blogs.msdn.com/b/ms-identity-support/</a>
Forefront TMG blog: <a href="https://blogs.technet.com/b/isablog/">https://blogs.technet.com/b/isablog/</a>
Forefront UAG blog: <a href="https://blogs.technet.com/b/edgeaccessblog/">https://blogs.technet.com/b/edgeaccessblog/</a>
Application Proxy blog: <a href="https://blogs.technet.com/b/applicationproxyblog/">https://blogs.technet.com/b/applicationproxyblog/</a>
The Surface Team blog: <a href="https://blogs.technet.com/b/surface/">https://blogs.technet.com/b/surface/</a>

<em><span style="color: #ffffff">FIM 2010</span></em>]]></content:encoded>
    </item>
    <item>
      <title>HOWTO: How to loop through proxyAddresses and update the primary SMTP</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/howto-how-to-loop-through-proxyaddresses-and-update-the-primary-smtp</link>
      <pubDate>Wed, 26 Aug 2015 12:59:54 GMT</pubDate>
      <dc:creator><![CDATA[Tim Macaulay]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/2015/08/26/howto-how-to-loop-through-proxyaddresses-and-update-the-primary-smtp/</guid>
      <description><![CDATA[The purpose of this document is to provide an illustration of how to setup a Management Agent Rules...]]></description>
      <content:encoded><![CDATA[<p class="WordSection1">The purpose of this document is to provide an illustration of how to setup a Management Agent Rules Extension to loop through the list of proxyAddresses and based on the mail suffix set/change the Primary SMTP address.</p>

<div class="WordSection1">
<table style="width: 951px;height: 92px" border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td valign="top" width="623">   <strong>Disclaimer</strong></td>
</tr>
<tr>
<td valign="top" width="623">This document is an illustration.  It is highly recommended to test this in a test environment prior to implementing into production.  You want to test in a test environment to be able to understand how this illustration will fit into your environment and ensure that all your business rules are met.</td>
</tr>
</tbody>
</table>
</div>
<p class="WordSection1">In this illustration I will utilize the following:</p>

<div class="WordSection1">
<ul>
	<li>Two Active Directory Management Agents with a minimal set of attributes
<ul>
	<li>Attributes will be minimal along with proxyAddresses</li>
	<li>No provisioning only projection and join</li>
	<li>One way flow</li>
</ul>
</li>
	<li>Management Agent Rules Extension (C#)</li>
</ul>
</div>
&nbsp;

In this illustration I will be using two Active Directory Management Agents.  If you do not have your Active Directory Management Agents already created, you will need to create them prior to proceeding with the document.

<a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/6014.mas.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/6014.mas.png" alt="" border="0" /></a>

We will follow the following outline of steps:
<ol>
	<li><a href="#_Create_Management_Agent">Create the Management Agent Rules Extension</a></li>
	<li><a href="#_Update_Source_Active">Update Source Active Directory Management Agent</a></li>
	<li><a href="#_Update_Target_Active">Update Target Active Directory Management Agent</a></li>
	<li><a href="#_Rules_Extension_–">Visual Studio Solution – Add the code</a></li>
	<li><a href="#_Rules_Extension_–_1">Visual Studio Solution – Build the Solution</a></li>
	<li><a href="#_Rules_Extension_–_2">Visual Studio Solution – Copy the DLL</a></li>
	<li><a href="#_Additional_Information_/">Additional Information</a></li>
</ol>
<h1>Create Management Agent Rules Extension</h1>
Here we will walk through the steps to create a Management Agent Rules Extension.  The Management Agent Rules Extension will be where we read and update the proxyAddresses attribute as it flows through the Synchronization Service Engine.
<ol>
	<li>Open the Synchronization Service Manager Console and select Management Agents</li>
	<li>From the Actions menu select Create Extension Projects &gt; Rules Extension<a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/3247.actionsmenu.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/3247.actionsmenu.png" alt="" border="0" /></a>&nbsp;</li>
	<li>Create Extension Project Window<a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/1524.extensionwindow.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/1524.extensionwindow.png" alt="" border="0" /></a>
<ol>
	<li><strong>Programming Language</strong>: Visual Basic or Visual C#</li>
	<li><strong>Visual Studio Version</strong>: Choose your version of Visual Studio</li>
	<li><strong>Project Name</strong>: Name of your Management Agent Extension
(<em>For this illustration I am going to use the default RulesExtension</em>)</li>
	<li><strong>Project Location</strong>: where do you want to store the source code for this Rules Extension</li>
	<li><strong>Launch in VS.NET IDE</strong>: Default is checked.  Recommend to uncheck and open manually in Visual Studio</li>
</ol>
</li>
	<li>Once complete, click ok</li>
</ol>
<h1>Update Source Active Directory Management Agent</h1>
The source Active Directory Management Agent is where the object will start in the object flow.
<ol>
	<li>Open the Synchronization Service Manager Console and select Management Agents</li>
	<li>Select the Source Active Directory Management Agent</li>
	<li>From the Actions menu, select Properties and go to Configure Attribute Flow</li>
	<li>proxyAddresses attribute flow
<ol>
	<li>Mapping Type: Rules Extension</li>
</ol>
</li>
</ol>
<table style="width: 516px;height: 58px" border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td valign="top" width="623"><strong><em>Note</em></strong><em>: Recommend using a unique, easy to find Flow Rule Name. In this illustration I am using “proxyAddressUpdate”</em></td>
</tr>
</tbody>
</table>
&nbsp;
<p style="padding-left: 60px">b. Flow Direction: Import Attribute Flow</p>
<p style="padding-left: 60px"><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/8814.flowdirection.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/8814.flowdirection.png" alt="" border="0" /></a></p>
<p style="padding-left: 30px">5. Click Ok to go back to the Management Agent Properties Window</p>
<p style="padding-left: 30px">6. Select Configure Extensions and update the Rules Extension Name with the name of your DLL (The name of your project “.DLL”)</p>
<a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/6708.configureextensions.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/6708.configureextensions.png" alt="" border="0" /></a>
<p style="padding-left: 30px">7. Once updated, click Ok until you are back at the Synchronization Service Manager Console</p>
&nbsp;
<h1>Update Target Active Directory Management Agent</h1>
<ol>
	<li>Open the Synchronization Service Manager Console and select Management Agents</li>
	<li>Select the Target Active Directory Management Agent</li>
	<li>From the Actions menu, select Properties and go to Configure Attribute Flow</li>
	<li>proxyAddresses attribute flow
<ol>
	<li>Mapping Type: Direct</li>
	<li>Flow Direction: Export Attribute Flow<a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/0804.caf.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/0804.caf.png" alt="" border="0" /></a></li>
</ol>
</li>
	<li>Once updated, click Ok until you are
back at the Synchronization Service Manager Console</li>
</ol>
<h1>Rules Extension – Visual Studio Solution</h1>
It is recommended that you have Visual Studio on the Synchronization Service Manager Console, as it makes debugging easier if needed.
<ol>
	<li>Open the Microsoft Visual Studio Solution by navigating where you saved the solution and double click on the SLN file.  (SLN file = Visual Studio Solution File)<a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/5040.slnfile.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/5040.slnfile.png" alt="" border="0" /></a>&nbsp;</li>
	<li>Locate the function void IMASynchronization.MapAttributesForImport.
<ol>
	<li>We are using MapAttributesForImport so that the new values for the proxyAddresses attribute will be in the Metaverse Object.  Below you will find an example of the code utilized to review the proxyAddresses and change the primary SMTP based on mail suffix.<a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/0572.code.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/0572.code.png" alt="" border="0" /></a></li>
</ol>
</li>
</ol>
<h1>Rules Extension – Build Visual Studio Solution</h1>
<ol>
	<li>From the Project Menu select RulesExtension Properties ( this would be the name of your rules extension project )</li>
</ol>
<p style="padding-left: 60px"><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/4251.projectmenu.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/4251.projectmenu.png" alt="" border="0" /></a></p>
<p style="padding-left: 30px">2. Select Build and then click Browse beside Output Path</p>
<p style="padding-left: 60px"><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/3005.build.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/3005.build.png" alt="" border="0" /></a></p>
<p style="padding-left: 30px">3. By default, this will take you to the Extensions folder.  Here, create a new folder called New Rules Extension.</p>

<table style="padding-left: 30px" border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td valign="top" width="623">Note: If you already have a build path, simply create a folder for your new compiled project</td>
</tr>
</tbody>
</table>
<p style="padding-left: 30px">4. Double click on the new folder and then click the Select Folder button in the lower right</p>
<p style="padding-left: 30px">5. From the Build menu select Build Solution</p>
<p style="padding-left: 60px"><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/4174.buildmenu.png"><img src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/4174.buildmenu.png" alt="" border="0" /></a></p>

<h1>Rules Extension – Copy the DLL to the Extensions Folder</h1>
<ul>
	<li>Navigate to the %programfiles%\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions folder</li>
	<li>Create a new folder called Rules Extension Backup
<ol>
	<li>It is always important to back up your existing rules extension.  If you were to have a problem with a new DLL then you will be able to rollback fairly easily.</li>
	<li>Copy the Existing DLL, if you have one, to the Rules Extension Backup folder</li>
	<li>Copy the New DLL from the New Rules Extension Folder that you created in the previous section to the Extensions folder.</li>
	<li>Now you are ready to test</li>
</ol>
</li>
</ul>
<h1>Additional Information / Resources</h1>
<ul>
	<li> <strong>How to create a Management Agent Rules Extension</strong>: <a href="https://msdn.microsoft.com/en-us/library/windows/desktop/ms695365%28v=vs.100%29.aspx">https://msdn.microsoft.com/en-us/library/windows/desktop/ms695365%28v=vs.100%29.aspx</a></li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>Support-Tip (MIISACTIVATE.EXE): Logon failure: the user has not been granted the requested logon type at this computer</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/info-miisactivate-logon-failure-the-user-has-not-been-granted-the-requested-logon-type-at-this-computer</link>
      <pubDate>Wed, 12 Aug 2015 15:46:51 GMT</pubDate>
      <dc:creator><![CDATA[Tim Macaulay]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/2015/08/12/info-miisactivate-logon-failure-the-user-has-not-been-granted-the-requested-logon-type-at-this-computer/</guid>
      <description><![CDATA[PRODUCT FOCUS

 	Microsoft Identity Manager Synchronization Service 2016
 	Forefront Identity...]]></description>
      <content:encoded><![CDATA[<h2><strong>PRODUCT FOCUS</strong></h2>
<ul>
 	<li>Microsoft Identity Manager Synchronization Service 2016</li>
 	<li>Forefront Identity Manager Synchronization Service 2010</li>
</ul>
&nbsp;
<table>
<tbody>
<tr>
<td><span style="text-decoration: underline"><strong>NOTE</strong></span></td>
<td><span style="color: #999999">MIISACTIVATE.EXE has been around since the days of Microsoft Identity Integration Server 2003 and has had it's single focus of activating a new Synchronization Server Client with the backend Synchronization Service Database.</span>

<span style="color: #999999">I mention this, because I be using a later version of the product to test, but this tool is supported with versions of the Synchronization Service dating back to MIIS 2003.</span></td>
</tr>
</tbody>
</table>
<h2></h2>
<h2><strong>PROBLEM SCENARIO DESCRIPTION</strong></h2>
<p style="padding-left: 30px">You attempt to run the MIISACTIVATE.EXE command-line to activate a new FIM Synchronization Service Server.  In doing so, you receive the below error message.</p>

<h2><strong>ERROR MESSAGE</strong></h2>
<p style="padding-left: 30px">The operation encountered am error and cannot be completed.</p>
<p style="padding-left: 30px">Error: Logon failure: the user has not been granted the requested
logon type at this computer</p>
<p style="padding-left: 30px">Error Code 569</p>

<h2 style="padding-left: 30px"><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/8345.ERROR.png"><img alt="" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/8345.ERROR.png" border="0" /></a></h2>
<h2><strong>CAUSE</strong></h2>
<p style="padding-left: 30px">The Synchronization Service Account is in the Local Security Policy &gt; Local Policies &gt; User Rights Assignment &gt; Deny log on as a service.</p>

<h2 style="padding-left: 30px"><a href="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/3632.DENYLOGOONASSERVICE.png"><img alt="" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/3632.DENYLOGOONASSERVICE.png" border="0" /></a></h2>
<h2><strong>RESOLUTION</strong></h2>
<ol>
 	<li>Remove the FIM Synchronization Service Account from the Local Security Policy</li>
 	<li>Execute the MIISACTIVATE.EXE command-line</li>
 	<li>After success add the FIM Synchronization Service Account back to the Local Security Policy</li>
</ol>
<h3 style="padding-left: 30px"><strong>LOCAL SECURITY POLICY</strong></h3>
<ul>
 	<li style="padding-left: 30px">Local Security Policy &gt; Local Policies &gt; User Rights Assignment &gt; Deny log on as a service</li>
</ul>
&nbsp;
<h2><strong>ADDITIONAL INFORMATION</strong></h2>
<ul>
 	<li><strong>MIISActivate: Server Activation Tool:</strong> https://technet.microsoft.com/en-us/library/jj590194(v=ws.10).aspx</li>
</ul>]]></content:encoded>
    </item>
    <item>
      <title>[HOTFIX] A new hotfix rollup package is available for Microsoft Forefront Identity Manager 2010 R2 SP1</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/a-new-hotfix-rollup-package-is-available-for-microsoft-forefront-identity-manager-2010-r2-sp1</link>
      <pubDate>Wed, 06 May 2015 10:58:39 GMT</pubDate>
      <dc:creator><![CDATA[Tim Macaulay]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/2015/05/06/a-new-hotfix-rollup-package-is-available-for-microsoft-forefront-identity-manager-2010-r2-sp1/</guid>
      <description><![CDATA[A hotfix rollup package (build 4.1.3634.0) is available for Microsoft Forefront Identity Manager...]]></description>
      <content:encoded><![CDATA[<a href="https://support.microsoft.com/en-us/kb/3048056/" target="_blank"><img style="float: left;padding-top: 0px;padding-left: 0px;padding-right: 0px;border-width: 0px" title="HF2" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/metablogapi/5037.HF2_2EAD5383.png" alt="HF2" width="100" height="100" align="left" border="0" /></a>A hotfix rollup package (build <strong>4.1.3634.0</strong>) is available for Microsoft Forefront Identity Manager 2010 R2 Service Pack 1 (FIM 2010 R2 SP1). The build number for BHOLD components that are included in this release is <strong>5.0.2959.0</strong>. This hotfix rollup package resolves some issues and adds some features that are described in the article below.

<a href="https://support.microsoft.com/en-us/kb/3048056/" target="_blank">3048056</a> - A hotfix rollup package (build 4.1.3634.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2 SP1 (<a title="https://support.microsoft.com/en-us/kb/3048056/" href="https://support.microsoft.com/en-us/kb/3048056/">https://support.microsoft.com/en-us/kb/3048056/</a>)

<strong>J.C. Hornbeck</strong> <strong>| Solution Asset PM | Microsoft GBS Management and Security Division</strong>

<strong><span style="color: #c0504d">Get the latest System Center news on</span> </strong><a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><strong>Facebook</strong></a><strong> <span style="color: #c0504d">and</span> </strong><a href="https://twitter.com/#!/MS_SystemCenter"><strong>Twitter</strong></a><strong>:</strong>

<a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><img title="clip_image001" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image001_64a4101d-1898-43ad-8493-b15123a8f037.gif" alt="clip_image001" width="89" height="21" border="0" /></a> <a href="https://www.twitter.com/MS_SystemCenter"><img title="clip_image002" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image002_e463ef66-6372-4614-ad1b-a2e20e16de5f.gif" alt="clip_image002" width="89" height="21" border="0" /></a>

System Center All Up: <a href="https://blogs.technet.com/b/systemcenter/">https://blogs.technet.com/b/systemcenter/</a>

Configuration Manager Support Team blog: <a href="https://blogs.technet.com/configurationmgr/">https://blogs.technet.com/configurationmgr/</a>
Data Protection Manager Team blog: <a href="https://blogs.technet.com/dpm/">https://blogs.technet.com/dpm/</a>
Orchestrator Support Team blog: <a href="https://blogs.technet.com/b/orchestrator/">https://blogs.technet.com/b/orchestrator/</a>
Operations Manager Team blog: <a href="https://blogs.technet.com/momteam/">https://blogs.technet.com/momteam/</a>
Service Manager Team blog: <a href="https://blogs.technet.com/b/servicemanager">https://blogs.technet.com/b/servicemanager</a>
Virtual Machine Manager Team blog: <a href="https://blogs.technet.com/scvmm">https://blogs.technet.com/scvmm</a>

Microsoft Intune: <a href="https://blogs.technet.com/b/microsoftintune/">https://blogs.technet.com/b/microsoftintune/</a>
WSUS Support Team blog: <a href="https://blogs.technet.com/sus/">https://blogs.technet.com/sus/</a>
The RMS blog: <a href="https://blogs.technet.com/b/rms/">https://blogs.technet.com/b/rms/</a>
App-V Team blog: <a href="https://blogs.technet.com/appv/">https://blogs.technet.com/appv/</a>
MED-V Team blog: <a href="https://blogs.technet.com/medv/">https://blogs.technet.com/medv/</a>
Server App-V Team blog: <a href="https://blogs.technet.com/b/serverappv">https://blogs.technet.com/b/serverappv</a>
The Surface Team blog: <a href="https://blogs.technet.com/b/surface/">https://blogs.technet.com/b/surface/</a>
The Application Proxy blog: <a href="https://blogs.technet.com/b/applicationproxyblog/">https://blogs.technet.com/b/applicationproxyblog/</a>

The Forefront Endpoint Protection blog : <a href="https://blogs.technet.com/b/clientsecurity/">https://blogs.technet.com/b/clientsecurity/</a>
The Forefront Identity Manager blog : <a href="https://blogs.msdn.com/b/ms-identity-support/">https://blogs.msdn.com/b/ms-identity-support/</a>
The Forefront TMG blog: <a href="https://blogs.technet.com/b/isablog/">https://blogs.technet.com/b/isablog/</a>
The Forefront UAG blog: <a href="https://blogs.technet.com/b/edgeaccessblog/">https://blogs.technet.com/b/edgeaccessblog/</a>]]></content:encoded>
    </item>
    <item>
      <title>[HOTFIX] A FIM 2010 R2 hotfix rollup is now available for the Generic LDAP connector</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/a-fim-2010-r2-hotfix-rollup-is-now-available-for-the-generic-ldap-connector</link>
      <pubDate>Wed, 29 Oct 2014 09:08:53 GMT</pubDate>
      <dc:creator><![CDATA[Tim Macaulay]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/2014/10/29/a-fim-2010-r2-hotfix-rollup-is-now-available-for-the-generic-ldap-connector/</guid>
      <description><![CDATA[A new hotfix rollup package is available for Microsoft Forefront Identity Manager 2010 R2. This...]]></description>
      <content:encoded><![CDATA[<a href="https://support.microsoft.com/kb/3008177"><img style="float: left;padding-top: 0px;padding-left: 0px;padding-right: 0px;border-width: 0px" title="Hotfix160_thumb23" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/metablogapi/3302.Hotfix160_thumb23_7961C2AB.jpg" alt="Hotfix160_thumb23" width="100" height="100" align="left" border="0" /></a>

A new hotfix rollup package is available for Microsoft Forefront Identity Manager 2010 R2. This hotfix rollup package resolves some Generic LDAP connector issues and adds some additional new features and functionality. These additions are described in the "More Information" section of the article below.

For all the latest details and a down load link, please see the following:

<a href="https://support.microsoft.com/kb/3008177">KB3008177</a> - A hotfix rollup (build 1.0.419.911) is available for the Generic LDAP connector (<a href="https://support.microsoft.com/kb/3008177">https://support.microsoft.com/kb/3008177</a>)

<b>J.C. Hornbeck</b> <strong>| Solution Asset PM | Microsoft GBS Management and Security Division</strong>

<b><span style="color: #c0504d">Get the latest System Center news on</span> </b><a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><b>Facebook</b></a><b> <span style="color: #c0504d">and</span> </b><a href="https://twitter.com/#!/MS_SystemCenter"><b>Twitter</b></a><b>:</b>

<a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><img title="clip_image001" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image001_64a4101d-1898-43ad-8493-b15123a8f037.gif" alt="clip_image001" width="89" height="21" border="0" /></a> <a href="https://www.twitter.com/MS_SystemCenter"><img title="clip_image002" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image002_e463ef66-6372-4614-ad1b-a2e20e16de5f.gif" alt="clip_image002" width="89" height="21" border="0" /></a>

System Center All Up: <a href="https://blogs.technet.com/b/systemcenter/">https://blogs.technet.com/b/systemcenter/</a>
System Center – Configuration Manager Support Team blog: <a href="https://blogs.technet.com/configurationmgr/">https://blogs.technet.com/configurationmgr/</a>
System Center – Data Protection Manager Team blog: <a href="https://blogs.technet.com/dpm/">https://blogs.technet.com/dpm/</a>
System Center – Orchestrator Support Team blog: <a href="https://blogs.technet.com/b/orchestrator/">https://blogs.technet.com/b/orchestrator/</a>
System Center – Operations Manager Team blog: <a href="https://blogs.technet.com/momteam/">https://blogs.technet.com/momteam/</a>
System Center – Service Manager Team blog: <a href="https://blogs.technet.com/b/servicemanager">https://blogs.technet.com/b/servicemanager</a>
System Center – Virtual Machine Manager Team blog: <a href="https://blogs.technet.com/scvmm">https://blogs.technet.com/scvmm</a>

Windows Intune: <a href="https://blogs.technet.com/b/windowsintune/">https://blogs.technet.com/b/windowsintune/</a>
WSUS Support Team blog: <a href="https://blogs.technet.com/sus/">https://blogs.technet.com/sus/</a>
The RMS blog: <a href="https://blogs.technet.com/b/rms/">https://blogs.technet.com/b/rms/</a>

App-V Team blog: <a href="https://blogs.technet.com/appv/">https://blogs.technet.com/appv/</a>
MED-V Team blog: <a href="https://blogs.technet.com/medv/">https://blogs.technet.com/medv/</a>
Server App-V Team blog: <a href="https://blogs.technet.com/b/serverappv">https://blogs.technet.com/b/serverappv</a>

The Forefront Endpoint Protection blog : <a href="https://blogs.technet.com/b/clientsecurity/">https://blogs.technet.com/b/clientsecurity/</a>
The Forefront Identity Manager blog : <a href="https://blogs.msdn.com/b/ms-identity-support/">https://blogs.msdn.com/b/ms-identity-support/</a>
The Forefront TMG blog: <a href="https://blogs.technet.com/b/isablog/">https://blogs.technet.com/b/isablog/</a>
The Forefront UAG blog: <a href="https://blogs.technet.com/b/edgeaccessblog/">https://blogs.technet.com/b/edgeaccessblog/</a>]]></content:encoded>
    </item>
    <item>
      <title>[HOTFIX] New hotfix available to fix PowerShell connector issue in FIM 2010 R2</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/new-hotfix-available-to-fix-powershell-connector-issue-in-fim-2010-r2</link>
      <pubDate>Thu, 23 Oct 2014 13:39:04 GMT</pubDate>
      <dc:creator><![CDATA[Tim Macaulay]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/2014/10/23/new-hotfix-available-to-fix-powershell-connector-issue-in-fim-2010-r2/</guid>
      <description><![CDATA[A hotfix rollup package (build 1.0.419.911) is available for Microsoft Forefront Identity...]]></description>
      <content:encoded><![CDATA[<a href="https://support2.microsoft.com/kb/3008179"><img style="float: left;padding-top: 0px;padding-left: 0px;padding-right: 0px;border-width: 0px" title="Hotfix160_thumb2" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/metablogapi/6560.Hotfix160_thumb2_1175E7FF.jpg" alt="Hotfix160_thumb2" width="100" height="100" align="left" border="0" /></a>

A hotfix rollup package (build <b>1.0.419.911</b>) is available for Microsoft Forefront Identity Manager 2010 R2. This hotfix rollup package resolves a PowerShell connector issue and adds one feature as well as new functionality. These additions are described in the "More Information" section of the article below.

For all the latest details and a down load link, please see the following:

<a href="https://support.microsoft.com/kb/3008179">KB3008179</a> - A hotfix rollup (build 1.0.419.911) is available for a PowerShell connector issue (<a href="https://support.microsoft.com/kb/3008179">https://support.microsoft.com/kb/3008179</a>)

<b>J.C. Hornbeck</b> <strong>| Solution Asset PM | Microsoft GBS Management and Security Division</strong>

<b><span style="color: #c0504d">Get the latest System Center news on</span> </b><a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><b>Facebook</b></a><b> <span style="color: #c0504d">and</span> </b><a href="https://twitter.com/#!/MS_SystemCenter"><b>Twitter</b></a><b>:</b>

<a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><img title="clip_image001" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image001_64a4101d-1898-43ad-8493-b15123a8f037.gif" alt="clip_image001" width="89" height="21" border="0" /></a> <a href="https://www.twitter.com/MS_SystemCenter"><img title="clip_image002" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image002_e463ef66-6372-4614-ad1b-a2e20e16de5f.gif" alt="clip_image002" width="89" height="21" border="0" /></a>

System Center All Up: <a href="https://blogs.technet.com/b/systemcenter/">https://blogs.technet.com/b/systemcenter/</a>
System Center – Configuration Manager Support Team blog: <a href="https://blogs.technet.com/configurationmgr/">https://blogs.technet.com/configurationmgr/</a>
System Center – Data Protection Manager Team blog: <a href="https://blogs.technet.com/dpm/">https://blogs.technet.com/dpm/</a>
System Center – Orchestrator Support Team blog: <a href="https://blogs.technet.com/b/orchestrator/">https://blogs.technet.com/b/orchestrator/</a>
System Center – Operations Manager Team blog: <a href="https://blogs.technet.com/momteam/">https://blogs.technet.com/momteam/</a>
System Center – Service Manager Team blog: <a href="https://blogs.technet.com/b/servicemanager">https://blogs.technet.com/b/servicemanager</a>
System Center – Virtual Machine Manager Team blog: <a href="https://blogs.technet.com/scvmm">https://blogs.technet.com/scvmm</a>

Windows Intune: <a href="https://blogs.technet.com/b/windowsintune/">https://blogs.technet.com/b/windowsintune/</a>
WSUS Support Team blog: <a href="https://blogs.technet.com/sus/">https://blogs.technet.com/sus/</a>
The RMS blog: <a href="https://blogs.technet.com/b/rms/">https://blogs.technet.com/b/rms/</a>

App-V Team blog: <a href="https://blogs.technet.com/appv/">https://blogs.technet.com/appv/</a>
MED-V Team blog: <a href="https://blogs.technet.com/medv/">https://blogs.technet.com/medv/</a>
Server App-V Team blog: <a href="https://blogs.technet.com/b/serverappv">https://blogs.technet.com/b/serverappv</a>

The Forefront Endpoint Protection blog : <a href="https://blogs.technet.com/b/clientsecurity/">https://blogs.technet.com/b/clientsecurity/</a>
The Forefront Identity Manager blog : <a href="https://blogs.msdn.com/b/ms-identity-support/">https://blogs.msdn.com/b/ms-identity-support/</a>
The Forefront TMG blog: <a href="https://blogs.technet.com/b/isablog/">https://blogs.technet.com/b/isablog/</a>
The Forefront UAG blog: <a href="https://blogs.technet.com/b/edgeaccessblog/">https://blogs.technet.com/b/edgeaccessblog/</a>]]></content:encoded>
    </item>
    <item>
      <title>[HOTFIX] New FIM 2010 R2 hotfix for the WebServices connector</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/new-fim-2010-r2-hotfix-for-the-webservices-connector</link>
      <pubDate>Thu, 23 Oct 2014 13:16:15 GMT</pubDate>
      <dc:creator><![CDATA[Tim Macaulay]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/2014/10/23/new-fim-2010-r2-hotfix-for-the-webservices-connector/</guid>
      <description><![CDATA[A hotfix rollup package is available for Microsoft Forefront Identity Manager 2010 R2. This...]]></description>
      <content:encoded><![CDATA[<a href="https://support2.microsoft.com/kb/3008178"><img style="float: left;padding-top: 0px;padding-left: 0px;padding-right: 0px;border: 0px" title="Hotfix160_thumb2[3]" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/metablogapi/1121.Hotfix160_thumb23_2502224D.jpg" alt="Hotfix160_thumb2[3]" width="100" height="100" align="left" border="0" /></a>

A hotfix rollup package is available for Microsoft Forefront Identity Manager 2010 R2. This hotfix rollup package resolves some WebServices connector issues and adds some features as well as new functionality. These are described in the article below.

For all the latest details and a down load link, please see the following:

<a href="https://support.microsoft.com/kb/3008178">KB3008178</a> - A hotfix rollup (build 1.0.419.911) is available for the WebServices connector (<a href="https://support.microsoft.com/kb/3008178">https://support.microsoft.com/kb/3008178</a>)

<b>J.C. Hornbeck</b> <strong>| Solution Asset PM | Microsoft GBS Management and Security Division</strong>

<b><span style="color: #c0504d">Get the latest System Center news on</span> </b><a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><b>Facebook</b></a><b> <span style="color: #c0504d">and</span> </b><a href="https://twitter.com/#!/MS_SystemCenter"><b>Twitter</b></a><b>:</b>

<a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><img title="clip_image001" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image001_64a4101d-1898-43ad-8493-b15123a8f037.gif" alt="clip_image001" width="89" height="21" border="0" /></a> <a href="https://www.twitter.com/MS_SystemCenter"><img title="clip_image002" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image002_e463ef66-6372-4614-ad1b-a2e20e16de5f.gif" alt="clip_image002" width="89" height="21" border="0" /></a>

System Center All Up: <a href="https://blogs.technet.com/b/systemcenter/">https://blogs.technet.com/b/systemcenter/</a>
System Center – Configuration Manager Support Team blog: <a href="https://blogs.technet.com/configurationmgr/">https://blogs.technet.com/configurationmgr/</a>
System Center – Data Protection Manager Team blog: <a href="https://blogs.technet.com/dpm/">https://blogs.technet.com/dpm/</a>
System Center – Orchestrator Support Team blog: <a href="https://blogs.technet.com/b/orchestrator/">https://blogs.technet.com/b/orchestrator/</a>
System Center – Operations Manager Team blog: <a href="https://blogs.technet.com/momteam/">https://blogs.technet.com/momteam/</a>
System Center – Service Manager Team blog: <a href="https://blogs.technet.com/b/servicemanager">https://blogs.technet.com/b/servicemanager</a>
System Center – Virtual Machine Manager Team blog: <a href="https://blogs.technet.com/scvmm">https://blogs.technet.com/scvmm</a>

Windows Intune: <a href="https://blogs.technet.com/b/windowsintune/">https://blogs.technet.com/b/windowsintune/</a>
WSUS Support Team blog: <a href="https://blogs.technet.com/sus/">https://blogs.technet.com/sus/</a>
The RMS blog: <a href="https://blogs.technet.com/b/rms/">https://blogs.technet.com/b/rms/</a>

App-V Team blog: <a href="https://blogs.technet.com/appv/">https://blogs.technet.com/appv/</a>
MED-V Team blog: <a href="https://blogs.technet.com/medv/">https://blogs.technet.com/medv/</a>
Server App-V Team blog: <a href="https://blogs.technet.com/b/serverappv">https://blogs.technet.com/b/serverappv</a>

The Forefront Endpoint Protection blog : <a href="https://blogs.technet.com/b/clientsecurity/">https://blogs.technet.com/b/clientsecurity/</a>
The Forefront Identity Manager blog : <a href="https://blogs.msdn.com/b/ms-identity-support/">https://blogs.msdn.com/b/ms-identity-support/</a>
The Forefront TMG blog: <a href="https://blogs.technet.com/b/isablog/">https://blogs.technet.com/b/isablog/</a>
The Forefront UAG blog: <a href="https://blogs.technet.com/b/edgeaccessblog/">https://blogs.technet.com/b/edgeaccessblog/</a>]]></content:encoded>
    </item>
    <item>
      <title>[HOTFIX] A new hotfix rollup (build 4.1.3559.0) is available for Forefront Identity Manager 2010 R2</title>
      <link>https://docs.microsoft.com/archive/blogs/ms-identity-support/a-new-hotfix-rollup-build-4-1-3559-0-is-available-for-forefront-identity-manager-2010-r2</link>
      <pubDate>Wed, 18 Jun 2014 11:28:24 GMT</pubDate>
      <dc:creator><![CDATA[Tim Macaulay]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.msdn.microsoft.com/ms-identity-support/2014/06/18/a-new-hotfix-rollup-build-4-1-3559-0-is-available-for-forefront-identity-manager-2010-r2/</guid>
      <description><![CDATA[A hotfix rollup package (build 4.1.3559.0) is available for Microsoft Forefront Identity Manager...]]></description>
      <content:encoded><![CDATA[<a href="https://support.microsoft.com/kb/2969673"><img style="float: left;padding-top: 0px;padding-left: 0px;padding-right: 0px;border-width: 0px" title="Hotfix160_thumb2" src="https://msdnshared.blob.core.windows.net/media/MSDNBlogsFS/prod.evol.blogs.msdn.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/23/97/metablogapi/2502.Hotfix160_thumb2_5DE04E8C.jpg" alt="Hotfix160_thumb2" width="100" height="100" align="left" border="0" /></a>A hotfix rollup package (build 4.1.3559.0) is available for Microsoft Forefront Identity Manager 2010 R2 (FIM 2012 R2). This hotfix rollup package resolves some issues and adds some features that are described in the article below.

For all the details as well as download instructions, please see the following:

<a href="https://support.microsoft.com/kb/2969673">KB2969673</a> - A hotfix rollup (build 4.1.3559.0) is available for Forefront Identity Manager 2010 R2 (<a href="https://support.microsoft.com/kb/2969673">https://support.microsoft.com/kb/2969673</a>)

<b>J.C. Hornbeck</b> <strong>| Solution Asset PM | Microsoft GBS Management and Security Division</strong>

<b><span style="color: #c0504d">Get the latest System Center news on</span> </b><a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><b>Facebook</b></a><b> <span style="color: #c0504d">and</span> </b><a href="https://twitter.com/#!/MS_SystemCenter"><b>Twitter</b></a><b>:</b>

<a href="https://www.facebook.com/pages/Microsoft-System-Center-Support/111513322193410"><img title="clip_image001" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image001_64a4101d-1898-43ad-8493-b15123a8f037.gif" alt="clip_image001" width="89" height="21" border="0" /></a> <a href="https://www.twitter.com/MS_SystemCenter"><img title="clip_image002" src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/BlogFileStorage/blogs_technet/medv/WindowsLiveWriter/MEDVPrintingOptionsandIssuesyoumayencoun_8540/clip_image002_e463ef66-6372-4614-ad1b-a2e20e16de5f.gif" alt="clip_image002" width="89" height="21" border="0" /></a>

System Center All Up: <a href="https://blogs.technet.com/b/systemcenter/">https://blogs.technet.com/b/systemcenter/</a>
System Center – Configuration Manager Support Team blog: <a href="https://blogs.technet.com/configurationmgr/">https://blogs.technet.com/configurationmgr/</a>
System Center – Data Protection Manager Team blog: <a href="https://blogs.technet.com/dpm/">https://blogs.technet.com/dpm/</a>
System Center – Orchestrator Support Team blog: <a href="https://blogs.technet.com/b/orchestrator/">https://blogs.technet.com/b/orchestrator/</a>
System Center – Operations Manager Team blog: <a href="https://blogs.technet.com/momteam/">https://blogs.technet.com/momteam/</a>
System Center – Service Manager Team blog: <a href="https://blogs.technet.com/b/servicemanager">https://blogs.technet.com/b/servicemanager</a>
System Center – Virtual Machine Manager Team blog: <a href="https://blogs.technet.com/scvmm">https://blogs.technet.com/scvmm</a>

Windows Intune: <a href="https://blogs.technet.com/b/windowsintune/">https://blogs.technet.com/b/windowsintune/</a>
WSUS Support Team blog: <a href="https://blogs.technet.com/sus/">https://blogs.technet.com/sus/</a>
The AD RMS blog: <a href="https://blogs.technet.com/b/rmssupp/">https://blogs.technet.com/b/rmssupp/</a>

App-V Team blog: <a href="https://blogs.technet.com/appv/">https://blogs.technet.com/appv/</a>
MED-V Team blog: <a href="https://blogs.technet.com/medv/">https://blogs.technet.com/medv/</a>
Server App-V Team blog: <a href="https://blogs.technet.com/b/serverappv">https://blogs.technet.com/b/serverappv</a>

The Forefront Endpoint Protection blog : <a href="https://blogs.technet.com/b/clientsecurity/">https://blogs.technet.com/b/clientsecurity/</a>
The Forefront Identity Manager blog : <a href="https://blogs.msdn.com/b/ms-identity-support/">https://blogs.msdn.com/b/ms-identity-support/</a>
The Forefront TMG blog: <a href="https://blogs.technet.com/b/isablog/">https://blogs.technet.com/b/isablog/</a>
The Forefront UAG blog: <a href="https://blogs.technet.com/b/edgeaccessblog/">https://blogs.technet.com/b/edgeaccessblog/</a>]]></content:encoded>
    </item>
  </channel>
</rss>