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.
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.
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
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)
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).
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 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 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 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 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 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")
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.
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.
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
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"
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