Hanz Blog

How to create a feature receiver that update a theme

mshanz — Fri, 06 Feb 2009 09:39:46 GMT

Pre request:

· Windows Server 2003 SP1 or above

· Visual Studio 2008 Pro or above

· Visual Studio Extension for SharePoint 1.3 CTP or later

Steps:

Start Visual Studio

Create a SharePoint project using Empty template

· =>File=>New=>Project

· Visual C#=>SharePoint=>Empty

· Type name as MyThemeFeature

· Select FullTrust(Deploy to GAC) on the Select Trust Level popup window

· =>OK

Extract the Public Key token

· Open Visual Studio Command Prompt

· Go to the folder \MyThemeFeature\Properties\ folder

· Run Sn –p MyTheamFeature.snk > publicKey.snk

· Run Sn –t publicKey.snk > Token.txt

· Open Token.txt

· Copy the public key token

Create a New Feature with the event receiver

· Switch to WSP view

· Click refresh button so that MyThemeFeature is showing on the root note

· Click create new feature button

· On the Feature Scope Settings popup, select Add feature receiver, =>OK

· Rename Feature1 to MyThemeFeature

· Open feature.xml file

· Inside feature.xml file, rename the title from feature1 to MyThemeFeature

· Add ReceiverAssembly and ReceiverClass attribute so that the feature.xml file now looks like this: (the PublicKeyToken should be from the Token.txt file you copied before.)

<?xml version=”1.0” encoding=”utf-8”?>

<Feature Id="b3c387b3-5f74-4054-bb70-8b45c7549afa"

Title="MyThemeFeature"

Scope="Web"

Version="1.0.0.0"

Hidden="FALSE"

DefaultResourceFile="core"

xmlns="http://schemas.microsoft.com/sharepoint/"

ReceiverAssembly=" MyThemeFeature, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9f4da00116c38ec5"

ReceiverClass=" MyThemeFeature. FeatureReceiver1"

</Feature>

Edit event receiver to use your theme

· Open FeatureReceiver1.cs file

· Modify the FeatureActivated and FeatureDeactivating methods as the following:

public override void FeatureActivated(SPFeatureReceiverProperties properties)

{

SPWeb web = properties.Feature.Parent as SPWeb;

web.ApplyTheme("YourThemeName");

}

public override void FeatureDeactivating(SPFeatureReceiverProperties properties)

{

SPWeb web = properties.Feature.Parent as SPWeb;

web.ApplyTheme("none");

}

· You need to replace the above “YourThemeName” with the them name you want. For example “Jet”

Deploy and test your solution

· Right click on MyThemeFeature project and select Deploy

· Browser to your site.

· You may need deactivate and activate the MyThemeFeature to see your theme applied.

How to search Contoso Business Data Catalog (BDC) in SharePoint Guidance

mshanz — Thu, 05 Feb 2009 21:00:28 GMT

Pre request:

Install Visual Extension for SharePoint 1.3 CTP https://connect.microsoft.com/Downloads/DownloadDetails.aspx?SiteID=428&DownloadID=15946

Install the TypeMock 5.21 or later (not required if you don’t want to run the test project)
http://www.typemock.com/Downloads.php

Run on the command prompt: “C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe” –I

Download the Source code drop

· Download SPG v2 Iteration 2 Drop from http://www.codeplex.com/spg ( http://www.codeplex.com/spg/Release/ProjectReleases.aspx?ReleaseId=22570 )

· Don’t do anything that specified the in the Download page. You will perform different steps.

Install the Catalog and Pricing WCF service

Run C:\drop\Source\PSS\Contoso.LOB.Services\ generatecert.bat

Start IIS Manager and create a new website with tcp port number 8585 and pointing to path c:\inetpub\wwwroot (please don’t point to the c:\drop\source\pss\contoso.lob.services folder). Execute permission is needed.

Go to the AppPool of the above site. Make sure that the the Identity of the App Pool is a member local windows account. Do not use network service account.

