When you say that it's not pulling in the roles from the AD what to you mean? Do you mean it's not automatically creating DNN security roles that are in the AD or that it's not adding the users to the DNN security roles that are named the same as they are in the AD? If it's the first one then that's not how Authentication works. You have to create the Security Roles in DNN. If it's the second.....synchronization has never quite worked correctly. It'll sync the roles the very first time a user logs in and their DNN account is created but won't catch changes after that. Stuart Hilbert created a fix for DNN3 that does do the sync everytime a user goes to the site and I converted it to work with DNN 4 (look for the DNN AD Fix Updated thread). However with DNN 4.4.1 and maybe 4.4.0 DNN doesn't seem to acknowledge the logins as long as the process hasn't shut down on the server (ie: I come to work and go to the intranet site first thing in the morning before anyone else so the process has shut down on the server from the day before. It'll register my login. But if I visit it again at lunch time and other users have been going there all morning so the process has never timed out or shutdown and the DNN eventlog won't show me as logging in and none of the log in procedures run.).

I'm in the middle of another project for work that needs to be done soonest but once I'm done that I'm going to look at writing a DNN service that'll sync the roles on a regular basis. A side benefit of this is that it should negate the need for Stuart and I to update the code everytime a new version of DNN comes out.