Adai.
Once again, thanks you for the quick response. Government agencies require the use of a smartcard for logon to a Windows domain and the account option "smart card is required for interactive logon" enabled on the AD account. When this boxed is checked, all interactive logon would require the smartcard to logon. So that means windows users can only now logon to the OnCommand Console if this option is turned off (which violates their security rules) on their AD account. The only work around I can see is if they have a local account on the Windows server hosting the OnCommand install (Again a more minor security finding). Local accounts aren't preferred and would seem to be taking a step backward as they require more management. If OnCommand supported smartcard, then the user would simply have to have the rights, a smartcard, and a pin #. That make sense?
Cecil