Open the C:\drop\Source\PSS\ Contoso.PSS.sln and rebuild the solution (this will create a web application under the above web site). Don’t Deploy the solution. If you only have VS Pro, you may not be able to open the test project. But that is OK. If you want, you may remove all the test projects in the solution.

Browse to http://localhost:8585/Contoso.LOB.Services/ProductCatalog.svc and you should see the ProductCatalog Service page

Browse to http://localhost:8585/Contoso.LOB.Services/Pricing.svc and you should see the Pricing Service page

Import Product Catalog BDC Definition

Start => Administrative Tools=>SharePoint 3.0 Central Administration

=>SharedServices1

=>Import Application Definition (under Business Data Catalog)

Browse to the C:\drop\Source\PSS\ProductCatalogDefinition.xml file, =>Open

Leave the "File Type" and "Resources to import" options with default values

Click "Import"

Try a Search

· In the search box of a site, type “zune” and click search. You will probably not get any result.

Set the Farm Search Service Account

The search service will run using this account. Setting or changing this account affects all index and query servers in the server farm.

The farm search service account must not be a built-in account for security reasons and for it to access the database and content index. Examples of built-in accounts are Local Service and Network Service.

· Start => Administrative Tools=>SharePoint 3.0 Central Administration

· =>Operations=>Services on server

· =>Office SharePoint Server Search

· On /_admin/SearchServiceInstanceSettings.aspx page, set the User name and Password for the Farm Search Service Account

Set the Default Content Access Account

Specify an account to use as the default account when crawling content. This account must have read access to the content being crawled.

To avoid crawling unpublished versions of documents, ensure that this account is not an administrator on the target server.

· Start => Administrative Tools=>SharePoint 3.0 Central Administration

· =>SharedServices1=>Search settings (under Search)

· =>Default content access account, this brings you to /ssp/admin/_layouts/contentaccessaccount.aspx page

· Type the Account and Password.

Configure BDC search in Central Admin

· Make sure that your search is configured using “Office SharePoint Server Search” so that BDC search is available.

· Start => Administrative Tools=>SharePoint 3.0 Central Administration

· =>SharedServices1=>Search settings (under Search)

· =>Content sources and crawl schedules

· =>New Content Source, this will bring up “Add Content source” page /ssp/admin/_layouts/addcontentsource.aspx

o Under Name: type ContosoBDCSource (or a more logical name)

o Under Content Source Type: select Business Data

o Under Applications: select “Crawl selected applications” and check ContosoProductCatalogService

o Under Crawl Schedules: Full Crawl = None; Incremental Crawl=None

o Start Full Crawl: do not check “Start full crawl of this content source”. The reason for the above is that you will manually start the crawl

o Click OK

Create Search Scopes

· Start => Administrative Tools=>SharePoint 3.0 Central Administration

· =>SharedServices1=>Search settings (under Search)

· =>Scopes

· =>New Scope, call it ContosoBDCScope

· Click on "Add Rules" where it says "Empty - Add Rules" on the newly added scope, ContosoBDCScope

· Specify a Content Source from the drop down and select ContosoBDCSource, =>OK

· You can either wait a few minutes or issue an update. This can be done from the main search settings page.

· After having issue an update, you will see that the search scope ContosoBDC now has some items populated in it. You can also confirm that by refreshing the View Scopes page till Update status is ready for contosoBDCScope:

· Your search is now ready to use. However, it have to crawl the Source first.

Try a Search

· In the search box of a site, type “zune” and click search. You will probably not get any result. This is because you have not crawled the ContosoBDCSource

Start Crawl the BDC Source

· Start => Administrative Tools=>SharePoint 3.0 Central Administration

· =>SharedServices1=>Search settings (under Search)

· =>Content sources and crawl schedules

· Select drop down on ContosBDCSource => Start Full Crawl

· Wait until the status turns to Idle for ContosoBDCsource (by refreshing the page)

Start a search

· In the search box of a site, type “zune” and click search. You should see the result similar to this one:

· You will get an error if you click Product.aspx or the other link below it since this page does not actually exist. The data you see is in the ContosoBDCSource.

References

http://blah.winsmarts.com/2007-4-SharePoint_2007__BDC_-_Enabling_Search_on_business_data.aspx

http://msdn.microsoft.com/en-us/library/ms549284.aspx

How to fix the error when restarting Windows SharePoint Services Search

mshanz — Wed, 04 Feb 2009 01:10:31 GMT

If you stop the “Windows SharePoint Services Search” and start it again using:

Central Administration=>Operations=>Services on server=>Windows SharePoint Services Search=>Stop
Central Administration=>Operations=>Services on server=>Windows SharePoint Services Search=>Start

You might get the following error:

database_name on np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query contains user-defined schema. Databases must be empty before they can be used. Delete all of the tables, stored procedures and other objects or use a different database.

You can fix the problem by deleting the database in the SQL Server:

Stop the SQL Server Express Services: Start => All Programs => Administrative Tools => Services => SQL Server (SQLEXPRESS) => Right click Stop
Delete the following file
C:\Windows\SYSMSI\SSEE\MSSL.2005\MSSQL\DATA\WSS_Search_ Servername.mdf
C:\Windows\SYSMSI\SSEE\MSSL.2005\MSSQL\DATA\WSS_Search_ Servername_log.LDF
Restart SQL Server Express Services: Start => All Programs => Administrative Tools => Services => SQL Server (SQLEXPRESS) => Right click Start

Restart the Windows SharePoint Services Search Again:

Restart the Windows SharePoint Services Search: Central Administration=>Operations=>Services on server=>Windows SharePoint Services Search=>Start
In the Configure Windows SharePoint Services Search Service Settings page, In the Search Database section, type a new database name in the Database Name field. Click Start. (Note: You might get an error if you use the old database name)

How to Publish SharePoint Content from an Authoring Farm inside Corporate Network to a Production Farm in DMZ

mshanz — Mon, 02 Feb 2009 14:22:00 GMT

How to Publish SharePoint Content from an Authoring Farm Inside Corporate Network to a Production Farm in DMZ

Introduction

This article is based on my experience on development and testing Microsoft SharePoint Guidance 2.0 for Microsoft Patterns and Practice team. We are writing a reference implementation for MOSS 2007. The RI simulates a company named Contoso with two downstream partners: Partner1 and Partner2. Contoso is deploying a MOSS extranet application for Partner1 and Partner2 to use. The extranet will have a publishing site collection with two sub sites, one for Patner1 and the other for Partner2. The extranet will also have two collaboration sites, one for each partner.

In summary, there will be three site collections in the production farm:

A publishing site collection (shared by all partners, each has a sub site)
A collaboration site collection between Contoso and Parnter1
A collaboration site collection between Contoso and partner2

MOSS Version Requirement

Microsoft Office SharePoint Server 2007 Enterprise version is required for content publishing and BDC feature to work.
Authoring farm and the production farm should have the same MOSS version.
Infrastructure Update for Microsoft Office Servers (KB951297) should be installed on both farms for the deployment to work cross machine boundary. If you don’t install the infrastructure update on the production farm, the content deployment from authoring farm to production farm may not work.

Farm Topology

This article assumes you have two server farms: one internal farm in your corporate intranet dedicated to your authors/editors/designers and a second farm in the Internet-facing network DMZ that hosts your production site. Your internal farm is read/write, while your production farm is read-only for the publishing site collection and read/write for the two collaboration site collections. The DMZ and intranet are separated by a fire wall such as an ISA server. The following is an example topology:

A Simple Back-to-back Perimeter Topology with Content Publishing for MOSS

This is a simple farm without much redundancy. You can make you DMZ farm smaller by combining Central Admin and Web Server in to one. But most probably, you may want to expand it to have the following.

