SharePoint 2010

Something New

Posted by Jim on September 16, 2017
O365, Office 365, SharePoint 2010, SharePoint 2013, SharePoint 2016 / Comments Off on Something New

SOMETHING NEW ….: SharePoint Broken Link Manager

Something new that hit the market a year or so ago is this new tool for supporting broken links . I mean who hasn’t got the call from the Vice Presidents office about links that don’t work? Why does this keep happening?

Well beyond durable links of 2016 there is a real need to have a tool to keep these links working and viable for the system.Broken Link Manager for SharePoint and Office 365.

I honestly think this toolkit is a really great way to support broken links and it’s available in all version. The product will build a report on all links found in your SharePoint Sites, and provide ability to auto-correct these links from within the tool. Perfect for after moving a site, list or library and after a SharePoint migration.

If you have broken links in SharePoint on-premise or SharePoint Online and need to ‘automatically’ convert them to use Document IDs or valid links, then you can use this tool to do just that.

Here is a sample report that can be generated by this tool to help manage and oversee broken links by site over time:

Who loves SharePoint!

Can BindTuning Benefit Your Deployment:

Posted by Jim on September 07, 2017
Azure, O365, Office 365, SharePoint 2010, SharePoint 2016 / 1 Comment

Yes …yes …yes …Lets just cut to the chase. If you are a consultant, or a system integrator delivering robust SharePoint solutions, how do you seal the deal? Bind Tuning …

Just imagine that next week you are going onsite to do the final architectural and design pitch. You’ve spent the past weeks working on your proposal. You plan to show them the SharePoint test environment you’ve built, which includes sample sites, taxonomies.  Still something isn’t quite right…

You’re not really a design expert and you are using all the same boring out-of-the-box SharePoint branding. In fact, your demo is just like everyone else’s. Problem is, you just don’t have the 80 hours it takes to create a sharp custom theme or incorporate the company’s color scheme along with a modern-look design.

Then you need this tool …

BindTuning is a multi-platform themes marketplace that provides all the tools you need to achieve a custom branding solution for SharePoint in minutes.

If you are building your solution on SharePoint on-premises, SharePoint in Azure, Office 365, 2010,2013, 2016 versions or in’s dedicated, private cloud, BindTuning has a branding solution that fits.

For creating a custom branding solution with BindTuning is easy that even a child can do it. BindTuning’s unique Magic Tool will amaze you! If you have a logo or if you’re trying to match an existing website, use the Magic Tool to quickly create a color scheme to match. It doesn’t get any easier.

The templates are fully responsive, supporting mobile devices out-of-the-box, and the final package includes all the branding resources you need. From master pages, page layouts, to css and JavaScript, all is included.

A current project with an Atlanta manufacturing company proved to be much more than promised. We even got custom support for no additional cost. Amazing ………. Support and help was also impressive.

I totally support and recommend the template and custom WebParts.

You will not be disappointed. If I had only had this for 2000, 2003, 2007 🙁




Using New Branding on WSS site

Posted by Jim on June 18, 2015
SharePoint 2010, SharePoint 2013 / Comments Off on Using New Branding on WSS site

Foundation site’s can be very challenging to build new template skins for. I diffidently encourage the use of third party templates to get traction and produce good low budget designs. Here is an example of one I did recently. The actual effort took less than 1 days.



How to Setup SSRS in SharePoint Integrated Mode

Posted by Jim on June 10, 2013
SharePoint 2010 / Comments Off on How to Setup SSRS in SharePoint Integrated Mode

After I installation and configuration of my new farm I realized that I did not install SQL Server Reporting Services in SharePoint mode or in native mode fro 2010 ….. GRrrrrrrrrr ate!

I was told that his a must on a standard install ….. but Luckily, that’s an easy thing to fix. I went to add features to my existing SQL installation. In the feature selection screen I chose install Reporting Services.

When I got to the Reporting Services configuration screen the only option available was, “Install, but do not configure the report server.” But, I did not panic. That did not mean I wouldn’t be able to configure the SSRS to be in a SharePoint Integrated mode.

I’ve decided to write a short guide to explain how to configure SSRS to be in a SharePoint Integrated mode.

1. After the SSRS installation process finishes on your SQL Server click on Start -> Microsoft SQL Server 2008 R2 -> Configuration Tools -> Reporting Services Configuration Manager.

2. Choose the Server Name and Reporting Services instance and click on Connect.

3. The following screen is important because it shows us the status of your SSRS server. When you finish your configuration process you can go back to this screen and see the Report Server mode will be set to a SharePoint Integrated mode.

4. Navigate to the Database tab and click on Change Database.

5. Choose to create a new report server database and click on Next.

6. Perform a connection test and if it succeeded continue and click on next.

7. Choose the SharePoint integrated mode and click on next.

8. Choose authentication type and your service credentials. Click on Next.

