2019 – Microsoft officially announced the Next Office version 2019

Posted by Jim on September 29, 2017
O365, Office 365, SharePoint 2019 / Comments Off on 2019 – Microsoft officially announced the Next Office version 2019

Microsoft has announced Office 2019, the next perpetual Office update and the follow-up to the most recent release, Office 2016. Due for release in the second half of 2018, Microsoft says that preview versions of the latest Office suite will start rolling out in mid-2018.

In the announcement, Microsoft was fairly tight lipped with what to expect. However, the company did tease certain improvements and features we can expect, including enhanced inking, new PowerPoint animations, three D, and more. From Microsoft:

Office 2019 will add new user and IT capabilities for customers who aren’t yet ready for the cloud. For example, new and improved inking features—like pressure sensitivity, tilt effects, and ink replay—will allow you to work more naturally. New formulas and charts will make data analysis for Excel more powerful. Visual animation features—like Morph and Zoom—will add polish to PowerPoint presentations. Server enhancements will include updates to IT manageability, usability, voice, and security.

It’s definitely interesting to see another perpetual license version of Office on deck for release, particularly as Microsoft has put more and more emphasis on its Office 365 service in recent years. “Office 2019 will be a valuable upgrade for customers who feel that they need to keep some or all of their apps and servers on-premises,” Microsoft says. We should learn much more about Office 2019 and what’s new in the coming months as we move towards a preview release


SharePoint 2016 Feature: Durable Links

Posted by Jim on September 16, 2017
O365, Office 365, SharePoint 2016 / Comments Off on SharePoint 2016 Feature: Durable Links

SharePoint 2016 Feature: Durable Links

New to SharePoint 2016, Durable Links is an effective tool providing link integrity management for documents on SharePoint and Office Online Server. The process works by assigning resource ID to individual documents and the resource IDs themselves are stored in the content database linked with the source documents.

So, when a user selects the Durable Link to a document, the SharePoint Server 2016 searches for it using the resource ID and opens it in the Office Online Server. In this way, Durable Links help in preserving and maintain the integrity of the documents’ linking URLs, even when they are renamed or moved.

So how does it work … let’s take for example. Here is an ID added at the end of the URL like this: fg12g0fcd105b45148d4b6c2f2xx231ce http://sharepoint-site/document-library/document.docx?d=fg12g0fcd105b45148d4b6c2f2xx231ce

What you can see here is that the first part of the URL path is Path Based. Now, if the document is moved to another document library and renamed to say, Proposal, then the new link will be like this: http://sharepoint-site/proposals/proposal.docx?d=fg12g0fcd105b45148d4b6c2f2xx231ce

In the first part of the URL that is path based will change to show the new path and document name, however the ID behind d=remains the same.

Ultimately, what is happens is that when a user comes across the old URL, SharePoint will redirect the user to the document location, which in turn opens the document in the Office Online Server.


  • SharePoint Durable Links provides another great step forward to help prevent the broken links problem in SharePoint documents as it automatically appends a resource ID to documents and makes it easier to use.
  • Durable Links works with documents that can be opened on Office Online Server i.e. MS Office files and PDF; however, it doesn’t seem to work with web pages or list items. (NOTE: In Office 365, as of date of this article, durable links does NOT work with PDF files (but the Document ID link does). PDF durable links (with q=xxx) only seems to work with on premise SharePoint 2016)

So in SharePoint 2016 Durable Links definitely expands on the functionality that the Document ID service failed to do in terms of handling broken links in legacy systems

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!

Office 365 Updates – August

Posted by Jim on September 08, 2017
O365, Office 365 / Comments Off on Office 365 Updates – August

August release of O365 introduces some significant change to the product. In fact they will blow your mind. The first life changing feature introduced is a new template set?

