We used a very useful tool to make our SharePoint environment responsive after application pool recycles or web server restarts (iisreset) for years which is available under the GPLv2 license on CodePlex. It is called SPWakeUp which is a quite fast and simple tool to breathe new life into your server before you add that back to "production".
Issues with the original solution
As our environment grew, the wake up of the SharePoint sites took so long, for instance waking up a SharePoint environment with a ~0.5TB database took about a half hour which in our case meant high risk because as a general practise we remove the server from the load balancer for the maintenance period and we only add that back after the wake up. The second problem with the application was that it is full of memory leaks which in this case is not a serious issue because when the application stops the memory will be freed, but not too nice anyway.
As per our original goal, we wanted to speed up the wake up process (reduce the time required for the run), also we wanted to reduce the memory usage by eliminating memory leaks. To achieve these goals a large part of the application has been modified/rewritten, but we tried to keep the most of the original source code and processing logic as possible. It means that for instance we tried to keep the wake up order of the sub sites within each site collection although changing the order would meant less code.
Multi threaded application
The "verbose" mode has been extended with multi threading capabilities. The application will open each site on its own thread. Because the application utilize the thread pool object, it will not consume the resources of the server, but it will run faster after the collection of the sites on the portal.
How it works
The followed process is very easy:
Reads the farm configuration (Web application list)
Navigates through the site collections and sub sites
Based on the site list, it can parallely send http or http requests to the portal.
As the original version of the software is distributed under GPLv2, this software must follow that license as well.
SPWeakUp.zip (35.79 kb)
Compilled code.zip (16.33 kb)
When you use Internet Explorer, it can be very comfortable to say yes for the password saving prompt, simply because it is stored in a secure way in your Windows profile on your computer. The only issue with this, that if you save not just form authentication passwords but Server/Windows authentication passwords as well, the browser will try to logon automatically to the specific system.
If you would like to change your identity - prevent Internet Explorer to use Single Sing-on (SSO) - you have to delete the saved password. If you don't want to search for panels on the Control Panel, simply run the following command in the Run popup:
After that press the [enter] button. On the panel appear go to the second tab called Advanced and press the Manage passwords button. There you can delete all of your saved passwords but of course you should remember your deleted passwords because you won't be able to log on to your systems anyway.
Who ever used the Sent to Notepad feature on Windows XP will wonder how it is possible to hide this functionality extensibility on Windows Vista. The root cause of our problem is the following: by default an administrator is not a real administrator on the computer without the elevation of privileges and that's why we don't have access to the Send To folder using general methods but following the next few steps we will be able to overcome on this behaviour:
Create a shortcut to the NotePad.exe file in any folder, for instance in the c:\temp folder
Start a simple command prompt (Windows button + R, cmd + [enter])
Step into the SendTo folder (cd SendTo)
Copy your shortcut to this SendTo folder using the following DOS command: "copy c:\temp\notepad.lnk ."The dot (.) is necessary at the end because that stands for the current folder.
Use the Send To Notepad feature
Another interesting thing: after the successful copy if you check the content of the SendTo folder using the DIR command, you will find that empty. Just like if you run the command prompt in elevated mode (using the Run As Administrator option).