Windows Internal Database & “Windows Server Update Services” ( WSUS ) DB

 

Background

As part of a SQL Server Inventory exercise we have been working on since Summer 2017, noticed 3 machines running “Windows Internal Database” version 2005.

 

Patch Report

Here is a snapshot of GM’s report…

inventory_20171110_0630AM

 

Examination

Let us remote desktop to the SCCM machine and see whether GM’s fingerprinting bears true.

 

Windows Version

We ran winver to deduce the version of Windows

Command

 
winver
 

Output

winver_20171110_0508AM

 

Explanation

We are running Windows Server 2008/R2 with Service Pack 1 ( SP1 )

 

File System

Windows Internal Database are packaged as part of the main application’s installer and very little customization is allowed to the WID sub-component.

Therefore we can learn a lot based on the OS Folder where it is installed.

 

Control Panel – File Options

Let us access Control Panel \ File Options and make sure that it is configured for Administrative needs.

 

Images

Images – Before

controlPanel_folderOptions_20171110_0458PM

 

Images – After

controlPanel_folderOptions_20171110_0459PM

 

Explanation

  1. Uncheck
    • Hide extensions for known file types
    • Hide protected operating system files
  2. Checked
    • Show hidden files, folders, and drives

File System

Application Targeted Folder

Folder Win OS Application
C:\Windows\sysmsi\ssee\ Windows Server 2008 – x64 bit Windows SharePoint Services 3.0

Windows Server Update Services 3.0

 C:\Windows\WID  Windows Server 2012 – x64 bit Windows Server Update Services v 2012

Folders

Folder – C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL

SQL Server

SQL Server – Error Log

SQL Server – Error Log – File Structure

SQL Server – Error Log – File Structure – Files

SQL Server – Error Log – File Structure – File – ErrorLog

SQL Server – Error Log – File Structure – File – ErrorLog – Contents

Reviewing SQL Server’s error log gets us quite a bit of information and so let take the opportunity to take a quick cursory look.

Content

2017-10-29 21:35:33.28 Server Microsoft SQL Server 2005 - 9.00.5000.00 (X64)
Dec 10 2010 10:38:40
Copyright (c) 1988-2005 Microsoft Corporation
Windows Internal Database (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)

2017-10-29 21:35:33.28 Server (c) 2005 Microsoft Corporation.
2017-10-29 21:35:33.28 Server Authentication mode is WINDOWS-ONLY.
2017-10-29 21:35:33.28 Server Logging SQL Server messages in file 'C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG'.
2017-10-29 21:35:33.28 Server Registry startup parameters:
2017-10-29 21:35:33.28 Server -d C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf
2017-10-29 21:35:33.28 Server -e C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG
2017-10-29 21:35:33.28 Server -l C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\mastlog.ldf
2017-10-29 21:35:34.76 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query ].
2017-10-29 21:35:34.78 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2017-10-29 21:35:34.76 spid5s Server name is 'SCCM\MICROSOFT##SSEE'. This is an informational message only. No user action is required.
2017-10-29 21:35:34.79 spid5s Starting up database 'msdb'.
2017-10-29 21:35:34.79 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2017-10-29 21:35:42.03 spid51 Starting up database 'SUSDB'.
2017-10-29 21:35:42.28 spid51 Recovery is writing a checkpoint in database 'SUSDB' (5). This is an informational message only. No user action is required.
Interpretation
  1. Microsoft SQL Server 2005 – 9.00.5000.00 (X64)
    • Microsoft SQL Server 2005
      • Version is 2005
    • 9.00.5000.00
      • Service Pack 4 ( SP4 )
    • X64
      • 64-bit
  2. Windows Internal Database (64-bit) on Windows NT 6.1 ( Build 7601: Service Pack 1)
    • Version is Windows Internal Database (64-bit)
    • Windows NT 6.1
      • OS  ( Windows Version – Wikipedia – Link )
        • Windows 7
        • Windows Server 2008 R2
        • Windows Home Server 2011
    • Build 7601 : Service Pack 1
      • SP1

SQL Server – SQL Server Configuration Manager

Launch sql server configuration manager to review “SQL Server Services

Image

SQL Server Configuration Manager

SQL Server Configuration Manager – Properties – Service
Image

Explanation

  1. Binary Path
    • C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\Binn\sqlservr.exe -sMICROSOFT##SSEE
      • Instance’s name is MICROSOFT##SSEE
  2. Name
    • Windows Internal Database (MICROSOFT##SSEE)

 

Installed Programs

Control Panel – Add or Remove Programs

Image

Explanation

  1. Applications Installed
    • Name :- Windows Server Update Services 3.0 SP2
    • Date :- 7/29/2015
    • Version :- 3.2.7600.226

 

SQL Server – SQLCMD

Let us quickly use sqlcmd to get metadata

Connect to SQL Server Instance using sqlcmd

Command

sqlcmd -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -E

Output

sqlcmd – Version using @@version

SQL

select [@@version] = @@version
go

Output

Explanation
  1. Version is MS SQL Server v2005 – 9.00.5000 ( x64 )
    • Version :- MS SQL Server v2005
    • Version # :- 9.00.5000
      • SP4
    • Bitness
      • x64

sqlcmd – list databases using sys.databases

SQL

select name, create_date from sys.databases
go

Output

Explanation
  1. Databases
    • System
      • master, tempdb, model, msdb
    • User / Application
      • susdb
        • susdb created on 2015-July-29th

Summary

Confirmed that GM’s patch report is indeed accurate.

We have a few Windows Internal databases on our network.

Will complete the steps of aligning each of them to specific Products, Vendors, and in-house support engineers.

 

References

  1. Microsoft
    • Microsoft Developer
      • VedMS
        • Following is the steps to connect to these Windows internal database on Windows 2012 machine. This to access the WAP configuration from the ADFS configuration database.
          Published On :- 2014-August-19th
          Link
  2. Edgewood Solutions LLC ( mssqltips.com )
    • Edwin Sarmiento
      • Administering your Windows Internal Database MICROSOFT##SSEE instance
        Link
  3. System Specialist .NET
    • Move or Delete a WSUS 4 Windows Internal Database (WID) on Windows Server 2012
      Link