Add more web servers to the load balanced clustered web servers. We chose to have two web servers to demonstrate the distributed session cache. For the performance purpose, this may not be enough for you business.
Clustered SQL servers.
Dedicated app servers for indexing, querying, excel calculation, and etc. It is also common to add indexing or querying roles to web front end servers. If you do that, make sure that querying and indexing role are deployed in different servers.
For the performance reason, you may have a clustered ISA servers facing the internet for redundancy and caching purpose.
The Perimeter Network should allow data flow from Corporate Net.
The authoring farm is usually simpler than the production farm unless you need to do performance test. Since the production farm is already very simple, the authoring farm is configured identical to the production farm.

Security Considerations

Security by Isolation

Isolate farm into different network

Isolate Extranet Farm in DMZ

Isolate authoring farm inside corpnet so outsiders can’t access it

Isolate web collection in the different IIS application pool and different DB

Isolate Publishing Site collection in its own publishing application pool and its own DB
Isolate Partner1 collaboration site collection in its own Partner1 application pool and its own DB
Isolate collaboration site collection in its own Partner2 application pool and its own DB

Isolate publishing content in different sub site under the publishing site collection

Partner1 publishing sub site for Partner1
Partner2 publishing sub site for Partner1

Isolate people in to different roles in the aspnet authentication provider

Partner1 role for employee in Partner1
Partner2 role for employees in Partner2
Admin role for the company employee that managing the DMZ

Security by authentication and Access Control

Control access to SharePoint content by divide web application into different zones

Web application in DMZ is separated into default zone and extranet zone.
Extranet zone uses form based authentication (FBA).
Default zone uses windows authentication.
Both zones access the same content.
Authoring->Publishing will be between the authoring farm and the DMZ’s default zone (not the extranet zone)

Control access to publishing sub site by only authorizing appropriate roles

Partner1 publishing sub site only allows roles Partner1 and Admin access
Partner2 publishing sub site only allows roles Partner2 and Admin access

Control Access to SQL Database

User Windows authentication Mode instead of SQL Server Authentication for tighter data security.

Control Access to Backend Services

Create special groups for accessing Backend Services
Mapping user account to backend group using SSO
Never open backend services to public

Control Search Access

Create special groups for search
Do not use admin account for search. Admin account has too much power.
Apply security trimming.

Block security holes

Consider block cross site, cross site collection, cross webapp query for important list.
Consider block important content from been searched. Require credential for search important content.

Security for the Servers

Harding windows server 2003 sp1 by running the security configuration wizard.
Shutting off Unnecessary Services in the server
Implement File level security
Running windows server update services
Verify security using the Microsoft Baseline security analyzer (MBSA)

Security in Transport

Consider Using SSL

Security Hardening SharePoint Sites

Given only appropriate access the following site or site collection:

Partner1Collaboration Site collection =>Partner1, Admin
Partner2Collaboration Site collection =>Partner2, Admin
Partner1 Publishing Sub Site =>Partner1, Admin
Partner2 Publishing Subsite =>Partner2, Admin
Central Admin =>Admin

Lock down /_layouts/people.aspx page for everyone except Admins since publishing Site collection is shared by Partner1 sub site and Partner2 Sub Site. Here is how to do it: How to lock down /_layouts/people.aspx page for SharePoint 2007 and Microsoft Office SharePoint Server 2007

Setup the authoring and production farm for Non-publishable Components

Deployment will not deploy Programs, Assemblies, Features, Configuration information such as Web.config files. They have to be set up separately. You have to install all required WSPs, and assemblies, and features. You need to setup you configuration files correctly.

Manually set up the farms

You often need to start from a clean server, install SharePoint, create web applications, extend web application to various zones, install SharePoint WSPs, create web collections and web sites, enable features, start work flows, populate users in local machine or in a security provider database, create SharePoint user groups and individual users, and etc.

Sometimes you need to install in various configurations such as such as Win2K3, Win2k8, 64 bit, 32bit PC, and various farm configurations. It may be too time consuming if you have to run of the setup steps manually. Fortunately, there are ways to automate some of those steps.

