Jan 30
Consider the following scenarios that occur when you upgrade Microsoft Windows SharePoint Services 2.0 or Microsoft Windows SharePoint Services 3.0:
| |
Scenario 1
You install Windows SharePoint Services 2.0 Service Pack 1 (SP1). After you do this, the version number that is listed in Site Settings is not updated to the version number for the latest updates or for the latest Windows SharePoint Services 2.0 service pack. For more information about how to obtain the Windows SharePoint Services 2.0 major release versions, see the following Microsoft Knowledge Base article:
875358 (http://support.microsoft.com/kb/875358/) You must update all the Web servers that are running Windows SharePoint Services in a Web farm
|
| |
Scenario 2
You upgrade from Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0. If you detach the Windows SharePoint Services 2.0 database before the upgrade has completed, the upgrade is not completed successfully. |
| |
Scenario 3
You use the gradual method to upgrade from Microsoft SharePoint Portal Server 2003 to Office SharePoint Server 2007 or from Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0. However, the upgrade is not completed. When you view the Central Administration Web site under Administrative Tasks, the upgrade status displays Job Pending. |
| |
Scenario 4
You try to perform an inplace upgrade of SharePoint Portal Server 2003 to Office SharePoint Server 2007. However, the upgrade is not completed. When you view the Central Administration Web site under Administrative Tasks, the upgrade status displays Job Pending. |
Share This
Jan 30
Use the Packages feature to export and to import a Windows SharePoint Services Web site
You can use the Packages feature to move a Web site as empty content. When a Web site is moved as empty content, list data that is part of the original Web site does not move with the Web pages in the package. However, documents in a document library are packaged and will be moved with the Web pages in the package.
To use the Packages feature to move a Windows SharePoint Services Web site from one server to another, follow these steps:
| 1. |
Start FrontPage 2003, click File, and then click Open site. |
| 2. |
In the “Look In” list, locate your source Web site, and then click Open. |
| 3. |
Click Tools, click Packages, and then click Export. |
| 4. |
In the “Files in Web site” list, click the Web site folder, and then click Add. |
| 5. |
Click OK. |
| 6. |
In the Save in box, click the folder where you want to save your Web package, click Open, and then click Save. |
| 7. |
When you receive the message that states that the Web package has been saved, click OK. |
| 8. |
Click Tools, point to Packages, and then click Import. |
| 9. |
In the “Look In” list, open the folder where you saved your Web package, click the Web package file, and then click Open. |
| 10. |
In the Destination box, type the URL of the Web server where you want to import the Web site package.
Alternatively, you can click Browse to locate the Web server where you want to import the Web site package. |
| 11. |
Click Import. |
| 12. |
In the Security Warning dialog box, click Yes. |
| 13. |
In the Web Package Your_Package_Name deployment complete dialog box, click OK. |
Read the rest of this entry »
Share This
Jan 30
dim dayweekdim strBackup dayweek = datepart("w",(date)) strBackup = """C:Program FilesCommon FilesMicrosoft Sharedweb server extensions60BINstsadm""" + _
"-o backup -url http://companyweb -filename x:backupscompanyweb" + cstr(dayweek) + ".dat -overwrite"
Set WshShell = WScript.CreateObject("WScript.Shell") Return = WshShell.Run(strBackup, 0, true) Set WshShell = Nothing
To add this script as a scheduled task, follow these steps:
| 1. |
Open Control Panel. |
| 2. |
Double-click Scheduled Tasks. |
| 3. |
On the File menu in Scheduled Tasks, point
to New, and then click Scheduled
Task. |
| 4. |
Type a name for the scheduled task, such as
Companyweb Backup. |
| 5. |
Double-click the new task to open the task
properties. |
| 6. |
In the Run box, type cscript
Drive:\Wssback.vbs.Note In this step, Drive is the location of
the Wssback.vbs file. |
| 7. |
Click Set password, type the password for
the user account that the task will use in the Password box
and in the Confirm password box, and then click
OK. |
| 8. |
Click the Schedule tab, configure the
appropriate schedule, and then click OK. |
| 9. |
To test the scheduled task, right-click the task, and then
click Run. After the task runs, visit the location that you
specified for the backup file to verify that the script created the file. |
Powered by ScribeFire.
Share This
Jan 30
To turn on Windows SharePoint Services usage logging in an Office
SharePoint Server farm, you must first turn on Usage Analysis
Processing in Windows SharePoint Services 3.0, and then turn on
Advanced Usage Analysis Reporting service in Shared Services
Administration. To do this, follow these steps:
| 1. |
Click Start, point to All
Programs, point to Administrative Tools, and then
click SharePoint 3.0 Central Administration. |
| 2. |
On the Central Administration page, click Operations. |
| 3. |
On the Operations page, under Logging and Reporting, click Usage Analysis Processing. |
| 4. |
In the Logging Settings section, click to
select the Enable logging check box. |
| 5. |
In the Log file location box, type the
location where you want to store the log file. The default location
for the log file is \Program Files\Common Files\Microsoft Shared\Web Server Extension\12\Logs. |
| 6. |
In the Number of log files to create box,
type a number between 1 and 30.In general, use a number that is one
to three times the number of database servers in your server farm, with a
maximum number of 30 log files. |
| 7. |
In the Processing Settings section, click
to select the Enable usage analysis processing check box. |
| 8. |
Under Run processing between these times
daily, specify the range of times to start the usage analysis log
processing.In the Start box, select the earliest
time of day to start running log processing. In the End box,
select the latest time to start running log processing. |
| 9. |
Click OK. |
Powered by ScribeFire.
Share This
Recent Comments