Skip to main content

Notes from Sydney SPUG session

Took some notes today @ Sydney #SPUG session "SharePoint 2013 -Technical Overview" facilitated by Aaron Saikovski from Microsoft:

Took some notes today @ Sydney #SPUG session "SharePoint 2013 -Technical Overview" facilitated by Aaron Saikovski from Microsoft:

1. Search is big in SharePoint 2013 + Exchange 2013

2. Managing risks

  • Central policies 
  • Audit policies 
  • RMS encryption 
  • Info protection and prevention policies 
  • Secure configuration for published environments 
  • Protect and preserve 

3. Manage costs

  • Adaptive cross-premise environments with public and private clouds 
  • Comprehensive I/O performance across disk & data 
  • Storage optimization with Shredded Storage 
  • Application aware routing and management ñ max availability and protects from attack 
  • Unprecedented scale through Distributed Cache
  • Social and security tokens ñ claims. 
  • Rich navigation and performance reduction through Minimal Download. Reduce bandwidth. 

4. Manage time

  • Resilient and simple automation with PowerShell 3.0 
  • Option to upgrade on a site collection level. 

5. Upgrade

  • In-Place upgrade has gone. 
  • Only database attach upgrade. 

6. Service Applications

  • Services can be individually consumed by any Web Application 
  • SharePoint 2010 farms can consume: Search, User Profiles, Secure Store, BCS from 2013. 


  • App Management ñ install SP apps from Office Marketplace or the App Catalog ñ user code service?
  • SharePoint Translation Services ñ simple language translations of Word, PPT, XLIFF files into HTML
  • Work Management Service ñ Task aggregation across systems like SharePoint, Exchange and Project 
  • Azure Workflow Server ñ provides externalized host using REST and OAuth to run workflows 
  • Office Web Apps ñ no longer a service application. Office Web Apps are decoupled from SharePoint and require separate server infrastructure. 
  • Web Analytics ñ no longer a service application. Now part of search role. 

7. Search

  • Has been combined into a single enterprise search platform (FAST + SP Search = Enterprise Search) 
  • Deeply integrated into the platform. Social, eDiscovery, Analytics etc. 
  • New topologies, components and features to consider 
  • Scaling and sizing guidance is currently in progress "Continuous crawling" of SharePoint sources 
  • Easier to manage and failover 
  • Keep an eye on TechNet for Upgrade guidance 


  • No more Search Server Express 
  • SkyDrive Pro is an evolution of SharePoint Workspace. 
  • Users must have a My Site created in order to use all social features. 
  • Document preview from Search Results. Needs Office Web Apps. 
  • You can use any Web authoring tool to customize SharePoint pages 

Key Takeaways

  • Plan for Claims Authentication ñ Default 
  • Design for Cloud (Private/O365/Azure/Hybrid) 
  • There are MANY changes 
  • Don't be afraid to scale 
  • Refer to TechNet for guidance 
  • SharePoint 2013 is still a beta product!!


Popular posts from this blog

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server.

According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition.
The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you wou…

SharePoint 2010 Search Issue - FQDN Crawl

I have recently set up a standalone SharePoint 2010 environment.

The Web application was created with host header and the site collection is accessible from the client machines, but not internally. That was because of using FQDN to access the Web site.

The error when I tried to access site internally was similar to the one described here:

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version

And the search returned the following error in the Event Log:

"The start address cannot be crawled.

Context: Application 'Search_Service_Application', Catalog 'Portal_Content'

Details: This item could not be crawled because the crawler could not connect to the repository."

One of the suggestions was to disable the loopback check, but that would compromise the Web server.

So what I have done was:

1. Added a binding to my IIS Web site for a different port. Let's say my Web server name is win-v7m…

SharePoint 2013 - Setting Up External Content Type

There were earlier posts where we discussed External Content Types setup for SharePoint 2010:

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

External Content Types - Reload - Setting up for SQL Server database using SQL Server authentication - SharePoint 2010 Server

This one is about creating connection to the custom SQL Server database (External System) in SharePoint 2013.

1. Create Secure Store Service Target Application

1.1. Go to Central Administration -> Manage Service Applications -> Secure Store Service Application. Click "Generate New Key" if required:

1.2. Provide Pass Phrase:

1.3. Create "New" to create new Target Application:

1.4. Provide the name and other parameters and click "Next":

Note: It's good idea to specify "Group" for Target Application Type. In that case you would be able to manage access to the external data using Active Directory groups rather …