Overview of the Microsoft Baseline Security Analyzer

Like Microsoft Software Update Services, the Microsoft Baseline Security Analyzer (MBSA) is a security toolkit component born out of the Microsoft Strategic Technology Protection Program (STPP).

MBSA v1.2 is available for download from the Microsoft website and provides a graphical and command line interface that can perform local or remote scans of Windows systems. MBSA runs on Windows Server 2003, Windows 2000, and Windows XP systems and will scan for common security misconfigurations in the following Microsoft products:

  • Windows NT 4.0.
  • Windows 2000.
  • Windows XP.
  • Windows Server 2003.
  • Internet Information Services (IIS) 4.0, 5.0, and 6.0.
  • SQL Server 7.0 and 2000.
  • Internet Explorer (IE) 5.01 and later.
  • Office 2000, 2002 and 2003.

MBSA also scans for missing security updates for the following Microsoft products:

  • Windows NT 4.0.
  • Windows 2000.
  • Windows XP.
  • Windows Server 2003.
  • IIS.
  • SQL.
  • Exchange.
  • IE.
  • Windows Media Player.
  • MDAC.
  • MSXML.
  • VM.
  • Office.
  • Content Management Server.
  • Commerce Server.
  • Host Integration Server.
  • BizTalk Server.

MBSA replaces and expands on the former HFNetChk tool to check for required hotfixes but two useful command line variants (which must be run from the folder where Microsoft Baseline Security Analyzer is installed) are:

mbsacli /hf -h computername -u username -p password

(used to check against the Microsoft Windows Update servers for missing hotfixes); and:

mbsacli /hf -h computername -sus susservername -u username -p password

(used to check against a specified SUS servers for missing hotfixes).

MBSA should be run periodically to check for security issues, finding workstations with vulnerabilities and/or weak passwords, allowing steps to be taken to force a user to take action.

Tracking down IBM BIOS updates

The IBM website is not always the easiest to navigate and I spent ages today tracking down the latest BIOS for a number of servers. To save someone else the same issues in future, I recommend that to quickly find the latest BIOS for a PC or server, search for +flash +BIOS +update +modelnumber.

More search tips are available from the IBM website.

Connecting to a server’s console session using RDP

One of my colleagues introduced me to a switch I had mot previously encountered for connecting to the console session on a server using the Microsoft Terminal Services/Remote Desktop Connection (RDP) client. Although not presented by the GUI interface, the mstsc command includes the /console switch. For the full command syntax, type mstsc /? or refer to the Microsoft Windows Server 2003 product documentation.

Controlling the creation of Active Directory replication connections

The knowledge consistency checker (KCC) is a Microsoft Windows 2000 and Microsoft Windows Server 2003 component that automatically generates and maintains the intra- and inter-site replication topology.

Whilst the KCC generally works well, sometimes it may be necessary to prevent the KCC’s automatic generation of replication connections (a scripted method is also available).

It should be noted that manually creating Active Directory connections to tailor the replication topology increases the administrative workload as the KCC will no longer dynamically alter connections to reflect changes in the network topology or replication failures.

Further information on optimising Active Directory replication is available on the Microsoft website.

Determining costs for Active Directory site links

Whilst reviewing a colleague’s Active Directory design document today, I came across the following model for determining the cost of a site link, depending on the available bandwidth:

Replication cost = 1024 x 1/logbandwidth (in Kbps)

The following table gives some example costs for common bandwidth values:

Bandwidth (Kbps) Replication cost
28 702
56 586
64 567
96 517
128 486
256 425
512 378
1024 340
2048 309
4096 283