Sometimes you come upon a strange KB article - which makes you wonder why that information is public or what’s the general purpose of the article is… I found this one today:

How to extend the Windows Server 2008 evaluation period
http://support.microsoft.com/kb/948472

This is quoted from the article:

SUMMARY

This article describes how to extend, or re-arm, the Windows Server 2008 evaluation period. The evaluation period is also known as the "activation grace" period. These instructions apply to any edition of Windows Server 2008. This includes evaluation copies.

INTRODUCTION

Evaluating Windows Server 2008 software does not require product activation. Any edition of Windows Server 2008 may be installed without activation, and it may be evaluated for 60 days. Additionally, the 60-day evaluation period may be reset (re-armed) three times. This action extends the original 60-day evaluation period by up to 180 days for a total possible evaluation time of 240 days.
Note Although you can reset the 60-day evaluation period, you cannot extend it beyond 60 days at any time. When you reset the current 60-day evaluation period,

…

FireFox when compared to IE has many features which can be turned on and off. Users can play with the tweaks for enhanced user experiences. Here is a short tutorial on how to speed up your internet connection with FireFox. Follow these steps:

1. In FireFox address bar (where you type the website address) type about:config and hit enter.
2. In filter box just below the address type in network.
3. Then scroll down half way untill you see network.http.pipeling. Click on the right column to change the value to True.
4. Now below this row change the value of network.http.pipeling.maxrequests to 10.
5. Then click ok and restart FireFox.

(more…)

address type, config, experiences, Firefox, follow these steps, Internet, internet connection, knowledge base, maximum value, mozilla, mozillazine, pipelining, servers support, then scroll down, tweaks, Web, website address

I have seen this issue too many times now, so I have to write this short blog about it!

Have you ever seen this error when trying to connect to a Remote Desktop enabled machine using MSTSC/Remote Desktop Client:

Remote Desktop Disconnected
The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connecting again later. If the problem continues to occur, contact your administrator.

Well, I’ve seen it so many times now, especially on ISA servers… Even after the RDP sessions have worked nicely, sometimes, for some reason, the RDP settings can be changed - or even “corrupted”. In most cases the above error has something to do with NIC (Network Interface Card) adapter binding to RDP.

If you are experiencing this issue go read the Microsoft KB article: “You can not establish a Remote Desktop session to a computer running one of the affected products”. You will find it here http://support.microsoft.com/kb/555382 - good luck!