I’m not very impressed by the Windows Integration module of Community Server 2.0. It provides simple SSO in a multi-domain AD environment but that’s all it does. I would like to see it pull the email address and display name of the user from AD automatically at very least. Currently, it just defaults to [logonname]@[defaultdomain], where the default domain is specified in the config and does nothing with the display name. This might work in a single domain environment, but not multi-domain.
I’d also like to see roles connected to AD groups, so that I can control access through AD administration. As it is, I have to add people to certain roles within CS. This is made somewhat more ridiculous by the fact that their CS account is only created when they first logon. In one instance I have a restricted blog (which, btw, seems to work well – security is good), so to allow a person to see it, they must first access the site, then let me know they’ve done that so I can add the role to their newly created account, after which they can access the restricted blog.
I think this needs a lot of work.
TechnogIT 
I appologize for your dissappointment with the Windows Authentication module. All it was made to do was to link CS to IIS when using Windows/AD authentication. All it knows about the user is their basic credentials. IIS doesn’t provide their real name or their email address.
The functionality you’re talking about describes our planned LDAP connector to the T. In order to get additional information on a user, the best way would be through LDAP. This way, we could retrieve their name/email address, and be able to link roles in CS to groups in AD and monitor who is added/removed from them.
This won’t be coming until CS v3.0, partially because it will require .NET 2.0 and CS will soley use .NET 2.0 in v3.0. It would not be very practical on .NET 1.1, as in .NET 2.0 the LDAP support is highly improved and better suited for middleware type applications.
I hope that you will stick around and revisit this in CS v3.0.
Thanks,
Ken Robertson
Telligent Systems, Inc.
Of course I look forward to this module.