Warning: Declaration of WarpMenuWalker::start_lvl(&$output, $depth) should be compatible with Walker_Nav_Menu::start_lvl(&$output, $depth = 0, $args = Array) in /home4/x15denis/public_html/wp-content/themes/yoo_nano2_wp/warp/systems/wordpress/helpers/system.php on line 678

Warning: Declaration of WarpMenuWalker::end_lvl(&$output, $depth) should be compatible with Walker_Nav_Menu::end_lvl(&$output, $depth = 0, $args = Array) in /home4/x15denis/public_html/wp-content/themes/yoo_nano2_wp/warp/systems/wordpress/helpers/system.php on line 678

Warning: Declaration of WarpMenuWalker::start_el(&$output, $item, $depth, $args) should be compatible with Walker_Nav_Menu::start_el(&$output, $item, $depth = 0, $args = Array, $id = 0) in /home4/x15denis/public_html/wp-content/themes/yoo_nano2_wp/warp/systems/wordpress/helpers/system.php on line 678

Warning: Declaration of WarpMenuWalker::end_el(&$output, $item, $depth) should be compatible with Walker_Nav_Menu::end_el(&$output, $item, $depth = 0, $args = Array) in /home4/x15denis/public_html/wp-content/themes/yoo_nano2_wp/warp/systems/wordpress/helpers/system.php on line 678
Denis Stadler – SharePoint & Dynamics CRM Consultant

Office 365 – SharePoint Online – Declare Record Field Value Has a Different Time Zone

Written by Denis Stadler on . Posted in Office 365

I have a SharePoint Online site collection, which has the In Place Record Management site collection feature enabled.

I have created also a document library, where I upload invoices and declare them as records, in order to enforce a 5 years retention policy. The problem is that, the time value in the Declared Record field of the item has a different value then the one showed by the system’s clock. It seems that it is working on another time zone.

Office 365 – SharePoint Online – The required feature is not enabled for this column type

Written by Denis Stadler on . Posted in Office 365

Yesterday I was creating a new Enterprise Wiki site in a SharePoint Online site collection. The interesting thing that I found out, was the fact that I was not able to configure the default “Wiki Categories” managed metadata column.

And an interesting error message was there:

The required feature is not enabled for this column type.

After investigating for a while I realised that the issue was cased because

enterprise-wiki-publishing-site

Step by Step: How to Implement an Enterprise Wiki

Written by Denis Stadler on . Posted in Collaboration

Post Summary

The main business reason which made me to start the discussion about the necessity of having an Enterprise Wiki was to encourage many-to-many communication between the team’s members. But, there were others like:

  • The necessity of having a central repository tool which hosts, in my case, technical knowledge and information accumulated during the IT projects;
  • The necessity of categorizing  the information (both as Taxonomy and “Folksonomy”) in order to access it faster;
  • Search engine.

Having said that, the natural choice was to implement an Enterprise Wiki in SharePoint 2010. The other advantages gained by choosing it are: Versioning, Approval (at the end Enterprise Wiki is a publishing site, but for sharing technical resources I don’t think it’s necessary).

Before strating, I would suggest consulting the following TechNet articles:

Prerequisites

In order to deploy an Enterprise Wiki we need the following:

  • A site collection created based on one of the publishing site templates or another site collection where the SharePoint Server Publishing Infrastructure feature is activated at the site collection level;
  • Managed Metadata Service and Search Services (if we want to search within the Wiki :) ) shared service applications up and running.

Implementation

Basically what I have to do is to deploy a SharePoint 2010 built-in feature. I have a publishing site collection – Intranet where I will add an Enterprise Wiki as a child site which will host my content.

Step by Step: How to Implement a Three-Tier SharePoint Farm

Written by Denis Stadler on . Posted in SharePoint 2010

Post Summary

The purpose of this article is to describe how to implement a medium SharePoint Farm – three-tier, four-servers.  Before going into details I would like to recommend you to download the following file: Topologies for SharePoint 2010.

If you want you can download this post as a PDF file – How to Implement a Three-Tier SharePoint Farm.

My SharePoint Topology

My environment is hosted on Windows Server 2008 R2 Hyper-V and consists of four servers: SQL, SPLive1, SPLive2 and an Application Server.

Basically the services in farm will be split according to the following table (please take into consideration only the production environment – highlighted with green):


Warning: Parameter 1 to W3_Plugin_TotalCache::ob_callback() expected to be a reference, value given in /home4/x15denis/public_html/wp-includes/functions.php on line 3208