How to fix a messed up domain controller

Just get rid of it!

• Disconnect the DC from the network
• Run dcpromo /forceremoval
• From 2003, use NTDSUTIL to do a "metadata cleanup" to clean the DC out of your AD.  (See below) If you have at least one Windows Server 2008 DC, then open Active Directory Users and Computers from a 2008 DC, find the bad DC, right-click and delete.

Metadata Cleanup using NTDSUTIL
MS Article 216498 explains how to forcibly remove a domain controller account from AD using NTDSUTIL.
http://support.microsoft.com/kb/216498

Time to Check Sysvol
Sysvol is a share you can find on every domain controller, a share that contains files needed by DCs -- the big ones are the file components of group policy objects (GPOs), pieces called "group policy templates" or GPTs, as well as login scripts. Sysvol is a neat, built-in implementation of DFS (Distributed File Services) that is multi-master, meaning that if you have four DCs named DC1, DC2, DC3 and DC4, then you can drop a file into any one of those four Sysvol folders, and eventually DFS will ensure that there's a copy of that file in each of the other three Sysvols. The fact that you can introduce a new file into the family of Sysvols is why it's said to be "multi-master." On 2003 SP3 and later, there's a command that lets you force replication between a source DC (DC3, in this example) and a destination DC (DC2, in this example) that looks like this:

ntfrsutl.exe forcerepl DC2 /r "Domain System Volume (SYSVOL share)" /p DC3

Check SYSVOL before upgrading
Go to a DC. In its Sysvol, create a file, such as [dcname].txt. After you have created a small text file on each DC whose name reflects the DC that you created it on. Wait a while and go to each DC and look in its Sysvol... there should be a file for each domain controller. If, for example, DC4's dc4.txt shows up nowhere, then DC4 probably has the problem. To fix it, run DCPROMO to demote it and, if the rest of the network doesn't see that you've demoted it, remove the DC's account from the Domain Controllers OU and remove its metadata. Once it is successfully removed, test again by creating another unique file in each DC's Sysvol and be sure everything is cool.

Thanks to:
http://www.minasi.com/newsletters/nws1205.htm

Microsoft Product Support Lifecycle

http://support.microsoft.com/lifecycle/?LN=en-us&x=13&y=5

Operational limits of Word Documents

MS KB 211489
Very interesting:
The maximum file size is limited to 32 MB for the total document text only and does not include graphics, regardless of how the graphics image is inserted (Link to file, Save with document, or Wrapping style) into the document. Therefore, if the file contains graphics, the maximum file size can be larger than 32 MB.

Hey, Scripting Guy! How Can I Delete All the .BAK Files in a Folder That Are More Than 7 Days Old?:
"dtmDate = Date - 7

strDay = Day(dtmDate)

If Len(strDay) < 2 Then
strDay = '0' & strDay
End If

strMonth = Month(dtmDate)

If Len(strMonth) < 2 Then
strMonth = '0' & strMonth
End If

strYear = Year(dtmDate)

strTargetDate = strYear & strMonth & strDay

strComputer = '.'

Set objWMIService = GetObject('winmgmts:\\' & strComputer & '\root\cimv2')

Set FileList = objWMIService.ExecQuery _
('ASSOCIATORS OF {Win32_Directory.Name='C:\Scripts'} Where ' _
& 'ResultClass = CIM_DataFile')

For Each objFile In FileList
strDate = Left(objFile.CreationDate, 8)
If strDate < strTargetDate Then
If objFile.Extension = 'bak' Then
objFile.Delete
End If
End If
Next"

Test drive the 2007 Microsoft Office release - Help and How-to - Microsoft Office Online: "Test drive the 2007 Microsoft Office"
Test drive Office 2007 over the internet without installing it.

Microsoft Exchange: Publish different free/busy time periods: "Microsoft Exchange: Publish different free/busy time periods"
By default, Outlook will publish two months of free/busy information. While you're able to change this interval in Outlook (by going to (Tools > Options > Calendar Options > Free/Busy Options), Outlook Web Access is also subject to this two-month default, which can prove to be quite inconvenient since OWA users don't have an easy way to change this setting. To make matters worse, even if you do configure Outlook with a longer interval, Outlook may eventually revert back to the two month default. While you can run Outlook with the /cleanfreebusy switch to correct the problem, it still may not "stick."

The solution: On your Exchange servers, add a registry key that redefines the two month default value into something more suitable for your organization.

-Open the registry editor.
-Browse to the key HKLM\Software\Microsoft\ExCDO\Parameters.
-Under this key, add a DWORD entry named "FBPublishMonth".
-The value of this new entry is a number, which is the number of months for which you would like to publish free/busy information across the board, for all users.
-Restart IIS and the System Attendant services on your Exchange servers.

Help and Support: "Microsoft Support Lifecycle
Microsoft’s Support Lifecycle policy provides consistent and predictable guidelines for product support availability at the time of product release and throughout the product life. By understanding the product support available, customers are better able to maximize the management of their IT investments and strategically plan for a successful IT future. "

Event ID 9646 is logged when you try to send many messages in Exchange Server 2003

XCON: Site Connector and RPC Communication Within Sites Over a VPN