Just installed FIM 2010 RC1 and going through the documentation http://technet.microsoft.com/en-us/library/ee534890%28WS.10%29.aspxFew points1. I am finding it bit difficult to read the documentation due to font size and spacing between the lines. I literaly struggle to move from one line to another due to spacing between the line.2. No logical order of documents. The sequenece in which one should start is not mentioned anywhere. Document X assumes that reader has already completed the exercise in Document Y, Document Y assumes Doucment Z etc...3. Hard to understand some of the concepts, the way things are explained.- Sachin

This is good feedback, Sachin! I will add your post later to the suggestion box. I totally understand your point regarding the order we have discussed this point several times internally. However, this is not as simple as it may seem to be. I dont believe, there is an A-Z order since FIM covers a lot of different scenarios. For RTM, we are working on implementing a block structure that consists of 1. Conceptual Information 2. Feature step-by-step guides 3. Scenario step-by-step guides So, for declarative provisioning, you will find something like 1. Understanding Declarative Provisioning 2. Introduction to inbound/outbound synchronization 3. Publishing AD from two authoritative data source We are grouping related information around these blocks. This means, that one should at least read first the feature based guides before looking into the scenarios. Thoughts, questions or other feedback? I have noticed some issues with the template on the platform, too, and will file some bugs. Regarding the concepts, could you please be a bit more specific? Im already collecting feedback on declarative provisioning here. Please feel free to add feedback to this post. What are concepts you find difficult to understand? Do have for things you have learned suggestions for better explanations? Next to constructive criticism, which is always welcome, it would also be helpful to know what you guys like. This applies next to the documentation also things like the ScriptBox. For example, I dont see much feedback regarding the scripts, which makes it a bit hard to determine whether putting time into them is really worth it. So, All, please take at least advantage of the voting mechanism on this forum as it really helps to see what you like.Cheers,MarkusMarkus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Hi Markus I found understanding MPR and WF conecpt bit difficult to understand. Here are some of the points which comes to mind after reading 3 walkthroughs. 1. Duplication of information in 'Introduction to Inbound/Outbound Synchronisation' guide. 2. It is very helpful to have documents as word documents or PDF file. That way it is very easy to provide feedback like 'Page x, Line Y needs this correction'. While going through the online documentation, I noticed at couple of places either step is missing or is repeated but cosidering the huge size of the html page it takes bit of energy to write precise feedback mentioning all the details like title of the section, where etc... :-) 3. Not sure why cetain things are explained in great detail again and again like 'How to create run profile', 'How to run MA' etc. Once explained either at the begining of the document or in 'Intro Documentation', I think it should be ok just to mention the name of the file. Table format used to mention the Run Profile is quite good and self explainatory. 4. I think, documents should have more use cases covering all the features and what happens at each stage. e.g. A user created in Portal, then how that user will end up in Set, then how MPR is triggered, how WF is triggered etc.... If use cases can cover all the options of MPR and WF and present this information pictorially that would really help to understand the concept. 5. More to follow... Cheers Sachin

Excellent this makes all a lot of sense. Most (if not all) of it will be incorporated into the RTM doc set. Please move on!!! Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Thanks Sashin and Markus! I've followed this discussion with big interest and agree with many things. I would like to add that I wish more understanding in whats goes on beneath what you are "configuring" inside the product of two reasons... It allows for understanding why and why not things should be done in the way it's documented, easier remembrance and as a bonus it will be easier to perform all different kind of scenarios without the need of documentation. //HenrikHenrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

Hi Markus! It seems there's a hole in the documentation regarding getting custom resource types into the sync engine... Unless I've missed it. //HenrikHenrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

How about including a glossary, since this technology is new to many of us and the terms can be confusing.

Someone have to success to install and configure FIM 2010 on server 2008 R2 enterprise ? Someone have a documenation step by step ? Thanks

Hi Kit, The FIM 2010 glossary can be found here: http://technet.microsoft.com/en-us/library/ee534910(WS.10).aspx If there are missing terms, or confusing definitions, please let us know.

Hi Megan! I got really confused when I had a look at this page: http://msdn.microsoft.com/en-us/library/microsoft.identitymanagement.webui.controls.aspx The page is a part of the MSDN FIM Service Managed Reference states that all objects required for displaying a custom Wokflow Activity within FIM UI isn't supported. Is this really true or is it just a problem with the documentation? //HenrikHenrik Nilsson, ILM/FIM MVP Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

It's complicated. Although the API has been tested, it has not been tested in a wide variety of 3rd party applications and so we had to put in that disclaimer. If the SDK documentation indicates that an API is intended for internal use only, we strongly recommend that you not try to use it. That API may later be removed or the implementation changed without notice. If the SDK documentation only says that it is not supported (and does NOT say it is for internal use only), then it is probably okay to use. If you run into problems using it, then you can still ask for help from the support team to help figure out what the problem is. It is "supported" in that sense.