9. Verify the information in the summary screen and if everything seems fine click on Next.

10. Navigate to the Web Service URL tab and after configuring the Web Service Site information click on Apply.

If you haven’t created a site in SharePoint for SSRS yet, this is the time to create it.

11. Navigate to the SharePoint 2010 Central Administration and click on General Application Settings.

12. Click on Reporting Services Integration. 

13. In the Report Server Web Service URL provide the URL we have created in section 10. Choose an authentication mode and User credentials. Choose whether to activate the feature on all existing site collections or in specified site collection. Click on OK.

Once the process finishes you will get the following screen:

14. Navigate back to the General Application Settings screen choose the Add a Report Server to the Integration option.

15. Provide the Server name and choose an instance.

16. Provide the SSRS Service account credentials and click on OK.

Congratulations! You have installed SSRS and can start using SharePoint’s features and enhancements for Reporting Services!

Sharepoint Farms

Posted by Jim on February 23, 2012
SharePoint, SharePoint 2010 / Comments Off on Sharepoint Farms
Why a multi-farms?
SharePoint farm is fundamentally a collection of SharePoint role servers that provide for the base infrastructure required to house SharePoint sites and provide for other services, such as enterprise search. The farm level is the highest level of SharePoint architecture, providing a distinct operational boundary for a SharePoint environment. Each farm in an environment is a self-encompassing unit made up of one or more servers, such as web role servers, service application role servers, and SharePoint database servers.
In many cases, a single SharePoint farm is not enough to provide for all the needs of an organization. Some deploy multiple SharePoint farms to provide for test environments, farms where development can occur, or farms for extranet users or Internet use. You need to define how many farms are required for an organization when beginning the design process, because the number of farms created can directly reflect on the physical architecture of the servers in a SharePoint environment. Generally speaking, the more farms required, the more hardware is needed, so a full understanding of what can be gained by deploying multiple farms is first required.

Deploying Test Farms

Any production SharePoint environment should have a test environment in which new SharePoint web parts, solutions, service packs, patches, and add-ons can be tested. This applies to all organizations, regardless of size. It is critical to deploy test farms, because many SharePoint add-ons could potentially disrupt or corrupt the formatting or structure of a production environment, and trying to test these new solutions on site collections or different web applications is not enough because the solutions often install directly on the SharePoint servers themselves. If there is an issue, the issue will be reflected in the entire farm.
Because of these reasons, many organizations create a smaller SharePoint farm just for testing. The farm should be similar to the existing environments, with the same add-ons and solutions installed and should ideally include restores of production site collections to make it as similar as possible to the existing production environment. All changes and new products or solutions installed into an environment should subsequently be tested first in this environment.

NoteThe SharePoint server or servers used for a test farm or even a production farm do not necessarily need to be installed on physical hardware; many scenarios with SharePoint servers installed on virtual server infrastructure are possible.



Deploying Development Farms

Developers in an organization that makes heavy use of SharePoint often need environments to test new applications, web parts, solutions, and other SharePoint customization. These developers often need a sandbox area where these solutions can be tested, and potentially one with different characteristics from production. These environments are also typically quickly provisioned and deprovisioned, so test environments are not the best location for them.
For these organizations, it may make sense to deploy one or more development farms so that developers have the opportunity to run their tests and develop software for SharePoint independent of the existing production environment. When developed, these applications can first be tested in the test farm and then finally deployed into production. For information on automating the creating of test farms using virtual host management software.

Deploying Extranet or Intranet Farms

Another reason to deploy multiple farms is for security. For security reasons, it is not generally recommended to have an internal SharePoint document management or intranet environment directly accessible from the Internet unless it is secured by an advanced reverse proxy platform such as Microsoft’s Forefront Edge line that includes the Threat Management Gateway or Unified Access Gateway products.
Even for environments properly secured for inbound access, there may be scenarios in which SharePoint content needs to be made accessible by external users, such as in anonymous Internet portal scenarios or for extranet partner scenarios. Because a SharePoint farm requires high connectivity between farms members, it subsequently becomes necessary in these cases to deploy dedicated SharePoint environments in the DMZ of a firewall or in another isolated network.

SharePoint Content Deployment can be used to push site content from one farm to another, for example, when content from an internal farm is pushed to an external extranet farm on a regular basis. The extranet farm remains secure and cannot access content on the internal farm, but users can still access required content that has selectively been chosen for publishing.



Deploying Global or Distributed Multifarm Environments

