Past editions of operating systems used 32-bit addressing schemes, which effectively limited support for single disk devices to 2 terabytes (TB) or less.  The GUID Partition Table (GPT) is a replacement for the older MBR.  Currently, x86-based computer systems use a legacy BIOS that will not support the use of GPT drives as a boot device.  However, depending on the operating system, support has been added for GPT drives as additional data volumes only.

Based on the limitations around booting to drives larger than 2TB in size and the other OS limitations, Dell will not ship any servers with a RAID configuration larger than 1.8TB.  If an array greater than 1.8TB is specified in the system configuration, then the system will ship with several RAID slices that are each 1.8TB or less.

This Dell Community forum post details the process of creating RAID arrays larger than 2TB:

http://www.dellcommunity.com/supportforums/board/message?board.id=pes_hardrive&thread.id=25686

Instructions to convert a disk to a GPT Disk for one large > 2TB partition (Win2k3 SP1):

http://kb.ciprico.com/lore/article.php?id=315

Problem

The Catalog Database was not created at installation, or became corrupted.

Solution

Create the Catalog Database manually from the command line.

1. From the Windows Start menu, go to Programs > Accessories > Command Prompt. The Command shell opens.
2. Get the name of the Server, which is the database instance or host name.
3. Enter the createdbu command to create the new Catalog Database, including:
   • Server name
   • User name or “” (two double quotes) for trusted connection
   • Password or “” (two double quotes) for no password for trusted connection
   • Component (enter LogServer, Reporter, or Both)
   • New Catalog Database name
   • Database path (C:\Program Files\Websense\SQL)

   Be sure to include spaces in between each command and enclose each command with double quotes. For example:

   createdbu "WS-DB-SERVER" "ws_admin" "password1" "LogServer" "newlogdb63" "C:\Program Files\Websense\SQL"

   To see the options available with the createdbu command, enter the following:

   C:\Program Files\Websense\SQL\CreateDbU.exe - Help

   NOTE	It may take a few minutes for the database to be created. Both the catalog and partition databases should exist once the process is complete.

4. Go to Microsoft SQL Server to verify that the new Catalog Database has been created. For Microsoft SQL Server 2000, go to Enterprise Manager. For Microsoft SQL Server 2005, go to Management Studio.
   1. For SQL Server 2000, the default path for Microsoft SQL Server 2000 is: C:\Program Files\Microsoft SQL Server\Enterprise Manager
   2. Expand the navigation tree to reveal the SQL Server name and the folders beneath it.
   3. Open the Databases folder to see the new Catalog Database (for this example, newlogdb63).
5. Restart the Log Server.
   1. Go to the Windows Start menu and select Programs > Websense > Utilities > LogServer Setup. The Log Server Configuration displays with multiple tabs.
   2. Go to the Connection tab and click Stop in Service Status.
   3. Click Start in Service Status. You should see a message that says the service is running.
6. Update your Explorer Settings.
   1. Go to Enterprise Explorer via Programs > Websense > Web Reporting Tools.
   2. Select Settings in Enterprise Explorer.
   3. Check the View the catalog database option.
   4. Click Save Settings.
7. Go to Database Administration in the Reporting Tools Portal to see that the new Catalog Database name is displayed. At the top of the Database Administration screen, you will see Settings for: <machine name> \ <new Catalog Database name>.

Here are some examples of  shortcuts to type from Start –> run

 Blog info:

http://blogs.technet.com/wsus/archive/2007/05/15/srvhost-msi-issue-follow-up.aspx

What you need:

1) Microsoft KB 927891 - link

2) Build 0374 AU client/ WSUS 3.0 client: - link

 Other related too: Microsoft (SysInternals) Process Explorer - link

http://www.iespell.com/

Symantec article reference: http://seer.support.veritas.com/docs/261457.htm

Reg key to change is: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Backup\Fail Jobs on Corrupt Files
Change value to 0.

This has stopped me from running HP printer setup, Quickbooks setup, Add new Printer Wizard, and the SBS add new computer wizard.  Its a pain and I think its something we should turn off on all new installs.  Heres the article on how to do so by adding the “AlwaysOff” switch to the boot.ini file:

 http://support.microsoft.com/kb/875352