Sign In
Share this page on Facebook Share this page on Linkedin Share this page on Twitter Email a link to this page
  • Feb.12.2017

    How would you like to be able to edit branding files locally on your machine (not through Windows Explorer to SharePoint), make that your local path for TFS for proper source control, and have your changes immediately sync to SharePoint on premises or in the cloud for testing?  This is the story of how we achieved that, and how you can easily integrate that into your own development processes.

    I'll start by describing the end result, then our journey that got us there, and end with what you need to use this yourself.

    [Read More]
  • May.06.2015

    ​Day three at Microsoft Ignite in Chicago.  Lots of sessions, and lots of parties.  Honoured to win the Best Implementation of a Governance or Security Solution for SharePoint at the Metalogix and the SharePoint Best of Breed Awards last night for Extranet User Manager and our work at the Ontario Association of Children's​ Aid Societies.  Detail in the News Release.

    As expected, no earth shattering fundamental changes for SharePoint 2016.  Microsoft has been pretty clear that their first investments are in the cloud, and then those features come back into on premise.  Web content management has been a big focus area for us, and no announcements there.  No deprecation of features there either, which is good news.  For our WCM clients on SharePoint 2010 still, I would say it is safe to upgrade to SharePoint 2013 now, as that architecture is looking fundamentally the same in SharePoint 2016.

    Three top sessions for me so far.  Decks and videos are available on Channel 9.

    [Read More]
  • Dec.04.2012

    ​On December 4th I delivered a Webinar on Rich Media Support in SharePoint 2013.  I focused on enhancements to image and video support in the new platform, specifically:

    Image renditions
    • Site owners can define standard sizes (renditions) for images that apply across the site
    • As content authors load and use images, SharePoint automatically creates these different renditions to optimize the site visitor's experience
    • Content authors can resize and crop images right in the browser, without the need for Photoshop or image management software
    • Video is becoming more and more important for both internal and external sites
    • 2013 has a new video content type that is actually a document set
    • Drag and drop a video into SharePoint, and the video and thumbnail (automatically extracted from the first frame) are put in the document set
    • Content authors can play the video in the browser, and select a different frame for the thumbnail, or upload their own
    • Additional video formats (renditions) can be loaded into the document set for playing back on different devices
    • Windows Azure Media Services further extends this by providing cloud-based transcoding (converting to different formats) and massively scaled streaming support (think London Olympics), as well as Smooth Streaming and HTTP Live Streaming (HLS, for Apple iOS adaptive streaming) support

    Links to the presentation and video can be found below:

    Presentation - Rich Media Support in SharePoint 2013 
    Video - Rich Media Support in SharePoint 2013

  • Dec.04.2012

    On December 4th I ​delivered a Webinar on Extranets in SharePoint 2013, and also spoke to the licensing changes that will really change the game for both Extranets and public web sites. For on-premise installations, Microsoft is eliminating the For Internet Sites license requirement, bringing the licensing costs down significantly. Likewise in the cloud, Microsoft now provides up to 10,000 external user accounts for Extranets in Office 365, with no additional subscription fees.

    More details about the webinar as well as links to the presentation and video can be found below

    Presentation - Extranets in SharePoint 2013
    Video - Extranets in SharePoint 2013

  • Jun.25.2012

    ​This is a problem that has been plaguing me for years.  When you access a SharePoint site with a fully qualified domain name (FQDN) such as, you get repeatedly prompted for credentials.  A FQDN has periods in the name, as in the URL above.  Since we do a lot of work with Extranets, we typically use SSL (secure https sites) and FQDNs on our sites, since they will be accessed externally as well as internally.

    The first fix is in the browser itself.  In order to have the browser pass your logged on credentials to the server, it needs to be in the Intranet zone.  FQDNs are automatically considered to be Internet sites by the browser.  To change this do the following:

    1. From the browser Tools menu, select Internet Options
    2.  Go to the Security tab
    3. Select Local intranet
    4. Click Sites
    5. Click Advanced
    6. Add the FQDN to the Websites list

    The above was the easy part, and applies to the browser.  However if your applications use WebDav, you still get prompted for credentials, even if you are already logged in with the correct credentials.  This will cause you grief with all the Office applications (Word, Excel, PowerPoint, InfoPath), opening a library in Explorer (so you can move files around easily), and many other situations.

    Our Systems Administrator and resident guru Wes found the appropriate changes needed to support this.  Basically you'll need to add a registry entry to each client computer, after which you should not be repeatedly prompted for credentials.

    1. From the Start-Run menu run RegEdit
    2. Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WebClient\Parameters path
    3. Right-click Parameters and create a New Multi-String Value
    4. Name it AuthForwardServerList
    5. Enter one or more FQDNs that you want the rule to apply to

    Note that you can also enter wildcards such as *, for both the Intranet zone browser settings and the WebDav support.

    Of course the ideal way to do both of these is by adding a Group Policy Preferences to your AD (which is what Wes did).

  • Dec.18.2011

    ​It's been out since 2009, but I haven't spent the time until now to play around with Microsoft's ULS Viewer.  For those of you that have dug around in the ULS log files SharePoint puts in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS, you'll really appreciate this tool.  Basically it will read in those log files and parse them, presenting them ina nice tabular format.  Once you have them in that format, the tool makes it easy to sort, filter, and analyze them.


    While not officially supported by Microsoft, it is available on their site at  There is no install, it is just an executable that you run.  You don't need to run it from the server if you have a network share to the ULS logs.

    There's lots you can do with the tool.  One of my favourite features is the ability to filter, particularly by correclation ID.  When you get the dreaded "Unkown error" with a correlation ID, it is easy to track those down and analyze them.  You simply do the following:

    1. Launch the ULS Viewer
    2. File - Open From - ULS
    3. Enter the path for the ULS logs of they are remote
    4. Edit - Modify Filter
    5. Choose Correlation and enter the ID to filter by

    The other nice thing is the tool is real time, and will continue to bring in new entries live from the log files.  Of course there are lots more features that are easy to explore through.

  • Oct.29.2009

    You may have often seen this popup come up on a public facing site that you are browsing too.  It is because the SharePoint Server is trying to load the control, and it is not in the list of pre-approved controls in IE7.  The control is used to display presence information in a SharePoint site.  This shows up as the small circle presence indicator tied into Windows Live Messenger.

    I was getting this popup on this blog site, so I thought I would share how we deal with it.  Since this is on a server that only serves public-facing content, I decided to follow the server based solution outlined below.

    This was adapted from a Microsoft SharePoint Blog article by Michael Gannotti and makes reference to Microsoft Support KB article 931509:

    [Read More]
  • Oct.28.2009

    Everyone remember getting frustrated by SharePoint’s “An unexpected error has occurred” that gets displayed by default when something goes wrong in SharePoint?  Well it still happens in SP2010, but the good news is the same fix takes care of it.

    For those of you that haven’t come across the fix for this, it requires an edit to the web.config for the web application you are getting the error on.  Typically we do this on development and QA servers.  If you’re doing it in a farm, remember that you need to do the change to all front-end servers, or guarantee that you are hitting a specific web front-end.

    The web.config is found in the home directory for the web application.  This is typically c:\inetpub\wwwroot\wss\VirtualDirectories and then the folder for your web application.  To see the full errors make the following two changes.  Opening the web.config in Notepad and searching for the tags (there is only one for each) is the easiest way to do this.

    • Set: CustomErrors="Off"
    • Set: CallStack="true"

    Once you’ve done this change, you’ll see the full .NET error details and call stack for the error that occurred.

Copyright ©2013 Peter Carson