Looks like a bug. It will be fixed next week. Thank you very much for reporting this.

Not yet. I will let you know here when it is ready.

The next release (with the requested patch) is planned for Friday.

I tested the new version and found the following:

• Domain is Server 2008 R2 native.

• If I do not choose "Assign applications to Windows\AD Users" the program words as expected.  If I choose that option and try to login with a domain account it tells me there are no applications available for me on the server.  Once I uncheck the box to assign applications then it works fine.
• If I check the box to "Assign applications to Windows\AD Users" and then click the "Update Users" button it will not list domain users.

I guess the trouble seems to be with enumerating domain users from group membership and then trying to apply specific applications to each user.  In the previous version the application would enumerate the domain users and allow me to assign specific apps to a specific domain user account but it would fail on authentication\authorization.  The new version authenticates fine but does not allow me to assign apps to users.

Could you verify you are seeing the same thing I?

Thanks

The domain info is filled out...the program works with permitting access based on group (to all applications) but it does not work when trying to lockdown applications to specific users.  That tells me that AD authentication is working (if I try it with an AD account outside the permitted group I get an error) so I think we are OK there.  The problem seems to be enumerating domain members of the local group -- for some reason it cannot enumerate them.  It will, for example, enumerate local accounts (administrator, etc) but just has issues with the domain members.

Thanks Mirek...when testing I tried a variety of different methods.  The last method was to use a domain admin account and it still did not work.  If you are seeing different results that I then it could be something specific to my domain configuration rather than the software.  I am running in Server 2008 R2 native mode (not mixed) in my test environment.  The weird thing is this piece worked prior to the upgrade (although I couldn't connect from the client) and nothing in my test domain has changed.

Sorry I haven't responded -- I have been traveling the last couple of weeks.  I just tested 3.5.2.0.a and there are still issues resolving domain usernames when trying to assign specific applications.  It will resolve any local users that are members of the group but it will not resolve domain usernames.  This piece did work in the version that was available on 1/15 (although there were other issues).  I have tested this on both a 2008 R2 domain and a 2003 domain and both have the same result.  Is there a server side debug mode where we can capture where it is failing?