What is Windows Internal Database(MICROSOFT##SSEE)
Windows Internal Database is a relational data store used by the following applications and services.
•Active Directory Rights Management Services (AD RMS)
•Windows Server Update Services
•Windows System Resource Manager
These applications and services share a single instance of the data store.
The Windows Internal Database is a varient of Microsoft SQL Server Express 2005, and is included with Windows Server 2008 and Windows Server 2008 R2. It is also included in Windows Sharepoint 3.0 and Windows Server Update Services (WSUS) 3.0/3.2, where a full version of Microsoft SQL Server may not be available. Other services can also use this database engine if needed, such as Active Directory Rights Managements Services, and Windows System Resource Manager. Once the Windows Internal Database has been installed, it can’t be uninstalled via the “add/remove features” wizard (it appears greyed out, so you can’t de-select it).
The tool used to connect to the Windows Internal Database is the same as used for the full version (and express editions) of Microsoft SQL Server, which is the SQL Server Management Studio (or SQL Server Management Studio Express). The main thing to note with the Windows Internal Database, is the fact that you cant make remote connections to the database. It is designed so that only the computer that has it installed, can access the databases. As such, the only connection method you can use to connect to a Windows Internal Database, is to use the Named Pipes protocol. When connecting to a Windows Internal Database, you must used the fairly obscure named pipes syntax, which will be listed below, as the server/instance name in SQL Server Management Studio.
The server/instance name to connect to is:
You must also use “Windows Authentication” as the authentication method to connect to this database.
If you get Login failure error with below error message "Error: 18456, Severity: 14, State: 11."
Please run the SQL Server Management Studio application by first right clicking the shortcut, and selecting “Run as Administrator”. Even if your account has admin rights on the server, it still may be necessary to perform this step.