After installing (upgrading) W7 Device Manager shows that this device cannot load.  Solution is to manually specify the Legacy driver.

%systemroot%\Inetpub\Adminscripts

adsutil.vbs Set MSFTPSVC/DefaultLogonDomain "DOMAIN" [include quotes]

Restart FTP service

Upgraded nVidia 8400 GS driver which resulted in intermittent, then constant, high fan noise.  System Restore didn't cure it.

Installing current BIOS (A06 -> A15) fixes this.

Free utility to strip out and store attachments in the file system while keeping a pointer ti the attachment in Outlook.

http://www.kopf.com.br/outlook/

Version 2.8 of PFDAVAdmin can be downloaded here:

http://www.microsoft.com/downloads/details.aspx?familyid=635be792-d8ad-49e3-ada4-e2422c0ab424&displaylang=en

It seems to need .NET 1.1 to access the Exchange mailboxes and public folders.  This is best done on an admin machine (not the Exchange server as installing v1.1 might break v2.0 and Exchange itself!).)

Download 1.1 and SP1 here:

http://www.microsoft.com/Downloads/details.aspx?FamilyId=262D25E3-F589-4842-8157-034D1E7CF3A3&displaylang=en
http://www.microsoft.com/Downloads/details.aspx?familyid=A8F5654F-088E-40B2-BBDB-A83353618B38&displaylang=en

Installing .NET on Vista x64 gives a compatibility error (with IIS), although installs okay.  See http://www.mydigitallife.info/2007/12/27/install-microsoft-net-framework-11-on-windows-vista-fix-regsvcsexe-fails-error/ for related (?) details.

http://printer1.blogspot.com/

Fading magenta problem on HP 2605: http://www.fixya.com/support/t203256-no_magenta_printing_out

Many more articles on this site.

Exchange 2003 IMAP4

Certain users cannot login although domain usernames and passwords are correct. Error message:

* NO Logon failure: unknown user name or bad password

Resolution: check user's mailbox name (alias) is the same as their account name.

Will cause problems such as negative ping times and USERENV errors.

Add /usepmtimer to boot.ini

Maybe error indexing an Outlook item?

net stop wsearch (might have to set service to "Disabled")

Regedit -> HKLM\Software\Microsoft\Windows Search

Give self Full Control -> "SetupCompletedSuccessfully" change to "0"

For each of following keys, give self Full Control and Take Ownership (& propogate), then delete

HKLM\Software\Microsoft\Windows Search\Applications\windows
HKLM\Software\Microsoft\Windows Search\CatalogNames\windows
HKLM\Software\Microsoft\Windows Search\Databases\windows
HKLM\Software\Microsoft\Windows Search\Gather\windows
HKLM\Software\Microsoft\Windows Search\Gathering Manager\Applications\windows
HKLM\Software\Microsoft\Windows Search\UsnNotifier\windows

rd %ProgramData%\Microsoft\Search\Data\Applications\Windows /S /Q

Set Windows Search to "Automatic"

net start wsearch

Check "SetupCompletedSuccessfully" now has value "1"

SBS (and WHS?) if not dcpromo'd will, after seven days, shut down every hour.  The process sbscrexe.exe is created by the SBCore service.  If terminated it will immediately restart and it cannot be stopped.  The service SBCore cannot be set to "disabled".

There are two (three?) ways to work around this.  All will likely violate the MS EULA.

• Use Process Explorer to 'suspend' sbscrexe.exe
• Give Administrators permissions to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SBCore (and child nodes) and change the 'Start' DWORD from 2 to 4
• Deny the Everyone group all access to C:\WINDOWS\system32\sbscrexe.exe
• In Process Explorer kill sbscrexe.exe - it shouldn't restart
• services.msc should now show SBS Core Services as disabled

• An alternative approach is to disable the 'SBS Core Services' service in a particular hardware profile (ie can't do a outright disable) assuming there is only one hardware profile.

• Finally, repeated kills of the sbscrexe.exe process might completely kill it for a single session.

Edit - having an ntbackup process running in the background seems to stop sbcore from shutting down.