One piece of the puzzle must be addressed regardless of all other consideration factors. You must comply with the laws applicable to your industry. So, before you make your decision, you need to understand your regulatory environment and the corresponding required IT controls.
If you and your financial services organization are in the process of making decisions regarding a new SharePoint installation or platform, you must consider many factors, especially if you are planning to use SharePoint for processes and documents that support your customers.
Search is a powerful tool, a very welcome and useful feature on any site. SharePoint farms can be especially large, and finding what you need quickly is extremely important. The Search Service Application in SharePoint provides this key feature to its users. This feature can extend beyond just your local SharePoint farm, however.
The Fabulous 40 templates for SharePoint, or Application templates for Windows SharePoint Services 3.0, became very popular in many MOSS 2007 environments. They were originally created just as examples of what could be done with custom templates in SharePoint, however, they were quickly adopted into many production environments as-is, dispite the original intent. Looking over the list of available templates, it's easy to see why. There is a lot there.
Navigation within SharePoint can often cause confusion and frustration among users and admins. Whether it’s users not understanding where they are, or Admins not knowing how to structure things in a sensible way, Navigation can be challenging. Today we are going to take a look at a fairly common (and frustrating) scenario – cross site collection navigation. By default SharePoint 2010 and 2013 do not allow for cross site collection navigation, meaning the same navigation set or structure isn’t available to an entire web application. One site collection cannot easily link to items in another without using custom, hard coded links.
As a Google search suggests, I didn’t make up the word, but I like the terminology, so I am going to use the phrase for this article. A “FrankenPortal” is a way to describe a bunch of technologies cobbled and hacked together to the point where a server should really have bolts strapped to the side of it, meant to resemble the Frankenstein monster.
In the previous installment of this article, Utilizing The Power Of SharePoint Search – Part 1 (Centralizing Search Results From Mulitple Sources), we configured the SharePoint Search Application to index some external resources, and make that content centrally searchable from within SharePoint.
Recently I undertook the task of migrating our on-premise Exchange 2007 server to Office 365/Exchange Online. This was a major undertaking, which in and of itself could be an entire series of blog posts spanning many, many... many posts. This is something that I may tackle at some point in the near future. But for now, what I'm going to focus on here is how I set out to get SharePoint sending it's various emails and alerts using Exchange Online.