On February 19th, Microsoft has announced that "Office Web Apps" will now be called "Office Online". For those that don't know already, it is Microsoft's online version of Microsoft Office where users don't need the Microsoft Office client installed in order to author/edit Microsoft Office Documents (i.e. Word, Excel, PowerPoint). This was done in order to alleviate the confusion on the word "Apps" in "Office Web Apps". Office Online can be seen and used by anybody with a OneDrive (formally SkyDrive) or OneDrive for Business account. Be sure to test out the real time co-authoring capabilities as they are a huge time saver!
I am happy to say that I will be speaking at SharePoint Summit Toronto on Tuesday May 27th, 2014 from 11:30 AM - 12:45 PM.
I will be speaking amongst some great local and well known industry speakers. Be sure to register now in order to get free entrance to the Excellence Gala.
My session details are as follows:
Real World tips and tools to build your SharePoint 2013 Records Management System
This session will bust the myth that SharePoint is not a good platform and robust enough to build out your SharePoint 2013 Records Management System. Noorez Khamis [Microsoft SharePoint Server MVP] will delve into demos and real world examples of how to start the build out of your SharePoint 2013 Records Management system from scratch. It will talk to many of the built in and add-on features that will help ease your deployment while showing you how your system can scale to an Enterprise Records Management system.
About SharePoint Summit Toronto
Built around the theme of Discover, Innovate, Build, the conference's 2014 edition will zero in on new developments and improvements in the latest version of SharePoint. The conference will be especially content-rich for every user, from beginners to Super Users. Our program of presentations and workshops will be stronger than ever. Some of the reasons to come include:
- Advanced training sessions covering improvements in the latest version of SharePoint
- Meet-the-experts roundtables focused on organizations' current concerns
- Keynote speaker and SharePoint MVP Ruven Gotz
- More than 60 speakers, including some of the industry's best-known SharePoint influencers and MVPs
- Case study workshops to share experience-based SharePoint expertise
- The Second edition of the SharePoint Excellence Gala
- Registration fees reduced by 20%
Hope to see you there!
On Feb 25th, 2014, Microsoft finally released the long awaited SP1 for SharePoint and Office 2013. Service Pack 1 (15.0.4569.1506) is a very important update for SharePoint 2013 as it rolls up all of the cumulative updates thus far plus some very big platform updates such as:
- Support for Windows 2012 R2 Server
- A re-branding and re-tooling of SkyDrive and SkyDrive Pro to OneDrive and OneDrive for Business.
- Internet Explorer 11 Compatibility Fixes
- More support for Touch devices
- Additional app-model API capabilities
- PowerMap for Excel
- Ability to configure Yammer and OneDrive and how they display on the SuiteBar
SP1 will be available through Microsoft Updates very soon but if you are eager, you can download them directly via the following links:
SharePoint Server 2013 SP1 (KB 2817429)
SharePoint Designer 2013 SP1 (KB 2817441)
Office Web Apps Server 2013 SP1 (KB 2817431)
Office 2013 SP1 (KB 2817430)
For the full list of downloads, changes and capabilties, refer to the this Office Updates blog post.
I have been blogging on SharePoint Technology topics for almost 5 years now and being a SharePoint advocate, I felt it necessary to use SharePoint for my blogging. It helps me identify the "goods" and the "needs improvement" capabilities of blogging in SharePoint for myself and for when my clients seek advice. Historically, I had my own hosted server running SharePoint 2007 Foundation which I manually upgraded to SharePoint 2010 Foundation. It provided me all the on-premises tools necessary to customize, design, code and cater my blog to my liking.
With the emergence of the "Cloud", I felt it necessary to make the switch to SharePoint Online within Office 365 to avoid the pains and costs of maintaining my own server and to educate myself in the process. My blogs have been lucky enough to be mentioned in some people's top blogs list (i.e. Mark Jones Top SharePoint Blogs Listly and Dynamics 10 Top 50 SharePoint Sites) so it was very important to me to ensure all of my historic posts would be migrated to the new system. Some of the decision criteria I had to make included the following:
Will the Office 365 public SharePoint site have the capabilities I need for blogging?
The blog and overall publishing capability within the public version of SharePoint Online is relatively new and doesn't provide the full functionality that I am used to as on-prem versions (i.e. Content Search Web Parts, etc…). There is no real blog "site" or "site-template", it is all on the root public site within Publishing Pages and custom blog web parts on those pages. After playing around, it does have the basic functionality I needed to blog although comments seem to now be handled via a new social plug in mechanism and my old comments will now be lost.
What are the steps I would take in transfering my domain over to Office 365?
I had an existing Office 365 Subscription and was easily able to change my DNS and Office 365 settings to point to the new Blog site by following the instructions outlined in Office 365 (basically adding some CNAME and A settings).
How will I perform the migration?
I definitely did not want to manually migrate (i.e. copy and paste) all of my historic posts to the new system so I had to choose a tool. Luckily my friends at Sharegate allowed me to use their tool to do the migration and it was indeed a very easy process using their tool.
How will I design the site?
To design the site, the folks at BindTuning had some nice and easy to deploy templates for the default Office 365 SharePoint Online public site. I customized it on their site and deployed it to my blog site quite easily using their tools and step by step instructions.
How will I post to and edit entries in my new blog?
Over the years, I have been spoiled by using Windows Live Writer for my blogging needs but it is not yet supported with Office 365 yet. Luckily Office 365 has a "Launch blogging app" capability which opens up MS Word for editing the blog and has all the basic capabilities that I require.
Is there a way to not lose my current SEO rankings and links?
I do not have a solution for this (yet) so I will have to wait for the search engines and users to re-crawl and fix up their links to my articles since my legacy links were in a different format.
Overall, it was a good learning experience and I will keep trying to enhance this new blog using a combination of out-of-the-box SharePoint Online tools with SharePoint Designer and I am sure that Microsoft will be making enhancements to what they offer in the SharePoint Online public site as well.
Thought this might be handy to those folks who write a lot of architecture/design documentation like myself.
The latest information on these database types and descriptions can be seen on the following TechNet article:
Upon installation of a SharePoint 2013 Server Enterprise farm, the following SharePoint database are created on an instance of SQL Server 2012:
Profile||The Profile database stores and manages users and associated information. It also stores information about a user's social network in addition to memberships in distribution lists and sites.|
Synchronization||The Synchronization database stores configuration and staging data for use when profile data is being synchronized with directory services such as Active Directory.|
Social Tagging||The Social Tagging database stores social tags and notes created by users, alongside their respective URLs.|
|4||Word Automation Services service application database ||The Word Automation Services database stores information about pending and completed document conversions and updates. The Word Automation Services Timer Job processes and distributes this information as queued conversion job items to application servers.|
|5||Managed Metadata Service service application database||The Managed Metadata service application database stores managed metadata and syndicated content types.|
|6||SharePoint Translation Services service application database||The Machine Translation Services stores information about pending and completed batch document translations with file extensions that are enabled.|
|7||PerformancePoint Services service application database||The PerformancePoint Services database stores temporary objects and persisted user comments and settings.|
|8||Project Server service application database||Project Server creates a separate database for each instance of Project Web App. *Requires Project Server which is not in scope|
|9||SQL Server Power Pivot Service service application database||The Power Pivot Service database stores data refresh schedules, and Power Pivot usage data that is copied from the central usage data collection database. *SQL Server 2012 Power Pivot for SharePoint 2013 requires SQL Server 2012 Analysis Services (SSAS), Business Intelligence or Enterprise edition.|
|10||State Service service application database||The State Service database stores temporary state information for InfoPath Forms Services, Exchange Server, the chart Web Part, and Visio Services.|
|11||SQL Server system databases||SharePoint Server 2013 is built on SQL Server and uses the SQL Server system databases. SQL Server does not let users directly update information in system objects such as system tables, system stored procedures, and catalog views. Instead, SQL Server provides a complete set of administrative tools that let users fully administer their system and manage all users and objects in a database. For more information about the SQL Server system databases, see System Databases.|
The master database records all the system-level information for a SQL Server instance. This includes logins, configurations, and other databases.|
The model database is used as the template for all databases created on the SQL Server instance. Any modifications made to the model database are also applied to all databases created afterward.|
The msdb database is used by SQL Server Agent for scheduling alerts and jobs.|
|15||tempdb database||The tempdb database holds temporary objects or intermediate result sets. For example, it holds all temporary tables, temporary stored procedures, and any other temporary storage needs. The tempdb is recreated every time SQL Server starts.|
|16||Report Server Catalog database||The SQL Server Reporting Services Report Server Catalog database stores all report metadata including report definitions, report history and snapshots, and scheduling information. When Report Server Catalog is used, report documents are stored in SharePoint content databases. *Installed when SSRS is installed|
|17||ReportServerTempDB database||The SQL Server Reporting Services ReportServerTempDB database stores all the temporary snapshots while reports are running *Installed when SSRS is installed|
|18||Report Server Alerting database||The Report Server Alerting database stores all Data Alerts metadata and runtime information that is required to produce Data Alerts for Reporting Services operational reports. Data from reports is processed in the database to match rules that are defined in Alert Definitions. *Installed when SSRS is installed|
For those folks in the Ottawa area this week, be sure to catch my session on:
Taking Control and Shaping your Career and your Future in Microsoft SharePoint Technologies
“In this session you will learn about many of the different roles, jobs and aspects that a current career in SharePoint has to offer and what they entail. Learn about opportunities for advancement in Microsoft SharePoint technologies and on how you can excel at the aspect of SharePoint that you love best. The session will also talk and theorize about the future landscape that Microsoft has for SharePoint with the emergence of Office 365 and Windows Azure cloud based technologies”
There are some great sessions so be sure to visit the web site and register at: https://spsevents.org/worldwide/Ottawa/
Technorati Tags: SharePoint
As we all know, getting new and existing Microsoft SharePoint customers to the “cloud” aka Office 365 & Azure has been the major push for Microsoft as of the last year or so. This can be seen from internal Microsoft employee restructuring along with their sales incentives, SharePoint Online product redevelopment to have feature parity with the on-premises version, the new app model, and generally Microsoft marketing in general. Although this trend will not stop anytime soon, it is comforting to see Bill Baer (senior product manager on the Microsoft SharePoint marketing team) officially indicate on the Microsoft SharePoint blog that Microsoft is still dedicated to their customers who have or who have aspirations for on-premises deployments of SharePoint.
For those who are evaluating whether to use SharePoint internally on-premises versus a competitor and were scared that Microsoft will stop supporting it soon in exchange for Office 365, this type of messaging should help your decision in continuing to use SharePoint as an on-premises platform.
In the article Bill Baer states:
“We remain committed to delivering support and solutions for our customers whether in the cloud or on-premises, through cumulative updates, future service packs and content to ensure that wherever you have SharePoint deployed, behind the firewall or in the cloud, customers will continue to have the support they need to ensure the continued success and benefit of constant innovation.”
View the full blog here –> http://blogs.office.com/b/sharepoint/archive/2013/10/04/transforming-business-with-microsoft-sharepoint.aspx
Even though SharePoint Server 2013 has been released for a while now, I still see developers who aren’t taking advantage of a new feature in SharePoint 2013 that will make their implementation, code analysis and debugging a lot easier.
The developer dashboard was initially released in SharePoint 2010. It was designed to provide diagnostic information to troubleshoot problems with SharePoint page level components (i.e. web parts, master pages, etc…) that would be difficult to isolate without viewing backend logs or debugging through code.
In SharePoint 2013, there has been a massive improvement to the developer dashboard now:
- No longer a page control which only shows info about current request but now a separate window which shows you ALL requests since you started developer dashboard session!
- The new Developer Dashboard has ULSViewer elements in it, no more digging through the 15 hive for the logs folder using notepad or ULSViewer to find your correlation id, you have it right there!
- You can also see SharePoint server info, SQL calls, Service Calls, ULS and SPRequests all from this view in a nice tabbed view
- Works by using dedicated WCF service (diagnosticsdata.svc) designed for the purpose of providing tracing information for developer dashboard
- Turned off by default and doesn’t even show on the page until it is turned on
- Uses the “Usage and Health Data Collection Service Application”
- many more… get more about it here http://technet.microsoft.com/en-ca/sharepoint/fp123606.aspx
To enable, run this in SharePoint Management Shell:
$content = ([Microsoft.SharePoint.Administration.SPWebService]::ContentService)
$appsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::On
See it appear at the top right of your SharePoint page beside the “Focus on Content” area once you enabled it, clicking on it will pop up the Developer Dashboard in a new browser window which you can leave open for various requests:
To disable, run this in SharePoint Management Shell:
$content = ([Microsoft.SharePoint.Administration.SPWebService]::ContentService)
$appsetting.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::Off
In a recent post by Bill Baer (Microsoft SharePoint Senior Product Manager), he indicates that anyone who has installed SharePoint Server 2013 who wants to be able to install future product updates, should install the SharePoint Server 2013 March 2013 Public Update. See a full description.
He goes on to say the following:
“Q: Do I need to install the SharePoint Server 2013 March 2013 Public Update?
A: The SharePoint Server 2013 March 2013 Public Update establishes a baseline for future product updates and must be installed to support the installation of future product updates.”
When installing the update, remember to follow his outline process of stopping the SPSearchHostController, OSearch15, and SPTimerV4 services before installing the update or you will be waiting for a long time (could be up to an hour or more) for the update to complete, especially in a farm environment.
Welcome to Rez's SharePoint Blog Spot
I'm a SharePoint Server MVP and Solution Architect who enjoys working with the most cutting-edge Microsoft technologies.