# Monday, January 26, 2009

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


outlookattremover-setup.exe (536.3 KB)
Monday, January 26, 2009 1:44:49 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Thursday, January 22, 2009

Version 2.8 of PFDAVAdmin can be downloaded here:


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:


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.


Thursday, January 22, 2009 8:32:03 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Wednesday, January 21, 2009


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

Many more articles on this site.

Wednesday, January 21, 2009 7:56:44 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Thursday, January 15, 2009

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.

Thursday, January 15, 2009 6:17:15 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Tuesday, January 13, 2009

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

Add /usepmtimer to boot.ini


Tuesday, January 13, 2009 10:26:45 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Friday, December 05, 2008

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"


Friday, December 05, 2008 3:06:16 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Tuesday, November 04, 2008

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.


whs | sbs
Tuesday, November 04, 2008 7:06:44 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Friday, October 31, 2008

Won't run from Control Panel in Vista (x64).  System has quiet UAC prompts via GPO/gpedit.

Solution is to "run as administrator"; or WinKey -> wercon -> Ctrl-Shift-Enter


Friday, October 31, 2008 8:27:53 AM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Thursday, October 30, 2008

In Vista x64 after a while crashes, then won't (ever) scan more than two pages without crashing.

Seems disabling OCR in the scan profile gets around this (or creating a new OCR-less profile).#

Thursday, October 30, 2008 7:27:39 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Wednesday, October 29, 2008
:: Fixes problem with client machines not showing up on the server due to imaging method

reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v AccountDomainSid /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v PingID /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientId /f
reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate /v SusClientIDValidation /f
@echo Triggering detection after resetting WSUS client identity
net stop wuauserv
net start wuauserv
wuauclt /resetauthorization /detectnow

See: http://www.wsuswiki.com/ClientFAQ and http://support.microsoft.com/?scid=kb%3Ben-us%3B903262&x=13&y=11

(AccountDomainSid and PingID weren't listed) SusClientIDValidation is new to WSUS v3.

Wednesday, October 29, 2008 4:54:23 PM (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback