Even though I’ve grown accustomed to simply typing in a period (.) for the shutdown reason, and clicking OK, even that gets old, therefore, below is the registry key to use for disabling it altogether in Server 2003/2008:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Reliability]
"ShutdownReasonOn"=dword:00000000

Ahh, much better!

Note:  If you want this same functionality in Windows XP, there is a different registry location for that which is referenced here.

https://www.bing.com/docs/submit.aspx

To determine whether or not your site has already been indexed by Bing, simply use this syntax and type the following in the Bing search box:  site:www.yoursite.com

If you get any results, it has been crawled by the MSNBot crawler.

I used an old CD spindle cover as a stand, then simply pushed two pushpins (mine happened to have black and red tips - SCORE!) through the top at the correct distance, then found some random items for the headset to sit on so the angle would be correct.  Voila!  It’s charging and will be ready by the time I wake up.  W00t!!

For the curious, in the picture above (click for larger), the positive lead is the right outermost pin, and the negative lead is the left outermost pin.

Necessity breeds innovation again (and by again, I am referring to my original Jawbone home-built charger, which I must say was more interesting)!

Warning:  I take no responsibility for any of YOUR actions that would lead to the destruction of anything at all, if you decide to attempt this DIY solution.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Directory\Background\shell\TaskMan]
@="Task Manager"

[HKEY_CLASSES_ROOT\Directory\Background\shell\TaskMan\command]
@="taskmgr.exe"

You could easily replace this with any other program you frequently run as well J.

Or perhaps one similar to this?

Unfortunately, these types of “unexpected error” messages do not provide any level of detail as to the actual problem, but instead, only inform you, the admin, there was some type of error that prevented the expected page from coming up properly.

When this happens, there are two changes I make in the application’s web.config file, which have always helped uncover the true problem.

To show the call stack:

Change

<SafeMode MaxControls="200" CallStack="false"
DirectFileDependencies="10" TotalFileDependencies="50"
AllowPageLevelTrace="false">

to

<SafeMode MaxControls="200" CallStack="true"
DirectFileDependencies="10" TotalFileDependencies="50"
AllowPageLevelTrace="false">

To turn custom errors off, so the error and the call stack can be shown:

Change

<customErrors mode="On" />

to

<customErrors mode="Off" />

I’ve seen others mentioning the need to change AllowPageLevelTrace="false" to AllowPageLevelTrace="true", however, I have not had to do this with SharePoint thus far.

One you’ve saved your web.config, the appdomain will be torn down and reloaded on the next incoming request (this happens automatically upon any change to the web.config, by design) and you should be ready to find out your true error.

This is a very basic script, but answered the question easy enough.  Hopefully, it can help you in some way as well:

On Error Resume Next
Const wbemFlagReturnImmediately = &h10
Const wbemFlagForwardOnly = &h20
arrComputers = Array("localhost")

For Each strComputer In arrComputers
   WScript.Echo
   WScript.Echo "=========================================="
   WScript.Echo "Computer: " & strComputer
   WScript.Echo "=========================================="

   Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2")
   Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_Processor", "WQL", _
                                          wbemFlagReturnImmediately + wbemFlagForwardOnly)

   For Each objitem in colitems
WScript.Echo objItem.DeviceID
WScript.Echo "   DataWidth    = " & objItem.DataWidth
WScript.Echo "   AddressWidth = " & objItem.AddressWidth

If objItem.DataWidth > objItem.AddressWidth Then
         WScript.Echo "Your hardware is 64-bit capable, but you are running on a 32-bit operating system."
End If
   Next
Next

Simply save the above as a file and run it via “cscript <filename.vbs>” as normal.

If you download hotfixes on a regular basis, this may be old news for you, but if not, you may find use in the below.  Most, if not all recent hotfix articles contain the means to obtain the hotfix electronically, without having to call into support beforehand.  This can be a great timesaver.

Here’s how to go about doing it, in detail.  I will be using following article as an example:  https://support.microsoft.com/kb/961755.

This happens to be SharePoint’s WSS February Uber Cumulative Update.  Simply click the link at the top left of the article to view and request the hotfix:

By default, the page attempts to detect your platform, and, if successful, may only show the x86 or x64 version of the hotfix by default, so I’ve highlighted a couple of useful things to click below. The first will show you all available hotfixes for all platforms and languages.  This is not very intuitive and really should be shown by default, in my opinion, to save everyone some grief:

From there you can select both and download as normal.

Finally, if you want to see additional information about the hotfixes, click the “Show additional information” link, as I’ve highlighted above:

This reveals the detailed build information, among other useful things.

Note:  You can enable both options at once to view all of the details, which again, I feel should just be shown by default…