Author Archives: admin

SharePoint 2013 RoadShow – Pittsburgh, PA

I am Attending the Pittsburgh SharePoint 2013 Roadshow.  Topics include:

  • Building Extranets & Hybrid SharePoint deployments for the enterprise and how do you plan to sell it internally?  What are the project drivers? 
  • The Art of SharePoint – Why projects fail – that’s what we plan on exploring this is interactive session.  
  • Governance – is your SharePoint environment a mess, unruly, proliferation of uncontrolled sites and content, you’ll walk away with some great ideas and learn how to get your environment ready for upgrade.
  • Workflow an interactive walk through on how to take advantage of some very simple concepts to save you a whole bunch of time.  

Notes from Presentations and points of interest?

  1. SharePoint 2013 Workflows or workflow engine includes a new server component for managing and processing workflows. Initial conversations around this topic included running this component on its own server.
  2. Free (30-day trials) SharePoint 2013 on sharepoint.com.  There are also additional free-like resources available for MSDN users.
  3. Building Workflows with Visual Studio and its drag & drop tools
  4. Extranets and Hybrid SharePoint Deployments -
    1. Group Discussions on Usage – Client Sites, Client Project Sites, Collaborative BI Solution, Document Transfer (FTP) with Clients and Suppliers, Submission of Materials Request, Data Dashboards (Items on Hand, Forecasts, production amounts), No-Access-To-VPN Workaround, E-mail alternative, Co-author documents, Reduce customer service interactions.
    2. SharePoint 2013 uses claims authentication, SAML 1.1 (AD FS) 2.0.
    3. HyBrid Architecture – Bi-Directional or 1- way
      1. Bi-Directional – Search and BCS can interact with both internal and external farms. This architecture requires the use of a reverse proxy.  The primary goal is that it allows the internal users to work seamlessly between both internal and external farms.
  5. Authoring in Place vs. Publishing – where will you create content?  Marketing Material, brochures, etc.. can utilized a publishing approval workflow.
  6. Cross-Site Publishing – can create content in one site collection and publish to another collection. Catalogs now use HTML and CSS.  Performance improvements are available, because this features runs off the Search Index.
  7. Goal & Success Factors – “EMPOWER YOUR END-USERS” – However – define security, retention policy. Create attractive design – it is a reflection of your company.  Ensure adequate performance.  Content must be current! Content must be relevant and not overwhelming.  Easy to Use!
  8. Branding – SP2013 has enhanced Theme Features. “Composed Themes”, allows an end-user to apply some customizations to the branding, but with keeping with an overall – global theme.  Also can switch the master page through “Device Channels” – iPad, Laptop, PC, phone, etc….
  9. Single Source – One File & One Truth -
  10. SharePoint 2013 extranet licensing – there is a new licensing structure in place, which can make a 2013 extranet less expensive.
  11. PM Questions
    1. What are you trying to achieve?
    2. How will we know when we’re done?
    3. Can you quantify your spending on a SharePoint Project?  How expensive will it be, to go without?
  12. Information Management – how to handle content, finding policies.
  13. Governance & Planning for Governance
    1. Governance uses people, process, technology, and policies to define a service, resolve ambiguity, and mitigate conflict within an organization.
    2. People – roles and responsibilities
    3. Process – how to accomplish common tasks such as creating new site or requesting new business requirements
    4. Technology – leveraging features and tools to enforce policies through technology
    5. Policy – collection of principles – what site owners, designers, developers should/shouldn’t do.
    6. Mistakes: not defining policies on how to use SharePoint
    7. Mistakes: empowering users without appropriate training and guidance
    8. Mistakes: Letting users SharePoint like an enterprise application
    9. Mistakes: not treating information like an enterprise asset
    10. Mistakes: not planning for scale and/or growth
    11. Establish clear decision making authority and escalation procedures
    12. Ensure the solution strategy is aligned with business objectives
    13. ensure that content is retained in compliance with record retention guidelines
    14. ensure that site designers understand best practices
    15. 5 Pillars of Governance Activity Mapping (Slide)
    16. What are the key components of a “Search Center of Excellence”?

SharePoint 2010 – Cant’ create lists or activate Enterprise features after content DB upgrade

After upgrading a 2007 Content DB, I ran into a number of strange issues. The most troublesome included the inability to create new lists (the silverlight web part was empty), and when activating collection level features for SharePoint 2010 Enterprise I would get an error about the list being deleted by another user….

To resolve these issues, I had to delete the “relationships” list, delete the existing “Pages” library, and then follow this blog to create a “solutions” list:

http://raymondlittle.wordpress.com/2011/09/07/no-list-of-site-templates-in-silverlight-create-form/

No list or site templates available in Silverlight create form

After a recent upgrade from SharePoint 2007 to SharePoint Server 2010 the client noticed when a new site was created it used the default SharePoint 2010 look and feel. This wasn’t an issue until they tried to create a list in this site when they found the Silverlight popup box was displayed but the available list templates was empty and instead the in progress icon was displayed.

I spent a considerable amount of time looking for any additional details in the event viewer and the ULS logs but there was no details on why this was happening. I suddenly remember I had a similar issue withsetting the theme in a new SharePoint site after the upgrade. The error in that situation was the theme gallery hadn’t been properly created so I check and there was no solution gallery at the root of the site.

I then used the same solution as with the theme gallery error. I when to the root of the site and went to create a new list. In the create screen I then changed the URL and removed the feature section of the URL and changed the template ID, see below.

URL to create a custom list
http://sitename/_layouts/new.aspx?FeatureId={00bfea71-de22-43b2-a848-c05709900100}&ListTemplate=100

URL to create a solution gallery list
http://sitename/_layouts/new.aspx?ListTemplate=121

I set the name to be solutions and click create. This created a new solutions gallery under the catalogs section of the site. When I went back to my new SharePoint 2010 site and tried to create an new list I was presented with the available list templates.

SharePoint Migration 2007 (MOSS) to SharePoint 2010 (SP2010)

How To migrate a list: http://community.bamboosolutions.com/blogs/sharepoint-2010/archive/2010/11/17/sharepoint-2010-cookbook-migrate-a-single-list-from-sp-2007-to-sp-2010.aspx

Powershell Script for listing Site Permissions: http://lovedjohnysmith.wordpress.com/2011/02/03/using-powershell-list-sharepoint-site-users-roles-groups-on-all-sites/

Clean Up Document Versions: http://lovedjohnysmith.wordpress.com/2012/08/13/cleanup-document-versioning-in-sharepoint-2007/

25 Things to do before you migrate:http://www.sharepointdiary.com/2012/09/25-things-to-document-before-you-start.html

Step by step Migration: http://www.sharepointdiary.com/2011/09/migrate-from-moss-2007-to-sharepoint.html

List of SP Utilities: http://www.sharepointdiary.com/2010/01/my-favorite-sharepoint-utilities.html

In SP2010 how to work iwth users and groups via PowerShell: http://sharepointnadeem.blogspot.com/2012/02/using-powershell-to-work-with.html

PowerShell Script to list all Groups in Site:

[System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”)

$site = New-Object Microsoft.SharePoint.SPSite(“http://yourservername/sites/yoursitecollection “)

$groups = $site.RootWeb.sitegroups

foreach ($grp in $groups) {“Group: ” + $grp.name; foreach ($user in $grp.users) {“  User: ” + $user.name} }

$site.Dispose()