Using PowerPoint to create SharePoint Themes

Something interesting I learned recently about SharePoint 2010 was the fact that you can use powerpoint themes as sharepoint themes.


1. Open PowerPoint (I’m using PowerPoint 2007)
2.  Under the “Design” tab, choose a theme and specify your preferred color schema

3. Save the file in “Office Theme” (*.thmx) format
4. Navigate to the site settings of your SharePoint site collection and go to the Themes gallery
5. Click “Upload Document” from the ribbon and upload the theme file that you previously saved – you should now see your theme within the Theme gallery
6.  Go back to site settings and click “Site theme” under the “Look and Feel” category to change the site theme
7. You should now be able to select the theme you uploaded and even further customize the colors/fonts.

8. Once you apply your theme, you should see the changes!



SPC2011: How the SharePoint Dev Team Troubleshoots Performance and Reliability

Notes from the SharePoint Conference 2011
Session:  How the SharePoint Dev Team Troubleshoots Performance and Reliability


  • captures performance
  • have one outer monitored scope to identify code
  • wrap calls to external code in monitored scope
  • specify SQL & SPRequestCounter
  • do not use in a for loop (due to resources)

Developer Dashboard

  • Can include SPMonitored scopes (unless its for sandbox)
  • Includes header and trace information

Caveats to the Developer Dashboard

  • available to all site administrators
  • trace logs may contain sensitive information
  • Only for aspx – not with ajax, scripts, office rich clients requests

Usage database

  • IIS logs
  • timer job executions
  • event logs
  • SQL queries (blocking, deadlock)

Caveats to Usage database

  • 7 day retention default (can change)
  • failed requests wont appear
  • SQL is costly for usage
  • only works for single farm

SPDiagnostic Studio 2010

  • troubleshoot visually

Caveats to SPDiagnostic Studio 2010

  • built for internal
  • not ideal for monitoring
  • good for bug finding/exploration

SPC2011: Best Practices from the Field: Managing Corporate Metadata and Taxonomies

Notes from the SharePoint Conference 2011
Session:  Best Practices from the Field: Managing Corporate Metadata and Taxonomies
  • Terms – max: 7 levels deep
  • managed metadata can be imported
  • Content Type Syndication (this is new) – federated service for reusing content types across the enterprise
  • Design Best Practices

– define purpose of taxonomy
– avoid deeply nested taxonomies: start with 2-3
– do not underestimate the time for prep

  •  Technical

– Translate business requirements to sharepoint capabilities
– understand limits (max level = 7, max term sets in term store = 100, max terms in termset = 30,000, max terms in term store = 1,000,000)
– multilingual consideration

  • Business Best Practices

– Identify ownership
– Keep it simple
– factor ongoing maintenance
– identify change control protocol
– define governance

  • Challenges: Life science area

– complex process to ensure traceability for FDA audit
– patent expiration
– drug discovery
– account for regulatory compliance and record retention

SPC2011: Best Practices for User Profiles

Notes from the SharePoint Conference 2011
Session: Best Practices for User Profiles

1. Don’t  enable personal sites just for search

2. Host mysites on its own web application

3. Don’t create personal sites ahead of time

4. Encourage users to observe and use existing tags -> consistency
*FAST search does not index social tags

5. Enable metadata keywords
– list settings > metadata publishing
– follow tags as interest in MySite
– get all info about tag in MySite newsfeed
– tags don’t have permissions but search is security trimmed so users wont see anything they aren’t supposed to

6. Ratings are overrated. Use with caution

7. Enable Activity feed timer job (may be disabled by default)
– default scheduling is hourly – may want to change according to your needs

8. Take time to plan
– what are the business goals?
– which features do you want enabled?
– what permissions should users have?
– what profile properties do you need? (talk to HR/AD group)
– create governance around tagging, ratings, updates, and privacy

9. The AD group may lie to you

10. Configure write back to AD to show picture of users in outlook and lync

12. Use dedicated account for synchronization
Each connection needs to be configured separately – AD, BCS, LDAP

13. Remove disabled users
userAccountControl = 2 filter

Check out:
– Spence Harbor’s blog for more details
– White paper on technet about planning for user profiles

SPC2011: Clearing away the clouds: what’s hype and what’s real about cloud adoption

Notes from the SharePoint Conference 2011
Session:  Clearing away the clouds: what’s hype and what’s real about cloud adoption


  • capability on demand
  • reduce cost


  • Most companies start by moving their email to the cloud
  • Also consider try before buying

Challenge: end users overlook IT and engage cloud services

Getting Ready

  • Engage compliance/legal groups
  • Determine why to move to the cloud (ie. flexibility, cost)
  • Determine where to start (ie. email, storage, business applications)
  • Find areas of least risk
  • Look for vendors
  • Create criteria for moving off the pilot
  • Create criteria for success

Why to consider waiting

  • Complex customizations
  • Cost saving is the only driver
  • Custom applications/integration
  • No buy-in from upper management

Talking to the boss

  • Compare cloud to current
  • Don’t minimize risk
  • Describe exit plan
  • Make sure peer and other leaders are behind it
  • Research what other organizations are doing

Passed 70-576: PRO Designing and Developing Microsoft SharePoint 2010 Applications

Today I passed the 70-576: PRO Designing and Developing Microsoft SharePoint 2010 Applications!

This resource definitely helped me study in the short amount of time that I had:

Multiple Web Part Connections in SharePoint 2010

Unlike SharePoint 2007, SharePoint 2010 allows you to do more than one web part connection to a list view web part out of the box! That also means you can use more than one filter web part on a list view web part!

Here is a screen shot that exemplifies using multiple web part connections:


In this screenshot, a user can filter by the project AND by the project phase to find related tasks. Sure you can filter the “Related Project” and “Project Phase” fields on the Tasks list view web part separately by clicking on each of the field titles and filtering them but using web part connections makes it easier for the user to switch between projects and project phases. Also, if the user is new to SharePoint, it’s not immediately obvious that you can filter by clicking on the field title, whereas clicking on a project to filter all tasks related to the project is more intuitive.

You can even add to this example by using filter web parts – ie. You can use a current user filter web part to show only the tasks assigned to you.

Being able to have multiple web part connections to a list view web part opens the door to all sorts of possibilities for slicing and dicing data within a list!