To change the application pool for an existing Windows SharePoint
Services site (IIS virtual server):
-Ensure that the new application pool is running under the same
identity the old AppPool is running as. (if you don’t, then SharePoint
may not be able to connect to the content or configuration database)
-In IIS, expand Web Sites.
-Right-click on the virtual server you want to change and select properties.
-On the ‘Home Directory’ tab, under the ‘Application settings’
section, change the ‘Application pool:’ to the new application pool
and click Apply, then OK.
-Back in the Internet Information Services Manager, expand the virtual
server you are changing by clicking the + sign beside the name.
-For every Virtual Directory (default virtual directories for a WSS
site are _layouts, _vti_bin, and _wpresources)under the website,
ensure they are running under the new application pool by:
–>Right-clicking on the virtual directory, select Properties.
–>Under the ‘Application settings’ section, change the ‘Application
pool:’ to the new application pool if necessary, and click Apply, then
You can map a network share to a SharePoint site (or individual
document library) doing the following:
net use s: http://sharePointserver/somesite/doclib
Note that if there is a space in the path, you need to use quotes
around the url:
net use s: “http://sharePointserver/somesite/shared documents”
Also need to ensure the WebClient service is running.
This would be really useful for automated uploading of documents
through scripts, etc.
1-Copy the databases from the old SQL server to the new one.
2-Then, in the config database on the new SQL server, open the Servers
table in the config database.
3-Change the Name and Address fields that have the old SQL server name
to the new SQL server name.
4-Open the SharePoint Central Administration page and click on “Set
configuration database server” under the Server Configuration section.
5-Change old SQL server name to new SQL server name. Click OK.
6-Again on the SharePoint Central Administration page, click on
“Configure virtual server settings”, and then click on a website you
want to change.
7-Click on “Manage content databases” under Virtual Server Management.
8-Click “Add a content database” and then ensure “Specify database
server settings” is selected.
9-Enter the SQL server name and database name. Enter 100 for each of
the following boxes and click OK. (Notice the content database that
was already there will have a 0 under the “Current Number of Sites”
column. This is because SharePoint realizes you are trying to
substitute. You can then remove the old database from the WSS list.)
Repeat steps 6-9 for any additional sites.
I know there are several steps, but it is truly the easy way. It goes
much smoother than any other way (in my experience).
Ensure the account used for the Application Pool has rights to the
databases (both config and any content db).
Note: Editing SharePoint databases can make your configuration ‘unsupported’ by Microsoft
Here is a little info on setting alerts using the STSADM command (from the Windows SharePoint Services Admin Guide). It can also check/change many other settings. Take a look:
You can manage alerts from the command line by using the GetProperty and SetProperty operations with Stsadm.exe. You can set the following properties to configure how alerts work.
Property —-> Description
alerts-enabled —-> Turn alerts on or off.
alerts-limited —-> Specify whether users are limited to a specific
number of alerts.
alerts-maximum —-> Specify the maximum number of alerts users can create.
job-immediate-alerts —-> Specify how often to check for immediate
alerts (in minutes).
job-daily-alerts —-> Specify the time of day (using a 24-hour clock)
to send out daily alerts.
job-weekly-alerts —-> Specify the day of the week and time of day
(using a 24-hour clock) to send out
The following example shows the syntax to use to turn off alerts:
stsadm.exe -o setproperty -url -pn alerts-enabled