For environments with multiple geographical locations, it may make sense to deploy multiple farms in different geographical locations. This enables SharePoint content to be consumed locally and is what is recommended in scenarios in which WAN links are not as robust. Consider several key points before deciding where to deploy geographical farms:
  • A single SharePoint farm should not span a WAN link and should ideally be limited to one geographical location. In some organizations, in which the definition of WAN includes at least 1GB of bandwidth with less than 1ms of latency between offices located relatively close to one another, it may be possible to stretch a farm across locations, but this is the only scenario in which this would be supported. If you need to consume content locally, it must be part of a separate farm.
  • There is no native way to do two-way replication of content between farms with SharePoint 2010. However, several third-party companies on the market enable this type of functionality, which can be advantageous in disaster recovery scenarios in which content is replicated to multiple farms.
  • For many organizations, it may make more sense to deploy a single, centralized SharePoint farm in one location rather than to deploy siloed SharePoint farms in multiple locations. Clients access SharePoint using the latency tolerant HTTP/HTTPS protocols, so access to a centralized infrastructure may make sense. It also has the advantages of providing a single URL to access SharePoint and keeps data in one location. Organizations need to decide if the level of service accessing SharePoint across a WAN is sufficient for this to be a possibility.

Planning for Multiple Farms

Consider several key points when designing a SharePoint environment to include multiple farms:
  • All SharePoint server roles, with the exception of the database role, can only be a member of a single farm. You cannot have a SharePoint server reside in more than one farm at a time.
  • A single database server can contain databases from multiple farms, though it is generally recommended to limit the number of content databases on a single SQL instance to no more than 50.
  • If deploying multiple farms on a single SQL server, be sure to use a common naming convention for each farm database so they can be logically organized on the SQL server. For example, naming all databases with the prefix SP_Farm1, SP_Farm2, and so on can help identify which databases belong to which farm.
  • All farm members must have near-full network connectivity (1Gb+ Bandwidth, <1ms latency) to all other farm members, with a large number of open ports with nearly all of them open. This effectively limits scenarios in which firewalls separate farm members, unless all ports are open between hosts.
  • Although not required to have a test environment exactly match production in terms of the number of servers or the type of server roles, it is critical that the web role servers in each environment match each other so that more effective testing can take place.

Global Navigation – Pros and Cons

Posted by Jim on April 20, 2011
SharePoint, SharePoint 2010, SharePoint Designer / 4 Comments

Global Navigation ………… what is missing and what can you do to make changes.


First let me tell you a story about a customer that really needed support in this area. Despite constant consultation with them on the topic of SharePoint navigation in an enterprise environment they demanded a single navigation bar through all there site collections. Well 25 site collections is not a simple task and yes this is a large company with significant data storage needs so what to do.


1)     You can recommend the use of customer providers to embed into custom navigation system and thus provide automated global navigation control. However what you gain in control using this method you will also lose in the automated functionality of the OOTB Navigation bar.

2)     So when you lock down navigation you will loose the ability to have SharePoint manage navigation through its’ standard deployment method.

3)     If you chose to give up automation here is a simple fix that actually is a fall-over from MOSS 2007 methods of addressing this same issue.

4)     Remember your giving up automation and that my friends is not what SharePoint is all about?


STEPS for Installing Global Navigation Provider’s SharePoint 2010.


1)      Build out your custom XML provider we will call ours.

CustomTopNavMenu.sitemap ….example :


<siteMapNode title=”Home” url=”/” >
    <siteMapNode title=”Departments” url=”/Departments”>
        <siteMapNode title=”Corporate Services” url=”~/dept/CorporateServices”/>
        <siteMapNode title=”Finance” url=”~/dept/Finance”/>

        <siteMapNode title=”Engineering” url=”/dept/Engineering”/>

        <siteMapNode title=”Business Development” url=”/dept/BD”/>


    <siteMapNode title=”Services” url=”~/Services”>

        <siteMapNode title=”Human Resources” url=”/sites/HR”/>

        <siteMapNode title=”IT” url=”/sites/IT”/>


  <siteMapNode title=”Resources” url=”~/Resources”>

     <siteMapNode title=”Training” url=”/Training”/>

     <siteMapNode title=”Forms” url=”/Docs/Forms/”/>





2)     Put “CustomTopNavMenu.sitemap” into the layout bin of both WFE servers. //14/TEMPLATES/LAYOUTS/

3)     Add to all Site Collection Web Config files throught the IIS web path on both servers.

Edit Web Config to include the new XML sitemap provider …. Search for sitemap.
<add name=”MyCustomSiteMapProvider” siteMapFile=”_layouts/CustomTopNavMenu.sitemap ” type=”Microsoft.SharePoint.Navigation.SPXmlContentMapProvider, Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c” />

4)     Open Master page for that site collection up in designer and add the following
a. Open SharePoint Designer (SPD) and open the master page for your site

b. Look for the line <SharePoint:AspMenu and add the following right above it:

<asp:SiteMapDataSource ShowStartingNode=”True” runat=”server”
       SiteMapProvider=”MyCustomSiteMapProvider” />

5)     Change data providers in the Master Page.


And BAM it’s done!