Communications templates. Great looing templates that leverage the core capabilities of list and libraries to produce a awesome experience for the business ( https://blogs.office.com/en-us/2017/06/27/sharepoint-communication-sites-begin-rollout-to-office-365-customers/ )




Yammer improvements. A new Yammer activity report for Office 365 users helps administrators understand how their organizations connects across Yammer. The Yammer activity report is now available in the Office 365 admin center. Additional changes introduce Yammer for iPad has been improved with universal search, automatic sign-in, and an updated design.

Co-authoring in Excel.  “With Excel co-authoring, you’ll find it easy to know who else is working in a spreadsheet and view their changes as you work.” This feature is available on Windows for all Office 365 subscribers.

AutoSave in Word, Excel, and PowerPoint. Office 365 customers who store their documents in OneDrive and SharePoint can now access AutoSave in Word, Excel, and PowerPoint. This is a feature I’ve actually noticed in Word for the Windows desktop.

New education features for Microsoft Teams. This month, Microsoft Teams picks up a number of new features, including OneNote Class Notebook support, class assignments distributed through Teams, and improved IT controls. These features are available to all Office 365 Education subscribers on Windows, Mac, and web.

Rich profiles in Outlook for Windows. Microsoft is rolling out a redesigned experience for connect with colleagues, external contacts, and group in Outlook for Windows for all Office 365 commercial customers.


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 Fpweb.net’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 🙁




Do you need an Isolated Search Server

Posted by Jim on July 23, 2017
O365, SharePoint 2013, SharePoint 2016 / Comments Off on Do you need an Isolated Search Server

When do you introduce a search server. The current farm was searching document at 6 hour intervals with incremental search only focused on a small segment of the 2 terabyte content in the farm. The reason for such slow search was because of the impact of running the search more aggressively. It has always been know the impact of search on the application tier of a farm but I never thought anyone would not see the need to scale and isolate given the need to produce search results in a small to medium farm.

So when do you introduce a search server into a SharePoint farm.

The volume of content that you have in your search index affects what resources you need to host the farm. Work out approximately the number of items that you plan on making searchable. Here are some examples of items: documents, web pages, SharePoint list entries, and images. Remember that each entry in a SharePoint list counts as one item.

When you have established a figure, multiply it by what you think the expected growth of that content will be over the next 12 months.

For example, if you’re starting out with 12,000 indexed items, and you expect the volume of that content to triple over the next 12 months. You should plan for 36,000 searchable items.

It’s not always easy to assess how big or small to make your search architecture. The size of your search architecture depends on the volume of your content, the crawl rate, the query throughput, and the level of high availability that you require. There are sample search architectures that we advise using as a basis to plan your own farm. The sample search architecture that you choose depends on how much content has to be searchable:

Volume of content Sample search architecture
0-20 million items Small search farm
0-80 million items Medium search farm
0-200 million items Large search farm
0-500 million items Extra large search farm

Although these sample search architectures use virtual machines, you can use both physical servers and virtual machines according to the strategy of the overall SharePoint Server 2016 solution of your search architecture.


If you have up to 20 million items, the small search farm will probably be the most suitable farm for you. We’ve estimated that this search architecture can crawl 50 documents per second, and serve in the order of 10 queries per second. With a crawl rate of 50 documents per second, it takes search 110 hours to crawl 20 million items in the first full crawl.

If you have between 20 and 80 million items, the medium search farm will probably be the most suitable farm for you. We’ve estimated that this search architecture can crawl 100 documents per second, and serve in the order of 10 queries per second. With a crawl rate of 200 documents per second, it takes search 280 hours to crawl 80 million items in the first full crawl.

Large search farm

 If you have between 80 and 200 million items, the large search farm will probably be the most suitable farm for you. We’ve estimated that this search architecture can crawl 200 documents per second, and serve in the order of 10 queries per second. With a crawl rate of 200 documents per second, it takes search 280 hours to crawl 200 million items in the first full crawl.

In my case the performance of the farm was very poor. The general introduction of an isolated search server would help improve the crawl process but the solution could also be achieved by improving performance by increasing RAM and retuning the search crawl.  To test this I went to my O365 tenant and to the existing site Farm and preformed a search test:

  1. Up loaded a small document with a unique word pattern that could be searched and timed for how long it took to introduce the document to the crawl results.
  2. MY O365 Ternate was almost immediate. The document showed up within seconds.
  3. The Farm took hours.

It’s obvious there needs to be some changes.