Original article here.
You can make the server execute a script at shutdown time by using the Group Policy Editor, which is an MMC (Microsoft Management Console) snap-in. I will explain how to use the Group Policy Editor shortly, but first, we need to create the batch file that will shut down the Exchange services.
Originally from here
Open Explorer and go to “C:\Program Files\Microsoft Windows Small Business Server\Backup”
Make a copy of bkprunner.exe
Download and extract XVI32.
Run XVI32.exe
Open bkprunner.exe in XVI32
The address range $10F0-$11B7 is used for backups to .bkf files
The address range $11B8-$1277 is used for backups to tape
To turn off verify when backing up to a .bkf
Go to address $113A
In the hex pane (the middle one), type in the following hex values:
6E 00 6F 00 20
This enters in the text “no ” in Unicode format.
Original from HERE
Copy of orginal post:
I mentioned before that Windows XP does not allow concurrent sessions for its Remote Desktop feature. What this means is that if a user is logged on at the local console, a remote user has to kick him off (and ironically, this can be done even without his permission) before starting work on the box. This is irritating and removes much of the productivity that Remote Desktop brings to Windows. Read on to learn how to remove that limitation in Windows XP SP2
Hopefully most people know that MOSS is a superset of WSS. In other words, MOSS takes the foundation laid by WSS v3.0 and expands upon it, creating features that sit on top of it, utilize the core WSS framework, and extend it in such a way that is beneficial to larger companies, enterprise deployments, and portal scenarios. The following is a list of things that MOSS provides that WSS v3.0 does not. I figured it would be a waste of text to show the features that the two have in common, or the places in which MOSS re-uses WSS functionality without change or enhancement.
http://dotnetaddict.dotnetdevelopersjournal.com/moss_vs_wss.htm
http://office.microsoft.com/en-us/sharepointtechnology/FX101758691033.aspx?ofcresset=1
http://blogs.officezealot.com/rbedell/archive/2005/10/27/8365.aspx
Useful link on how to analyse a windows BSOD memory dump.