Sign In
Share this page on Facebook Share this page on Linkedin Share this page on Twitter Email a link to this page
  • 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).

  • Feb.15.2012

    ​SharePoint has become mission critical, complex, and wide-ranging in most enterprises. How do we apply the best practices of ALM in this environment? In this session I cover the following:

    • System Center Virtual Machine Manager and AutoSPInstall to quickly provision dev, test, and production farms by leveraging HyperV
    • Visual Studio and Team Foundation Server to manage an Agile Scrum team
    • Build servers and automated testing to create a continuous integration environment
    • Moving code and content in both directions through a dev/test/prod lifecycle
    • How to capture as much of the SharePoint configuration in components that can be deployed, rather than manual steps

    The goal is to build a change management process that merges the content authored in production with the code written in development effectively. 

    ​Key Learnings

    • How to create an environment to support your SharePoint Development and QA teams
    • Agile and continuous integration in a SharePoint environment
    • The value of automated testing
    • Demonstration
    • Provisioning of test environments through SCVMM
    • Live automated build and test scenario

    The Application Lifecycle Management for SharePoint in the Enterprise deck is available for download. 




    Details on session dates can be found at


  • Apr.16.2011

    So you've got a public-facing web site built on SharePoint 2010, and you'd like to use the surveys to poll anonymous users.  How do you go about doing that?  Well there's a number of different things you need to do.

    The first step of course is to create your survey.  Go ahead and create a new survey (typically from the View All Site Content page).  Setup your questions and defaults, and make sure everything looks good from that perspective.

    You would think that your next step is to setup permission.  Actually it isn't.  Before you can do that, you need to turn off the ViewFormPagesLockDown hidden feature that is turned on by default on publishing sites.  Now don't worry, we're not going to leave it off, as that opens a big security hole on your publishing sites.  We just need to turn it off temporarily.  To do that, run the following command on your farm.

    [Read More]
  • Dec.23.2010

    I've been meaning to post about this for some time now, so I decided there is no time like the present.  All of the tips below apply to both MOSS 2007 and SharePoint 2010.

    When you are setting up a SharePoint site, performance is often an overlooked item.  It is particularly important for public web sites, but Intranet sites an collaborative sites benefit from this as well.  We'll use our own Envision IT public web site ( as the example.  The items that we'll cover are:


    • Setting up the site collection object cache to improve the content query web part performance.  These web parts are used extensively in the sites
    • Enabling and configuring the cache profiles (which are off by default)
    • Turning on the disk-based BLOB cache for binary objects (images, PDFs, etc.)
    • Setting up a wake-up script to run nightly to hit the sites and cause the caches to get initialized and populated, as well as ASP.NET started up
    [Read More]
  • Jan.25.2010

    I've been writing this blog for a few months now, so I figured it was time to explain a bit about how the blog site is built.

    Being a Microsoft Gold Partner focused on SharePoint, I felt we should use SharePoint for our blog sites.  Of course I quickly ran into some limitations in doing that, particularly in a public facing blog site.  Things like anonymous commenting (with anti-spam protection) and friendly URLs were important to me.

    It didn't take long to dig into the Community Kit for SharePoint: Enhanced Blog Edition to help with this.  This is a CodePlex project that can be found at

    Called CKS:EBE for short, it solves a lot of my problems.  For a good blog posting on what it is, I would recommend having a look at

    Of course not everything worked perfectly.  At first I didn't have the CAPTCHAs running (those funny distorted letters and numbers you have to type in so a site knows you are a real person).  It didn't take too long for the blog spammers to find me, and start over-running the site with automated spam comments.

    I tried enabling the CAPTCHA, but it didn't work for me.  I eventually found, which explains that the CAPTCHA only works on certain themes like Wildlife.  Of course the Default I was using it didn't.  I followed the thread in the post and used SharePoint Designer to update my Default theme, and the CAPTCHA fields started showing up.  However it still didn't work in the root site (which is what I am using), so as of today I still don't have them working.  No spam comments coming in anymore, but no comments at all either.  I'll have to keep plugging at that and keep you updated.

  • Jan.25.2010

    By default when accessing a SharePoint 2010 site over https, you get the following dialog displayed warning about mixed content (the exact dialog depends on your version of IE and Windows).

    This is noted in a TechNet posting at:

    The issue is that the following script tag is being inserted by SharePoint:

    [Read More]
Copyright ©2013 Peter Carson