Using STSADM and custom console app to automatically setup SharePoint Site

STSADM tool can complete many of your setup steps. For those tasks you cannot achieve with STSADM, one solution is to write a console application. This is the method we chose. We wrote a console app to modify the web.config file in the Central admin web app and extranet web app. You can download the setup batch file and custom console app source code from SPG v2 Iteration 2 Drop http://www.codeplex.com/spg/Release/ProjectReleases.aspx?ReleaseId=22570.

Extending STSADM to set up SharePoint Site automatically

Instead of writing your custom console application to carry out tasks that can not be done by STSADM, you can extend STSADM yourself or use third party STSADM extensions.

Using Backup-Restore to automatically setup SharePoint Site

You can use STSADM backups, automated SQL Backups, integrated IISBack.vbs script to automate your restore for setup. However, you need to use other methods (including manual) to setup your farm and then create the backup.

I recommend you at least perform manually setup once in your dev/test environment. Once it comes to setup the authoring and production farm, you should automate your process.

Prepare Production Farm for Content Deployment

Create Blank Site Collection by following steps

You can only deploy to a blank site when you initially deploy to the production farm.

Start Central Administration in the Production Farm
Under Application Management
Select Create or extend Web application
Select Create a new Web Application
Choose an easy to remember port number
Type in a user name and credentials to create a new app pool
Type in a descriptive database name
Leave all other settings at the default and click OK, then wait for the Web application to be created
Click Create Site Collection
Ensure that your new Web Application is selected
Type in any name for the Title (it will be overwritten later)
Select "Blank Site" as the template. This step is IMPORTANT, because Blank Site is the only template that you can import any other template into
Type in the names for the site collection owners
Click OK

Allow Incoming Content Deployment Jobs in the Production Site by following steps

Start Central Administration in the Production Farm
Select Operation
Select Content deployment settings
Select Accept incoming content deployment jobs
Select Do not require encryption and click OK

Prepare Authoring Farm for Content Deployment

Create Content by following steps

Create site collections
Create sub sites
Create pages

Create Content Deployment Path in the Central Admin of the Authoring Farm by following steps

Start Central Administration in the Authoring Farm
Select Content deployment paths and jobs
Click New Path
Type a descriptive name for the path. Select the web application and site collection for the staging site. Then type in the URL of the Central Administration web site of the production site.
Click Connect
Once you see "Connection succeeded", select the web application and site collection that you created for production. You can also choose to deploy user names and security if you want the new site to have the same users and permissions
Click OK

Create Content Deployment Job in the Central Admin of the Authoring Farm by following steps

Click New Job
Type a name, and then select the path you created
Keep all other default values, and click OK

Run Content Deployment Job in the Authoring Farm

From the context menu on the job, select Run Now
Refresh the page, and then click on the text Running
Watch the status of the job
When the status changes to Succeeded, you can click on the URL to the production site to verify that the content was deployed

Considerations when Updating Features and Installing WSP in the Production Farm

You need to be careful when installing a WSP, updating/activating features, changing web.config files, or running other jobs that might change the SharePoint behavior in the production farm. Immediately after installation and before the new content is deployed, your production site may be broken. For example, a feature activation might add/hide/modify a column in a list, and make the list broken before the new content gets deployed.

It it is recommended that after making any changes to the SharePoint, you should immediately deploy you content from the authoring or staging server to assure that the contents are in synch with other non-content artifacts such as web configurations files, assemblies, activated features, the files in the 12 hive . You should keep the time interval as small as possible.

Core Concept on Content Publishing

Path: A path is a connection between a source farm and a destination farm. The path contains information about which source web application and site collection you are deploying, authentication information for the destination farm, and the web application and site collection on the destination farm. In short, a path represents the mapping between your authoring and production site collections.

Job: A job is associated with a path, and it determines exactly which sites in the source site collection will be deployed and on what schedule. You can have many different jobs for a given path, each running on different schedules and deploying specific sections of your site.

