HP Imaging and Printing Security Center 2.0 - Installing IPSC Using Local Instance of SQL Server 2012

1
HP IMAGING AND PRINTING
SECURITY CENTER 2.0
TECHNICAL BRIEF
Installing IPSC Using Local Instance of SQL
Server 2012
In all previous versions of SQL Server prior to SQL Server 2012, the role of sysadmin is
automatically assigned to the login of NT Authority\System. When a specific login is a
member of the sysadmin server role, access to SQL Server is unrestricted. Some things to
take away with respect to the sysadmin role are:
This role can do anything within SQL Server.
This role completely bypasses all security checks.
This role can do everything any other role can do and more.
This is the most powerful role in SQL Server.
Beginning with SQL Server 2012, database engine security enhancements now include
provisioning during setup, new property list permissions, new user-defined server roles and
new ways of managing server and database roles. These changes were implemented by
Microsoft to provide greater security at install time.
As a result of the enhanced security in SQL Server 2012, the role of sysadmin is not
automatically provisioned and therefore might contribute to database connectivity issues for
applications or more specifically, installers of applications attempting to access the SQL
Server 2012 database engine.
IPSC installation is not exempt from this enhanced security. So, unless the IPSC
installer is granted SQL Server Administrator rights during SQL Server 2012 setup
(See Figure 1 below), the installer must be provided sysadmin rights later and
before IPSC is installed with the option to utilize a local instance of SQL Server
2012.

Summary of content (2 pages)