RELEASE DATE: July 2021

Download This Version Now!

Improvements

• Implement IPB Lockdown for Schlage locks connected to Authentic Mercury protocol controllers.
• Utilize Trusted SQL connections for all SMS Operator connections to the SMS database for Active Directory linked Operators in place of Operator SQL login connections.
• Optionally use a trusted SQL connection via the logged in Active Directory account in place of the SMSAdmin SQL login
• The SMSAdmin SQL login is still required on workstations where the Database Maintenance application is executed due to the elevated privileges required to create and update SQL jobs, regardless if an Active Directory linked or traditional SQL login Operator runs the application.
• Allow services configured with an Active Directory service account (via the Windows Service Manager service properties Log On tab) to use Trusted SQL connections for connections to the SMS database in place of the SMSAdmin SQL login connection.
• Provide the option to link SMS Operators to an Active Directory account. Operator passwords are not stored in the SMS database for Active Directory linked Operators.
• Elevate Operator permissions if the Security Group assigned to the Operator contains access to System Security.
• The Active Directory accounts for SMS Operators running System Security must contain permissions to read all Active Directory objects/OUs containing Active Directory Users who will become AD-Linked SMS Operators.
• Add new “AD Integration” tab to provide settings to control System Security Active Directory querying.
• The Active Directory accounts for SMS Operators running System Settings to configure System Security Active Directory container search filtering must contain permissions to read all Active Directory objects/OUs containing Active Directory Users who will become AD-Linked SMS Operators.
• Provide the option to specify that an Active Directory service account should be used for Database Connections for all SMS services on the workstation. The account used must have full permissions to SMS Data Folder and SMS database.
• Provide the option to specify that the logged in Active Directory account is used to connect to the SMS SQL Server via a trusted connection in place of the SMSAdmin SQL login.
• Active Directory linked Operators are authenticated via Active Directory using the Operator’s entered Active Directory password without Single Sign-on (SSO) enabled. If SSO is enabled for an Active Directory linked Operator, the currently logged in Active Directory user account is validated against Active Directory and the SMS Operator table.
• Active Directory linked Operators are authenticated via Active Directory using the Operator’s entered Active Directory password without Single Sign-on (SSO) enabled. If SSO is enabled for an Active Directory linked Operator, the currently logged in Active Directory user account is validated against Active Directory and the SMS Operator table.
• Implement optional diagnostic logging.

Hot Fixes

• Alarm comments attributed to an incorrect Operator under some circumstances.
• Error selecting Cardholder field adding annotation in certain circumstances.
• Errors Incorrectly logged to Windows Event Logs.

Note: SMSAdmin is used in the SMS context when no Operator is logged into SMS (i.e. start-up applications) or elevated permissions are required (SQL job creation/update and archive export, System Security user creation and Report Launcher restore archive history). Active Directory linked Operator’s running these applications will require elevated SQL permissions (see software manual). SMS will continue to use some SQL login connections and the SMSAdmin account until ALL Operators, ALL SMS services and all SMS Workstation Registry Settings are configured for optional Active Directory accounts and Trusted SQL connections. The SMSAdmin account is always required for the Database Maintenance application. SMSAdmin is used in the SMS context when no Operator is logged into SMS (i.e. start-up applications) or elevated permissions are required (SQL job creation/update and archive export, System Security user creation and Report Launcher restore archive history). User’s running these applications will require elevated SQL permissions (see software manual).

Full Release PDF: SMSv7