Schedule: a job has a schedule and can deploy content updates regularly without the need to manually kick it off every time. For example, let’s say you have a Press Releases site that needs to be updated every hour, and an Employee Bios site that only needs to be updated every month. You would create two different jobs, one that runs every hour and deploys the Press Releases site, and another that runs monthly and deploys the Employee Bios site.

What will get deployed? By default, deployment only deploys the changes since the last successful deployment. If there aren’t any changes, the deployment will complete without redoing any unnecessary work. Deployment automatically picks up the dependent page layout or images and packages them up along with the page itself – even if the dependent resources aren’t in the same site. Full deployments every time can also be configured which will deploy everything even there is no change.

Deployment copies only content such as web pages and resources used by the copied pages. When a web page is deployed, any items in the content database that the page depends on, such as images, style sheets, or layout pages, are also deployed.

Content deployment deploys only the last major and the last minor version of each item where versioning is enabled.

You have option to deploy the entire site collection or a selection of sets.

What will NOT get deployed? Deployment does not deploy any of the following file types:

Programs
Assemblies
Features
Configuration information, such as Web.config files
In progress workflows, such as workflows designed with SharePoint Designer
Items in the recycle bin

Quick Deploy: It is a special job called that is automatically created for every path in any site collection with the Publishing Resources feature enabled. This job, once enabled in a path, wakes up every few minutes (15 minutes, by default) and checks a special list for content that should be deployed. If the site owner has rights, he or she can deploy pages quickly to production by using the “Quick Deploy” link on the Page Editing toolbar. This adds that page to the special list, which the Quick Deploy job will check the next time it wakes up. By default, only the site owner has the Quick Deploy right. In order to give other users the same privileges, you simply add them to the Quick Deploy Users group.

Best practices for publishing portals

A technet article http://technet.microsoft.com/en-us/library/cc850698.aspx listed following 12 best practices for publishing portals:

Deploy at least three front-end Web servers
Make query-driven Web Parts efficient
Make sure that lists and databases follow recommended limits to optimize query performance
Separate authoring and publishing environments
Separate your staging environment from the authoring environment
Make sure you have the latest updates installed!
Do not edit the destination site directly
Avoid management tasks and bulk operations in the authoring environment during peak hours
Use caching!
Start with a well-configured infrastructure that uses recommended hardware
Set application pool recycling settings for better availability
Monitor key counters to manage performance

Notes

It is important to note that content deployment is a one-way process: content is copied from a source site collection to a destination site collection. The content deployment feature does not support round-trip synchronization from source to destination and back again. Therefore, any changes that are made to the destination site collection will remain on the destination site collection only until they are deleted on the destination site collection, or are overwritten by a content deployment job that is set to deploy all content, including content that was previously deployed. Because of this, you should consider restricting permissions on the destination site collection so that users cannot make changes directly to content stored within that site collection.

One limitation in creating content deployment paths is that the source and destination path must exist in different content databases. This is because all of the GUIDs that are used to define sites, Web pages, lists, and items will be transferred with the site when it is deployed. For this reason, you cannot deploy a site to the same database as the source site.

If you create a sub site in the destination collection without using the content publishing feature, it will NOT get wiped out by the deployment. If you happen to have a sub site in the authoring farm with the same path name, your deployment will fail with error “The specified name is already in user …”. The best practice is Not to create sub site directly in the production destination site.

Background Info:

· http://blogs.msdn.com/sharepoint/archive/2006/05/02/588140.aspx

· http://blogs.msdn.com/jackiebo/archive/2007/02/26/content-deployment-step-by-step-tutorial.aspx

· http://technet.microsoft.com/en-us/library/cc627268.aspx

· http://blogs.msdn.com/gayanpeiris/archive/2008/03/24/content-deployment-in-wcm.aspx

How to lock down /_layouts/people.aspx page for SharePoint 2007 and Microsoft Office SharePoint Server 2007

mshanz — Sat, 24 Jan 2009 11:00:00 GMT

