Adding this for reference, in case, I need to activate/revert on my workstation.
Below is a summary of the “two top things that cause trouble in production ASP.NET web sites,” per Scott Hanselman, which he obtained from deep within Microsoft Developer Support. Go here to read the complete article.
#1 Issue – Configuration
Seems the #1 issue in support for problems with ASP.NET 2.x and 3.x is configuration.
| Symptoms | Notes |
| OOM Performance High memory Hangs Deadlocks |
There are more debug=true cases than there should be. |
#2 Issue – Problems with an External (non-ASP.NET) Root Cause
Sometimes when you’re having trouble with an ASP.NET site, the problem turns out to not be ASP.NET itself.
| Issue | Product | Description | Symptoms | Notes |
| Anti-virus software | All | Anti-virus software is installed onto Servers and causes all kinds of problems. |
|
This consists of all AV software reported by our customers. All cases do not report the AV software that is being used so the manufacturer is not always known. KB821438, KB248013, KB295375, KB817442 |
| 3rd party Vendors | All | This is a category of cases where the failure was due to a 3rd party manufacturer. |
|
The top culprits are 3rd party database systems, and 3rd party internet access management systems |
| Microsoft component | All | Microsoft software |
|
Design issues that cause performance issues like sprocs, deadlocks, etc. Profile your applications and the database! (Pro tip: select * from authors doesn’t scale.) Pair up DBAs and programmers and profile from end to end |
1. Choose Tools -> Import and Export Settings…
2. Select Reset All Settings and click Next
3. Select whether you would like to save the current settings and click Next
4. Select the settings you want to use and click Finish
Posting for archival purposes [via Blogsdna].
1. Download Concurrent Sessions enabler file
2. Once downloaded, extract the files into a directory (for the purposes of this guide, it will be assumed that the files have been extracted to the folder C:\Win7RDP )
3. Open Windows Explorer to the above folder
4. Right Click on “install.cmd” and select “Run as Administrator”
5. Wait for the script to run entirely. At the end, you should see something similar to the below…
6. That’s it! Test it out.