text:
exchange_tmphttp://blogs.technet.com/b/exchange_tmp/atom.aspxTelligent Community 126.96.36.199162 (Build: 126.96.36.199162)2011-11-29T00:36:00ZBetter with SharePointhttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/better-with-sharepoint.aspx2011-11-29T21:30:51Z2011-11-29T21:30:51Z
PerformancePoint Services in Microsoft SharePoint Server 2010 (PPS) makes it easy and convenient to organize and share your business insights. Upcoming blog posts by Office BI pros will delve into the following topics:

Efficiently organize PPS content in SharePoint Server

Easily share up-to-date information

Quickly preview PPS content in SharePoint

Build impressive PPS scorecards based on SharePoint lists

Stay tuned for more on these topics! If you have suggestions for other topics, please leave a comment below.

 Poornima Hanumara Program Manager| Office BI

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxFast Prototyping with PowerPivothttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/fast-prototyping-with-powerpivot.aspx2011-11-29T21:12:54Z2011-11-29T21:12:54Z
Today's "better together" post is by Poornima Hanumara, a program manager on the Office BI team. Thank you Poornima, and to our readers, have a great week!

I want to quickly prototype a new dashboard to keep track of the products in my sporting goods store.

PowerPivot is a great tool to create a data model. This model can be used as a data source for PerformancePoint Services to create a dashboard.

Here's the simple dashboard I want to create:

To get started I need:

PowerPivot add-in for Excel 2010

Sharepoint Server 2010 with PowerPivot installed and enabled

PerformancePoint Services for SharePoint 2010

It was a quick 3 step process to create the dashboard:

Step 1: Create a PowerPivot model

I used Excel, which had my sample data to create a PowerPivot model using some help from the PowerPivot TechNet Virtual Lab.

I created a PivotTable in Excel using the model and put all the measures in the Values field. Without doing this, PerformancePoint will not be able to distinguish measures from dimensions. So, make sure all the fields you want to use as measures are in the Values field in the PivotTable Field List!

Step 2: Publish the workbook to Sharepoint

I saved the workbook to the Sharepoint Server which had PowerPivot for Sharepoint enabled:

Step 3: Use the workbook's URL in the data source connection string in Dashboard Designer

I set the connection string to the PowerPivot datasource by using the following format:

PROVIDER=MSOLAP;DATASOURCE=http://contoso/Documents/PowerPivot_Sample.xlsx

Create a PowerPivot Data Connection has step-by-step instructions on how to create a new datasource.

In the familiar PerformancePoint Dashboard Designer, I created the dashboard and deployed it to Sharepoint. The final dashboard looks pretty similar to the initial sketch!

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxGetting Data in PerformancePointhttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/getting-data-in-performancepoint.aspx2011-11-29T21:12:11Z2011-11-29T21:12:11Z
PerformancePoint Services 2010 (PPS) provides a variety of ways to use data in analytic solutions. The usage of Analysis Services cubes and SharePoint lists in PerformancePoint is relatively well understood. Upcoming posts from the Office BI team will focus on some less well-understood aspects of getting and using data in PerformancePoint dashboards.

Here are the topics that we plan to cover:

Using Excel Services to create data that is presented in PerformancePoint scorecards

Using PowerPivot to incorporate publicly available data sets in your PerformancePoint dashboards

How to use Cascading filters to deal with cubes that contain large dimensions.

If you'd like to hear about something else, or have tips about novel ways to get and use data in PerformancePoint, please leave a comment below.

Dave Sherman | Senior Program Manager | Office BI

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxIntro to Excel Services Data Sourceshttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/intro-to-excel-services-data-sources.aspx2011-11-29T21:11:35Z2011-11-29T21:11:35Z
Introduction

The Excel Services Data Source in PerformancePoint 2010 allows you to create data using familiar Excel tools and methods that you can then surface in PerformancePoint scorecards.

To demonstrate the use of the Excel Services Data Source, I'll walk you through creating a scorecard that shows information about U.S. state government finance. The data for the this scorecard will be in an Excel workbook in a SharePoint document library.

My Example Workbook

For this example, I've created a sample workbook containing data about U.S. state government finances and population. The data in my workbook came from the site http://www.census.gov. I downloaded three workbooks from this site containing information about US state revenue, expense, and population in 2008. I consolidated this information into one workbook and then created a summary table called "StateFinances2008" containing simple metrics for each state like Revenue per Person and the Debt to Cash and Securities ratio. This workbook is attached to this blog post.

Saving the Workbook to SharePoint

To use a workbook like the one I've created as a PerformancePoint data source, first save it to a SharePoint site with Excel Services enabled. To do this, use Save to SharePoint in Excel, setting the publishing options as described below.

Publishing options control which parts of the workbook are exposed though Excel Services. Publishing options are set using Publish Options as shown:

Expose only the StateFinances2008 data table by selecting it on the Show tab of the Publish Options dialog:

Here's the workbook in my BI Center document library:

Creating the Excel Services Data Source

With the workbook in place, create a new data source using PerformancePoint Dashboard Designer:

When prompted to select the type of data source, choose Excel Services as shown:

Once the data source is created, configure it to reference the workbook you saved to your SharePoint site. Supply all the information required to retrieve the desired information from the workbook: the site address, the document library name, the name of the workbook, and the name of the data table in the workbook. The following image shows this information for the data source I created:

Next, supply the names of the columns in your new data source. The column names aren't automatically copied from the data table in the workbook. To do this click on the View tab and then select each column and enter an appropriate column name in the Details pane on the right. Here's an image illustrating this process:

Once you've finished this, your data source is complete.

Using the Data Source

After the data source is in-place, creating KPIs and a scorecard that show data in the work book is straight-forward. Using the approach described in the post Creating simple budget KPIs from SharePoint Lists, you can create KPIs and a scorecard based on your new Excel Services data source. For my sample, I created three simple KPI:

 KPI	 Actual (all from the Excel Services data source)	 Target	 Scoring Pattern

 Revenue/Person	 Revenue/Person	 $5,000	 Closer to target is better

 Expense/Person	 Expense/Person	 $5,000	 Closer to target is better

 Debt/Cash & Securities	 Debt/Cash & Securities	 0.25	 Decreasing is better

I placed these KPIs on columns and put the State dimension from my Excel Services data source on rows with all states selected.

Here's a snapshot of the dashboard containing my scorecard:

Conclusion

Although this is a simple example, Excel Service data sources enable more sophisticated PerformancePoint solutions that leverage the power of Excel and Excel Services to retrieve, manipulate, and calculate data.

Dave Sherman | Senior Program Manger | Office BI

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxCascading Filters in PerformancePoint Serviceshttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/cascading-filters-in-performancepoint-services.aspx2011-11-29T21:10:52Z2011-11-29T21:10:52Z
One long-awaited and much-requested feature for PerformancePoint, Cascading Filters, is available in SharePoint Server 2010 SP1. I wanted to go through the deployment of a dashboard using Cascading Filters to show both the ease and a little of the power this feature provides.

The concept of cascading filters is that the output of one filter becomes the input of another; or more precisely, the choices made in one filter limit the choices available in another. Typically, this would be filters in the same hierarchy: time, geography, or organization, for example.

Before showing how to set up a dashboard with cascading filters, I'd like to show you a working example, focusing on just the filters.

In this example, using the Contoso Retail DW database's Sales cube, we have a geography-based (country, state/province, and city) filter cascade. With everything in place, the filter zone of the dashboard looks like this.

Changing the "States or Provinces" filter selection to another state makes the choices for the Cities filter change.

Suppose we change the "North America" filter choice.

If we pull down the "States or Provinces" filter, notice that it shows only the Canadian Provinces.

If we disconnect the "North America" filter from the "States or Provinces" filter and re-deploy, notice how the list grows.

By "uncascading" the filters, we see the benefit we were getting with cascading filters – refining the choices in one filter based on choices made in another filter.

Let's look at how this dashboard was made, and add in a report to better visualize the filter cascade's output.