You can lock down the /_layouts/people.aspx page for all uses (except “Full Control” users) by doing the following steps:

1. Login on the top site (not the central admin site) of your site collection as a site collection admin or a full control user.

2. Click: Actions->Site Settings->People and Groups

3. Click: All People

4. Click: Settings->List Settings

5. Click: Advanced Settings

6. Check (see the following picture)

* “Only their own” on Read access

* “Only their own” on Edit access

You are done.

The above security hardening will lock down the access to _layouts/people.aspx for users with permissions such as “Design”, “Manage Hierarchy”, “Approve” “Contribute” “Read” and “Restricted Read”. However, you cannot lock down the user with “Full Control”. (see the following picture)

Fix for the failure when running patterns & practices SharePoint Guidance Integration and Build Verification Tests

mshanz — Thu, 04 Dec 2008 12:18:00 GMT

If you failed running the test cases for BVT, do the following to fix it.

read bvt_integration_tests_readme.txt.
make sure that that Contoso training site is running. For example, having http://localhost/training running as a Contoso training site.
Open Config.cs file under HelperClasses folder. make sure the following:

siteURL is the running training site you want to test
make sure that the yor are the owner of the site and the site colleciton.
Maker sure that spgemployee and spgmanager are created in the local PC
make sure that spgemployee is added to the Contoso Employees group (do this in the SharePoint site)
make sure that spgmanager is added to the Contoso Managers group (do this in the SharePoint site)

if the workflow related test cases fail, check the site to make sure that workflow is running correct. If not, make sure the workflow for Registrations List is enabled. To do that, click Lists->Registrations->Settings->List Settings->Workflow Settings, make sure Registration Approval v1 is under the Workflow Name and click it. Under the Change a Workflow: Registrations page, make sure the Start Options have the following tow boxes checked: “Allow this work flow to be manually started …” and “Start this worflow weh a new item is created”

Hello From Hanz

mshanz — Thu, 20 Nov 2008 23:02:00 GMT

My blog is up

Hanz Blog

How to create a feature receiver that update a theme

Pre request:

Steps:

Start Visual Studio

Create a SharePoint project using Empty template

Extract the Public Key token

Create a New Feature with the event receiver

Edit event receiver to use your theme

Deploy and test your solution

How to search Contoso Business Data Catalog (BDC) in SharePoint Guidance

Pre request:

Download the Source code drop

Install the Catalog and Pricing WCF service

Import Product Catalog BDC Definition

Try a Search

Set the Farm Search Service Account

Set the Default Content Access Account

Configure BDC search in Central Admin

Create Search Scopes

Try a Search

Start Crawl the BDC Source

Start a search

References

How to fix the error when restarting Windows SharePoint Services Search

If you stop the “Windows SharePoint Services Search” and start it again using:

You might get the following error:

You can fix the problem by deleting the database in the SQL Server:

Restart the Windows SharePoint Services Search Again:

How to Publish SharePoint Content from an Authoring Farm inside Corporate Network to a Production Farm in DMZ

How to Publish SharePoint Content from an Authoring Farm Inside Corporate Network to a Production Farm in DMZ

Introduction

MOSS Version Requirement

Security Considerations

Security by Isolation

Isolate farm into different network

Isolate web collection in the different IIS application pool and different DB

Isolate publishing content in different sub site under the publishing site collection

Isolate people in to different roles in the aspnet authentication provider

Security by authentication and Access Control

Control access to SharePoint content by divide web application into different zones

Control access to publishing sub site by only authorizing appropriate roles

Control Access to SQL Database

Control Access to Backend Services

Control Search Access

Block security holes

Security for the Servers

Security in Transport

Security Hardening SharePoint Sites

Setup the authoring and production farm for Non-publishable Components

Best practices for publishing portals

How to lock down /_layouts/people.aspx page for SharePoint 2007 and Microsoft Office SharePoint Server 2007

Fix for the failure when running patterns & practices SharePoint Guidance Integration and Build Verification Tests

Hello From Hanz