Fresh install of XP SP2 immediately updated to SP3 (Also, Office 2007 SP1 installed).

After, both Windows Update and Microsoft Update detect updates but fail to install any.  No error codes or entries in the event logs.  No info in WU Update History (nothing ever installed by this method).

Fix is install Windows Update Agent 3.0.

Save this to desktop then run the following from a .cmd file:

net stop wuauserv
"%userprofile%\Desktop\WindowsUpdateAgent30-x86.exe" /wuforce
regsvr32 "%windir%\system32\wup2.dll"
net start wuauserv
exit

See

http://www.broadbandreports.com/forum/r20453460-XP-Pro-Updates-Fail-after-Fresh-Install-and-XP-SP3-Loaded

When completing SBS setup on the final server during a Swing It! migration this error halts setup.

Solutions are: Bypass trust check

1. Start SBS setup process
2. Cancel
3. Locate Sitxxx.tmp temp (%temp%) Directory
4. Open Setup.sdb in text editor
5. Comment out the trust check line
6. Save and continue the setup process from the Sitxxx.tmp directory

Or change GUID on the replica DCs

1. Regedit - HKLM - Security - Permissions - Add Administrators - Full Control
2. Cmd - cd c:\windows\program files
3. nltest/domain_trusts/all_trusts/v
4. Record domain GUID string
5. Regedit - HKLM\SECURITY\Policy\PolDnDmG - change GUID to earlier recorded value - restart
6. Undo permission changes

See KB909639 and article at smallbizserver.net

"Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or because your computer account was not found."

Together with Event IDs 3210 and 40960

Prevent by:

HLM\SYSTEM\CurrentControlSet\Services\NetLogon\Parameters "DisablePasswordChange"=dword:00000001

See KBs 475468 and 888794

Or, Group/Local Policy

Local Computer Policy | Windows Settings | Security Settings | Local Policies | Security Settings | Local Policies | Security Options

- Domain Member: Disable machine account password changes (DisablePasswordChange)
- Domain Member: Maximum machine account password age (MaximumPasswordAge)
- Domain Controller: Refuse machine account password changes (RefusePasswordChange)

See: http://www.petri.co.il/forums/archive/index.php/t-10129.html

and: http://technet2.microsoft.com/WindowsServer/en/library/9f921edc-87f5-460e-89ee-9ca56ec1d0961033.mspx?mfr=true

and: http://technet2.microsoft.com/WindowsServer/en/library/3558c421-ba3d-4b8f-a107-b9058cc0f2861033.mspx?mfr=true

After Swing It! migration if required use: legacydn /forcewrite

SFC terminates at 39% with the above error.

%windir%\logs\CBS.log shows that a folder is not found:

2008-05-01 11:30:23, Error CSI 0000009b (F) STATUS_OBJECT_NAME_NOT_FOUND #1442392# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (STANDARD_RIGHTS_READ|FILE_READ_ATTRIBUTES), oa = @0x6be774->OBJECT_ATTRIBUTES {s:24; rd:NULL; on:[120]"\??\C:\Windows\WinSxS\x86_microsoft-windows-i..l-keyboard-0000420_31bf3856ad364e35_6.0.6000.16386_none_e499ad916795d771"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x6be794, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = 0x00004000, eab = NULL, eal = 0, disp = Invalid)

The folder \WinSxS\x86_microsoft-windows-i..l-keyboard ...etc is obviously corrupted (as it is now a 0kb file).

Used WinImage to extract this file from a Vista Business RTM vhd.  Comparing file size details of other folders and files suggested that this version would work.

To delete corrupt file/folder and replace with good version:

• Take ownership of corrupt folder/file and WinSxS folder (ie parent) only
• Give Full Control permissions to corrupt file and delete
• Copy replacement file
• Remove permissions from replaced folder and file(s)
• Give NT SERVICE\TrustedInstaller ownership of replaced folder/children and parent directory

Running SFC now completes, albeit with a further uncorrectable error:

... Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-mulanttsvoiceenudsk_31bf3856ad364e35_6.0.6000.16386_none_0d44c2d7a6e22754\M1033DSK.CSD do not match actual file [l:24{12}]"M1033DSK.CSD"

Which is corrected, as above.  Now SFC dectects and repairs a hash mismatch.  A further run completes with no errors.

Updating Nero Burning ROM?

Suggest backing up HKLM\Software\Classes first

Comment out:

;JoyV=Axis ...
;JoySlider1=Axis ...

Sharepoint Central Administration
Virtual Server Configuration
Configure virtual server settings
Default Web Site
Virtual Server Management
Define managed paths
Add New path -> certsrv -> Excluded path
OK

See: http://www.microsoft.com/technet/prodtechnol/biztalk/2006/library/a4swift/39916663-b80e-49d8-ba9b-49276eb564fc.mspx?mfr=true

After DS restore WSUS, SQL Reporting Services and SSEE failed to start.

For SSEE first extract ssee_10.msi from WSUSSetup*.msi\wYukon and then run the following command:

msiexec /i ssee_10.msi CALLERID=OCSetup.exe REINSTALL=ALL RINSTALLMODE=omus /qn REBOOT=ReallySupress /l*v c:\ssee_repair.log

Update Services (WSUS) wouldn't reinstall complaining about a lack of .NET Framework 2.0 and .NET Framework 2.0 wouldn't reinstall due to "... incompatible with a previously installed one" (ie NET2.0 SP1).  Solution is to change/repair from add/remove programs and reboot.

Reporting services is fixed by this, too.

Finally, for any EVENT IDs 1309s to run %WINDOWS%\Microsoft.NET\Framework\V2.0.50727\aspnet_regiis.exe -i

References:

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

http://www.brienposey.com/kb/database_corruption_4.asp

Steps for my -1019 on 65GB mailbox store.  Took 8 hours.

eseutil /d e:\exchsrvr\mdbdata\priv1.edb /te:\tempdfrg*.edb /fe:\tempdfrg*.stm

This failed after 206 secs which was to be expected

eseutil /p e:\exchsrvr\mdbdata\priv1.edb /te:\temprepair*.edb

eseutil /mh e:\exchsrvr\mdbdata\priv1.edb

isinteg -s server02 -fix -test alltests

An alternative approach might have been to exmerge all mailboxes into a newly created database:

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