Office Online Server Update
Microsoft released Office Online Server (OOS), formerly known as Office Web Apps (OWA) earlier this year, and recently announce the first significant update to it. First the good news and that is that this November update provides improvements in the following eight functional areas of OOS:
Feature Pack 1 for SharePoint Server 2016
Microsoft promised! Microsoft delivered!
During the launch of SharePoint Server 2016, Microsoft said you no longer are going to have to wait for the next major release of SharePoint to obtain new features and functionality introduced in SharePoint Online.
Guess what? They followed through by releasing SharePoint Server 2016 Feature Pack 1 in early November 2016. A feature pack is similar to a CU, or Cumulative Update, in the sense it includes all previous updates for SharePoint Server 2016, which means you don’t have to install them before you install Feature Pack 1. But a Feature Pack...
I’ll be speaking at Live! 360 Orlando, December 5-9. Surrounded by your fellow industry professionals, Live! 360 provides you with immediately usable training and education that will keep you relevant in the workforce.
I’ll be presenting the following sessions:
· Integrating Office Online Server with SharePoint
· Managing Data Recovery in SharePoint
· Optimizing SQL Server for SharePoint
SPECIAL OFFER: As a speaker, I can extend $500 savings on the 5-day package. Register here: http://bit.ly/LSPK01_Home
All roads lead to Live! 360: the ultimate education destination! Bring the issues that...
I’m sure by now most of you have encountered SharePoint databases that have a SQL Server database data file (.mdf) at a size that is as little as several hundred MB’s, yet the associated log file (.ldf) is ginormous and may be GB’s in size. This ginormous transaction log file will continue to grow until the drive containing the transaction log (t-log) runs out of disk space. At this point there is no room for transactions to be added to the t-log, so users cannot perform insert, update, or delete actions in SharePoint. This restriction is applied because every type of SQL data modification is first written to the transaction log and...
When creating a web application in SharePoint 2013 it will communicate with SQL Server to create the supporting content database. Depending on what steps are used to create the Web Apps it sometimes creates the SharePoint database with a not-so-'friendly' database name and it may contain a ginormous GUID, (which I pronounce Goo-id) as part of the database name. When working with these databases it can become challenging to specify the name of the database within PowerShell or SQL Server so you'll want to rename the database to a more user-friendly name. You may also decide you need to move the database to a different location on your hard...
The Central Administration content database that is created during the installation of your SharePoint farm is probably the second most important database, with the SharePoint Configuration database being the first most important, so it is imperative that you are able to easily reference this database when performing administrative tasks. If you perform the SharePoint installation using the GUI the Central Admin database is created with a not-so-user-friendly name that includes a Globally Unique Identifier (GUID). This name makes it challenging to work with when writing scripts that reference the database because of the GUID included in...
The ability to upload files into SharePoint using the Windows Explorer window makes the migration of content into SharePoint significantly easier. The Windows Explorer mode option in SharePoint is also very beneficial if you want to move content from one location to another location in SharePoint. However, if you have not made one quick configuration change to Internet Explorer the time it takes to perform the upload, copy, or move within SharePoint is horribly slow.
You can follow these steps to significantly decrease the time necessary for these operations: