|
|
October 16 Tags: moss wss deployment isa aam Excellent Article on MSDN http://msdn.microsoft.com/en-us/library/cc441431.aspx Watch the VideoTags: msdn wss solution addsolution deploy solution workflow customize msbuild October 06 The
Microsoft Software + Services Blueprint folks have been kind enough to
build a blueprint for the use of Silverlight in SharePoint Web Parts.
The Silverlight Blueprint for SharePoint
is source code and guidance for developers describing how to use
Microsoft Silverlight and Microsoft SharePoint Products and
Technologies together in business applications and Internet web sites.
SharePoint applications that use Web Parts can now be built using
Silverlight user interface elements. This capability enables a fresh
look at data exposed through SharePoint Products and Technologies using
the modern graphics capability in Silverlight.
For
more information about samples that we’ve built that you can reuse,
customize, or extend for your SharePoint web sites and for links to
downloads and screencasts click here to go to the Silverlight Blueprint for SharePoint page on MSDN.
Regards, Saurabh Dhall Download Silverlight
Instructions on Silverlight Blueprint for SharePoint Official Web for Microsoft's Silverlight Following are the Steps for Sharepoint's Integartion with Silverlight.
These pictures come from a SharePoint image library http://www.wssdemo.com/today
but use a Data View web part to add each image to a SilverLight control.
Based on an SPS 2003 web part from http://binaryjam.wordpress.com/2007/06/05/sharepoint-silverlight-image-library-viewer-part/
The advantage of using the DVWP is that there is no code to be deployed to
the SharePoint server, just a few files that can be uploaded to a document
library.
|
|
How to build the Silverlight web part
|
|
Steps to create this on your own site using SharePoint Designer (no server access or web part installation required).
Assuming you have a SharePoint picture library already created. Copy any code below into notepad first.
- Create a Document Library to hold your web part page and the required SilverLight files (set template to Web Part Page)
- Create a folder called script in the document library
-
- Createsilverlight.js
- Main.js
- Silverlight.js
- Scene.xaml
- Photoitem.xaml
Create a Web Part Page in the library Edit the web part page in SharePoint Designer Insert a Data View of your picture Library (just select one field from the data source view) Set the data view layout to Plain Layout
Add the following code immediately before the
<xsl:call-template name="dvt_1"/> tag in the <xsl:template
match="/" section.
<xsl:text
disable-output-escaping="yes"><![CDATA[<script
type="text/javascript"
src="script/CreateSilverlight.js"></script> <script type="text/javascript" src="script/Silverlight.js"></script> <script type="text/javascript" src="script/Main.js"></script> <div id="SilverlightControlHost">Loading...<script type="text/javascript"> var localScene=new BinaryJamSFSPart.Scene('SilverlightControlHost', 'script'); createSilverlight('SilverlightControlHost', 'script/Scene.xaml', 'SilverlightControl','640','520', localScene); </script>]]></xsl:text>
Replace the dvt_1 template with the following
<xsl:template name="dvt_1"> <xsl:variable name="dvt_StyleName">PlnTitl</xsl:variable> <xsl:variable name="Rows" select="/dsQueryResponse/Rows/Row" /> <xsl:text disable-output-escaping="yes"><![CDATA[<script type="text/javascript"> ]]></xsl:text> <xsl:call-template name="dvt_1.body"> <xsl:with-param name="Rows" select="$Rows" /> </xsl:call-template> <xsl:text disable-output-escaping="yes"><![CDATA[</script></div>]]></xsl:text> </xsl:template>
Replace all the code between the <xsl:template name="dvt_1.rowview"> </xsl:template> with
localScene.PhotoItemsUrls['<xsl:value-of select="position()-1"/>'] = new BinaryJamSFSPartPhotoUrls('http://www.wssdemo.com<xsl:value-of select="@FileRef"/>','http://www.wssdemo.com/today/_t/<xsl:value-of
select="substring-before(@LinkFilenameNoMenu,'.')"
/>_<xsl:value-of
select="substring-after(@LinkFilenameNoMenu,'.')" />.jpg');
This adds the image url and calculates the thumbnail for the image (_ext.jpg). Substitute www.wssdemo.com with your site url and Today with your picture library.
Save your page and view it in the browser (mouse over the bottom of the image to get the selector to display) Overview of XSL Template changes | | |
Tags: Microsoft Sharepoint WSS MOSS WPF Silverlight Beta Integartion Silverlight WebPart CodePlex Solution
June 26 Guys,
Following are the latest Roll-ups (as on June 1st 2008) for the WSS & MOSS SP1. WSS 12.0.6316.5000 KB953137 WSS 12.0.6314.5000 KB952292 MOSS 12.0.6316.5000 KB953138
Order - WSS SP1 > MOSS SP1 > 953137 > 952292
> 953138
953137 Version Number always shows 0.0.0000.0 Incremental crawl doesn't crawl items in meeting workspace template doc lib Display item forms for calendar do not open the corresponding items when using the calendar view link to go to the display form. filtering of this file ended becasue the file reached maximum limit. SP1 removes DCOM permissions for OSearch causing search to fail.
952292 Cannot open menu on items in picture library with workflow enabled.
953138 Tools menu is available but no response if select any item when About is opened MOSS12 - Property Import Mapping for "Name/Preferred Name" maps despite being unmapped Thumbnails in the image library do not display in extranet publishing scenario CMS12 - Custom dictionaries don't work with extended characters SRCH12 - Filtering of this file ended because the file reached max limit MOSS: Image GET failing for team sites when blob cached enabled MOSS: Cannot delete last navigation item on subsites that don't inherit top link bar from parent SRCH12 - SP1 removes DCOM permissions for OSearch causing search to fail Users are able to publish pages without required fields after navigating back to the unpublished page. Ability to navigate away from page without data saved
MOSS Version Details:-
MOSS 20071 or WSS 3.0 post-SP1 hotfix
(KB948945)
12.0.0.6303
MOSS 20071 or WSS 3.0 post-SP1 hotfix
(KB941274)
12.0.0.6301
MOSS 20071 or WSS 3.0 post-SP1 hotfix
(KB941422)
12.0.0.6300
MOSS 20071 or WSS 3.0
SP1
12.0.0.6219
MOSS 20071 or WSS 3.0 October public
update
12.0.0.6039
MOSS 20071 or WSS 3.0 August 24, 2007
hotfix package 12.0.0.6036
MOSS 20071 or WSS 3.0
RTM
12.0.0.4518
MOSS 20071 or WSS 3.0 Beta 2
TR:
12.0.0.4407
MOSS 20071 or WSS 3.0 Beta
2:
12.0.0.4017
Office 12 (PDC image -
pre-beta):
12.0.0.3111
(This version of Office does not have a support link in the Add/Remove programs
dialog box).
Regards, Saurabh
Tags: 953138, 952292, 953137, kb953138, kb952292, kb953137, "MOSS SP1 Rollup", MOSS, SP1, Rollup, Roll-up, Roll, up, "content deployment", techacid
June 23 Thanks to Jose for sharing these details. - stsadm -o activatefeature {-filename <relative
path to Feature.xml> | -name <feature folder> | -id
<feature Id>} [-url <url>] [-force]
- stsadm -o activateformtemplate -url <URL to the site collection> [-formid <form template ID>] [-filename <path to form template file>]
- stsadm -o addalternatedomain -url
<protocol://existing.WebApplication.URLdomain> -incomingurl
<protocol://incoming.url.domain> -urlzone <default, extranet,
internet, intranet, custom> -resourcename <non-web application
resource name>
- stsadm -o addcontentdb -url <url>
-databasename <database name> [-databaseserver <database
server name>] [-databaseuser <database username>]
[-databasepassword <database password>] [-sitewarning <site
warning count>] [-sitemax <site max count>]
- stsadm -o adddataconnectionfile -filename <path to file to add> [-webaccessible <bool>] [-overwrite <bool>] [-category <bool>]
- stsadm -o add-ecsfiletrustedlocation -Ssp <SSP
name> -Location <URL|UNC> -LocationType SharePoint|Unc|Http
-IncludeChildren True|False [-SessionTimeout <time in seconds>]
[-ShortSessionTimeout <time in seconds>] [-MaxRequestDuration
<time in seconds>] [-MaxWorkbookSize <file size in Mbytes>]
[-MaxChartSize <size in Mbytes>] [-VolatileFunctionCacheLifetime
<time in seconds>] [-DefaultWorkbookCalcMode
File|Manual|Auto|AutoDataTables] [-AllowExternalData
None|Dcl|DclAndEmbedded] [-WarnOnDataRefresh True|False]
[-StopOpenOnRefreshFailure True|False] [-PeriodicCacheLifetime <time
in seconds>] [-ManualCacheLifetime <time in seconds>]
[-MaxConcurrentRequestsPerSession <number of requests>]
[-AllowUdfs True|False] [-Description <descriptive text>]
- stsadm -o add-ecssafedataprovider -Ssp <SSP name> -ID <data provider id> -Type Oledb|Odbc|OdbcDsn [-Description <descriptive text>]
- stsadm -o add-ecstrusteddataconnectionlibrary -Ssp <SSP name> -Location <URL> [-Description <descriptive text>]
- stsadm -o add-ecsuserdefinedfunction -Ssp <SSP
name> -Assembly <strong name|file path> -AssemblyLocation
GAC|File [-Enable True|False] [-Description <descriptive text>]
- stsadm -o addexemptuseragent -name <user-agent to receive InfoPath files instead of a Web page>
- stsadm -o addpath -url <url> -type <explicitinclusion/wildcardinclusion>
- stsadm -o addpermissionpolicy -url <url>
-userlogin <login name> -permissionlevel <permission policy
level> [-zone <URL zone>] [-username <display name>]
- stsadm -o addsolution -filename <Solution filename> [-lcid <language>]
- stsadm -o addtemplate -filename <template filename> -title <template title> [-description <template description>]
- stsadm -o adduser -url <url> -userlogin <DOMAIN\user> -useremail <someone@example.com> -role <role name> / -group <group name> -username <display name> [-siteadmin]
- stsadm -o addwppack -filename <Web Part Package filename> [-lcid <language>] [-url <url>] [-globalinstall] [-force] [-nodeploy]
- stsadm -o addwppack -name <name of Web Part Package> [-lcid <language>] [-url <url>] [-globalinstall] [-force]
- stsadm -o addzoneurl -url
<protocol://existing.WebApplication.URLdomain> -urlzone
<default, extranet, internet, intranet, custom> -zonemappedurl
<protocol://outgoing.url.domain> -resourcename <non-web
application resource name>
- stsadm -o allowuserformwebserviceproxy -url <Url of the web application> -enable <true to enable, false to disable>
- stsadm -o allowwebserviceproxy -url <Url of the web application> -enable <true to enable, false to disable>
- stsadm -o associatewebapp -title <SSP name> [-default | -parent] -url <Web application 1 url,Web application 2 url> [-all]
- stsadm -o authentication -url <url> -type
<windows/forms/websso> [-usebasic (valid only in windows
authentication mode)] [-usewindowsintegrated (valid only in windows
authentication mode)] [-exclusivelyusentlm (valid only in windows
authentication mode)] [-membershipprovider <membership provider
name>] [-rolemanager <role manager name>]
[-enableclientintegration] [-allowanonymous]
- stsadm -o backup -url <url> -filename <filename> [-overwrite]
- stsadm -o backup -directory <UNC path>
-backupmethod <full | differential> [-item <created path from
tree>] [-percentage <integer between 1 and 100>]
[-backupthreads <integer between 1 and 10>] [-showtree] [-quiet]
- stsadm -o backuphistory -directory <UNC path> [-backup] [-restore]
- stsadm -o binddrservice -servicename <data retrieval service name> -setting <data retrieval services setting>
- stsadm -o blockedfilelist -extension <extension> -add [-url <url>]
- stsadm -o blockedfilelist -extension <extension> -delete [-url <url>]
- stsadm -o canceldeployment -id <id>
- stsadm -o changepermissionpolicy -url <url>
-userlogin <DOMAIN\name> [-zone <URL zone>] [-username
<display name>] [{ -add | -delete } -permissionlevel
<permission policy level>]
- stsadm -o copyappbincontent
- stsadm -o createadminvs [-admapidname <app pool
name>] [-admapidtype <configurableid/NetworkService>]
[-admapidlogin <DOMAIN\name>] [-admapidpwd <app pool
password>]
- stsadm -o createcmsmigrationprofile -profilename
<profile name> [-description <description>]
[-connectionstring <connection string>] -databaseserver
<server> -databasename <name> -databaseuser
<username> [-databasepassword <password>] [-auth
windowsauth|sqlauth] -destination <url> [-rootchannel
<channelname>] [-destinationlocale <LCID>]
[-migrateresources onlyused|all] [-migrateacls yes|no] [-emailto
<address1;address2>] [-emailon success|failure|none|both]
[-keeptemporaryfiles Never|Always|Failure] [-enableeventreceivers
yes|no]
- stsadm -o creategroup -url <url> -name
<group name> -description <description> -ownerlogin
<DOMAIN\name or group name> [-type member|visitor|owner]
- stsadm -o createsite -url <url> -owneremail <someone@example.com> [-ownerlogin <DOMAIN\name>] [-ownername <display name>] [-secondaryemail <someone@example.com>]
[-secondarylogin <DOMAIN\name>] [-secondaryname <display
name>] [-lcid <language>] [-sitetemplate <site
template>] [-title <site title>] [-description <site
description>] [-hostheaderwebapplicationurl <web application
url>] [-quota <quota template>]
- stsadm -o createsiteinnewdb -url <url> -owneremail <someone@example.com> [-ownerlogin <DOMAIN\name>] [-ownername <display name>] [-secondaryemail <someone@example.com>]
[-secondarylogin <DOMAIN\name>] [-secondaryname <display
name>] [-lcid <language>] [-sitetemplate <site
template>] [-title <site title>] [-description <site
description>] [-hostheaderwebapplicationurl <web application
url>] [-quota <quota template>] [-databaseuser <database
username>] [-databasepassword <database password>]
[-databaseserver <database server name>] [-databasename
<database name>]
- stsadm -o createssp -title <SSP name> -url
<Web application url> -mysiteurl <MySite Web application
url> -ssplogin <username> -indexserver <index server>
-indexlocation <index file path> [-ssppassword <password>]
[-sspdatabaseserver <SSP database server>] [-sspdatabasename
<SSP database name>] [-sspsqlauthlogin <SQL username>]
[-sspsqlauthpassword <SQL password>] [-searchdatabaseserver
<search database server>] [-searchdatabasename <search
database name>] [-searchsqlauthlogin <SQL username>]
[-searchsqlauthpassword <SQL password>] [-ssl <yes|no>]
- stsadm -o createweb -url <url> [-lcid
<language>] [-sitetemplate <site template>] [-title
<site title>] [-description <site description>] [-convert]
[-unique]
- stsadm -o databaserepair -url <url> -databasename <database name> [-deletecorruption]
- stsadm -o deactivatefeature {-filename
<relative path to Feature.xml> | -name <feature folder> |
-id <feature Id>} [-url <url>] [-force]
- stsadm -o deactivateformtemplate -url <URL to the site collection> [-formid <form template ID>] [-filename <path to form template file>]
- stsadm -o deleteadminvs
- stsadm -o deletealternatedomain -url <ignored> -incomingurl <protocol://incoming.url.domain>
- stsadm -o deletecmsmigrationprofile -profilename <profile name>
- stsadm -o deleteconfigdb
- stsadm -o deletecontentdb -url <url> -databasename <database name> [-databaseserver <database server name>]
- stsadm -o deletegroup -url <url> -name <group name>
- stsadm -o deletepath -url <url>
- stsadm -o deletepermissionpolicy -url <url> -userlogin <login name> [-zone <URL zone>]
- stsadm -o deletesite -url <url> -deleteadaccounts <true/false>
- stsadm -o deletesolution -name <Solution name> [-override] [-lcid <language>]
- stsadm -o deletessp -title <SSP name> [-deletedatabases]
- stsadm -o deletessptimerjob -title <SSP Name> -jobid <SSP Timer Job Id>
- stsadm -o deletetemplate -title <template title> [-lcid <language>]
- stsadm -o deleteuser -url <url> -userlogin <DOMAIN\name> [-group <group>]
- stsadm -o deleteweb -url <url>
- stsadm -o deletewppack -name <name of Web Part Package> [-lcid <language>] [-url <url>]
- stsadm -o deletezoneurl -url
<protocol://existing.WebApplication.URLdomain> -urlzone
<default, extranet, internet, intranet, custom> -resourcename
<non-web application resource name>
- stsadm -o deploysolution -name <Solution
name> [-url <virtual server url>] [-allcontenturls] [-time
<time to deploy at>] [-immediate] [-local] [-allowgacdeployment]
[-allowcaspolicies] [-lcid <language>] [-force]
- stsadm -o deploywppack -name <Web Part Package
name> [-url <virtual server url>] [-time <time to deploy
at>] [-immediate] [-local] [-lcid <language>] [-globalinstall]
[-force]
- stsadm -o disablessc -url <url>
- stsadm -o displaysolution -name <Solution name>
- stsadm -o editcmsmigrationprofile -profilename
<profile name> [-description <description>]
[-connectionstring <connection string>] [-databaseserver
<server>] [-databasename <name>] [-databaseuser
<username>] [-databasepassword <password>] [-auth
sqlauth|windowsauth] [-emailto <address1;address2>] [-emailon
success|failure|none|both] [-excludeschema ] [-keeptemporaryfiles
Never|Always|Failure] [-enableeventreceivers yes|no]
- stsadm -o editcontentdeploymentpath -pathname
<path name> [-keeptemporaryfiles Never|Always|Failure]
[-enableeventreceivers yes|no] [-enablecompression yes|no]
- stsadm -o editssp -title <SSP name>
[-newtitle <new SSP name>] [-sspadminsite <administration site
url>] [-ssplogin <username>] [-ssppassword <password>]
[-indexserver <index server>] [-indexlocation <index file
path>] [-setaccounts <process accounts (domain\username)>]
[-ssl <yes|no>]
- stsadm -o email -outsmtpserver <SMTP server> -fromaddress <someone@example.com> -replytoaddress <someone@example.com> -codepage <codepage> [-url <url>]
- stsadm -o enablecmsurlredirect -profilename <profile name> -off
- stsadm -o enablessc -url <url> [-requiresecondarycontact]
- stsadm -o enumalternatedomains -url <protocol://existing.WebApplication.URLdomain> -resourcename <non-web application resource name>
- stsadm -o enumcontentdbs -url <url>
- stsadm -o enumdataconnectionfiledependants -filename <filename for which to enumerate dependants>
- stsadm -o enumdataconnectionfiles [-mode <a | u | all | unreferenced>]
- stsadm -o enumdeployments
- stsadm -o enumexemptuseragents
- stsadm -o enumformtemplates
- stsadm -o enumgroups -url <url>
- stsadm -o enumroles -url <url>
- stsadm -o enumservices
- stsadm -o enumsites -url <virtual server url> -showlocks -redirectedsites
- stsadm -o enumsolutions
- stsadm -o enumssp -title <SSP name> [-default | -parent | -all]
- stsadm -o enumssptimerjobs -title <SSP Name>
- stsadm -o enumsubwebs -url <url>
- stsadm -o enumtemplates [-lcid <language>]
- stsadm -o enumusers -url <url>
- stsadm -o enumwppacks [-name <name of Web Part Package>] [-url <virtual server url>] [-farm]
- stsadm -o enumzoneurls -url <protocol://existing.WebApplication.URLdomain> -resourcename <non-web application resource name>
- stsadm -o execadmsvcjobs
- stsadm -o export -url <URL to be exported>
-filename <export file name> [-overwrite] [-includeusersecurity]
[-haltonwarning] [-haltonfatalerror] [-nologfile] [-versions
<1-4> 1= Last major version for files and list items (default),
2= The current version, either the last major or the last minor, 3=
Last major and last minor version for files and list items, 4= All
versions for files and list items] [-cabsize <integer from 1-1024
megabytes> (default: 25)] [-nofilecompression] [-quiet]
- stsadm -o extendvs -url <url> -ownerlogin <domain\name> -owneremail <someone@example.com>
[-exclusivelyusentlm] [-ownername <display name>] [-databaseuser
<database user>] [-databaseserver <database server>]
[-databasename <database name>] [-databasepassword <database
user password>] [-lcid <language>] [-sitetemplate <site
template>] [-donotcreatesite] [-description <iis web site
name>] [-sethostheader] [-apidname <app pool name>] [-apidtype
<configurableid/NetworkService>] [-apidlogin <DOMAIN\name>]
[-apidpwd <app pool password>] [-allowanonymous]
- stsadm -o extendvsinwebfarm -url <url>
-vsname <web application name> [-exclusivelyusentlm] [-apidname
<app pool name>] [-apidtype
<configurableid/NetworkService>] [-apidlogin <DOMAIN\name>]
[-apidpwd <app pool password>] [-allowanonymous]
- stsadm -o forcedeleteweb -url <url>
- stsadm -o formtemplatequiescestatus [-formid <form template ID>] [-filename <path to form template file>]
- stsadm -o getadminport
- stsadm -o getdataconnectionfileproperty -filename <filename of the data connection file> -pn <property name>
- stsadm -o getformsserviceproperty -pn <option name>
- stsadm -o getformtemplateproperty [-formid <form template ID>] [-filename <path to form template file>] -pn <property name>
- stsadm -o getproperty -propertyname <property
name> [-url <url>] (SharePoint cluster properties:
avallowdownload, avcleaningenabled, avdownloadscanenabled,
avnumberofthreads, avtimeout, avuploadscanenabled,
command-line-upgrade-running, database-command-timeout,
database-connection-timeout, data-retrieval-services-enabled,
data-retrieval-services-oledb-providers,
data-retrieval-services-response-size, data-retrieval-services-timeout,
data-retrieval-services-update, data-source-controls-enabled,
dead-site-auto-delete, dead-site-notify-after,
dead-site-num-notifications, defaultcontentdb-password,
defaultcontentdb-server, defaultcontentdb-user, delete-web-send-email,
irmaddinsenabled, irmrmscertserver, irmrmsenabled, irmrmsusead,
job-ceip-datacollection, job-config-refresh, job-database-statistics,
job-dead-site-delete, job-usage-analysis, job-watson-trigger,
large-file-chunk-size, token-timeout, workflow-cpu-throttle,
workflow-eventdelivery-batchsize, workflow-eventdelivery-throttle,
workflow-eventdelivery-timeout, workflow-timerjob-cpu-throttle,
workitem-eventdelivery-batchsize, workitem-eventdelivery-throttle;
SharePoint virtual server properties: alerts-enabled, alerts-limited,
alerts-maximum, change-log-expiration-enabled,
change-log-retention-period, data-retrieval-services-enabled,
data-retrieval-services-inherit,
data-retrieval-services-oledb-providers,
data-retrieval-services-response-size, data-retrieval-services-timeout,
data-retrieval-services-update, data-source-controls-enabled,
days-to-show-new-icon, dead-site-auto-delete, dead-site-notify-after,
dead-site-num-notifications, defaultquotatemplate, defaulttimezone,
delete-web-send-email, job-change-log-expiration, job-dead-site-delete,
job-diskquota-warning, job-immediate-alerts, job-recycle-bin-cleanup,
job-usage-analysis, job-workflow, job-workflow-autoclean,
job-workflow-failover, max-file-post-size,
peoplepicker-activedirectorysearchtimeout,
peoplepicker-distributionlistsearchdomains,
peoplepicker-nowindowsaccountsfornonwindowsauthenticationmode,
peoplepicker-onlysearchwithinsitecollection,
peoplepicker-searchadcustomquery, peoplepicker-searchadforests,
presenceenabled, recycle-bin-cleanup-enabled, recycle-bin-enabled,
recycle-bin-retention-period, second-stage-recycle-bin-quota,
send-ad-email)
- stsadm -o getsitedirectoryscanschedule
- stsadm -o getsitelock -url <url>
- stsadm -o geturlzone -url <protocol://incoming.url.domain>
- stsadm -o import -url <URL to import to>
-filename <import file name> [-includeusersecurity]
[-haltonwarning] [-haltonfatalerror] [-nologfile] [-updateversions
<1-3> 1= Add new versions to the current file (default), 2=
Overwrite the file and all its versions (delete then insert),3= Ignore
the file if it exists on the destination] [-nofilecompression] [-quiet]
- stsadm -o installfeature {-filename <relative path to Feature.xml from system feature directory> | -name <feature folder>} [-force]
- stsadm -o listlogginglevels [-showhidden]
- stsadm -o listregisteredsecuritytrimmers -ssp <ssp name>
- stsadm -o localupgradestatus
- stsadm -o managepermissionpolicylevel -url
<url> -name <permission policy level name> [{ -add |
-delete }] [-description <description>] [-siteadmin <true |
false>] [-siteauditor <true | false>] [-grantpermissions
<comma-separated list of permissions>] [-denypermissions
<comma-separated list of permissions>]
- stsadm -o migrateuser -oldlogin <DOMAIN\name> -newlogin <DOMAIN\name> [-ignoresidhistory]
- stsadm -o osearch [-action
<list|start|stop>] required parameters for 'start' (if not
already set): role, farmcontactemail, service credentials [-f (suppress
prompts)] [-role <Index|Query|IndexQuery>] [-farmcontactemail
<email>] [-farmperformancelevel
<Reduced|PartlyReduced|Maximum>] [-farmserviceaccount
<DOMAIN\name> (service credentials)] [-farmservicepassword
<password>] [-defaultindexlocation <directory>]
[-propagationlocation <directory>]
- stsadm -o osearchdiacriticsensitive -ssp <ssp name> [-setstatus <True|False>] [-noreset] [-force]
- stsadm -o preparetomove {-ContentDB <DatabaseServer:DatabaseName> | -Site <URL>} [-OldContentDB <uniqueidentifier>] [-undo]
- stsadm -o profilechangelog -title <SSP Name> -daysofhistory <number of days> -generateanniversaries
- stsadm -o profiledeletehandler -type <Full Assembly Path>
- stsadm -o provisionservice -action
<start/stop> -servicetype <servicetype (namespace or assembly
qualified name if not SharePoint service)> [-servicename
<servicename>]
- stsadm -o quiescefarm -maxduration <duration in minutes>
- stsadm -o quiescefarmstatus
- stsadm -o quiesceformtemplate [-formid <form template ID>] [-filename <path to form template file>] -maxduration <time in minutes>
- stsadm -o reconvertallformtemplates
- stsadm -o refreshdms -url <url>
- stsadm -o refreshsitedms -url <url>
- stsadm -o registersecuritytrimmer -ssp <ssp
name> -id <0 - 2147483647> -typename <assembly qualified
TypeName of ISecurityTrimmer implementation> -rulepath <crawl
rule URL> [-configprops <name value pairs delimited by '~'>]
- stsadm -o registerwsswriter
- stsadm -o removedataconnectionfile -filename <filename to remove>
- stsadm -o removedrservice -servicename <data retrieval service name> -setting <data retrieval services setting>
- stsadm -o remove-ecsfiletrustedlocation -Ssp <SSP name> -Location <URL|UNC> -LocationType SharePoint|Unc|Http
- stsadm -o remove-ecssafedataprovider -Ssp <SSP name> -ID <data provider id> -Type Oledb|Odbc|OdbcDsn
- stsadm -o remove-ecstrusteddataconnectionlibrary -Ssp <SSP name> -Location <URL>
- stsadm -o remove-ecsuserdefinedfunction -Ssp <SSP name> -Assembly <strong name|file path> -AssemblyLocation GAC|File
- stsadm -o removeexemptuseragent -name <user-agent to receive InfoPath files instead of a Web page>
- stsadm -o removeformtemplate [-formid <form template ID>] [-filename <path to form template file>]
- stsadm -o removesolutiondeploymentlock [-server <server> [-allservers]
- stsadm -o renameserver -oldservername <oldServerName> -newservername <newServerName>
- stsadm -o renameweb -url <url> -newname <new subsite name>
- stsadm -o restore -url <url> -filename <filename> [-hostheaderwebapplicationurl <web application url>] [-overwrite]
- stsadm -o restore -directory <UNC path>
-restoremethod <overwrite | new> [-backupid <Id from
backuphistory, see stsadm -help backuphistory>] [-item <created
path from tree>] [-percentage <integer between 1 and 100>]
[-showtree] [-suppressprompt] [-username <username>] [-password
<password>] [-newdatabaseserver <new database server name>]
[-quiet]
- stsadm -o restoressp -title <SSP name> -url
<Web application url> -ssplogin <username> -mysiteurl
<MySite Web application url> -indexserver <index server>
-indexlocation <index file path> [-keepindex] -sspdatabaseserver
<SSP database server> -sspdatabasename <SSP database name>
[-ssppassword <password>] [-sspsqlauthlogin <SQL username>]
[-sspsqlauthpassword <SQL password>] [-searchdatabaseserver
<search database server>] [-searchdatabasename <search
database name>] [-searchsqlauthlogin <SQL username>]
[-searchsqlauthpassword <SQL password>] [-ssl <yes|no>]
- stsadm -o retractsolution -name <Solution
name> [-url <virtual server url>] [-allcontenturls] [-time
<time to remove at>] [-immediate] [-local] [-lcid
<language>]
- stsadm -o retractwppack -name <Web Part Package
name> [-url <virtual server url>] [-time <time to retract
at>] [-immediate] [-local] [-lcid <language>]
- stsadm -o runcmsmigrationprofile -profilename
<profile name> [-skipanalyzer ] [-onlyanalyzer ] [-startover ]
[-migratesincetime <DateTime string>] [-migrationfolder
<path>] [-exportonly ] [-importonly ] [-htmldiff <path>]
- stsadm -o runcontentdeploymentjob -jobname <name> [-wait yes|no] [-deploysincetime <datetime>] (<datetime> as "MM/DD/YY HH:MM:SS")
- stsadm -o scanforfeatures [-solutionid <Id of Solution>] [-displayonly]
- stsadm -o setadminport -port <port> [-ssl] [-admapcreatenew] [-admapidname <app pool name>]
- stsadm -o setapppassword -password <password>
- stsadm -o setbulkworkflowtaskprocessingschedule -schedule <recurrence string>
- stsadm -o setconfigdb [-connect] -databaseserver
<database server> [-databaseuser <database user>]
[-databasepassword <database user password>] [-databasename
<database name>] [-exclusivelyusentlm] [-farmuser]
[-farmpassword] [-adcreation] [-addomain <Active Directory
domain>] [-adou <Active Directory OU>]
- stsadm -o setcontentdeploymentjobschedule -jobname
<name> -schedule <schedule> (Schedule Parameter Examples:
"every 5 minutes between 0 and 59", "hourly between 0 and 59", "daily
at 15:00:00", "weekly between Fri 22:00:00 and Sun 06:00:00", "monthly
at 15 15:00:00", "yearly at Jan 1 15:00:00")
- stsadm -o setdataconnectionfileproperty -filename <filename of the data connection file> -pn <property name> -pv <property value>
- stsadm -o setdefaultssp -title <SSP name>
- stsadm -o set-ecsexternaldata -Ssp <SSP
name> [-ConnectionLifetime <time in seconds>]
[-UnattendedServiceAccountName <account name>]
[-UnattendedServiceAccountPassword <account password>]
- stsadm -o set-ecsloadbalancing -Ssp <SSP name> [-Scheme WorkbookUrl|RoundRobin|Local] [-RetryInterval <time in seconds>]
- stsadm -o set-ecsmemoryutilization -Ssp <SSP
name> [-MaxPrivateBytes <memory in MBytes>]
[-MemoryCacheThreshold <percentage>] [-MaxUnusedObjectAge
<time in minutes>]
- stsadm -o set-ecssecurity -Ssp <SSP name>
[-FileAccessMethod UseImpersonation|UseFileAccessAccount] [-AccessModel
Delegation|TrustedSubsystem] [-RequireEncryptedUserConnection
False|True] [-AllowCrossDomainAccess True|False]
- stsadm -o set-ecssessionmanagement -Ssp <SSP name> [-MaxSessionsPerUser <number of sessions>]
- stsadm -o set-ecsworkbookcache -Ssp <SSP
name> [-Location <local or UNC path>] [-MaxCacheSize
<storage in Mbytes>] [-EnableCachingOfUnusedFiles True|False]
- stsadm -o setformsserviceproperty -pn <option name> -pv <option value>
- stsadm -o setformtemplateproperty [-formid
<form template ID>] [-filename <path to form template
file>] -pn <property name> -pv <property value>
- stsadm -o setholdschedule -schedule <recurrence string>
- stsadm -o setlogginglevel [-category <
[CategoryName | Manager:CategoryName [;...]] >] {-default |
-tracelevel < None; Unexpected; Monitorable; High; Medium;
Verbose> [-windowslogginglevel < None; ErrorServiceUnavailable;
ErrorSecurityBreach; ErrorCritical; Error; Warning; FailureAudit;
SuccessAudit; Information; Success>] }
- stsadm -o setpolicyschedule -schedule <recurrence string>
- stsadm -o setproperty -propertyname <property
name> -propertyvalue <property value> [-url <url>]
(SharePoint cluster properties:, avallowdownload, avcleaningenabled,
avdownloadscanenabled, avnumberofthreads, avtimeout,
avuploadscanenabled, command-line-upgrade-running,
database-command-timeout, database-connection-timeout,
data-retrieval-services-enabled,
data-retrieval-services-oledb-providers,
data-retrieval-services-response-size, data-retrieval-services-timeout,
data-retrieval-services-update, data-source-controls-enabled,
dead-site-auto-delete, dead-site-notify-after,
dead-site-num-notifications, defaultcontentdb-password,
defaultcontentdb-server, defaultcontentdb-user, delete-web-send-email,
irmaddinsenabled, irmrmscertserver, irmrmsenabled, irmrmsusead,
job-ceip-datacollection, job-config-refresh, job-database-statistics,
job-dead-site-delete, job-usage-analysis, job-watson-trigger,
large-file-chunk-size, token-timeout, workflow-cpu-throttle,
workflow-eventdelivery-batchsize, workflow-eventdelivery-throttle,
workflow-eventdelivery-timeout, workflow-timerjob-cpu-throttle,
workitem-eventdelivery-batchsize, workitem-eventdelivery-throttle;
SharePoint virtual server properties:, alerts-enabled, alerts-limited,
alerts-maximum, change-log-expiration-enabled,
change-log-retention-period, data-retrieval-services-enabled,
data-retrieval-services-inherit,
data-retrieval-services-oledb-providers,
data-retrieval-services-response-size, data-retrieval-services-timeout,
data-retrieval-services-update, data-source-controls-enabled,
days-to-show-new-icon, dead-site-auto-delete, dead-site-notify-after,
dead-site-num-notifications, defaultquotatemplate, defaulttimezone,
delete-web-send-email, job-change-log-expiration, job-dead-site-delete,
job-diskquota-warning, job-immediate-alerts, job-recycle-bin-cleanup,
job-usage-analysis, job-workflow, job-workflow-autoclean,
job-workflow-failover, max-file-post-size,
peoplepicker-activedirectorysearchtimeout,
peoplepicker-distributionlistsearchdomains,
peoplepicker-nowindowsaccountsfornonwindowsauthenticationmode,
peoplepicker-onlysearchwithinsitecollection,
peoplepicker-searchadcustomquery, peoplepicker-searchadforests,
presenceenabled, recycle-bin-cleanup-enabled, recycle-bin-enabled,
recycle-bin-retention-period, second-stage-recycle-bin-quota,
send-ad-email)
- stsadm -o setrecordsrepositoryschedule -schedule <recurrence string>
- stsadm -o setsearchandprocessschedule -schedule <recurrence string>
- stsadm -o setsharedwebserviceauthn -ntlm | -negotiate
- stsadm -o setsitedirectoryscanschedule -schedule
<recurrence string> (Schedule parameter examples: "every 5
minutes between 0 and 59", "hourly between 0 and 59", "daily at
15:00:00", "weekly between Fri 22:00:00 and Sun 06:00:00", "monthly at
15 15:00:00", "yearly at Jan 1 15:00:00")
- stsadm -o setsitelock -url <url> -lock <none | noadditions | readonly | noaccess>
- stsadm -o setsspport -httpport <HTTP port number> -httpsport <HTTPS port number>
- stsadm -o setworkflowconfig -url <url>
{-emailtonopermissionparticipants <enable|disable> |
-externalparticipants <enable|disable> | -userdefinedworkflows
<enable|disable>}
- stsadm -o siteowner -url <url> [-ownerlogin <DOMAIN\name>] [-secondarylogin <DOMAIN\name>]
- stsadm -o spsearch [-action <list | start |
stop | attachcontentdatabase | detachcontentdatabase | fullcrawlstart |
fullcrawlstop>] [-f (suppress prompts)] [-farmperformancelevel
<Reduced | PartlyReduced | Maximum>] [-farmserviceaccount
<DOMAIN\name> (service credentials)] [-farmservicepassword
<password>] [-farmcontentaccessaccount <DOMAIN\name>]
[-farmcontentaccesspassword <password>] [-indexlocation <new
index location>] [-databaseserver <server\instance> (default:
josebda-moss)] [-databasename <database name> (default:
SharePoint_WSS_Search)] [-sqlauthlogin <SQL authenticated database
user>] [-sqlauthpassword <password>] -action list -action stop
[-f (suppress prompts)] -action start -farmserviceaccount
<DOMAIN\name> (service credentials) [-farmservicepassword
<password>] -action attachcontentdatabase [-databaseserver
<server\instance> (default: josebda-moss)] -databasename
<content database name> [-searchserver <search server name>
(default: josebda-moss)] -action detachcontentdatabase [-databaseserver
<server\instance> (default: josebda-moss)] -databasename
<content database name> [-f (suppress prompts)] -action
fullcrawlstart -action fullcrawlstop
- stsadm -o spsearchdiacriticsensitive [-setstatus <True|False>] [-noreset] [-force]
- stsadm -o sync {-ExcludeWebApps <web
applications> | -SyncTiming <schedule(M/H/D:value)> |
-SweepTiming <schedule(M/H/D:value)> | -ListOldDatabases
<days> | -DeleteOldDatabases <days>}
- stsadm -o syncsolution -name <Solution name>] [-lcid <language>] [-alllcids]
- stsadm -o syncsolution -allsolutions
- stsadm -o unextendvs -url <url> [-deletecontent] [-deleteiissites]
- stsadm -o uninstallfeature {-filename <relative path to Feature.xml> | -name <feature folder> | -id <feature Id>} [-force]
- stsadm -o unquiescefarm
- stsadm -o unquiesceformtemplate [-formid <form template ID>] [-filename <path to form template file>]
- stsadm -o unregistersecuritytrimmer -ssp <ssp name> -id <0 - 2147483647>
- stsadm -o unregisterwsswriter
- stsadm -o updateaccountpassword -userlogin <DOMAIN\name> -password <password> [-noadmin]
- stsadm -o updatealerttemplates -url <url> [-filename <filename>] [-lcid <language>
- stsadm -o updatefarmcredentials [-identitytype
<configurableid/NetworkService>] [-userlogin <DOMAIN\name>]
[-password <password>] [-local [-keyonly]]
- stsadm -o upgrade {-inplace | -sidebyside} [-url
<url>] [-forceupgrade] [-quiet] [-farmuser <farm user>]
[-farmpassword <farm user password>] [-reghost] [-sitelistpath
<sites xml file>]
- stsadm -o upgradeformtemplate -filename <path to form template file> [-upgradetype <upgrade type>]
- stsadm -o upgradesolution -name <Solution
name> -filename <upgrade filename> [-time <time to upgrade
at>] [-immediate] [-local] [-allowgacdeployment] [-allowcaspolicies]
[-lcid <language>]
- stsadm -o upgradetargetwebapplication -url <URL
to upgrade> -relocationurl <new URL for non-upgraded content>
-apidname <new app pool name> [-apidtype
<configurableid/NetworkService>] [-apidlogin <DOMAIN\name>]
[-apidpwd <app pool password>] [-exclusivelyusentlm]
- stsadm -o uploadformtemplate -filename <path to form template file>
- stsadm -o userrole -url <url> -userlogin <DOMAIN\name> -role <role name> [-add] [-delete]
- stsadm -o verifyformtemplate -filename <path to form template file>
Tag: Sharepoint MOSS STSADM Bin Logs WSS STS Search Crawl "Content Deployment" Template Solution Schedule Migration Enum Activate Content Extent May 21
WSS Hotfix Final Release for Rollup
KB 952698
Moving links via sitemanager.aspx does not work. Content Deployment job is stuck in 'Preparing' status
forever. Second full deployment un-ghosts pages on the target
site which were ghosted. Synchronization problems when running multiple content
deployment jobs. Incremental Content Deployment fails if a item has been
renamed and new item with same name has been created. Incremental Content Deployment fails if a site is
deleted and a new site is created with the same name. Variation page propagation performance
improvement. Incremental Content Deployment fails if a file and a
folder is deleted from a document library. DocLib Metadata is lost after upgrade from v2 to v3. Content Deployment Fails if compression is disabled. Incremental deployment fails if a publishing page was
deleted and restored from the recycle bin. Incremental content deployment fails when feature with
content type activated and deactivated without actually using the content
type. The Service Account (System account) gets added to site
collection when it is created through Self Site creation feature with
require secondary contact enabled. Error Render failed when total column is more than 13
columns. Quick deploy job fails if more than one page is waiting
to be quick deployed. Unable to download published version from the version
history page for larger files. Content Deployment duplicates columns when using
standard site definitions.
Copy
operations of Publishing Pages in Site Manager take around 20 minutes per
item.
MOSS Hotfix Final Release for
Rollup KB 952704
Search Keyword publishing dates
are decremented by one after editing the keyword. HotFix for MOSS Post SP1
Roll-Up package: Get error when view or edit list item located on
Navigation Bar after install Moss Post-SP1 Rollup package Q941274. Copy operations of Publishing
Pages in Site Manager take around 20 minutes per item.
Also: Plus whatever I’ve mentioned under KB 952698 list.
Correct order to install the rollups -
================ Order of installation:
=================
1. WSS
SP1
2. MOSS
SP1
3. 948945
4. 941422
5. 952698
6. 952704 PS: Regarding Previous Rollups please See this.
Tags: moss sp1 wss sp1 sp2 sharepoint microsoft 948945 941422 952698 952704 service pack erp business application webpart spd "content deployment" quick deployment "doc lib" "document library " "sharepoint bugs"
March 26
SharePoint Capacity
Planning Tool - Solution Accelerator
Are you
planning a SharePoint installation for a customer? Chances are, you have a lot
of questions.
- What is
the necessary hardware investment?
- What kind
of topology is needed to meet organizational requirements for availability
and performance?
- How will
additional users from a recent merger affect deployment?
When planning
a new SharePoint deployment, you will need a way to quickly characterize the
general topology and minimum hardware requirements to support expected usage
loads with adequate performance. You will need a way to explore plausible
scenarios and get pointed in the right direction. The SharePoint Capacity
Planning Tool gives you a quick way to draft topology and equipment sizing for
your particular scenario and usage profile.
This solution
reduces “SharePoint sizing” estimation efforts from a matter of days to a matter
of hours.
Description of the Tool
Imagine
a tool that you could use to input a few key facts about users, user needs,
business requirements, and organizational resources in order to:
- Build a
topology model based on this input
- Run
simulations that show the impact of this topology
- Generate a
summary report that will help you evaluate alternatives
The
SharePoint Capacity Planning Tool consists of System Center Capacity Planner
2007 (SCCP) models for:
- Microsoft
Office SharePoint Server 2007 (MOSS)
- Windows
SharePoint Services 3.0 (WSS)
The tool can
be used in pre-sales and feasibility studies of a deployment project to give you
a rough estimate of hardware requirements. The tool can generate estimated
performance metrics based on a simulation and provide useful Visio schematics of
the proposed deployment to be included in documents and proposals.
Overview
The
SharePoint Capacity Planning Tool is a set of free models of Windows
SharePoint Services 3.0 (WSS) and Microsoft Office SharePoint Server 2007
(MOSS). The two models use the analysis and simulation features of System Center
Capacity Planner 2007 (SCCP) to help you explore suitable IT infrastructure
options for your SharePoint deployment, based on the SharePoint usage
requirements for your organization that you provide to the tool. It can give you
a head start on planning your SharePoint topology by producing a first
approximation of the topology your organization needs. Architects, systems
integrators, and deployment engineers will find it to be a valuable starting
point for further refinements of the topology.
Feature Bullet Summary
·
Simple
installation and setup
·
Built-in
knowledge of Microsoft Office SharePoint Server 2007 ·
Built-in
knowledge of Windows SharePoint Services 3.0 ·
Recommended topology in a Graphical User Interface ·
Export
topology to Visio and server configuration to Excel ·
Create
custom hardware
Download Details.
Customers can
obtain the SharePoint Capacity Planning Tool on Microsoft Download. For a short
introduction to the tool and its usage, please go to this TechNet overview page:
http://go.microsoft.com/fwlink/?LinkID=93030
This Solution
Accelerator needs SCCP 2007 to be installed first.
For details
and download information for SCCP, please see Additional Resources.
This Solution
Accelerator is being included in Microsoft Services readiness material for
SharePoint architecture and planning.
Additional Resources
SharePoint Capacity Planning Tool on Microsoft Download Center
System Center Capacity Planner
Solution Accelerators on TechNet
Tags: Sharepoint capacity planning
March 06
Moving SharePoint 2007 databases from one server to
another server/instance
The problem is
that it is not that easy to just move the databases to a new database server
and have everything work. In SharePoint 2003, it was relatively simple to move
all the databases, but in 2007 there is a lot more involved with communication
between the databases making it a more complicated scenario. Outlined below are
the steps taken to move a SharePoint farm to a new database server.
- Perform a farm level backup of the current farm
using the SharePoint backup utility in Central Administration. Make sure
the backup gets saved to an accessible location either on this server or
on the network.
- Run the SharePoint Products and Technologies
Configuration Wizard to disconnect the server from the configuration
database. If there is only one server in farm, then all you have to do is
that server. If there are multiple servers in the farm, make sure the
server running central administration is the last server disconnected from
the farm. I don't believe this is a requirement, but I would recommend it
anyway.
- Once all the servers have been removed from the
farm. Run the SharePoint Products and Technologies Configuration Wizard on
the server to host the central administration site first to create a new
SharePoint farm. Once Server is configured, run the configuration wizard
on the remaining servers adding them to the new SharePoint farm.
- Start both the Office SharePoint Services Search and
the Windows SharePoint Services Search services
- Restore the backup made in step 1 using the
SharePoint restore utility in Central Administration. You will have to
supply the file path to the files that were backed up
- There are 4 steps to restoring from the backup.
Step 1 is to locate the backup set that was ran in Step 1

- Step 2 is selecting a backup to restore from the
location specified in the previous step
 - Step 3 is selecting a component of the backup to
restore... in this case you want to restore at the farm level
 - Step 4 is to select the restore options. In this
step you want to select new configuration for the type of restore and be
sure to go through all the databases, web applicatons, and SSP
information to specifiy the new database server name and database file
locations for each item. Double check everything before hitting ok.
 - Finally after all selections are made and the
restore process is kicked off, you see a summary of the restore in
progress.

Once restore is complete the
databases should be in their new location and the SSP should be backup and
running. To finish the move, you must reconfigure the farm using central
administration. Then kick off a full crawl to repopulate the content
index.Other related resources:-
How to move the databases that are used by
SharePoint Portal Server 2003 to a computer that is running SQL Server
http://support.microsoft.com/kb/894164/en-us
How to move a WMSDE content database that
resides on a Windows SharePoint Services 2.0 server to a Windows SharePoint
Services 3.0 server
http://support.microsoft.com/kb/925190/en-us
How to move SharePoint Portal Server 2003
from MSDE to SQL Server
http://support.microsoft.com/kb/837848/en-us
Tags: "Moving SharePoint 2007 databases from one server to
another server/instance" "Moving MOSS 2007 databases from one server to
another server/instance" " Moving MOSS Database"
Thanks, Saurabh
February 28 Post HotFix for MOSS SP1 Rollup
List of issues Fixed by MOSS SP1 Rollup - Final Release KB 948945
1. WSS12 - Incremental Content Deployment fails
if workflow status fields were removed on the source site 2. SRCH12 - Incremental Crawl does not complete -
proc_MSS_ProcessLinks 3. MOSS 2007 Content deployment import fails with Violation of
PRIMARY KEY constraint WebParts_PK error 4. WSS12 - Item versioning on a List with Lookup columns causes a
SQL exception 5. SRCH12 - The thumbnail displayed in the High Confidence results
web part points to the internal URL and it does not honor the AAM setting 6. WSS12 - Race Conditions in SPConfigurationDatabase initializaion
leak FileSystemWatchers 7. WSS12 - Unable to rename folders stored in a list 8. WSS12 - Downloading a document from a IRM protected document
library will cause server 100% CPU 9. WSS12 - Clicking a Document link which points to a URL
containing Chinese will cause "404 not found" error 10. WSS12 - Task updates sends phantom AssignedTo email
notifications with no update to field 11. WSS12 - The extreme slowness (15secs) we experience in the
stored proc responsible for getting the ACL for an item
(proc_SecGetListItemSecurity) when the count of items in a List exceeds
500,000. 12. WSS12 - Exporting from a Recovery farm and importing on
Production farm fails for a site collection if limits are set for Major and
Minor versions 13. SRCH12 - "Did you mean" functionality checks only last
word in phrase 14. WSS12 - Gantt Chart Today Shading time should be of Local System
instead of UTC time 15. SRCH12 - Best Bets do not get returned when using advanced
search -> All these words
List of issues Fixed by MOSS SP1 Rollup - Final Release KB 941422
- MOSS 2007: Missing timer jobs when you backup and
restore.
- WSS 3.0: Site Templates does not contain standard WebParts
- WSS: Posting a blog entry returns error 'Word cannot register
your account..:'
-
CDCR: New Zealand timezone changes - WSS/SPS 12
- RFH: Error Exporting to Spreadsheet after changing date field
requirement with Excel2003
- SPSv2->MOSS:WSS: Error message on upgrading Discussion
boards: "Violation of UNIQUE KEY constraint 'AllUserData_Url'"
- SPIncludeDescendents property does not function properly when
SPExportObjectType is set as SPFolder
- SRCH12 - Search Results HTML rendering error when folder name
has a trailing period
- WSS: RSS Feed update is delayed in Outlook and IE client
- SRCH12 - ACL changes did not get picked up via incremental crawl
for FileShare
- STSv2 --> WSS: SiteCount increments each time 'Refresh site
list' is clicked during Gradual Upgrade
- SRCH12 - BDC Content Source Not Returning Search For Single
Words
- WSS 3.0 - Welcome email retains OLD site name
- SRCH12 - Cannot search for anything beyond the second slide of a
powerpoint (ppt) presentation
- WSS: Limited permissions prevent restore from recycle bin into
source folder
- WSSv3: RHF: Calendar View of Calendar web part causes the page
to fail to be rendered for a user without the reader permission to this list
- WSSv3: RFH: Order changed on custom list column after upgrade
- SRCH12 - Excel file are not filtered if the name definition for
string are existing.
- WSS: 2007 Document Library issue with folder named - Forms
- WSSv3: RFH: SpWriter fails in OnIdentify if multiple SSPs get
enabled on a MOSS farm
- SRCH12 - While crawling FBA content, some cookies in the
response can be skipped
- WSSV3:Track Passport users by their PUID – need complete fix
(Office Live)
- WSS V3: Perf Fix for stored proc proc_SecListScopeGroups (Office
Live)
- WSSv3 RFH: XSLT grouping in data views doesn't work beyond 3
levels
- Custom view settings of list view web part in web part pages are
lost during content deployment
- WSSv3: User SIDs shortened likely when migrating user accounts
via V3 stsadm -migrateuser command
- WSS12 - Break item level inheritance takes too long, follow up
of QFE 17975
- WSS PRIME: Incremental Content Deployment fails if a list is
deleted and a new list is created with the same name.
- SRCH12 - OSearch leaks memory when crawling a BDC and SharePoint
content source
- WSS- Customer needs hotfix for OfficeQFE:19123 before SP1
- WSS - Upgrade action Detecting Security Setting Corruptions
does not handle host header mode well (Office Live)
- Could not start the Windows SharePoint Services Administration
Service on local computer after 6036 PU
To obtain the above rollups for MOSS SP1, you may please contact Microsoft.
Tags: MOSS SP1 Rollup 941422 & 948945 WSS 3.0 SP1 Rollup backout
Thanks, Saurabh
February 06 Re: "Content for this URL is excluded by the server because a no-index attribute."
In a nutshell
You can use a special HTML <META> tag to tell robots not to index
the content of a page, and/or not scan it for links to follow.
For example:
<html> <head> <title>...</title> <META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"> </head>
There are two important considerations when using the robots <META> tag:
-
robots can ignore your <META> tag. Especially malware robots that scan the
web for security vulnerabilities, and email address harvesters used by spammers
will pay no attention.
-
the NOFOLLOW directive only applies to links on this page. It's
entirely likely that a robot might find the same links on some other
page without a NOFOLLOW (perhaps on some other site), and so still
arrives at your undesired page.
Don't confuse this NOFOLLOW with the
rel="nofollow" link attribute.
The details
Like the /robots.txt, the robots META
tag is a de-facto standard.
It originated from a "birds of a feather" meeting at a 1996
distributed indexing workshop, and was described in meeting notes.
The META tag is also described in the HTML
4.01 specification, Appendix B.4.1.
The rest of this page gives an overview of how to use the robots
<META> tags in your pages, with some simple recipes.
How to write a Robots Meta Tag
Where to put it
Like any <META> tag it should be placed in the HEAD section of an HTML
page, as in the example above. You should put it in every page on your
site, because a robot can encounter a deep link to any
page on your site.
What to put into it
The "NAME" attribute must be "ROBOTS".
Valid values for the "CONTENT" attribute are:
"INDEX", "NOINDEX", "FOLLOW",
"NOFOLLOW". Multiple comma-separated values are allowed, but
obviously only some combinations make sense. If there is no
robots <META> tag, the default is "INDEX,FOLLOW",
so there's no need to spell that out. That leaves:
<META NAME="ROBOTS" CONTENT="NOINDEX, FOLLOW"> <META NAME="ROBOTS" CONTENT="INDEX, NOFOLLOW"> <META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
December 11
If
you have called into the PSS Support Center for SharePoint related
issues recently, you have probably encountered long hold times and slow
responses. Let's just say that SharePoint is an incredibly popular
product and case volumes are at an all time high. Our support
personnel are doing the best that we can to help you get your issue
resolved as quickly as possible, but we are struggling to provide the
quick resolution and high-quality support that you deserve and have
grown to expect from Microsoft. Everyone is working as diligently as
possible to help address your needs.
There are some things that you, the SharePoint support customer, can
do to help us support you better and make our communications more
efficient and effective. As you are working with our SharePoint
support teams, please keep the following tips in mind
- Give a complete and accurate description of the problem you are encountering. The
better the description you provide us at the beginning of the case, the
better the chance we have of providing you a resolution on first
contact. Please give us as much information as possible about the
problem in your initial communication to us. Take, for example, this
problem description: "Alerts not working after upgrade". There are
many ways this problem description could be better. A better problem
description might be something like this. "After upgrading content
from WSS v2 to WSS v3, alerts are not sent. Initial alert creation
email(s) are received, but alerts for document uploads/deletes are
not. This problem affects all documents libraries in all sites. The
content was upgraded using the in-place method"
- Provide accurate error messages. If your
problem results in an error message in the browser or event log, please
provide the complete text of the error whenever possible. If you can
provide a screen shot along with the text, that is even better
- Be precise with case Severity. It is very,
very important that case severity is accurate. If your case involves a
production server down situation where many users are impacted and
significant functionality is broken, then your case may warrant a
severity of "critical". However, please resist the urge to
artificially increase the severity in hopes of getting your
issue resolved more quickly. Improperly elevating severity can cause
resource re-allocations that disrupt service to other customers and
prevents us from properly servicing the most critical scenarios.
- Run SPSreports. SPSReports is a tool that you should download from http://www.codeplex.com/spsreport and
have handy for every SharePoint server you manage. You shouldn't
necessarily pre-install SPSreports because each release is time-bombed
but you should be familiar with it and know where to get it because
SPSReports is a very valuable data collection tool that will gather up
a ton of artifacts such as event logs, error logs, dll versions,
SharePoint topology information and many other things that will assist
our troubleshooting efforts. SPSreports generates CAB files that are
usually too large to email so please ask your support professional for
a file transfer site to use to upload the SPSReports data.
- Get complete contact information from your support professional.
Once you make contact with a support professional (referred to as SP),
collect the following contact information: Support Professional name.
Direct Phone Number, E-mail address, and manager name. Please use this
information to contact your designated support professional if your
case is not progressing properly and don't hesitate to leverage the
manager contact if your support professional is not responsive after
repeated attempts.
- Be cautious about reassignments. Once a
case has been assigned, calling back into the queue will result in your
case being assigned to the next available support engineer. These
type of reassignments could significantly delay progress on your case
and you may be better off trying to contact your assigned support
professional to arrange a callback. The exception here is after-hours
and high severity cases. If you really need to work after hours or
immediately then calling into the queue for the next available resource
may be your best option.
- Be willing to work via email. Easy Assist
conferences are a wonderful thing and make troubleshooting issues much
easier, however, once an issue has been well scoped and understood,
working via email may be most efficient. With case loads as high as
they are and callback schedules as full as they are, it is much easier
for your support professional to squeeze in a 15 minute email response
between callbacks than it is to schedule another Easy Assist or Phone
callback.
- Please keep scheduled callback commitments.
If you have a scheduled callback with your support professional, please
do everything possible to be available during the agreed upon time. It
may also be helpful to send your SP an email reminder about 30 minutes
before the appointment. This will both serve as a reminder to your SP
and give your SP an opportunity to inform you if he/she is delayed,
etc. If you need to reschedule, please let your SP know as early as
possible to ensure we can accommodate your new appointment needs. If
we miss a callback, please get back to us as soon as possible to
schedule the next callback. We try really hard not to miss callbacks,
but unfortunately, it does happen sometimes.
- Be patient but persistent. We appreciate
your patience during these difficult times. Your issues are important
to us and we will get back to you as quickly as we can. If for some
reason, you feel that the issue is not progressing properly, please
send an email requesting an update. This serves as a notification that
this issue is still a problem and will help us give you the appropriate
prioritization. If that doesn't get the response that you need, feel
to contact the SP's designated manager. The manager will work with
your assigned SP to get the case moving forward, or assign another
resource to your case.
- Leverage the community and self-help.
There are many blogs, forums, and self-help areas out on the Internet
that may be helpful in researching your issue. There are
many SharePoint experts from the community as well as Microsoft
employees lingering in the forum(s) and posting blogs that may be of
assistance to you. Also, the MOSS 2007 and WSS Version 3 documentation
is being delivered in a "continuous publication" model so keep checking
back for new content and keep searching to see what new stuff may be
out there.
Thanks for sticking with us through this time of growth and change.
We look forward to reaching the end of this painful period of growth. December 03
In this lab, you complete the following to
enable forms based authentication.
·
Make entries in the web.config
·
Configure forms authentication in central
administration
Make Entries in the Web.Config
As a first step to enable forms authentication, you need
to make entries in the web.config file of the SharePoint Central Administration
Web application and of the SharePoint (90) Web application you wish to use
forms authentication. Complete the following steps on the WFE. (Considering
that our Web-App is on Port 90)
1.
Locate the web.config file used by the
SharePoint Central Administration console.
a.
Open the Internet Information Services (IIS)
Manager.
b.
Expand the local computer and then Web Sites.
c.
Right-click SharePoint Central Administration v3
and select Properties.
d.
Open the Home Directory tab.
e.
Make note of the Local path.
f.
Close all dialog boxes and close the Internet
Information Services (IIS) Manager window.
g.
Open Windows Explorer and navigate to the Local
path you made a note in step 1 e.
2.
Open the web.config file of the Central
Administration Web site in Notepad.
3.
Open the CentralAdmin-web.config.txt file
located under X:\eDirectoryImport\ in Notepad and then do a CTRL+A and CTRL+C
to copy all text to clipboard.
4.
Paste the copied text under the
<system.web> root section in the web.config file. The text you paste
should look like the excerpt below. The parameters highlighted in red below
are:
|
LdapMembership
|
Ldapmembership is the membership provider you use to
connect to Active Directory.
|
|
server="DC"
|
DC is the server running Active Directory. DC will service
all LDAP requests for the SSP.
*DC is the name of the machine where we have Domain Controller.
|
|
port="389"
|
The default port number used by LDAP is 389.
|
|
userContainer=“CN=Users, DC=contoso, DC=com”
|
User objects in Active Directory are located inside the
Users container in the contoso.com domain.
Using contoso as an example of domain name.
|
|
userNameAttribute="sAMAccountName"
|
In Active Directory, user name is mapped to the
sAMAccountName attribute.
|
|
LdapRole
|
LdapRole is the role provider you use in this lab.
|
<membership defaultProvider="LdapMembership">
<providers>
<add name="LdapMembership"
type="Microsoft.Office.Server.Security.LDAPMembershipProvider,
Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71E9BCE111E9429C" server="dc" port="389"
useSSL="false" userDNAttribute="distinguishedName"
userNameAttribute="sAMAccountName" userContainer="CN=Users,DC=contoso,DC=com"
userObjectClass="person"
userFilter="(|(ObjectCategory=group)(ObjectClass=person))"
scope="Subtree"
otherRequiredUserAttributes="sn,givenname,cn" />
</providers>
</membership>
<roleManager
defaultProvider="AspNetWindowsTokenRoleProvider"
enabled="true" cacheRolesInCookie="true"
cookieName=".PeopleDCRole">
<providers>
<add
name="LdapRole"
type="Microsoft.Office.Server.Security.LDAPRoleProvider,
Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71E9BCE111E9429C"
server="dc"
port="389"
useSSL="false"
groupContainer="DC=contoso,DC=com"
groupNameAttribute="cn"
groupMemberAttribute="member"
userNameAttribute="sAMAccountName"
dnAttribute="distinguishedName"
groupFilter="(ObjectClass=group)"
scope="Subtree"
/>
</providers>
</roleManager>
5.
Save the web.config file and exit Notepad.
6.
Close the CentralAdmin-web.config.txt opened in
Notepad.
7.
Follow the same process to open the web.config
of the SharePoint (45000) Web application.
8.
Open the Application-web.config.txt file located
under X:\eDirectoryImport\ in Notepad and then do a CTRL+A and CTRL+C to copy
all text to clipboard.
9.
Paste the copied text under the
<system.web> root section in the web.config file. The text you paste
should look like the excerpt below. Note; the section is not the same as
mentioned in Step 4. The parameters are highlighted in red below:
<membership
defaultProvider="LdapMembership">
<providers>
<add name="LdapMembership"
type="Microsoft.Office.Server.Security.LDAPMembershipProvider,
Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71E9BCE111E9429C" server="dc" port="389"
useSSL="false" userDNAttribute="distinguishedName"
userNameAttribute="sAMAccountName" userContainer="CN=Users,DC=contoso,DC=com"
userObjectClass="person"
userFilter="(|(ObjectCategory=group)(ObjectClass=person))"
scope="Subtree"
otherRequiredUserAttributes="sn,givenname,cn" />
</providers>
</membership>
<roleManager defaultProvider="LdapRole"
enabled="true" cacheRolesInCookie="true"
cookieName=".PeopleDCRole">
<providers>
<add name="LdapRole"
type="Microsoft.Office.Server.Security.LDAPRoleProvider,
Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"
server="dc"
port="389"
useSSL="false" groupContainer="DC=contoso,DC=com"
groupNameAttribute="cn" groupMemberAttribute="member"
userNameAttribute="sAMAccountName"
dnAttribute="distinguishedName" groupFilter="(ObjectClass=group)"
scope="Subtree" />
</providers>
</roleManager>
10.
Save the web.config file and exit Notepad.
11.
Close the Application-web.config.txt file.
12.
Open a command prompt window and run iisreset.
It is recommended that when you make changes to the web.config, you perform an
iisreset on the WFE.
13.
Close the command prompt window.
Configure Forms-Based Authentication in Central Administration
Complete the following steps on the SHAREPOINT3 server to
enable forms-based authentication.
1.
Open the Application Management section in
SharePoint Central Administration.
2.
Click Authentication providers under the
Application Security section.
3.
Ensure you select SharePoint (90) in the Web
Application drop down.
4.
Click the Windows link. The Edit Authentication
page is displayed.
5.
Select the Forms option in the Authentication
Type section.
6.
Type LdapMembership in the Membership Provider
Name section.
ScreenShot
7.
Type in the name of the LDAP role provider as
LdapRole in the Role Manager Name text box. LdapRole is what we used in the
web.config file of the SharePoint (90) web application.
ScreenShot
8.
Click Save. SharePoint automatically enables
anonymous access on the Web application for which you enabled forms
authentication.
9.
Click on the Application Management tab in
SharePoint Central Administration.
10.
Click Policy for Web application under the
Application Security section.
11.
Click Add Users in the tool bar. The Add Users
page is displayed for you.
12.
Ensure you have the SharePoint (90) Web
application selected in the Web Application section.
13.
Select Default in the Select the Zone section.
14.
Click Next.
15.
Click the Browse icon in the Choose Users section. The Add People
and Groups dialog is displayed.
16.
Enter spsadmin in the Find text box and click
the find icon . Notice that the spsadmin user
properties are fetched.
ScreenShot
17.
Double-click the spsadmin user entry to add
the user to the Web application.
18.
Click OK to close the Add People and Groups
dialog box.
19.
Select Full Control – Has full control check box
in the Choose Permissions section.
20.
Click Finish.
Forms authentication is now enabled on the SharePoint (90)
Web application. When you browse to the http://sharepoint:90, you will be
redirected to the _layouts/login.aspx page instead of the /Pages/Default.aspx
page.
ScreenShot
The user spsadmin has full control on the http://sharepoint:90
Web application. You can try logging in as spsadmin with ‘password’ as the
password.
ScreenShot
Let me know if you still have any questions, you can write me on saudhall@microsoft.com or saudhall@gmail.comThanks, Saurabh Dhall
October 15 following are the steps...
1) Download and then install Microsoft SQL Server Native Client and Microsoft SQL Server 2005 Command Line Query Utility.
2) Identify the Sharepoint DB you want to move (look under %SystemRoot%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data)
3) Close the SharePoint services.
4) Open a command prompt .. (start - run - cmd)
5) Go to the Microsoft SQL Server 2005 Command Line Query Utility folder (under C:\Program Files\Microsoft SQL Server\90\Tools\binn)
6) Type sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E
7) Type EXEC sp_detach_db <Database_Name_to_be_moved> and press Enter
8) Type GO and press Enter
9) Move db files (.mdf and .ldf) from the Sharepoint DB previously detached to the new location.
10) Type
EXEC sp_attach_db @dbname = N'<Database_Name_to_be_moved>', @filename1 = N'<New_Location_Path>\ <Database_File_to_be_moved>.mdf', @filename2 = N' <New_Location_Path>\ <Database_Log_File_to_be_moved>.ldf’ (Ex:EXEC sp_attach_db @dbname = N'SharePoint_AdminContent_f9e992d3-3d22-4117-8725-26ce0dd0f652', @filename1 = N'E:\SharepointDB\SharePoint_AdminContent_f9e992d3-3d22-4117-8725-26ce0dd0f652.mdf', @filename2 = N'e:\SharepointDB\SharePoint_AdminContent_f9e992d3-3d22-4117-8725-26ce0dd0f652_log.ldf’)
11) Press Enter
12) Type GO and press Enter
13) Repeat steps 7 to 12 for each DB to be moved.
13) Type Exit and press Enter to exit SQLCMD
14) Type Exit and press Enter to close the Command Prompt.
15) Start the Sharepoint services previously stopped.
16) If search is causing some trouble, then full crawl is recommended, if that doesn't help much then try iisreset.
|