Friends and Life @Infosys

Time for me to move on. Today is my last day in Infosys.

Just want take this opportunity to thank everybody for all the support and guidance I have got from everybody during my tenure. It’s been the most memorable time I have had in infosys and Microsoft and really feel sad today to write the last day mail.

Guy's you are one of the best people I have ever meet and learn lots of thing during my tenure in Microsoft. I always felt privilege to be part of the team.

Thanks to Manish,Lyle, Anil,Alex,james and khalid for your support and learn myriad things from you all. My sincere thanks to each one of you!

I would like to thank all my leads, managers and colleagues for providing all the guidance, appreciation, encouragement whenever I needed. I would be taking away with me a lot of learning’s from here.

Wish all of you good luck and the best in life!        [V-ANSI]

Infosys.

Microsoft -- Hyderabad.

Notice Board in FIM

Notice Board in FIM, It is good to display the downtime and maintenance of FIM in home page instead of sending mail to the user.
I see the production team use to display this information in the home page of FIM, I did a little bit of investigation and here is my finding.

Click Administrator -> Home Page Resources ->Click New

At Work

The Energy drink in MS that come in Rescue at the time of escalation,calls and when nothing is working fine..cheers

Group TS

If your Sync Rule and MPR are fine, the best approach to investigate group errors is to find the error message in connector space.
Verify the group in FIM Connector space Search by RDN and Resource ID.
In AD Connector space search by RDN and CN name.

If you are able to locate the group in FIM connector space and the state of the connector is False then the group fails to project in metavers.Find the sync errors with the group that will help to narrow down the investigation.

PowerShell

The day was ending as usual  and before I leaved I have to move 500 servers to OU. At beginning I thought it will take 15 to 20 min using the script and will leave the day as usual.

I have used the bulk move script to move the servers to the OU, Hiccups started when the server are falling to move and to verify the list of server fail to move out of 500 servers will take more 2 hours to investigate.

 

Thought of using vlookup function in excel but it is not always show the result as excepted and then what next – Will powershell serve the need and the answer is YES.

 

Here are the steps how I did it…

 

There are two input file as.txt and ansi.txt

as.txt is the file that has been used in bulk move and ansi.txt is the list of all server in the OU after the bulk move.

PS C:\Users\Administrator> Compare-Object $(Get-Content C:\Users\Administrator\Desktop\as.txt) $(Get-Content C:\Users\Administrator\Desktop\ansi.txt) -includeequal Where-Object { $_.SideIndicator -like '<=' }

 

InputObject SideIndicator

 

----------- -------------

 

100 <=

 

Recovery of an group from the AD recycle bin.

Useful Link in Recovery of an group from the AD recycle bin.  http://darshanaj.wordpress.com/2011/11/29/active-directory-recycle-bin/

It work and able to recover the group that has been deleted in AD.
Note - Recovery of group deleted in FIM require few change in the attribute of the group in ADSI EDIT after recover the group as shown in the snapshot. -- I will cover the recovery of FIM manged group some where in future.

MPR configuration for FIM Portal Access

Using Power Shell to check your MPR configuration for FIM Portal Access

http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/73954797-afb4-4448-8c3e-af5b4f9e2eb5