//Build// Code on Weekend // Reach out if any one want to share cool FIM/MIM, IAM related Project. Mail : Any.Singha@gmail.com
Showing posts with label FIM 2010. Show all posts
Showing posts with label FIM 2010. Show all posts
Wednesday, 13 May 2020
Monday, 16 March 2020
How to add Owner to FIM Group (Powershell)
How to add display Owner to FIM Group (Powershell) , when the requirement is to add multiple owner from a txt file, the below is sample script which can be tweak.
<#-----------------------------------------------
Author : Anirban
----------------------------------------------- #>
If(@(Get-PSSnapin | Where-Object {$_.Name -eq "FIMAutomation"} ).count -eq 0) {Add-PSSnapin FIMAutomation}
$groupObject = Export-FIMConfig -customConfig "/Group[DisplayName = 'DisplayNameoftheGroup']" -Uri "http://localhost:5725" -OnlyBaseResources
$userObject = Export-FIMConfig -Uri http://localhost:5725 -onlyBaseResources -customConfig "/Person[DisplayName = 'DisplayNameoftheOwner']"
$importChange = New-Object Microsoft.ResourceManagement.Automation.ObjectModel.ImportChange
$importChange.Operation = 0
$importChange.AttributeName = "Owner"
$importChange.AttributeValue = $userObject.ResourceManagementObject.ObjectIdentifier
$importChange.FullyResolved = 0
$importChange.Locale = "Invariant"
$importObject = New-Object Microsoft.ResourceManagement.Automation.ObjectModel.ImportObject
$importObject.ObjectType = "Group"
$importObject.TargetObjectIdentifier = $groupObject.ResourceManagementObject.ObjectIdentifier
$importObject.SourceObjectIdentifier = $groupObject.ResourceManagementObject.ObjectIdentifier
$importObject.State = 1
$ImportObject.Changes = (,$ImportChange)
$importObject | Import-FIMConfig -Uri http://localhost:5725
<#-----------------------------------------------
Author : Anirban
----------------------------------------------- #>
If(@(Get-PSSnapin | Where-Object {$_.Name -eq "FIMAutomation"} ).count -eq 0) {Add-PSSnapin FIMAutomation}
$groupObject = Export-FIMConfig -customConfig "/Group[DisplayName = 'DisplayNameoftheGroup']" -Uri "http://localhost:5725" -OnlyBaseResources
$userObject = Export-FIMConfig -Uri http://localhost:5725 -onlyBaseResources -customConfig "/Person[DisplayName = 'DisplayNameoftheOwner']"
$importChange = New-Object Microsoft.ResourceManagement.Automation.ObjectModel.ImportChange
$importChange.Operation = 0
$importChange.AttributeName = "Owner"
$importChange.AttributeValue = $userObject.ResourceManagementObject.ObjectIdentifier
$importChange.FullyResolved = 0
$importChange.Locale = "Invariant"
$importObject = New-Object Microsoft.ResourceManagement.Automation.ObjectModel.ImportObject
$importObject.ObjectType = "Group"
$importObject.TargetObjectIdentifier = $groupObject.ResourceManagementObject.ObjectIdentifier
$importObject.SourceObjectIdentifier = $groupObject.ResourceManagementObject.ObjectIdentifier
$importObject.State = 1
$ImportObject.Changes = (,$ImportChange)
$importObject | Import-FIMConfig -Uri http://localhost:5725
Sunday, 9 October 2016
FIM 2010 R2 to MIM 2016 InPlace Upgrade [ excluded service and portal ]
As most of our FIM infrastructure is in Server 2008 R2, It always a business decision whether we are doing in place upgrade or migrate it over to totally new Server 2012.
FIM 2010 R2 to MIM 2016 InPlace Upgrade [ excluded service and portal ]
1. Snapshot of VM
2. Back up of your database
3. .Net framework of 4 or higher is supported by MIM, if it is not there make sure it is upgraded to 4 or higher version.
4. Change the compatibility level of SQL to 100 using SQL Management Studio.
5. Backup the encryption key
It is very important to back up the encryption key if you plan to use the existing database. The reason for this is that the server configuration, extension DLLs and other vital information is stored in the database. It will make life much easier in your migration upgrade.
6. Backup the extensions folder
This is not absolutely necessary unless you plan to start with a clean database. The extension DLLs are actually stored in the backend database as well as the extensions folder. If you backed up the encryption key before moving or restoring the existing database from FIM, then these DLLs will be re-populated into the extensions folder.
If for some reason you do not see the DLLs, then utilize your backup of the previous extensions folder to repopulate your Extensions.
7. Backup the source code.
Nowhere it is mentioned to uninstall the FIM , if you are doing a inplace upgrade you have to uninstall the FIM from Control Panel\All Control Panel Items\Programs and Features.
Once the FIM software uninstalled restart the server.
Navigate to the location of the Installation files for MIM 2016 Synchronization Service and begin the installation.
While installing point your SQL server instance to FIM Synchronization database of FIM and steps are same like FIM installation however the installer will discover the FIMSynchronization database and asked for the encryption key.After entering the Key it will start rebuilding your index and FIM will upgrade to MIM.
Please do test all your logic and upgradation in Test before moving to production.
All the Best..!!
FIM 2010 R2 to MIM 2016 InPlace Upgrade [ excluded service and portal ]
1. Snapshot of VM
2. Back up of your database
3. .Net framework of 4 or higher is supported by MIM, if it is not there make sure it is upgraded to 4 or higher version.
4. Change the compatibility level of SQL to 100 using SQL Management Studio.
5. Backup the encryption key
It is very important to back up the encryption key if you plan to use the existing database. The reason for this is that the server configuration, extension DLLs and other vital information is stored in the database. It will make life much easier in your migration upgrade.
6. Backup the extensions folder
This is not absolutely necessary unless you plan to start with a clean database. The extension DLLs are actually stored in the backend database as well as the extensions folder. If you backed up the encryption key before moving or restoring the existing database from FIM, then these DLLs will be re-populated into the extensions folder.
If for some reason you do not see the DLLs, then utilize your backup of the previous extensions folder to repopulate your Extensions.
7. Backup the source code.
Nowhere it is mentioned to uninstall the FIM , if you are doing a inplace upgrade you have to uninstall the FIM from Control Panel\All Control Panel Items\Programs and Features.
Once the FIM software uninstalled restart the server.
Navigate to the location of the Installation files for MIM 2016 Synchronization Service and begin the installation.
While installing point your SQL server instance to FIM Synchronization database of FIM and steps are same like FIM installation however the installer will discover the FIMSynchronization database and asked for the encryption key.After entering the Key it will start rebuilding your index and FIM will upgrade to MIM.
Please do test all your logic and upgradation in Test before moving to production.
All the Best..!!
Sunday, 3 July 2016
FIM SQL Group Membership
Do you love SQL and not in favour to invoke powershell Script to get the list of membership of the group in AD ? and want to find the membership of the group in SQL.
And there are SQL query to find the group mebership of FIM Group.
Just run the below SQL query, the name of the group is grouptest.
And there are SQL query to find the group mebership of FIM Group.
Just run the below SQL query, the name of the group is grouptest.
select
displayName,employeeID from
mms_metaverse where object_id
in ( select reference_id
from mms_mv_link where
attribute_name ='member'
and object_id
in (select object_id from
mms_metaverse where displayname in ('grouptest')))
Thanks
Saturday, 4 June 2016
ECMA : Get-Schema
Writing my first ECMA connectors with Webservice [ Get-Schema ] ... The road was not easy for a admin to write code or to build connectors for the webservice, During this process I picked C# book and learn the content of Interface and Webservice. For beginer it is recomded to learn the below topic before witing the code.
1. Interface
2. How to call a webservice C#.
Get Schema , While building the connector we have to write the schema.Schema may be define as the field or property of the connector.
The below is the schema code, I hope it help some one in writing the schema of the connectors who want to learn how to build the connector in FIM or MIM.
Here I have two property or filed "FirstNAme" and "SecondName".
The field or Attribute in the connector
Thats all... for today,.. Happy Coding.
1. Interface
2. How to call a webservice C#.
Get Schema , While building the connector we have to write the schema.Schema may be define as the field or property of the connector.
The below is the schema code, I hope it help some one in writing the schema of the connectors who want to learn how to build the connector in FIM or MIM.
Here I have two property or filed "FirstNAme" and "SecondName".
The field or Attribute in the connector
Thats all... for today,.. Happy Coding.
Wednesday, 24 February 2016
Saturday, 11 July 2015
NewBee Post for sharepoint in Installation of FIM Portal 2010
> As a NewBee to FIM the hardest part is to configure the sharepoint for the FIM portal, The below are not the best practise.However it will give you an fair idea how to install at the first go, I have skipped the installation for FIM portal. It will only show how you have configure your sharepoint site.
> My Machine name is NewBee and domain joined.
>Install the sharepoint site from the internet.
Sunday, 5 October 2014
Sync Error Series - An object with DN "CN=" already exists in management agent
Note : This series is for the Beginner and trouble shooting the Error With Sync Engine, Based on Test Lab, Highly advice do not do Full Sync of the Management Agent. Errors are Fun, Debug It...!!
The Management Agent Run and see the error message in the Stack information.
"Microsoft.MetadirectoryServices.ObjectAlreadyExistsException: An object with DN "CN=4,OU=FIMOU,DC=corp,DC=fim2010,DC=com" already exists in management agent "ADMATest".
at Microsoft.MetadirectoryServices.Impl.ConnectorImpl.Commit()
at Miis_Metaverse.MVExtensionObject.Microsoft.MetadirectoryServices.IMVSynchronization.Provision(MVEntry mventry)"
Step 1. Search the user in metaverse and the object will not existing in MV as it fails during the provisioning, First challenge is to bring the Object in MV.
Step 2. Disable the Provisioning Rule Extension ( Tool-Options)
Unchecked the option Enable Provisioning Rule Extension.
Step 3. Go to the connector space of the MA and commit preview, this will project the object in MV.

After Step 3,checked the option Enable Provisioning Rule Extension. See Step 2,
Step 4. See How to join connector Space Object to a MV object, the tech net link is below

The Management Agent Run and see the error message in the Stack information.
"Microsoft.MetadirectoryServices.ObjectAlreadyExistsException: An object with DN "CN=4,OU=FIMOU,DC=corp,DC=fim2010,DC=com" already exists in management agent "ADMATest".
at Microsoft.MetadirectoryServices.Impl.ConnectorImpl.Commit()
at Miis_Metaverse.MVExtensionObject.Microsoft.MetadirectoryServices.IMVSynchronization.Provision(MVEntry mventry)"
The error message arise because there is already an existing object with the same DN in provisioning connector space.
Step 1. Search the user in metaverse and the object will not existing in MV as it fails during the provisioning, First challenge is to bring the Object in MV.
Step 2. Disable the Provisioning Rule Extension ( Tool-Options)
Unchecked the option Enable Provisioning Rule Extension.
Step 3. Go to the connector space of the MA and commit preview, this will project the object in MV.

After Step 3,checked the option Enable Provisioning Rule Extension. See Step 2,
Step 4. See How to join connector Space Object to a MV object, the tech net link is below
Join a Connector Space Object to a Metaverse Object Link
Go to Joiner Tab and Join the existing disconnect object to newly project object in MV.
This will fix the Error .. !!
Tuesday, 23 September 2014
Thursday, 18 September 2014
Sunday, 6 July 2014
Distribution Group Management
Disclaimer: The purpose of
this document to show how group management can be configure in FIM environment,
all the test has been done in virtual basement lab environment. It is highly
advice to test your architecture design in Test environment before deploying in
Production environment. It carry no right and it implementer will be fully responsible
for its own act without analyzing the risk impact.
Monday, 23 June 2014
FIM Error 1068 :the dependency service or group failed to start.
It is simple as the name suggests the dependency service is
not started; You have to start all the dependency service first before you
starting your FIMSynchronizationService.
Do not start any services by trial and error method
process, as I tried to figured out what is wrong in my LAB.
Know all of your dependency service password,If not take the help of SQL Admin to know the
password of the SQL services
.
Find the service you can't start in services.msc, right
click and open properties. Go to dependency and make sure all those are
started. 99% of the time one of those services hasn't started.
Cheers.. !!!, I was able to start my FIMSynchronizationService.
Happy Troubleshooting and Good Night
Sunday, 15 June 2014
Adding Multiple user to Group in FIM portal
"YOU Can get what you want if you
help enough other people to get what they Want".
The Powershell way of doing thing,Feel Free to Tweak it as per your needWednesday, 11 June 2014
New series : HOW to create new attribute for user in FIM Portal
The below is the Link : Hope it will help you in creating new attribute in Portal.
New series : HOW to create new attribute for user in FIM Portal
New series : HOW to create new attribute for user in FIM Portal
Stop Wishing.Start Doing
Saturday, 7 June 2014
Sunday, 27 April 2014
Synchronization Rule
The strategy of group creation in AD can be defined in Sync
Rule, It is very important to know how to customize the DN so the group can be
sync to respective OU in AD.
FIM Administrator can customize the DN in Outbound Sync Rule,
so the group can be create to respective OU in AD.
For example.
IIF(Eq(groupLocation,"Bangalore"),"CN="+mailNickname+",OU=Groups,OU=Bangalore,DC=XXX,DC=com",IIF(Eq(groupLocation,"Pune"),"CN="+
mailNickname +",OU=Groups,OU=Pune,DC=XXX,DC=com",Null())) àDN
Sunday, 23 March 2014
Friday, 14 February 2014
Sunday, 26 January 2014
Thursday, 9 January 2014
Search Scopes in FIM 2010.
Search Scopes in FIM 2010.
What is the use - To display the attribute in the main UI of the portal.Taking as example - The Users are not showing their EmployeeID details in the main UI of the portal.
Go to Administrator , Search Scopes, All Users, Results
In Attribute type EmployeeID.
IISRESET
Subscribe to:
Posts (Atom)
-
Note : This series is for the Beginner and trouble shooting the Error With Sync Engine, Based on Test Lab, Highly advice do not do Full Syn...
-
This article can be refer as reference only, how can you build your first Management Agent connect to Service Now. The samples code show...
-
Rules are the construct through which IdentityIQ allows the addition of custom business logic at specific points within the execution fl...