If running Microsoft Office SharePoint Server 2007 (MOSS 2007) and created a site from a collaborative template such as the Team Site template or Blank Site template, you may notice that by default you do not see the Advanced Search option to the right of your search box as you do when you create a Publishing Portal or Collaboration Portal.

Top Level Collaboration Portal Search Box

Top Level Team Site Search Box

To get started to use the Advanced Search, a page from which to perform your query and then another to display the search results should be there. MOSS 2007 has page layouts / template for each of these as well as provides customizable web parts to create everything completely from scratch to suit specific requirements. However the quickest would be to create a sub site using the Search Center template as this site template already contains the elements required. The steps are as follows:

1. From the home page of top level site, select Create from Site Actions menu.
2. Select Sites and Workspaces.
3. Fill in the details for new site. Make sure to select the Search Center template under Enterprise tab. And to inherit permissions of your top level site since it would ensure all users of top level site will be able to access the advanced search interface.
4. Click Create button to complete the creation of new search site.
5. It will be redirected to home page of new search site. The page displays a search box with a link to Advanced Search page.  
6. Click the Advanced Search link.
7. From the Advanced Search page, copy the URL of this page.
8. Select Site Settings from the Site Actions menu.
9. Because you are on a sub site to your top level site where the majority of site collection settings exist, you need to then select Go to Top Level Site Settings.
10. Select Search Settings.  
11. Select the top option and paste in the Advanced Search webpage. The URL  should end with /{the URL  name of search site}/advanced.aspx.  
12. Click OK.
13. When returned to the home page of team site, Advanced Search link will now appear & clicking it will load the Advanced Search webpage.

• The scheduling engine, Active Cache, and Gantt charts all have improvements.
• There is additional reliability with earlier versions of the .mpp format.

Project Server sends two types of e-mail messages automatically:

·        Notifications

·        Reminders

The system sends a Notification message immediately whenever an event in an enterprise project triggers this action. If the project manager changes the schedule of tasks in the project, the system automatically sends a Notification e-mail message to all team members affected by the schedule change.

The system can also send Reminder messages to any user who subscribes to Reminders in Project Server. For example, a user can set up a Reminder subscription asking Project Server to remind him/her 2 days before the start of a new task.

To set up e-mail subscriptions for both Notifications and Reminders, users of Project Server 2002 and 2003 must navigate to the Project Web Access home page and click the Alert Me About My Tasks and Status Reports link in the Actions pane on the left. On the Alert Me About My Tasks and Status Reports page, each user can set up his/her own subscriptions to e-mail messages from Project Server. Users of Project Server 2007 must click the Personal Settings link in the Quick Launch menu and then click the Manage My Alerts and Reminders link.

Resolution for Project Server 2002 and 2003

To customize the content of e-mail Notifications and Reminders in Project Server 2002 or 2003, refer to the following article in the MSDN Library:

Customize Project Server E-mail Notifications and Reminders for 2002 and 2003

Note: Although the article refers specifically to Project Server 2002, the information is applicable to Project Server 2003 as well.

Resolution for Project Server 2007

To customize the content of e-mail Notifications and Reminders in Project Server 2007, refer to the following article in the MSDN Library:

Customize Project Server E-mail Notifications and Reminders for 2007 Only

To start ensure that you actually have a SearchCenter site installed on the site. Without this, there will be no place for the scoped searches to target and the scopes will not show up.

After ensured that SearchCenter is installed, go to SharedServices to sure that the scopes are there. With MOSS, usually two defined scopes out of the box, All Sites and People. Make sure that scopes are there and there is data in them.

If above two are confimed then go to the base site for your collection. Log in as the Administrator and click on “Site Settings - Modify All Site Settings”.

From All Settings, find the Search Scopes link in the Site Collection Administration column and click on it.

SharePoint might lose the scoping information, if it has lost it for your site collection, you will see your two scopes here in the category of Unused Scopes. In order to reset your scopes correctly, click on the “New Display Group” button on the menubar.

