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.
   

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

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).#

:: 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
cls
@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.

One or more of the following:

1. In adapter's TCP/IP DNS properties untick "register in DNS"
2. Stop DNS server listening on IP of adapter
3. Add the following DWORD = 1

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\<Interface name>\DisableDynamicUpdate

At install service accounts (RTCSservice, RTCComponentService) are created.

After a few weeks address book synchronisation began failing and after a restart all OCS services refused to start.

Appears service accounts' passwords had expired by a GPO.  Simply setting password to never expire allowed the services to start.  Address book sync problems needed the LSGroupExpAppPool application pool to be manually started.

Use launchapp

Operating systems older than Vista:

SELECT Version FROM Win32_OperatingSystem WHERE Version < "6" 

Vista and 2008 only:

SELECT Version FROM Win32_OperatingSystem WHERE Version LIKE "6.0%" 

Only Win XP SP2:

SELECT Version FROM Win32_OperatingSystem WHERE Version = "5.1.2600"

W2K8, regardless of SP. (ie Not equal to workstation (1))

SELECT * FROM Win32_OperatingSystem WHERE Version LIKE “6.0.%” AND ProductType <> “1”

Only on Windows Server 2008 Core servers.  Here is a sample query (wrapped for readability, this should be done as a single line in the filter dialog):

SELECT OperatingSystemSKU FROM Win32_OperatingSystem WHERE OperatingSystemSKU = 12 OR OperatingSystemSKU = 39 OR OperatingSystemSKU= 14 OR OperatingSystemSKU = 41 OR OperatingSystemSKU = 13 OR OperatingSystemSKU = 40 OR OperatingSystemSKU = 29

These values map back to HEX values, which map back to:

PRODUCT_DATACENTER_SERVER_CORE
0x0000000C

PRODUCT_DATACENTER_SERVER_CORE_V
0x00000027

PRODUCT_ENTERPRISE_SERVER_CORE
0x0000000E

PRODUCT_ENTERPRISE_SERVER_CORE_V
0x00000029

PRODUCT_STANDARD_SERVER_CORE
0x0000000D

PRODUCT_STANDARD_SERVER_CORE_V
0x00000028

PRODUCT_WEB_SERVER_CORE
0x0000001D

Only on a certain day of the week:

To do this, your WQL queries (one filter per GPO that you wanted to set, remember) would be:

Select DayOfWeek from Win32_LocalTime where DayOfWeek = 1

Select DayOfWeek from Win32_LocalTime where DayOfWeek = 2

Select DayOfWeek from Win32_LocalTime where DayOfWeek = 3

One is Monday, two is Tuesday, etc.

Select only laptops (ie computers without sodimm memory:

Select * from Win32_PhysicalMemory where FormFactor != 12

Not a server:

SELECT ProductType FROM Win32_OperatingSystem WHERE ProductType = “1”

See: http://blogs.technet.com/askds/archive/2008/09/11/fun-with-wmi-filters-in-group-policy.aspx