With the recent release of Microsoft Teams, you may be wondering what the differences between Teams and Office 365 Groups are. At AIS, we’re always on the forefront of the latest Office 365 services, and given our long-time partnership with Microsoft, we’ve actually been using both Microsoft Teams and Office 365 Groups for while now. We’ve gotten a solid sense of what both services are good at and what they’re…not so good at. At least not yet. Read More…
If you need managed services to maintain peak IT network operations, consider us here at Applied Information Sciences. We’ll manage all your IT services for a predictable cost so you can focus on more strategic investments. AIS’ Managed Services Practice provides ongoing responsibility for monitoring, patching and problem resolution for specific IT systems on your company’s behalf.
- Backup and Restore
- Incident Response
AIS’ Managed Service Practice has up to 24×7 coverage for initial responses to incidents through a combination of dedicated, part- and full-time staff, both onshore and offshore. AIS prides itself in being on the leading edge of managed services support. Our collaborative, disciplined approach is committed to quality, value, time and budget. Read More…
I decided to build my own solution since it would be a relatively simple design and it would let me dig into KnockoutJS. In addition, it would be easier to use TypeScript to build an easier-to-maintain solution since it incorporates many of the ECMAScript 6 features like classes and modules, among others. Read More…
I came across an interesting bug while trying to add a user the Administrators of a Search Service Application in SharePoint 2013. When I tried adding the user, and clicking OK, and error is returned: “User does not have permission to perform this action” along with a correlation ID. Further investigation in the ULS logs revealed that the problem was SQL permission related: “The EXECUTE permission was denied on the object ‘proc_MSS_GetConfigurationProperty’, database ‘SPSearch’, schema ‘dbo’.” Additionally performing a search fails and logs the error: “There was an exception in the Database. Please retry your operation and if the problem presists, contact an administrator.” (The error message has a typo too). Read More…
Recently, I encountered an issue with SharePoint 2013 search crawls where .pdf files smaller than 1 MB reported a warning: “The item has been truncated in the index because it exceeds the maximum size”. The default MaxDownLoadSize for documents in SharePoint is 64MB, which was more than enough the handle these relatively small .pdf files.
After I reached out to some co-workers; one suggested that the error might be a false-positive and the entire document had been crawled. I tested this by first searching for words at the end of the document and no matches were found; this would be expected if it were truncated. Next, I tried searching for text in the middle of the document, no matches were found either. I thought it must have truncated a lot of text and tried searching for text contained at the very beginning of the document. No results were found! So when the warning said it truncated the item, it had truncated the whole document. Read More…
Your company’s SharePoint site should be personalized to reflect your brand and culture. How your site looks can impact how much it’s used. One of the easiest ways to complete this personalization is by incorporating graphics that “match” your organization. Sometimes you have a great set of graphics and icons to start with, and sometimes it can be difficult to find “exactly” what you are looking for. In these instances I have to create my own graphic from “scratch” or by using a few found images. Read More…
Do you feel like the guy or gal at the party who missed the topic of discussion and now you’re stuck in the middle of a conversation with no idea what’s happening? Have you overheard endless hours about an application called SharePoint yet you still aren’t sure why anyone would need it? It came out in 2001, but you probably actually heard about it in 2007. Your office likely got it a few years back and now, just now you are either being told, or encouraged, to use it, all while your IT guys ramble on about upgrading from SharePoint 2010 to SharePoint 2013. If this sounds like something you have or are currently experiencing, then let’s take a step back to the basics of what SharePoint is, and what it can do for you. Read More…
Maybe it’s too hard to update, so everyone simply assumes the information there is outdated. Maybe the search functionality consistently returns irrelevant results. Maybe it’s not accessible from a smartphone or tablet.
Whatever the reason, the result is the same: poor user adoption has doomed your intranet.
For over 30 years, we’ve been building complex intranets for businesses and organizations of all types and sizes, leveraging the latest technology platforms to create beautiful, usable intranets that solve business problems and eliminate common user pain points.
Our latest whitepaper, Building the Intranet Your Employees Expect, walks you through the building blocks required to design an intranet that not only incorporates today’s capabilities and features, but will also be an essential system that gets adopted, used and loved by your employees. Download your copy today!
In the world of SharePoint upgrades and migrations, a number of terms are thrown around and often used interchangeably. This post outlines several key terms that will be surfaced throughout a three-part series on upgrade/migration strategies for SharePoint 2013. If you would like to jump to another post, use the links below:
- Part 1 – Definitions (this post)
- Part 2 – Considerations Outside of SharePoint (Coming soon)
- Part 3 – Diving into Database Attach (Coming soon)
In past revisions of SharePoint, we had multiple ways to upgrade our farms (and the content within them) to the latest version using the tooling Microsoft provides. Over the years, Microsoft used a number of terms related to the types of upgrade available:
- In-place upgrade – Often considered the easiest approach, but the most risky. The setup of the new system is performed on existing hardware and servers.
- Gradual upgrade – Allows for a side-by-side installation of the old and new versions of SharePoint.
- Database attach/migration – Allows for the installation and configuration of an entirely new environment where content is first migrated, and then upgraded to the desired state.
As SharePoint matured, the number of available upgrade options dwindled. For instance, in an upgrade from SharePoint Portal Server 2003 to Office SharePoint Server 2007, we could follow any one of the three upgrade paths noted above to reach our desired end state. In an upgrade of Office SharePoint Server 2007 to SharePoint Server 2010 we still had two paths available: the in-place upgrade and the database attach approach. For SharePoint 2013, we’re left with just the database attach approach.
Before we dive further into the database attach upgrade scenario, it’s helpful to take a step back and establish a common language as we discuss the upgrade process. Read More…
My decision to join AIS six years ago was a revelation. After almost seven years spent working as an embedded IT analyst for various government customers, I joined AIS to support a customer who was implementing SharePoint. I soaked up everything I could about this (at the time) brave new world of SharePoint. I loved it.
SharePoint 2003 had been available for use in my previous office where I had initially set up out-of-the-box team sites for working groups to support a large department-wide initiative. I found it empowering to quickly set up sites, lists and libraries without any fuss (or custom coding) to get people working together. Working with my new team, I gained insight into what we could do with this tool in terms of workflow, integration and branding. It got even better when we migrated to SharePoint 2007. We made great strides in consolidating our websites and communicating to those who were interested exactly what the tools could do in terms of collaboration and knowledge management.
This ability for a power user to quickly create a variety of new capabilities exposed a deeper customer need – easier communications with IT. While we had all this great expertise and firepower to create and maintain IT tools and services, our core customer base did not have an easy way to quickly and reliably communicate their needs in a manner that matched their high operational tempo. It was a problem. We needed a way for our customers to quickly and easily communicate with us in order to really hear what they needed to meet their mission goals and work more effectively. Read More…