I'm looking for clarification of the licensing model for the RTM of FIM 2010 (when released) As I understand the model so far, from ILM 2007, I need: A FIM 2010 server licence for each FIM 2010 server FIM Certificate CAL's for each user (if I choose to use this feature) A FIM external connector licence (if I have external users, using the service) Plus SQL and OS licences as required.Are there any other FIM 2010 licences that I need to be aware of? I noted in an article that I read some time ago that some 'other' licences were needed if you planned to use the 'Codeless provisioning' features of FIM 2010. Is this correct? If so, what are these extra licences?Thanks in advance,Jon Bryan

You're correct on the licensing model of what I've learned and there's no other licenses. The 'Other' licenses you've read about is simply the FIM CAL's that except for 'Codeless provision' i.e. provision users to the FIM Service and/or letting them use the portals or self service functions also is required for managing certificates for users. You wont need any CAL's if you only use the Sync Service. //HenrikHenrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

Henrik,Thanks for the reply. However, I'm still not 100% clear on the codeless provisioning bit.Codeless provisioning is one of the main drivers for (potentially) migrating to using FIM 2010.From what I understand (fairly limited knowledge), 'codeless provisioning' operates via a SharePoint portal and a set of workflows that integrate with the sync service. The SharePoint portal is the free downloadable version, rather than the full product.Therfore, do you mean that FIM CAL's are required if you wish to use the codeless provisioning facilities of the product? Or are they purely used for certificate provisioning?Regards,Jon.

The portal is just the UI for the FIM Service. As soon as you provision users to FIM Service you need a CAL for them. It's the FIM Service that enables codeless provisioning but as i said earlier you can use the Sync Service without CAL's but then you're stuck with the old style sync rules where code is required for provisioning. //Henrik Henrik Nilsson Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

Many thanks Henrik,That makes sense. I suppose our licencing costs might be a little higher in that case!Regards,Jon.

For a little bit of clarification on my end, you're saying that you would need a CAL for every single user that gets provisioned into the FIM Service (Portal), regardless of whether those users are going to access the Portal or not? Also, when defining "users", is that any user-like object (i.e. from an HR database instead of Active Directory) that we are managing identity for? Thanks!-Michael

Any user-like objects that represents a physical person regardless source system! Did that clarify it? //HenrikHenrik Nilsson, ILM/FIM MVP Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

Yea. Thanks for the quick response!-Michael

Another question that's related. I haven't worked with any of the MS licensing stuff before, so my knowledge regarding it is slim to none. Let's say I have 100 users that I'm managing with FIM throughout the entire lifecycle. When the user is not longer a part of the company, and we deprovision (including filter out of FIM's process), would that free up a CAL to be used for a different identity? In essence, can we reuse CAL's once we remove an identity from FIM? Thanks!-Michael

Yes, you can reuse cals when objects are no longer "managed"! Henrik Nilsson, ILM/FIM MVP Blog: http://www.idmcrisis.com Company: Cortego (http://www.cortego.se)

Good deal. Thanks!-Michael