After firing up Dashboard Designer, we create the data connection. The above shows the dialog that will supply the data connection to the Analysis Services server for this example. (If you're following along creating this content, your Server will be different.) Once the data connection is saved, we can create the filters.

With the selection in the PerformancePoint Content section of the Workspace Browser, tell Dashboard Designer to create a filter.

Let's use the Member Selection filter template and, of course, the data connection we just created.

We want filters based on geography. The "Sales Territory" has several levels of geographic data. For this example, let's just use the "Sales Territory.Territory Hierarchy", which contains all of the geographies represented, but focus on the country level and slice off just the countries represented in its "North America" section. First, the Filter dimension:

Then, pick the members of interest.

Set the display method. The simplest type is the list.

We can name the filter "North America".

The next level of interest in the Sales Territory hierarchy is the state/province. Repeat the above process to create a filter for it from the dimension "Sales Territory.Territory Hierarchy" dimension, but this time, select only the children of Canada and United States.

Make this a List type filter, too, and name it "States or Provinces".

The final filter to be created is Cities, and will need the children of each Canadian Province and United States State.

Hint: A Select Grandchildren would come in handy. There is a shortcut you could take here: Use "Sales Territory.Sales Territory Name", which corresponds closely to the city level in the Hierarchy, as a dimension and select all the items The cascading functionality will pick the children of the upstream filter correctly.

Now, create a dashboard, one with several zones, and a scorecard and/or a report. Drag the filters and the reports and scorecards onto the dashboard. Try to arrange the filters in a natural flow from the highest level to the lowest for the best experience for the dashboard user.

Now, the magic. To connect the "North America" filter to the "States or Provinces" filter, either

· Drag and drop the Member Unique Name from the "North America" filter onto the "States or Provinces" filter

--or--

· Use Create Connection for the "North America" filter (from the Ribbon's Edit section or its triangle menu) to send values to the "States or Provinces" filter, with a source value of "Member Unique Name".

Similarly, connect the "States or Provinces" to the Cities filter, using Member Unique Name.

Connect the Cities filter to any desired reports and scorecards. Deploy the dashboard, and the whole system will be ready for use.

The Apply Filters Button, or Paint it Once

One seemingly minor part of the SP1 upgrade—the ability to add the Apply Filters button to a dashboard from within Dashboard Designer—ties in very closely well with Cascading Filters.

What really makes the Apply Filters button a good addition to Cascading Filters is that it lets you settle all the filter choices before the scorecards and reports "repaint", so you aren't waiting for the scorecards and reports during every adjustment of the filters.

Adding the button couldn't be simpler. It's sitting at the top of the list of filters in the Dashboard Designer's dashboard editor's Details pane.

Select it and use the Add To Zone control or just drag it onto the dashboard.

Now, when the user of the deployed dashboard changes a filter setting, other filters that are "downstream in the cascade" (dependent on that filter) will update, but reports and scorecards won't, letting the user find the exact filter settings desired, at which point the user can click the button and get all the filter values applied at once.

Here, for example, is the dashboard we've been building with the filters all applied. The Apply Filters button is inactive, because there are no pending filter changes.

Now, change the "States or Provinces" filter to Ontario. The Cities filter adjusts to the new upstream values (I opened it to show the new choices available) and the Apply Filters button turns on, but the report doesn't change at all.

Clicking the Apply Filters button makes the report update to the new value and the button go back to its inactive state.

So, that's one path through the wonderful land of Cascading Filters! Appropriate deployment of Cascading filters will improve the efficiency and reduce frustration and wait times for the users of your dashboards. If you would like more information, be sure to visit this TechNet article.

Happy Dashboarding!

Paul Thrasher,
Office BI Test Engineer

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxCreating simple budget KPIs from SharePoint Listshttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/creating-simple-budget-kpis-from-sharepoint-lists.aspx2011-11-29T21:10:10Z2011-11-29T21:10:10Z
In this post we're going to walk through how our favorite fictional company Litware uses PerformancePoint Services with SharePoint list data to do simple "under budget" KPIs.

In Litware's party planning committee we log how much we spend on events using a SharePoint list. Corporate's creating a corporate balanced scorecard using PerformancePoint Services, and they've asked us to contribute a KPI showing how we're doing. For now our KPI will be based on the data we have, and the rules will be >100% budget is warning, >120% budget is bad. Later we can swap in other sources of information, for example employee anticipation around the next golf scramble, into the KPI's definition to make it a more accurate or more predictive metric, and the changes will flow into the higher level scorecard that uses the KPI.

Here's a sample of our spending history list. Let's create the KPI and scorecard from this point.

I launch Dashboard Designer from the Business Intelligence site template homepage. First I create a new data connection using the SharePoint List template:

After the data source appears in Workspace Browser I give it a name and point it towards the specific list in the site:

Very important: based on the settings above, the unattended service account for PerformancePoint Services must have access to the list. I can find out if it does by clicking "Test Data Source."

I'm done with the data source, so I save the data source to SharePoint:

Now we're ready to build the KPI and a test scorecard. I create a scorecard in PerformancePoint Content using the SharePoint List template; this will create both our KPI and the test scorecard:

Next I select the data connection we created. Then on the next screen I add a KPI, select the columns representing Actual and Target, and select "Closer to Target is Better" for some flexibility later:

I click "Next" through the rest of the wizard to get a KPI and scorecard added to the workspace, and I see what I have so far as the scorecard updates. The exact rules haven't been set yet (remember we're after >100% budget is warning, >120% budget is bad) and I'm going to get a stern warning if I format dollars with this precision:

To change these I need to edit the KPI. I select it in the Workspace Browser, and then change the number format and thresholds:

That's better!

Although corporate probably won't care about this detail when they integrate the KPI into their scorecard, I can break the number down by the individual event titles, or any other column in the list, by dragging the field into the scorecard.

Tip: I use the "Named Sets" instead of "Dimensions" so that new rows in the SharePoint list will automatically show up in the scorecard:

After I click Update in the Edit tab of the ribbon, here's the result:

I save both the scorecard and KPI in the workspace, and now I can put it into SharePoint using the PerformancePoint Services Scorecard webpart. I think I'll touch up the test scorecard for use by our team, and I'll tell corporate my work here is done; they can find the KPI for broader use at http://intranet.litware.com/corp/hr/partyplanning/Lists/PerformancePoint%20Content/

Wade Dorrell

Program Manager, Office BI

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxUsing Project Server 2010 with PerformancePoint Serviceshttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/using-project-server-2010-with-performancepoint-services.aspx2011-11-29T21:09:32Z2011-11-29T21:09:32Z
Today's post is by Denise Stendera, a writer on the SharePoint business intelligence team. Thanks Denise!

Got Project? When you create a Project Web App in SharePoint Server, you automatically get a Business Intelligence Center. If PerformancePoint Services is configured, you can use Dashboard Designer to create project management dashboards.

For example, you can create a dashboard to track project resource usage like the one shown in the following image:

Using the dashboard filter, users can select one or more projects for which they want to view performance. The scorecard then updates to display information for the items that are selected in the filter. For example, if a user selects two items in the filter, the scorecard displays information for only those items. Similarly, if users select all the items in the filter, the scorecard displays information for all the projects.

Curious about how to create a dashboard like this for your organization?

Here's how we did it, in three steps:

We began by installing and configuring Project Server 2010 as described in Deploy Project Server 2010 to a server farm environment. As part of that process, we created a Project Web App (PWA) site and configured reporting for Project Server.

We then configured PerformancePoint Services to work in our environment, as described in Use Project Server with PerformancePoint Services.

Using sample data from the downloadable Microsoft Project 2010 Demonstration and Evaluation Installation Pack, we used Excel Services together with PerformancePoint Services to create our dashboard. (Detailed steps are included in Track project resource usage by using a dashboard.)

Using Excel, we created, configured, and published a workbook to SharePoint Server. The workbook uses an external data connection to Project Server timesheet data. It contains a PivotTable report and a PivotChart report comparing planned hours to actual hours by time period and by project.

Using Dashboard Designer, we created a SQL Server Table data connection.

Using the SQL Server Table data connection in Dashboard Designer, we created a scorecard. The scorecard contains a key performance indicator (KPI) that uses calculated metrics.

Using the same data connection in Dashboard Designer, we created a dashboard filter.

Using Dashboard Designer, we created an Excel Services report to display the PivotTable report and the PivotChart report we created earlier.

Using Dashboard Designer, we created a dashboard page and added the scorecard, Excel Services report, and filter to the page. We connected the filter to the scorecard and then published the dashboard to SharePoint Server.

It's that easy!

Be sure to see all the details in Track project resource usage by using a dashboard. And, take a look at our other business intelligence solutions and scenarios on TechNet.

Happy Dashboarding!

Denise Stendera

P.S. We're always interested in your feedback and suggestions. Please use comments to tell us what you think and what you'd like to see. You can also send us an email at mailto:email@example.com.

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxSharing Up-to-Date Information in Convenient Locationshttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/sharing-up-to-date-information-in-convenient-locations.aspx2011-11-29T21:08:29Z2011-11-29T21:08:29Z
As part of the Office Content Publishing group at Microsoft, our team writes Help content about business intelligence capabilities in SharePoint Server. In this blog, we'll look at how you can reuse and share your business intelligence content in team sites and other convenient locations.

Available in SharePoint Server 2010 is the Business Intelligence Center site template. You can use it to create and configure a place to store and organize your business intelligence content, manage user permissions to that content, and take advantage of content reusability.

Storing and Organizing Business Intelligence Content

The Business Intelligence Center serves as a central location where you can store and manage all your business intelligence content. It contains lists and libraries that contain specific kinds of content, including the following:

A Data Connections library that contains data sources that can be used by various applications, including Excel Services, PerformancePoint Services, Visio Services, Reporting Services, and so on.

A PerformancePoint Content list that contains dashboard items that were created by using Dashboard Designer, including data sources, reports, scorecards, key performance indicators (KPIs), dashboard filters, and dashboard pages.

A Dashboards library that contains published dashboards

A Documents library that you can use to store files. The Documents library also includes an Excel Services sample workbook.

Managing User Permissions to Business Intelligence Content

One really nice thing about the Business Intelligence Center is that once you set it up, users across your organization can access it, according to the permissions that are assigned to them. There are four main levels of permissions you can assign:

Read permissions that enable users to view information only

Contribute permissions that enable users to view, create, and edit items, such as data connections, reports, scorecards, KPIs, dashboard pages, and filters, but not to publish dashboards.

Design permissions that enable users to view, create, and edit items as well as publish dashboards.

Full Control permissions that enable users to view, create, edit items, publish dashboards, and view/change user permissions.

Reusing Business Intelligence Content

Another nice thing about the Business Intelligence Center is that it enables your organization to reuse items that have been created. For example, suppose that one dashboard author has created a nice sales report for a dashboard. Suppose that you want to use the same report in another dashboard. You can easily do that by using one of the following methods:

If the report and your dashboard are both created by using Dashboard Designer, you can simply open your dashboard for editing, and then add the report that you want to the page in Dashboard Designer. (For more information, see Add Items to a Dashboard Page.)

If either the report or your dashboard were not created by using Dashboard Designer, then you can use edit mode in SharePoint Server. Open a Web Part Page for editing, click "Add a Web Part" in a zone, and then use the Categories and Web Parts panes to locate the kind of Web Part that you want to add to the page. Then, click a link to open the tool pane for that Web Part, and specify the location and a name for the report. (For more information, see Creating Web Part Pages and Add a Web Part to a Page.)

You can reuse the same report in multiple locations, which cuts down on the time and effort required to share information.

More Information

Want more information about how to create, manage and share your business intelligence content? See the following resources:

Getting Started Content

Getting Started: Introduction to the Business Intelligence Center

Getting Started with Dashboards

Getting Started: PerformancePoint Dashboard Designer

Additional Content

Using Excel Services to Share Pieces and Parts of Excel Workbooks

Plan, Design, and Implement a PerformancePoint Dashboard

Create Data Connections by using Dashboard Designer

Create Reports and Scorecards by using Dashboard Designer

Create Dashboard Filters by using Dashboard Designer

Create and Assemble Dashboard Pages by using Dashboard Designer

Publish Dashboards by using Dashboard Designer

Our team is always interested in hearing from you. Please use Comments to give us your feedback. Is this information helpful? What else would you like to see? Let us know, and we will take that into account as we continue to publish more content.

Happy Dashboarding!

Denise Stendera

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxAnalytic Report Samples Published to MSDN Samples Galleryhttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/analytic-report-samples-published-to-msdn-samples-gallery.aspx2011-11-29T21:07:26Z2011-11-29T21:07:26Z
Two samples that work with PerformancePoint analytic reports are now available on MSDN.

· PerformancePoint Services 2010: Change Analytic Report Data Source Sample lets users change the data source that an analytic report points to.

· PerformancePoint Services 2010: Save Analytic Report Sample lets users save a copy of a navigated analytic report.

Both are packaged as SharePoint features in Visual Studio 2010 solutions.

Note: The samples were developed and tested on single-server farms. They work out-of-the-box in these simple test configurations, but they are not guaranteed to work with all configurations. If they do not work in your environment, you can modify the code (probably in the .aspx.cs file) in Visual Studio and then redeploy the feature.

Previously published PerformancePoint samples were moved to the Code Gallery archive site. (http://archive.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=PerformancePoint)

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxPerformancePoint Data Connection Libraries and Content Lists in SharePointhttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/performancepoint-data-connection-libraries-and-content-lists-in-sharepoint.aspx2011-11-29T21:06:32Z2011-11-29T21:06:32Z
All the items you create when you build BI solutions using PerformancePoint are stored in SharePoint. PerformancePoint data sources are stored in specialized SharePoint document libraries. PerformancePoint content is stored in specialized SharePoint lists; all the scorecards, KPIs, indicators, reports, filters, and dashboards that are created as part of a PerformancePoint solution are stored in SharePoint lists.

Explore In SharePoint with BI Center

You can explore this by creating a new site using the BI Center template (for instructions on how to do this see Getting Started: Introduction to the Business Intelligence Center). New BI Center sites contains a library called "Data Connections" and a list called "PerformancePoint Content". Links to the site's data connection library and content list are available in the quick launch area as shown in the following image:

The library "Data Connection" is the default location for storing PerformancePoint data sources and the list "PerformancePoint Content" is the default location for storing PerformancePoint reports, scorecards, filters, dashboard layouts, etc.

When you start the PerformancePoint Dashboard Designer (for more information on Dashboard Designer, see Getting Started: PerformancePoint Dashboard Designer) from the link your BI Center site as shown in the following images, it will connect to these locations and allow you to create and edit data sources and the content items that make up a PerformancePoint dashboard:

In the Designer, you can see the data source libraries and content lists you are using. For example, this is what you'll see when you launch the Designer from a BI Center site:

You can create additional data source libraries and contents lists in you BI center site to store your data sources and dashboard designs. You can use multiple data source libraries and content lists to partition the assets that make up your solutions so they can be secured appropriately and so they can be organized based on organizational areas, solution type, etc.

Use PerformancePoint in any non-BI Center Site

PerformancePoint can also be used without creating a BI Center site. PerformancePoint data source libraries and content lists can be created on any site where PerformancePoint is available. These libraries and lists provide you with direct access to the SharePoint Designer to create and edit data source, reports, scorecards, etc.

To create a new data source from a PerformancePoint data connection library:

Open the data connection library

Select the "Documents" in the library's tool bar

Select "New Document"

Select "PerformancePoint Data Source" from the resulting menu (see the following image). The PerformancePoint Dashboard Designer will be started and a new data source will be created.

To create a new report, filter, scorecard, etc. from a PerformancePoint content list:

Open the content list

Select the "Items" in the list's tool bar

Select "New Items"

Choose the type of item you would like to create (see the following image). Again, the PerformancePoint Dashboard Designer will be started and an item of the selected type will be created.

PerformancePoint data source, reports, scorecard, etc. can be edited directly from the SharePoint library or list that contain them. To do this:

Select the data source or content list item in the list or library.

Open the item's context menu

Select the operation "Edit in Dashboard Designer".

The following image show a PerformancePoint content list item and its context menu:

Preview PerformancePoint Reports and Scorecards in SharePoint

Finally, you can view reports and scorecards from the SharePoint content lists that contain them without starting the designer and without placing them in a dashboard. Here's the process:

Select the report or scorecard you'd like view in the PerformancePoint content list.

Open the report or scorecard's context menu.

Select the operation "Display Report" or "Display Scorecard".

The following images illustrate this. Select "Display Report" from the reports context menu in the content list:

Then the report will be displayed in a new tab in your browser:

Dave Sherman

Program Manager, Office BI

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxUsing Reporting Services in SharePoint Integrated Mode with PPS 2010 with SQL Server "Denali" CTP3http://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/using-reporting-services-in-sharepoint-integrated-mode-with-pps-2010-with-sql-server-denali-ctp3.aspx2011-11-29T21:05:30Z2011-11-29T21:05:30Z
The SQL Server team has made a small change to the location of the web service that PPS calls in order to render SQL Server Reporting Services reports when running in SharePoint Integrated mode. In this blog post, I'm going to go over how to work around that problem and get your reports rendering again.

The changes in Denali now have SSRS running inside the SharePoint Shared Service architecture, which in the long term will make management of this service a lot easier for the people responsible for making sure the service is up and running. As a consequence of this change, the web service that PPS relies on (ReportExecution2005.asmx) changed location. It is now located in the _vti_bin folder along with the other SharePoint web services. Accordingly, we need to point the Report Server URL parameter in Dashboard Designer to this folder.

Using SQL 2008 you would give this:

http://servername/ReportServer

With Denali, you now have to give this:

http://servername/_vti_bin/ReportServer

And if you're doing anything fancy with non root site collections, you'll also need to put that in the path, as follows:

http://servername/FancySiteCollectionName/_vti_bin/ReportServer

Here's a screenshot showing what it should look like in Dashboard Designer:

Once you make this change in Dashboard Designer and save the SSRS object, everything should work. No need to republish any Dashboards.

If you're having trouble getting Reporting Services to work in SharePoint integrated mode in the first place, here are a few resources that helped get me started:

http://msdn.microsoft.com/en-us/library/gg492276(v=SQL.110).aspx

http://blogs.msdn.com/b/querysimon/archive/2011/07/18/installing-sharepoint-2010-together-with-denali-ctp3.aspx

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxYou asked, we delivered: new Web App features now availablehttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/30/you-asked-we-delivered-new-web-app-features-now-available.aspx2011-11-29T18:52:51Z2011-11-29T18:52:51Z
On the Office Web Apps team, we are committed to improving our products based on your feedback. Since we launched the Web Apps just over a year ago, we've been listening to you, and today we're releasing new features based on what we've heard.

To everybody who has shared their opinion with us, we want to say a big THANK YOU!

Here's what we're delivering to you today, based on your requests:

OneNote Web App Ink display. We've heard from our OneNote customers who like to use pen-input devices on Tablet PCs to draw and write notes, and we've heard from others who enjoy using the Draw tools in OneNote to add ink and highlighting with the mouse or trackpad when working on PC. You've told us that you'd like to be able to view your handwritten notes and drawings in the OneNote Web App. With today's update, the OneNote Web App now displays ink.

Merge and Autofit cells in Excel Web App. Many Excel Web App customers have requested enhanced cell formatting in the Excel Web App, including the ability to merge cells, and to automatically fit cell sizes based on the content the cells contain (AutoFit). With today's update, you can now do both in the Excel Web App.

Print directly from Excel Web App in the browser. One of our top requests from Excel Web App customers is to print Excel spreadsheets directly from the Excel Web App. We think this enhancement will be a great time-saver when you need to print a spreadsheet by accessing your Excel documents stored on SkyDrive when you're away from your main PC.

Right-click menus in Excel Web App. We have also heard from Excel Web App customers that you'd like to be able to be able to use some of the same right-click short-cuts that are in Excel for the desktop. Now, you can right-click on cells in the Excel Web App to Cut, Copy, Paste, and work with HyperLinks.

Other improvements to make the Web Apps faster and more reliable. One of the most important things you've requested from us is to make the Web Apps faster and more reliable. Today's update includes a lot of behind-the-scenes improvements that do just that.

In the coming weeks, we'll be sharing some more details about how our team listens and acts on your feedback, and we'll share examples of how we've been improving product. Thanks again for all the suggestions, survey responses, and thoughtful comments in social media—please do keep them coming, because we're listening!

--Jenni French
Sr Product Manager, Office Web Apps

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxPublic Folder Replication Troubleshooting - Part 4: Exchange Server 2007/2010 tipshttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/29/public-folder-replication-troubleshooting-part-4-exchange-server-2007-2010-tips.aspx2011-11-28T19:12:38Z2011-11-28T19:12:38Z
Original post on US blog: January 11, 2008

Two years ago, I posted a three-part series on troubleshooting public folder replication. Part 1 discussed the replication of new data, Part 2 discussed the replication of existing data, and Part 3 discussed the replica deletion process and some common problems we saw with Exchange 2003. With this post, I want to update the series for Exchange 2007.

In Exchange 2007, public folder replication works basically the same way it always has. The troubleshooting steps in the first three parts of the series all still apply. However, the admin tools have changed and the common problems we see with Exchange 2007 are a little different, so that's what I want to cover here.

Changes in the Admin Tools

The event log is still your best tool for narrowing down a replication problem to a particular point of failure. In Part 1, I suggested turning up logging on Replication Incoming and Replication Outgoing to Maximum. That still applies, except that with Exchange 2007 you'll be using the Set-EventLogLevel cmdlet to set "MSExchangeIS\9001 Public\Replication Incoming Messages" and "MSExchangeIS\9001 Public\Replication Outgoing Messages" to the Expert level.

In Part 2, I described how to use the Synchronize Hierarchy and Synchronize Content options in ESM to force a status message and to timeout all outstanding backfill entries. You can still do this in Exchange 2007 via the Update-PublicFolderHierarchy and Update-PublicFolder cmdlets. These are also available in Sp1's public folder management tool, appearing as Update Hierarchy when the Public Folders root is selected and Update Content when a particular public folder is selected. Because you can use these from the command line, they are a lot more flexible than the Exchange 2003 options. For instance, it's now very simple to time out backfill entries for every folder that has a replica on your Exchange 2007 server with a simple "Get-PublicFolderStatistics | Update-PublicFolder" command. That wasn't possible in Exchange 2003 without a lot of clicking.

In Part 3, I described how to use the Public Folder Instances view to see if the deletion of a replica has completed. In Exchange 2007, you use the Get-PublicFolderStatistics command to see that same information.

Common Problems in Exchange 2007

The most common symptom I've seen so far is a store driver failure. For instance, a backfill response will be sent to an Exchange 2007 server, but if you look at the application log on the 2007 side you never see the incoming replication event. Message tracking shows that the replication message got to the hub transport server and then failed in the store driver.

This can happen for a number of reasons, and fortunately it usually is not that hard to troubleshoot. Your best troubleshooting approach in this case is to use the Pipeline Tracing and Content Conversion Tracing available on the hub transport server. If you run "Get-TransportServer | fl" you'll see a few settings related to this:

PipelineTracingEnabled : False
ContentConversionTracingEnabled : False
PipelineTracingPath : C:\Program Files\Microsoft\Exchange Server\TransportRoles\Logs\PipelineTracing
PipelineTracingSenderAddress : firstname.lastname@example.com

To find out why your backfill response is failing in the store driver, set the PipelineTracingSenderAddress to match the SMTP address of the public folder store that's sending the backfill response. Then set ContentConversionTracingEnabled to $true and PipelineTracingEnabled to $true, and reproduce the problem. After doing so, have a look in the folder specified by the PipelineTracingPath. You should find a subfolder called ContentConversionTracing, and an InboundFailures folder within that. In the InboundFailures folder, you'll have an EML file containing the replication message itself and a TXT file containing some information on the failure. The top of the TXT file will often give you a useful clue as to the reason for the failure.

For instance, in a few cases we've seen this output in the TXT file:

Microsoft.Exchange.Data.Storage.PropertyValidationException: Property validation failed. Property = [{00020329-0000-0000-c000-000000000046}:'Keywords'] Categories
Error = Element 0 in the multivalue property is invalid..

In this case it's complaining about the Categories property. This will happen if the public folder in question contains items on which the Categories property is set to be blank - such as with a single space - instead of truly being empty. You can see this by going into Outlook and choosing to view items by Category. You should find that there are two different sets of items with "None". To correct the problem, simply clear the Category on all of the "None" items using Outlook. You may have to set them to some other category and then set them back to None. Once the Categories property is truly clear, you'll only have one set of items that show "None", and the items will replicate successfully.

Another example:

Microsoft.Exchange.Data.Storage.PropertyValidationException: Property validation failed. Property = [{00062004-0000-0000-c000-000000000046}:0x8092] Email2AddrType
Error = Email2AddrType is too long: maximum length is 9, actual length is 35..

In this case its flagging the Email2AddrType property as a problem. We discovered that it had somehow been populated with the full email address on certain contacts, instead of containing only the address type that it normally should, such as 'SMTP' or 'EX'. Fixing that property allowed the items to replicate.

Sometimes the store driver will fail in a manner where it does not identify a specific problem property, such as in this output:

Microsoft.Exchange.Data.Storage.ConversionFailedException: Message content has become corrupted. ---> Microsoft.Exchange.Data.Storage.ConversionFailedException: Content conversion failed due to corrupt TNEF (violation status: 0x00000800)

This is what the failure looks like when you hit the problem described in KB 936000. Applying the fix to the Exchange 2003 server that's generating the replication message will correct that problem.

The important thing to take away from this is that Exchange 2007 does a lot of property validation to keep bad data from getting into the store. Although that's a good thing, it can keep public folder data from replicating from your Exchange 2003 servers until problems with the content are corrected on the 2003 server. ContentConversionTracing can help you identify these problems, and will often point you to the exact property causing the problem.

There's one more common problem you can identify with ContentConversionTracing, but it isn't caused by any actual problem with the content. The TXT file in the InboundFailures folder will look like this:

Microsoft.Exchange.Data.Storage.ConversionFailedException: The content conversion limit has been exceeded.
at Microsoft.Exchange.Data.Storage.InboundMimeConverter.ConvertToItem(MimePromotionFlags promotionFlags)
at Microsoft.Exchange.Data.Storage.ItemConversion.InternalConvertAnyMimeToItem(Item itemOut, EmailMessage messageIn, InboundConversionOptions options, MimePromotionFlags promotionFlags, Boolean isStreamToStream)
at Microsoft.Exchange.Data.Storage.ItemConversion.ConvertAnyMimeToItem(Item itemOut, EmailMessage messageIn, InboundConversionOptions options)

InboundConversionOptions:
- preferredCharset: iso-8859-1
- trustAsciiCharsets: True
- isSenderTrusted: False
- imceaResolveableDomain: contoso.com
- preserveReportBody: False
- clearCategories: True
- userADSession:
- recipientCache: Microsoft.Exchange.Data.Directory.Recipient.ADRecipientCache
- clientSubmittedSecurely: False
- serverSubmittedSecurely: False

ConversionLimits:
- maxMimeTextHeaderLength: 2000
- maxMimeSubjectLength: 255
- maxSize: 2147483647
- maxMimeRecipients: 12288
- maxRecipientPropertyLength: 1000
- maxBodyPartsTotal: 250
- maxEmbeddedMessageDepth: 30
- exemptPFReplicationMessages: True

First, notice the top line says, "The content conversion limit has been exceeded." Normally a public folder replication message is exempt from size limits and such, so why would this message be failing in this way? Notice that "isSenderTrusted" is False. This means the message came over an SMTP connection that was not authenticated. The sending server either failed to authenticate, or never even tried. This is very similar to what I described in the Common Problems section of Part 3, where an authentication failure would cause the XEXCH50 verb to fail in Exchange 2003. Because the sending server did not authenticate, the Exchange 2007 server applies the normal size limits to the message. If this is a content replication message with more than 250 attachments (not uncommon for a content backfill response), then it fails because it exceeds the limit. This often happens because an administrator has created a second Receive Connector which does not allow authentication, but has it configured such that it listens on the internal IP rather than the external IP. If that's not the cause, you may need to use a Netmon capture to identify the problem as I described in Part 3.

Conclusion

That should cover everything you need to know to narrow down public folder replication problems in an environment with Exchange 2007. All the old troubleshooting steps still apply; we just have different administrative tools and a different set of problems. Hope this helps!

- Bill Long

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxPublic Folder Replication Troubleshooting – Part 3: Troubleshooting Replica Deletion and Common Problemshttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/29/public-folder-replication-troubleshooting-part-3-troubleshooting-replica-deletion-and-common-problems.aspx2011-11-28T19:11:18Z2011-11-28T19:11:18Z
Original post on US blog: January 24, 2006

This is a third blog post about troubleshooting public folder replication issues. In first post we covered Troubleshooting the Replication of New Changes. The second blog post covered Troubleshooting the Replication of Existing Data. This post in this series will cover Troubleshooting Replica Deletion and Common Problems. To get the full picture, please read all referenced material!

Troubleshooting Replica Deletion

You removed an old server from the replica list on all your folders. However, when you go to Public Folder Instances for the old store in ESM, you still see a bunch of folders there. This is due to a problem with the replica deletion process. In the Exchange 2003 Sp2 version of ESM, if you try to delete a public store in this state, ESM presents a dialog stating:

"You cannot delete this public folder store because it contains folder replicas. To avoid data loss, right click the public folder store and use Move Replicas to move the replicas to a different server. It may take several hours until the content is replicated to the new server and the local replicas are removed."

When you remove a store from the replica list on a folder, that store does not immediately delete the data. Instead, it sends out a special 0x20 status request to all the other replicas. This is called a Replica Delete Pending Status Request (RDPSR), and can not be distinguished from a normal status request in the application log. A RDPSR contains a flag that indicates the replica is pending deletion. When the other stores receive this 0x20, they respond with a special 0x10 called a Replica Delete Pending Ack (RDPA). The RDPA indicates that it's ok to delete that data – but the other stores only send this 0x10 if they already have all the CNs that the pending deletion replica has. The replica will only be deleted once the store has received a 0x10 indicating that someone else has the data.

This means that if you delete the store before Public Folder Instances is empty, you are probably losing data. Only 2003 Sp2 ESM will stop you from doing this – in older versions you must manually check Public Folder Instances to see if it's ok to delete the store. You should always check Public Folder Instances before deleting a public store, and when 2003 Sp2 ESM gives you this warning, you should not try to ignore it or work around it – instead, you should troubleshoot the replica deletion process.

Note that prior to Exchange 2003 Sp2, the server that was removed from the replica list only sends the RDPSR once. If no one responds, you'll see that the folder just stays in Public Folder Instances indefinitely, unless you add the store back to the replica list and then remove it again, causing a new RDPSR to be sent. 2003 Sp2 changed this behavior so that the store will retry every hour until it gets a RDPA from someone.

Troubleshooting

This is almost the same as troubleshooting the backfill process.

1. Did the pending deletion replica send a 0x20?

Unless you already had logging turned up when you removed the replica, you won't know. Fortunately, you can just add the replica back and then remove it again. Then watch the application log for the 0x20.

2. Did the 0x20 reach the other replicas?

You should know the drill by now. Check the application logs on the other replicas to see if they received the 0x20.

3. Did any other replica respond with a 0x10?

This is the part you'll probably end up focusing on. If a replica received the 0x20 from the pending deletion replica, but did not respond with a 0x10, that means that the pending deletion replica has data that the other replica doesn't. Since you know it just received a 0x20 from that replica, then you also know that it already knows what data it's missing. Therefore, you'd expect to see a backfill request for that folder every 24-48 hours. Watch the application log, and troubleshoot it exactly like the normal backfill process described earlier.

4. Did the pending deletion replica receive the 0x10?

Once any other replica has all the data, that replica should respond with a 0x10. When the pending deletion replica receives that 0x10, it will finally be willing to delete that data. That doesn't mean it will happen immediately, though. If there are clients using that replica, it won't be deleted until later during online maintenance. If you want, you could speed this up by dismounting and mounting the store to disconnect the clients.

Common Problems

You may find that a server sent some type of replication message to another server, but the receiving server never logged the incoming message in the application log. However, message tracking says it was delivered locally to the store on that server. This behavior usually indicates either a problem with the <st1:place><st1:placename>Replication</st1:placename> <st1:placetype>State</st1:placetype></st1:place> table or a permissions problem on the SMTP virtual server.

Let's cover the easy one first. One problem that causes an incoming replication message to be ignored by the receiving server is a problem with the <st1:place><st1:placename>Replication</st1:placename> <st1:placetype>State</st1:placetype></st1:place>, or ReplState, table. Note that a problem with the ReplState table may also cause the server to fail to issue backfill requests (0x8) for some folders, so this information also applies to that situation. Each public store uses its ReplState table to track the state of replication for any replicated folders. The table contains multiple rows for each folder - one row per replica. It's possible for the rows in the ReplState table to get out of sync with the replica list, such that it has extra or missing rows. Sometimes you can get it to sync up again just by making a change such as removing a server from the replica list, applying the change, and then immediately adding it back, but this doesn't always work. Fortunately, a ReplState test was added to isinteg. See KB889331 for Exchange 2003, or KB892485 for Exchange 2000. As long as you have the updated isinteg.exe and store.exe, you can use isinteg to correct the problem with the ReplState table. If you run only the ReplState test, it is typically very fast - less than a minute even on a large public store. Once isinteg has been run, you may still need to go back and make a change to the folder to get the ReplState table to sync up with the replica list. After they're in sync, the server should be able to process the incoming replication messages, or should begin issuing backfill requests normally.

The other common problem that causes an incoming replication message to be ignored is an issue specific to Exchange 2003. An Exchange 2003 server requires that the sending server has the Send As right on the receiving SMTP virtual server. That is, if ServerA is Exchange 2003, and ServerB is sending a PF replication message to ServerA, ServerB must have Send As on ServerA's SMTP virtual server. Otherwise, ServerA does not process the incoming replication message. This permission is normally granted through the Exchange Domain Servers groups. If the Send AS right is the problem, all incoming replication messages from a particular server will fail. I find it easiest to identify this problem with a network trace taken while a replication message is being transferred from one server to another. The conversation should go like this:

ServerA: 220 ServerA.microsoft.com Microsoft ESMTP MAIL Service...

ServerB: EHLO ServerB.microsoft.com

ServerA: 250-ServerA.microsoft.com Hello

 250-TURN

 250-SIZE

 250-ETRN

 250-PIPELINE

 250-DSN

 250-ENHANCEDSTATUSCODES

 250-8bitmime

 250-BINARYMIME

 250-CHUNKING

 250-VRFY

 250-X-EXPS GSSAPI NTLM LOGIN

 250-X-EXPS=LOGIN

 250-AUTH GSSAPI NTLM LOGIN

 250-AUTH=LOGIN

 250-X-LINK2STATE

 250-X-EXCH50

 250 OK

The important part here is that ServerA must be advertising the GSSAPI NTLM LOGIN options. If you don't see these in ServerA's response to the EHLO, it's usually because Integrated Windows Authentication has been unchecked on the SMTP virtual server. This is mentioned in step 1 of KB843106 and step 3 of KB842273. As long as these authentication verbs appear, you should see ServerB try to use them:

ServerB: X-EXPS GSSAPI

ServerA: 334 GSSAPI supported

ServerB:

ServerA: 334 <more base64 encoded stuff>

ServerB: CRLF

ServerA: 235 2.7.0 Authentication successful.

If authentication does not succeed, you may have a kerberos problem or an issue with the computer account for ServerB. Next the servers will transmit linkstate information. After that, they finally get around to the business of transferring email:

ServerB: MAIL FROM:<email@example.com>

ServerA: 250 2.1.0 email@example.com....Sender OK

ServerB: RCPT TO:<email@example.com> NOTIFY=NEVER

ServerA: 250 2.1.5 email@example.com

ServerB: XEXCH50 2404 2

ServerA: 354 Send binary data

It's this last response to the XEXCH50 verb that's important. If the response is "354 Send binary data", then everything is fine, at least as far as permissions to the SMTP virtual server are concerned. If the GSSAPI NTLM login options were not advertised, or the authentication attempt failed, then it's expected that ServerA will instead respond with "504 Need to authenticate". If those steps succeeded, but ServerA still says "504 Need to authenticate" instead of "354 Send binary data", then ServerB does not have the Send As right on ServerA's SMTP virtual server. There are several ways this could happen. For one, when you delegate rights such as Exchange Full Administrator in ESM, that user or group inherits a deny on the Send As right. Therefore, using ESM to delegate admin rights to the computer account, the Exchange Domain Servers group, or some other group that contains the Exchange servers will break public folder replication. Another possibility is that the computer account is not in the Exchange Domain Servers group, which is how it normally has the Send As right. You'll need to evaluate the permissions on the SMTP virtual server and determine why the computer account for the sending server does not have the proper rights. See KB843106 and KB842273 for more details about the "504 Need to authenticate" problem.

Conclusion

You may have noticed as you read through this document that Sp2 for Exchange 2003 contains several important enhancements under the hood to prevent replication issues and assist in troubleshooting them. Environments with multiple public stores can really see a huge benefit from Sp2, especially when it comes to moving replicas between servers, and adding and removing public stores.

I hope this was helpful. Thanks to Dave Whitney for reviewing all this!

- Bill Long

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashxPublic Folder Replication Troubleshooting – Part 2: Troubleshooting the Replication of Existing Datahttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/29/public-folder-replication-troubleshooting-part-2-troubleshooting-the-replication-of-existing-data.aspx2011-11-28T19:09:00Z2011-11-28T19:09:00Z
Original post on US blog: January 20, 2006

This is a second blog post about troubleshooting public folder replication issues. In first post we covered Troubleshooting the Replication of New Changes. This blog post covers Troubleshooting the Replication of Existing Data and the last post in this series will cover Troubleshooting Replica Deletion and Common Problems. To get the full picture, please read all referenced material!

Troubleshooting the Replication of Existing Data

When new changes replicate, but old unchanged stuff doesn't, you have a backfill problem. The most typical situation where hierarchy backfill occurs is when a new public store is created. The most typical content backfill scenario is when a public store has been added to the replica list of a folder.

When you have a backfill problem like this, it may have already occurred to you that there's an easy workaround – just make a change to all the items. By doing this you circumvent the broken backfill process and replicate everything as new changes. Despite the fact that I wrote both of the tools that are typically used for this (PFDAVAdmin and ModifyItems), it's usually best to troubleshoot the backfill process and fix the root cause. If you just change everything to make it replicate, you may end up with the same backfill problem in the future when the replicas get out of sync again. That said, let's move on to discussing backfill. To understand the backfill process, it's first necessary to understand how changes are tracked.

Every folder and message in the store is assigned a Change Number (CN) when it is created and every time it is modified. When replication occurs, the CNs on each object are used to determine whether that object needs to be replicated. A group of CNs is called a CNSet. The CNSet for a particular folder on a particular server is called status information. This status information is included on every replication message. Every message type 0x2 contains the hierarchy status for the sending server. Likewise, every message type 0x4 contains the status information for that particular folder for the sending server. All other replication message types contain status information for their respective folders as well.

When a new public store mounts for the first time, it sends a status request (type 0x20) for the hierarchy to all the existing public stores. Similarly, when a new store is added to the replica list of a folder, that store will send a 0x20 to all other replicas of that folder. Like every replication message, a status request contains a CNSet of all CNs for the folder in question (or the hierarchy) that the originating store has, and asks the other stores to respond if they have CNs that the originator doesn't. Note that prior to Exchange 2003 Sp2, every replica was not asked to respond to the status request, so some stores would ignore the status request even if they had changes that the originating store did not. A 2003 Sp2 server will ask for responses from all replicas, and will respond even when the originating server did not specifically ask it to, as long as it has changes that the originating server does not. This can greatly improve the decisions made during the backfill process. The unique thing about a status request is that it doesn't contain any data to replicate - it just has a list of change numbers. The other stores respond with status messages (0x10), which list their own CNSets for that same folder (or the hierarchy). When the originating server receives the 0x10 messages, it compares the CNSet contained within to its own CNSet. If the 0x10 contains changes that the store doesn't already have, the backfill process begins.

The first step in the backfill process is to add entries to the backfill array for the folder in question. These entries have a CNSet that describes the missing changes, and a timeout value describing when the store will request the missing data. The backfill timeout will vary depending on the situation. In the case of a new public store being brought online or a new replica of a folder being added, the initial timeout is 15 minutes.

Backfill entries may be added to the backfill array during the course of normal operation as well. Consider a situation where a particular public store has broadcast two changes in two separate 0x2 messages. Let's say the administrator deletes the first 0x2 message out of the queue, but the second one makes it through. When the other servers receive this 0x2, they will find that the CNSet in the status information contains CNs that they never got. As a result, they will create backfill entries for that data. Backfill entries for missing data that was discovered during the normal course of replication will start with a timeout of 6 hours if the data is available in the same Routing Group (RG), or 12 hours if it is only available in a different RG. Each time a backfill request is issued, the next timeout will be 12 and then 24 hours for intra-RG requests, or 24 and 48 hours for inter-RG requests.

Every five minutes the store will check to see if any backfill entries have reached their timeout. If they have, a backfill request (type 0x8) is issued for the missing CNs, and the timeout is set to the next interval. A backfill request is not a broadcast; it is directed at a single server - one of the servers that previously indicated it had the missing CNs in the status information it sent to the requesting server. When that server receives the incoming 0x8, it immediately processes the request and responds with one or more backfill responses (0x80000002 for hierarchy or 0x80000004 for content), which contain the actual data for the requested change numbers. Like backfill requests, backfill responses are not broadcasts - they are sent only to the requesting server.

If the requesting server successfully processes the incoming backfill response, the CNs it contained are cleared from the backfill array on that store. Actually, any incoming message that contains CNs that are outstanding in the backfill array will cause those CNs to be cleared from the array.

Troubleshooting

As you can see, there are a lot more questions to answer when troubleshooting the backfill process.

1. Does the store know it's missing data?

First you should determine if the server even realizes that other stores have changes that it needs to request. Unfortunately, there is no supported tool or utility that will let you view the backfill array directly to see if it has anything in it. However, there are other more indirect ways of figuring this out.

One way is to wait. If the server knows it's missing data, it will be requesting it at least once every 24 or 48 hours. This means you can simply turn up logging and wait to see if a 0x8 message ever goes out. If you never see a 0x8 for the folder in question, but you are seeing 0x8's for other folders, you may have hit the outstanding backfill limit, which we'll discuss shortly.

Another option is to make sure the server receives the latest status information. Remember, the server only sends a status request that one time after you add the new replica. After that, the only status information it receives will be through the normal course of replication. So if its initial attempt to get status was lost because the 0x20 or the 0x10 in response was lost or deleted, it may sit there indefinitely and not even realize that it's missing anything. There are several ways to make sure the server has received status information for a folder.

- Go to a server that has all the data and make a change to the folder by adding, deleting, or modifying a message. In the case of the hierarchy, create, delete, or change the properties of a folder. The resulting 0x4 or 0x2 will contain status information for that folder or the hierarchy, respectively. When the server that's missing the data successfully processes the incoming replication message, you know that it has added any appropriate entries to the backfill array.

- Use the Synchronize Content option in Exchange 2003 ESM. This is a well-hidden but very useful option. To find it, go under the Public Folders tree and go to the folder in question. Highlight the folder in the left-hand pane. In the right-hand pane click the Status tab. Right-click on the server that has all the data and choose Synchronize Content. This does two things - it causes the server to issue a status request 0x20 for the folder, and it causes it to immediately timeout any backfill entries. Notice that I said you should Synchronize Content from the server that already has the data. You may wonder why you would do that, when it's the other server that has the backfill entries that need to be timed out. Remember that at this point we're just trying to ensure that the server missing the data KNOWS it has something to backfill. To that end, we can use Synchronize Content from the server that has the data to send a 0x20 to the server that doesn't. In this case we're not really interested in seeing a status 0x10 response to the 0x20. We just want the store missing content to receive a replication message for the folder from a store with content, so it can add the appropriate entries to the backfill array. The 0x20 from the server with the data serves this purpose. Note that in Exchange 2003 Sp2, Synchronize Content is now available for the hierarchy by right-clicking on the Public Folders node itself.

- Use the Replication Flags registry value (KB813629). If you put this value in place, along with the Enable Replication Messages At Startup value from KB321082, it causes the store to send a status request 0x20 for every folder on startup. Again, you would want to use this on the server that has the content - the point of this step is to get the server that has content to send its status information to the server that's missing content.

- Use 2003 ESM to send a backfill response. In 2003 Sp1, you could use the Send Hierarchy option to send a hierarchy backfill response and the Send Contents option to send a folder content backfill response. In 2003 Sp2, both of these options became Resend Changes. This sends a backfill response for the range of data you specify, but you probably shouldn't specify the whole range of data since that might satisfy all outstanding backfill entries and end up working around the original problem. Instead, specify a range of only a day or two. This causes a 0x80000002 or 0x80000004 to go to the target server, which again serves the purpose of giving it status information for the store that has the data.

Once you've used one of these options to force status information, and you've verified that the store missing the data received the incoming message by watching the application log, then you know it knows it's missing the data.

2. Does the store request the missing data?

After you've made sure the store know it needs to backfill some data, does it ever issue a backfill request? Recall that after it has tried to backfill the data a couple of times, You may have to wait 24 or 48 hours for the next backfill request, since that will be the longest timeout interval for intrasite and intersite backfills, respectively. There is one way to speed this up, and that is to use Synchronize Content again, but this time from the server that's missing the data. This will immediately timeout the backfill entries for that folder. However, you may still find that the store does not issue a backfill request for the folder you're focusing on. If this is the case, watch the app log for the next 24-48 hours. If the store is sending backfill requests for other folders, but not for the folder you're focusing on, it may have hit the outstanding backfill limit.

When you experience a situation where you've added replicas of a lot of folders to a new store, and replication seems fine at first but then grinds to a halt over the next day or two, you have probably hit the outstanding backfill limit. The outstanding backfill limit is a mechanism intended to throttle replication. By default, the store will only allow 50 outstanding backfill requests at a time. Once it has 50 outstanding, it will re-request those 50 over and over until they are satisfied. Once any one outstanding entry has been satisfied, that opens up a slot in the OBL for a new set of data to be requested. This means that if 50 requests are having problems being satisfied for whatever reason, replication can not proceed.

If you are seeing this behavior, you should watch the application log to see what the store is requesting. You'll be seeing periodic 0x8 messages for the current 50 outstanding backfill requests, and you'll find that no backfill response is received, which is why they're still outstanding. At that point you should change your focus to troubleshooting one of the folders the store is currently trying to backfill, since resolving the problem will allow it to move on to other folders.

There is one other option, and that is to increase the Oustanding Backfill Limit (OBL). You can do this by creating a registry value called Replication Oustanding Backfill Limit under the registry key for that store. The maximum value is 5000 decimal. However, once you do this the replication floodgates will open and it will be hard to determine which 50 folders caused it to choke. You'll need to postpone troubleshooting until things settle down again. Typically I recommend leaving the limit at 50 and fixing the problem, instead of working around it by increasing the limit.

If the OBL doesn't appear to be a problem, and you still aren't seeing outgoing 0x8 messages for the folder in question, see the "Common Problems" in last post of this series.

3. Does the other store respond to the request?

Once you have a backfill request to focus on, you need to determine if the backfill target ever got the request. Check the application log on that server for the incoming 0x8. You can also search the application log for the message ID mentioned in the outgoing event from the sending side. If you can find no sign of it in the application log, use message tracking to see how far it got. If it received the 0x8, it should respond almost immediately with one or more 0x80000002 or 0x80000004 messages (you will often see many backfill responses to a single backfill request, since the changes are not all sent in a single message). Of course, the time it takes to generate the backfill response messages will vary based on the data in the folder and the replication message size limit. For instance, if you set the maximum replication message size to 1 GB, the responding server could try to pack the entire hierarchy into a single backfill response, which might take an hour or more just to pack up!

4. Does the requesting server get the response?

Now it's time to check the application log on the requesting server to see if it received the backfill response. If not, track the message and see how far it got. If it received the backfill response and logged it in the application log, then that backfill request should have been satisfied and it should be able to move on.

As mentioned earlier, if you find that message tracking shows that one of these messages was delivered to the store, yet the application log does not show the incoming replication message, have a look at "Common Problems" in last post of this series.

In next blog post: Troubleshooting Replica Deletion and Common Problems.

- Bill Long

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashx1Public Folder Replication Troubleshooting – Part 1: Troubleshooting the Replication of New Changeshttp://blogs.technet.com/b/exchange_tmp/archive/2011/11/29/public-folder-replication-troubleshooting-part-1-troubleshooting-the-replication-of-new-changes.aspx2011-11-28T19:06:00Z2011-11-28T19:06:00Z
Original post on US blog: January 17, 2006

Note: this blog post is the first in a Public Folder Troubleshooting series. Please also make sure to check out part 2, part 3 and part 4 of the series.

Introduction

The purpose of this blog post series is to serve as a guide to troubleshooting public folder replication problems. It will not tell you exactly how to fix every possible replication problem. However, it will show you how to isolate every possible replication problem so that you focus your troubleshooting on the point of failure. Put another way, this post is intended to take you from a problem description like "The content on my old server isn't replicating to my new server" to a much narrower problem description like "My old server isn't responding to the status requests from my new server, therefore the new server doesn't know it's missing data and isn't trying to backfill. This means the problem is actually with the old server." This post will also describe how to identify a few of the most common replication problems. Before I get into the details of troubleshooting, I want to give an overview of my general approach to these issues.

The best troubleshooting tool for public folder replication is the application log. In order to isolate a replication problem, you must be able to follow the replication events in the log to see exactly where the process is breaking down. Typically, you should turn up Diagnostics Logging on Replication Incoming and Replication Outgoing to maximum as a starting point for troubleshooting. Each time a store sends or receives a replication message, it will log an event to that effect (assuming logging is turned up). The various kinds of replication messages can be differentiated by the 'Type' shown in the description of the event. I prefer to focus on the Type rather than the event ID for several reasons:

- Event IDs change between versions of Exchange. For instance, in Exchange 5.5 an outbound backfill request was a 3014. In Exchange 2000 and 2003 it's a 3016.

- Incoming and outgoing event IDs are different for each type. An outgoing hierarchy message is a 3018, while an incoming hierarchy message is 3028.

- Status requests and status messages use the same event IDs, even though they are two different types of messages. Thus, you can't distinguish between them from event ID alone.

Focusing on the Type is a little easier. You can easily correlate these with Event IDs by examining your application log. There are only 7 types, and you can see if the message is outgoing or incoming by looking at the Category of the event. If you focus on types instead of event IDs, all you need to remember is:

Hierarchy - 0x2

Content - 0x4

Backfill Request - 0x8

Backfill Response - 0x80000002 (for hierarchy) or 0x80000004 (for content)

Status - 0x10

Status Request - 0x20

Also note that Replication Errors logging is rarely helpful. Even when replication is working normally, most servers will generate lots of replication error events, such as event ID 3093 indicating there was an error reading a property. In most cases the property has no effect on replication and the error can be ignored. I recommend leaving Replication Errors logging at None unless you're looking for something specific, such as the problem described in this previous blog post.

Troubleshooting the Replication of New Changes

To troubleshoot public folder replication, you must first be familiar with the normal message flow that is expected when replication is working. Based on that knowledge, you can identify the point of failure when a problem arises. Before I discuss how to troubleshoot the replication of new changes, let's describe what the expected behavior is.

Hierarchy Replication

The replication of new hierarchy changes takes place whenever a folder is created or deleted, or a change is made to the properties of a public folder, such as the replica list, client permissions, description, administrative note, or storage limits. Note that this does not include the email addresses on a mail-enabled folder. The email addresses are stored on the directory object in the Active Directory, so changing them does not result in hierarchy replication. Only changing the properties stored in the public store itself will cause hierarchy replication.

Every 15 minutes (by default), the store broadcasts any changes that were made to the folder properties in one or more hierarchy replication messages. With logging turned up to Maximum on Replication Outgoing, you'll see an event like this on the server where the hierarchy was modified:

Event Type: Information

Event Source: MSExchangeIS Public Store

Event Category: Replication Outgoing Messages

Event ID: 3018

Description:

An outgoing replication message was issued.

Type: 0x2

Message ID: <email@example.com>

Database "First Storage Group\Public Folder Store (BILONGEXCH1)"

CN min: 1-72CF, CN max: 1-72D3

RFIs: 1

1) FID: 1-6994, PFID: 1-1, Offset: 28

 IPM_SUBTREE\NewFolder

Notice the "Type: 0x2" at the beginning of the description, identifying this as a hierarchy replication message.

A hierarchy replication message is sent from the originating server directly to all other public stores. There's no concept of topology for the replication of new changes. All changes to the hierarchy are sent directly from the server on which the changes were made to all other servers that have a public store associated with the same hierarchy. Every other server should log an incoming event showing a type 0x2 when they successfully process the incoming replication message.

Content Replication

Content replication takes place whenever a message is created or deleted, or the properties of a message are changed. The times at which the store broadcasts content changes for a folder can be modified by changing the replication schedule on that folder, but by default the changes will be broadcast every 15 minutes just like the hierarchy. A content replication message is identified by the type 0x4 in the event description. Once again, there is no concept of topology for the broadcast of new changes. When the content of a folder is modified on any given replica, that replica will send a 0x4 message directly to all other replicas of the folder. And again, every receiving server should log an incoming 0x4 event when they successfully process the incoming message.

Troubleshooting Steps

Those are the two most basic scenarios for replication. When new hierarchy changes or new content changes are not making it from one server to another, troubleshooting is very straightforward.

1. Did the server generate an outbound replication message?

So you made a change to a folder or you added content to a folder on particular server, and that content didn't make it to some other server. The first question to answer is did the target server broadcast the changes? When troubleshooting, it's important to keep track of what server you're working against when you make changes. There are several ways to accomplish this. In ESM, you can right-click on the Public Folders node and choose "Connect To" to point to a particular store. For the most part ESM will make any changes on the specified store, but be aware of one exception - Client Permissions. Prior to Exchange 2003 Sp2, when you changed Client Permissions through ESM, ESM would attempt to make the change against a store that houses a replica of the folder, even though this isn't necessary since the permissions are stored as a property of the folder in the hierarchy. With the 2003 Sp2 version of ESM, this was changed so that it now does make the change on the hierarchy you've pointed it to. When you're testing hierarchy replication by making changes through ESM, you should avoid using the permissions for testing since it may be hard to predict which store the change will be made against, unless you're running ESM from 2003 Sp2. If you're using Outlook and you want to verify which replica of a folder you are hitting, you can use MFCMAPI or a similar tool to view the PR_REPLICA_SERVER property of the folder. This will show you the name of the server that Outlook is using to access the content of that folder.

If the replication schedule is Always for the folder in question (which is always true for the hierarchy), and you don't see an outbound 0x2 or 0x4 within 15 minutes, then you know something is wrong on the originating server. If the server is not generating any outbound hierarchy or content broadcasts, the replication agent may have failed to start. One of the common scenarios is described in KB272999. The important thing to note here is the 3079 event:

Event ID: 3079

Source: MSExchangeIS Public

Type: Error

Category: Replication Errors

Description:

Unexpected replication thread error 0x3f0.

EcGetReplMsg

EcReplStartup

FReplAgent

This will be logged even with no additional logging turned up when you mount the public store. If the 3079 includes the "EcReplStartup" function, this means the replication agent failed to start and no new changes will be broadcast until the problem is corrected and the store is mounted again.

Hierarchy replication is also vulnerable to certain permissions problems when Exchange 5.5 public stores are present in the organization. When an Exchange 2000 or 2003 server sends a hierarchy replication message to an Exchange 5.5 server, it must produce a ptagACLData property (the 5.5-style permissions based on legacyExchangeDN) from the ptagNTSD property (the 2000-style permissions based on SID). This means each SID must be converted to a legacyExchangeDN. This SID to legacyExchangeDN conversion can fail for several reasons. For instance, if a SID resolves to more than one user, an event like this may be generated:

Event ID: 9528

Category: General

Source: MSExchangeIS

Type: Error

Description:

The SID S-1-5-21-408248388-469072634-37170099-1391 was found on 2 users in the DS, so the store cannot map this SID to a unique user.

The users involved are:

/DC=com/DC=company/CN=Users/CN=User1

/DC=com/DC=company/CN=Users/CN=User2

Since the SID can't be converted to a legacyExchangeDN, the store will fail to generate an outbound hierarchy broadcast message.

2. Was the message addressed to the server that didn't receive the change?

If the originating server generated the outbound message, the next step is to be sure it was addressed to the server that didn't receive the data. The easiest way to verify this is to track the message. In message tracking, you can just track the message ID that was reported in the outbound replication event. In the Message History window, the To: line will be visible. If the store that didn't receive the changes is not listed here, then again the focus should be on the originating server. Does it see that server in the organization? Does that server have email addresses on its public store object? Does the originating server see that store in the replica list on the folder in question?

3. Did the message make it to the destination server?

Once you've verified that the message was addressed to the destination server, the next question to answer is - did the message make it that far? You can determine this through message tracking. If message tracking says the message was delivered to the store, but you don't see an incoming replication event acknowledging the message, see the "Common Problems" section in the last post of this series.

In next blog post: Troubleshooting the Replication of Existing Data.

- Bill Long

OfficeLocalizationhttp://blogs.technet.com/OfficeLocalization/ProfileUrlRedirect.ashx


text:
Shared Leadership: Is It Time For A Change?
Download Now
Date Added: Feb 2010
Format: PDF
This paper investigates shared leadership and seeks to determine if more organizations should consider adopting a shared leadership model. Leadership affects the success and failure of every type of organization, and the complexity of today's business environment makes leadership increasingly more challenging. It is becoming more difficult for any single individual to possess all of the skills and abilities required to competently lead an organization today. A review of the literature indicates that while shared leadership has been practiced in some form for centuries, research on the subject is still in its infancy. An abundance of shared leadership studies fall in the domains of healthcare and education, two industries especially open to the concept.

subset: commoncrawl


text:
MJPEG Surveillance22.214.171.124
editor's review
2 comments
MJPEG Surveillance allows you to transform your computer into a surveillance system in order to capture images from your office or another location. The application can also notify you about the detected intruders by playing a sound alert.
In order to capture the images, the application needs to be connected to a USB camera or an IP camera. It supports multiple camera types and can record images from more video devices at the same time.
You can configure each camera by specifying the image quality and the motion sensor sensitivity in order to ignore certain environmental movements. The program can capture the frames that display a movement and insert an overlay with the current time in order to identify the images.
The motion sensor splits the image into 400 areas and calculates the light intensity in order to compare it with the previous frames. The grid can be customized to ignore a part of the received image in order to avoid false alerts.
By default, the surveillance system saves all the frames to a Motion JPEG movie which enables you to review them easily with the included MJPEG player. You can also export a certain frame as a JPG image or extract a various number of frames to a new MJPEG file.
The Player can also join two movies in order to consolidate the events from different dates or locations.
Since not all users have a player that can open MJPEG files, the application also includes a video conversion tool that changes the video output type. This utility uses the codecs installed on your computer and can create WMV, AVI or MP4 files.
During our test, MJPEG Surveillance required minimal resources during the image recording and movie conversion. The interface is rather simple and allows you to add cameras and configure settings by using the context menu.
If you need to use remote cameras as a surveillance system, MJPEG Surveillance provides the right tools for the job. Since it includes capture, playback and conversion tools you should try it before looking for more complex or costly solutions.
top FREE alternatives
top PAID alternatives


text:
Tire size?
View Single Post
Dodge Ram Forum Member
Join Date: Feb 2012
Location: Victoria, BC, Canada
Age: 34
Posts: 52
Gender: Male
Vehicle: 2012 Ram 1500
Trim Level: Laramie
Color: Black,Silver
Engine: 2009-20?? 345ci (5.7L) Hemi V8 390hp 407lb/ft
Rep Power:
If you go for wider then 12" be careful about the actual size of the tire when choosing a spacer.
For exemple my Nitto Trail Grappler size is 35X12.5R20 but on the Nitto web site they say that the actual size is 35.04 high and 13.39 wide (I didn't measure it myself but just to be sure I got myself 10mm - 3/8in Hub Centric Spacer)
For comparison Goodyear Wrangler MT/R actual size is 34.8 high and 12.5 wide and Toyo Open Country M/T actual size is 35 high and 13.0 wide.
Normaly a 12" wide tire shouldn't need a spacer but people recommend a 1/4 spacer for a 12.5" tire because they assume that it's only half an inch wider (or 1/4 inch closer inside) but since all 12.5" aren't the same you might want to make sure you know the actual tire size and how much spacer you will need!
just my 2 cents
View Public Profile
Send a private message to Kibagami
Find all posts by Kibagami


text:
Il Cuore di Dioniso Dimora D'Epoca
No prices found through our partners. Please contact the business directly or check some of our recommended alternatives.
How has this hotel rated in the past?
- Continental Breakfast
- Meeting rooms/conference facilities
- Drycleaning onsite
- Minbar in room
- Shuttle bus service
- Wireless internet connection in room (free)
Travelers also recommend:
TripAdvisor Reviews Il Cuore di Dioniso Dimora D'Epoca Marinella di Selinunte
Travel Blogs from Marinella di Selinunte
Found our limits
... with the choice to go further up and being wrong, or returning on our tracks we decided to go back. Amazing how much we had climbed, it took us quite some time going down the hill again.
We then continued route B in the heat - we are talking here around 35 degrees in the shadow, over 40 in the sun but hardly any place with shadow. We got happy when there was a cloud over the sun to give us some shadow. Strange how your habits change in ...
An easy trip they called it
... it is not what you want to have, especially not when you are biking. On the bike, you simply see the sweat evaporating from your arms.
Anyway, it was an interesting day, with a nice ending at the beach in preparation for the big trip of tomorrow! Two times a climb of approx 500 metres over 20 km each. We will see, it might be a walking day tomorrow....
Pictures will follow later - to busy to relax in the evenings now...
johan ...
Easy trip to Marsala
... and other ancient things in a large park, all poorly maintained, all panels with explanations completely empty,... But nice mosaics in the bathhouse.
The other thing in the park is the museum, where they have a boat - or small pieces of it at least - of the punic war. Nice, with lots of amphora and other elements they got out of the sea and the archeological field in the area.
Funniest part was the guy who ...
First trip - the big test
... cheese and ham, different sorts of homemade jam and of course many sweet things that they like but we typically don't take for breakfast. Also, i switched back to coffee here in sicily, that is to say expresso, lots of caffeine, almost no water and lots of sugar.
After a quick breqkfqst we left around 8.30 for our trip.
How stupid can you be to book a trip in Sicily in July with a bike. There are mountains, it is hot and ...
A sea trip
... a long queue it was a toilet break only!
All boarded the boat and the sun came out for us. Neil, Helen and I sat on the back seat and Helen and I sunbathed our white legs..... Was a lovely trip. Lorraine wasn't enjoying it as she gets sea sick and was a little worried that we had no life jackets on. We finished at San Vito Lo Capo where we had ...


text:
Thanks for taking the time to report this user.
Your participation helps keep Airbnb a safe and trusted community, and it doesn't go unnoticed!
I live in Tbilisi and work at a human rights NGO.
Elizabeth has completed online and offline ID verification.
Learn more »
Elizabeth was a great guest! She was easy to communicate with and get ahold and they left our home in great shape. We would recommend her to anyone. Would love to have them back anytime.
Thanks, Yuriy!
Brilliant guest.


text:
Experience a 19th-century English-style inn that once played host to President Franklin D. Roosevelt and save up to 45% on stays through fall.
Oct. 1 - Dec. 23
Marvel at panoramic ocean views from this luxe, 5-star Phuket resort. Members exclusively save 40% off stays through summer 2016.
Nov. 1, 2015 - July 31, 2016
Stunning fall foliage greets guests in the picturesque Smoky Mountains, where this rustic resort is offering a deal that saves nearly 50%.
Daily Oct. 1, 2015 - Nov. 28, 2015
Stay, play and dine with an overnight deal at the 4-star Marriott Gateway on the Falls that exclusively saves Travelzoo members 65% on current rates.
Select dates in Nov & Dec + other discounted dates
Save 30% off peak winter travel at this 4-Diamond resort and private island fit with Aruba's only private beach.
Jan. 3-31 & Feb. 19 - March 27
Coast to this historic B&B along the shorelines of Maine with a deal that includes an exclusive $25 dining credit, includes fall foliage weekends
Travel through January
Classic style and luxurious touches earned the Omni San Francisco a spot in TripAdvisor's top three San Francisco hotels.
Nov. 19-29; Dec. 18-30; Jan. 1-9
Savor secluded luxury at this AAA 4-Diamond resort, offering Travelzoo members exclusive savings on fall and winter stays at over half the price.
Oct. 18, 2015 - Feb. 29, 2016
Fresh from a $40 million renovation, the swanky Paramount Hotel is offering 50% savings and an upgraded room type for fall and winter travel.
Travel options into March 2016
The ultimate luxurious retreat, this property is a Travel + Leisure 500 World's Best Hotel
Nov. 16 - March 31; +$100 for Oct. 20 - Nov. 13
Stay here for a quiet location near Central Park, removed from the Times Square tourist crowds.
Travel January-February; select dates in November
Please go to your email and confirm your subscription.


text:
The best doctor you can get for your child ! Never in a hurry to leave a room, always answers all of your questions. Always giving out the best advice !
Should be on every mothers speed dial. BEST DOCTOR!!!! I wish I had a GP like him.
We've been taking our child here for two years and have been pretty happy. One of the important factors for us was that she has always returned phone calls the same ... Read more
Ignore the above review - that was probably just one isolated experience - I'm now a college student, but went to SF Day School and was a patient of Dr. Aicardi's my... Read more
A great and caring doctor
My daughter was a patient of Dr. Geertsma when she practiced in ExeterCalifornia. Dr. Geertsma is the best pediatrician we had the pleasure of seeing throughout my d... Read more
One of the best qualities of Dr. Cocalis is that he includes parents in the process and tries to explain everything to them as best as he can.
Dr. Glaser is a brilliant and excellent doctor with a big heart.
Sign up for our newsletter and get the latest health news and tips.