In order for the Scopes to show up in the Search Drop Down, place “Search Dropdown” in the Title box here. Place a description in the next field. Now check both of the scope “Display” checkboxes and select a position for each (usually it is All Sites (1) and People(2). Make the default scope “All Sites” and click on “OK”

Return to the view you will see your defined scopes in the new Category: “Display Group: Search Dropdown(2)”. And go to your site you will see that the scopes are now part of the dropdown box.

To set up Advanced Search, create another Display Group. In this group place “Advanced Search” in the title and check on “All Sites” and make “All Sites” the default, Advanced search shows up.

When you author a workflow in a declarative rules-based, code-free workflow editor, such as Office SharePoint Designer 2007, you are authoring that workflow directly against, and data-binding it to, a specific list or document library in Windows SharePoint Services 3.0. You are using a predefined list of workflow activities, and are not using any code. The workflow you design is not compiled as an assembly, but is stored as source files until Windows SharePoint Services 3.0 compiles the workflow the first time it runs.

This approach provides the following advantages:

• Workflows can be developed and tested rapidly.
• Because the workflow is specific to a given list, the following are simplified:
• The deployment process
• Security issues management
• Because workflows are not compiled into assemblies, workflows created in a declarative rules-based, code-free workflow editor such as Office SharePoint Designer 2007 can be deployed to servers where administrative policy prohibits custom code assemblies.

• Workflows can be created by users with less developer experience, such as Web designers or knowledge workers.

Because you author the workflow directly against and data-bind it to a document library, workflows authored in Office SharePoint Designer 2007 differ from those created using the Visual Studio 2005 Designer for Windows Workflow Foundation in the following important ways:

• You cannot deploy a workflow authored in Office SharePoint Designer 2007 to multiple lists. It is only valid for the list for which you created it.
• Because you are authoring the workflow directly against a list, the workflow is associated with the list at design time. Therefore, there is no association stage with workflows authored in Office SharePoint Designer 2007.
• You cannot modify workflows authored in Office SharePoint Designer 2007.
• You cannot author against a content type in Office SharePoint Designer 2007.

For a detailed comparison of Office SharePoint Designer 2007 and Visual Studio 2005 Designer for Windows Workflow Foundation, see Workflow Development Tools Comparison

Running Uncompiled Workflows

Because they contain no custom code, workflows authored in a declarative rules-based, code-free workflow editor such as Office SharePoint Designer 2007 are not compiled and deployed as assemblies. They are stored as their source files within Windows SharePoint Services 3.0, and only compiled into memory when needed.

For each site, the workflows of this type are stored in a separate document library. This document library contains a folder for each workflow authored in Office SharePoint Designer 2007. The folder contains all the source files necessary for the workflow, including the following:

• The workflow markup file
• The workflow rules file
• ASPX forms for any custom workflow forms that are needed

Windows SharePoint Services 3.0 includes a just-in-time compiler to compile the source files into a workflow the first time that workflow is started on an item. Windows SharePoint Services 3.0 retains the compiled workflow in memory until it is called again, much like servers caches compiled ASPX pages to speed execution performance the next time the page is called.

Each time a workflow is started on an item, Windows SharePoint Services 3.0 determines whether the workflow was deployed as an assembly or as source files. If a workflow assembly exists, Windows SharePoint Services 3.0 calls that assembly to create the workflow instance. If the workflow was deployed as source files, Windows SharePoint Services 3.0 next determines whether or not it already has a workflow compiled from those source files in memory. If it has, then Windows SharePoint Services 3.0 calls the in-memory complied workflow to create the workflow instance. If not, Windows SharePoint Services 3.0 uses its just-in-time compiler to compile the source files into an in-memory workflow, which it then calls to create the workflow instance.

Comparison between the capabilities offered by the Visual Studio 2005 Designer for Windows Workflow Foundation and Office SharePoint Designer 2007, and the workflows created with each.

Out Of the Box Workflows in Microsoft Office SharePoint Server 2007 :

• Approval workflow
• Collect Feedback workflow
• Collect Signatures workflow
• Disposition Approval workflow
• Group Approval workflow (available only in some languages)
• Translation Management workflow

Approval workflow

Approval workflow routes a document for approval and can be set up in serial or parallel, and preset the approvers. Typically used to send out a document to approvers, as a prerequisites to publishing the document. The document can be sent to:

• People one by one after each other ( = serial), or 
• Everyone at the same time ( = parallel)

Collect Feedback workflow

The Collect Feedback workflow routes a document for feedback. When completed all feedbacks are aggregated and sent to the originator.

Collect Signatures workflow

Rather than an approval,  Collect Signatures workflow requires digital signatures on the document. This workflow requires Office 2007 & can only be initiated from any Office 2007 client application.

Disposition Approval workflow

Disposition Approval workflow works with records management capabilities and Records Center. Allows to manage document expiration & retention. This can be used to make decisions as to what needs to be done with documents after they expire besides not just deleting the documents. For example, archive documents, send out notifications, etc.

Group Approval workflow (East Asian Document Approval)

Group Approval workflow routes a document for approval using stamp signatures and a group-oriented consensus process. It is only available for East Asian cultures. To support hierarchical approvals, this workflow uses a hierarchical control to select the approvers and stamping rather than signatures for approval.

Translation Management workflow

Translation Management workflow is used with Web content management features of SharePoint to support a translation workflow for content to multiple languages.

There is a drawback to open a Document Library in Windows Explorer view  and move multiple documents to other folders/libraries because the document’s properties get updated in the process (Date/Time, Modified, Modified By). This also applies to copying list data in data sheet view from one list to another.

To move the contents of a Library or List and preserve the item’s metadata/property values within the same site collection:

1. Create a blank destination List or Document Library.
2. You don’t have to worry about recreating custom fields. Move process will create the necessary.
3. Site Actions > Site Settings >> Go to the ‘Site Content and Structure’ page.
4. Navigate to your source List or Document Library and mark all the items that you would like to have moved.
5. Then click on Actions >> Move
6. You’ll then be prompted with a pop-up that will let you navigate to your destination List or Document Library.
7. After you select the destination, press the OK button.

By this method, all of the document properties/metadata while moving list items or documents from one location to another should be preserved.

If any user uploads any document and it remains checked out to the user, then no one else will be able to see that uploaded document because it was never checked in. Even the site owner can't see those  documents. There is an easy way to handle this situation. The site owner can go to the Document Library Settings page and click on the link to Manage checked out files. From here, can select the documents and click the Take Ownership of Selection link. Now, the site owner can enter the missing metadata and check the documents in so others can see them.

Verify that you have installed the most recent updates to Project Professional 2007 prior to troubleshooting. The Infrastructure Update for Microsoft Office Project 2007 includes enhancements to local project cache performance. In case your system does not have this installed, To install the Infrastructure Update for Microsoft Office Project 2007, see the associated download page (http://go.microsoft.com/fwlink/?LinkId=121884&clcid=0x409) on the Microsoft Download Center.

Whenever you open or save projects that are on Office Project Server 2007, the operations go through the local project cache. The local project cache is a new feature that is always turned on. The main advantages of the local project cache are improved reliability (all changes are always saved to the cache first and then to the server) and better performance (once opened, projects are always loaded from the cache, and only changes are downloaded from the server).

As per the architecture:

(1a) User opens a project for the first time.

(1b) Project is cached.

(2a) User opens the project for the second time. Project is opened from the cache.

(2b) Project changes (if any) are downloaded from Project Server.

(3a) User saves the project. Project is saved to the cache. User gets control back with minimal delay.

(3b) Project Professional saves the cached project to the server.

Cache size limit The cache size limit specifies the amount of hard disk space that may be used by the local project cache. If the size of cached projects in the local project cache exceeds this limit, the user is prevented from opening or saving projects from the server.

Use this procedure to configure the settings for local project cache location and cache size limit. The cache size limit specifies the amount of hard disk space that may be used by the local project cache.

Configure the local project cache location and cache size limit

1. In Project Professional 2007, click Tools, click Local Project Cache, and then click Cache Settings.
2. On the Cache Settings page, in the Cache location field, specify the location in which you want the local project cache to be situated. Click the Browse button to select a location.

By default, the local project cache is located on the computer on which you are connecting with Office Project Professional 2007 in: <drive>:\Documents and Settings\<userid>\Application Data\Microsoft\MS Project\Cache.

3. In the Cache size limit field, specify the maximum size of the local project cache. The default size is 2383 megabytes.
4. Click OK.

Configure browser security settings for ActiveX controls in Project Web Access 2007
ActiveX controls are used for certain functionality in Microsoft Office Project Professional 2007 and in Microsoft Office Project Web Access. In order for the ActiveX controls to work properly, the Office Project Web Access Web site must be added to the list of trusted sites in Internet Explorer. There are additional security settings that can be configured, but they are optional. This article describes how to configure these security settings.
Identify and perform the procedures that are needed in your environment

Attachment:

File comment: IE ActiveX controls in PWA 2007

IEsecsetactxPWA001.JPG [ 44.48 KiB Viewed 60 times ] http://www.kanavgupta.com/forum/viewtopic.php?f=4&t=35

Add the Project Web Access site to the list of trusted sites
1. In Internet Explorer, on the Tools menu, click Internet Options.
2. On the Security tab, in the Select a zone to view or change security settings box, click Trusted Sites, and then click Sites. The Trusted sites dialog box appears.
3. Clear the Require server verification (https:) for all sites in this zone check box.
4. In the Add this Web site to the zone box, type the URL for the Project Web Access site, and then click Add.
5. Click Close to close the Trusted sites dialog box.
6. Click OK to close the Internet Options dialog box.
Turn off Internet Explorer protected mode on a computer running Microsoft Windows Vista
1. In Internet Explorer, on the Tools menu, click Internet Options.
2. Click the Security tab, then clear the Enable protected mode check box.
3. Close Internet Explorer and then start it again to finish changing this setting.
Enable prompting on controls that are not safe for scripting
1. In Internet Explorer, on the Tools menu, click Internet Options.
2. On the Security tab, in the Select a zone to view or change security settings box, click Internet, and then click Custom level. The Security Settings — Internet Zone dialog box appears.
3. In the tree control named Settings, in the ActiveX controls and plug-ins section, select Prompt under Initialize and script ActiveX controls not marked as safe for scripting.
4. Click OK to save the change and close the Security Settings - Internet Zone window.
5. On the Security tab, in the Select a zone to view or change security settings box, click Local Intranet, and then click Custom level. The Security Settings — Local Intranet Zone dialog box appears.
6. Click OK to save the change and close the Security Settings - Internet Zone window.
7. Click OK to save the change and close the Internet Options dialog box.
Set "Allow Programmatic Clipboard access" to "Enable" or "Prompt" in Internet Explorer
1. In Internet Explorer, on the Tools menu, click Internet Options.
2. On the Security tab, in the Select a zone to view or change security settings box, click Internet, and then click Custom level. The Security Settings — Internet Zone dialog box appears.
3. In the tree control named Settings, in the Scripting section, select Prompt under Allow programmatic Clipboard access.
4. Click OK to save the change and close the Security Settings - Internet Zone dialog box.
5. On the Security tab, in the Select a zone to view or change security settings box, click Local Intranet, and then click Custom level. The Security Settings — Local Intranet Zone dialog box appears.
6. In the tree control named Settings, in the Scripting section, select Prompt under Allow programmatic Clipboard access.
7. Click OK to save the change and close the Security Settings - Internet Zone dialog box.
8. Click OK to save the change and close the Internet Options dialog box.
Enable cross-domain access
You may encounter a situation in which a user in a separate domain wants functionality provided by an ActiveX control. This situation can make that user's computer less secure, and thus it should be dealt with carefully. Planning for security is important because an ActiveX control is particularly vulnerable to attack. An application running on any Web site can use the control; all that it needs is the control's class identifier (CLSID). The control may be used in ways that you do not intend. Such an action might be friendly or it might be a malicious attack on the computer running the control.
Caution: Users should not, as a rule, enable cross-domain access on any zone apart from "Trusted Sites" because it is very dangerous, as it opens the door to attacks on in-domain resources from sites outside the domain. Be judicious about advising users to enable cross-domain access.

Business Power users may want or need to see reports from the Shared Service Provider.

The SSP operates almost identically to any other site collection, however certain pages and reports are not governed by the permissions setup in the Site Collection and to allow users to read these reports a policy for the SSP must be setup to grant these users read access.
Setting the SSPs Security Policy:

1. From Central Administration go to Application Management
2. Under Application Security got to Policy for Web application

3. Add a policy for the users or groups to read the SSP web application (Groups are always preferable over individual accounts)

4. Once configured verify the users and groups have access through in the Site Collection Security

·          Windows SharePoint Services 3.0 Application Template: Application Template Core

·          Windows SharePoint Services 3.0 Application Template: Help Desk

·          Windows SharePoint Services 3.0 Application Template: Knowledge Base

·          Windows SharePoint Services 3.0 Application Template: Document Library and Review

·          Windows SharePoint Services 3.0 Application Template: Absence Request and Vacation Schedule Management

·          Windows SharePoint Services 3.0 Application Template: Project Tracking Workspace

·          Windows SharePoint Services 3.0 Application Template: IT Team Workspace

·          Windows SharePoint Services 3.0 Application Template: Change Request Management

·          Windows SharePoint Services 3.0 Application Template: Room and Equipment Reservations

·          Windows SharePoint Services 3.0 Application Template: Call Center

·          Windows SharePoint Services 3.0 Application Template: Budgeting and Tracking Multiple Projects

·          Windows SharePoint Services 3.0 Application Template: Team Work Site

·          Windows SharePoint Services 3.0 Application Template: Inventory Tracking

·          Windows SharePoint Services 3.0 Application Template: Physical Asset Tracking and Management

·          Windows SharePoint Services 3.0 Sample: Example Master Pages

In order to successfully backup and restore SharePoint Farm from 5 servers to 1 test server, backup &  Restore the following:
-12 Hive files
-IIS MetaBase
-Inetpub directory
And also have been told, the following is not backed up in a STSADM backup /restore:
-Alternate Access Mappings
-Multiple Host Headers
-SSL Certificates
-Assigned IP addresses
-Custom Code (such as web parts, features, or workflows)
-Site Definitions
-Search Indexes
-Any changes to Windows Registry of your SharePoint servers

Site Settings > Modify All Site Settings > Navigation (under Look and Feel) > ensure "Show subsites" is checked.
Now within any of your subsites go to Site Actions > Settings > Navigation (under Look and Feel) > select "Display the same navigation items as the parent site" (under Global Navigation) > OK
You'll have to do that for each sub-site.

Running MOSS 2007 with MS Office 2007 Enterprise
1.  On the Actions Menu of a Team Site "Open With Access" option is missing.
2.  Trying to import data from a SharePoint list in Access 2007 does not return any data.

Open with Access would appear only in a list within the team site and not on Document Library.