In this video I demonstrate how to build a form using InfoPath Designer 2010 and publish it to a SharePoint Online environment. Once the form is published I build a very basic workflow using SharePoint Designer.

This video demonstrates the following concepts:

• Creating an enterprise forms library and a completed forms submission library
• Using InfoPath Designer 2010 to create a web form
• Publishing a form to SharePoint Online as a content type
• Promoting fields from the form to SharePoint document library metadata columns
• Associating a forms content type with a submission library
• Using SharePoint Designer to create a simple workflow

The video is 31 minutes long.

Recently I wrote a short blog post about using SQL Server 2012 with SharePoint 2010 where I pointed out some resources to help users get started with SQL 2012 and SharePoint.  From that blog post I received a question about configuring SharePoint 2010 Access Services with SQL 2012 Reporting Services.  Previously I wrote an article called Configuring Access Services with SharePoint 2010 that outlined how to get SQL Server Reporting Services from SQL Server 2008 R2 to work with SharePoint 2010 Access Services. Getting SQL Server Reporting Services (SSRS) from SQL Server 2012 working with SharePoint 2010 Access Services is slightly different.

A major change in SSRS 2012 is that it is installed as a SharePoint Service.  Once you have installed SSRS in your SharePoint 2010 farm you will need to make a few small updates in order for it to work with SharePoint 2010 Access Services.

The first update is to enable an ADS extension.  In previous versions of SSRS you would modify the rsreportserver.config file and add an XML node.  In SSRS 2012 you run the following PowerShell commands from the SharePoint 2010 Management Shell.  These commands must be run on the server in your SharePoint farm that is running the SQL Reporting Services SharePoint service.  Depending on your server configuration, you may be required to right click on the SharePoint 2010 Management Shell shortcut and choose “Run As Administrator”.

$apps = Get-SPRSServiceApplication
foreach ($app in $apps)
{
New-SPRSExtension -identity $app -ExtensionType “Data” -name “ADS” –TypeName      “Microsoft.Office.Access.Reports.DataProcessing.AdsConnection, Microsoft.Office.Access.Server.DataServer, Version=14.0.0.0, Culture=Neutral, PublicKeyToken=71e9bce111e9429c”
}

If you do not run the PowerShell script you will see an error similar to the one below when trying to view a Access Services 2010 report:

“An error has occurred during report processing. (rsProcessingAborted) An attempt has been made to use a data extension ‘ADS’ that is either not registered for this report server or is not supported in this edition of Reporting Services. (rsDataExtensionNotFound)”

After the ADS extension has been enabled you will need to modify the rssrvpolicy.config file on the SharePoint Server where the SSRS service is installed.  You can find the policy file located in the 14 hive:   ..14/WebServices/Reporting directory.   The specific modifications can be found towards the bottom of this TechNet article.  Please note that the rssrvpolicy.config file is in a different location for SQL Server 2010 Reporting Services.

If you do not make the proper changes to the rssrvpolicy.config file you will receive a security error when trying to run reports from Access Services 2010.

Once you have made all of the changes listed above your Access Services reports should work as expected.

Microsoft Press has made 10 books available for free in electronic format.  These books cover topics such as SQL Server 2012, SQL Server 2008 R2, Office 365 and Office 2010.  Download your copy while they are still available!  Many of the free books are offered in PDF, Mobi (Kindle) and epub formats.  Click on the book images below to be taken to download options.

One of the benefits of using cloud based services is that you are kept in an evergreen environment. As a result system requirements will be updated and changed to support the enhancements made to the services.

Recently the Office 365 System Requirements document was updated to include new requirements and end of support dates for specific operating systems, client software and browsers.

Two items stand out to me as being very important.  The first is that as of June 1st users will need SP1 installed for Office 2010.  The second item is that after October 1st Office 365 will not support Internet Explorer 7.

Below is a summary of the changes you need to be aware of.  These dates are related to Office 365 support only.

End of Support for Operating Systems
January 1, 2013 – Windows Server 2003
January 1, 2014 – Windows XP
January 1, 2014 – Windows Vista

Office Client Changes
As of June 1, 2012 Office 2010 will require SP1
Outlook 2003 can be used for email using POP and IMAP only

End of Support for Office Clients
April 9, 2013 – Office 2008 for Mac
April 9, 2013 – Entourage 2008 Web Services Edition
April 8, 2014 – Outlook 2003

Browser Requirement Changes
Support now covers latest Firefox “Release” version only.
Support now covers latest Chrome “Stable” version only.

End of Support for Browsers
October 1, 2012 – Internet Explorer 7
October 1, 2012 – Safari 4

On May 3rd Microsoft announced that Office 365 was granted the Authority to Operate under the Federal Information Security Management Act (FISMA) by the Broadcasting Board of Governors.  Julia White, Senior Director in the Microsoft Office Division posted the following on the Office 365 blog.

FISMA is important to our customers because it creates a process for federal agencies to certify and accredit the security of their information management systems.  IT solutions with FISMA certification and accreditation have federal agency approval for their use in line with the level of security established by that agency.

We take our responsibility to protect customer data very seriously.  While we”re pleased to have been granted FISMA ATO, Office 365 already meets the industry”s most rigorous global security and privacy standards.

Office 365 is the first and only major cloud based productivity service to sign EU Model Clauses with all customers.  In addition, we added the Data Processing Agreement (DPA) to the EU Model Clauses to address additional requirements from the EU member states.  Office 365 also signs the Business Associate Agreement (BAA) to meet the security requirements of the US Health Insurance Portability and Accountability Act (HIPAA).  Importantly, Office 365 signs the HIPAA-BAA, DPA and EU Model clauses with all customers regardless of size.  Along with EU Model Clauses and HIPAA, Office 365 is ISO 27001 certified.

We understand people have high expectations of any service provider and an interest in understanding where their data resides, who can access it and what we do with it. To that end, we created the Office 365 Trust Center to enable customers to learn more.

With FISMA, it becomes even easier for governments to choose Office 365 and join the ranks of the USDA, the first federal agency to deploy cloud services, the States of California, Minnesota and New York; the cities of San Francisco, Newark, Plano and many others.  The move to Office 365 is afoot in government, and the savings and benefits to citizens are considerable.  Today”s news should further hasten that transition.

References:

FISMA becomes latest security certification for Office 365
ZD Net: Microsoft: Office 365 for enterprises now FISMA-certified