Yes, here are some videos on how to install SharePoint 2016 Preview in Single Server Farm Mode using Windows Server 2012 R2 and SQL Server 2014.
Some assumptions here:
- VM is already join to a domain
- SP_Admin is a local administrator and we are log as it
- VM has two disk volumes C:\, D:\
- SharePoint 2016 Preview ISO is mounted already
- SQL Server 2014 ISO is mounted already
- VM has internet access
Step 1: Install Prerequisites
Step 2: Install SQL Server 2014
Step 3: Install SharePoint 2016 Preview
Friends, as part of a SharePoint 2013 Deployment process make sure you understand the customer base configuration for desktop computers and also other enterprise applications that integrates with SharePoint like Exchange Server.
As you may know, SharePoint 2013 has a bunch of features that work together with other products, specifically Exchange Server 2013 and Office 2013. Feature like Site Mailbox, Exchange Task Sync have direct dependency, so what happen if the customer has Exchange 2010 or Office 2010 in the desktop?
You will have customer complaining about why the Task Sync feature is not working. Probably they will report the following error “We weren’t able to sync your tasks. This could be because your mailbox is on an Exchange server that isn’t supported for syncing tasks. Please contact your administrator for more help”.
So please avoid unsatisfied customers, if Exchange Server 2010 and Office 2010 is the supported software make sure you disable Farm Level Exchange Task Sync feature so when users want to Sync task Outlook 2010 will fire up. So navigate to SharePoint Central Admin site and go to Manage Farm Features, deactivate the Farm Level Exchange Task Sync.
Deactivate Task Sync feature, works with Exchange Server 2013
This change will not impact the Work Management Service Application, so you still get the consolidated task view in you User Profile page. So now you can have Office 2010 playing nice with SharePoint 2013
SharePoint 2013 playing nice with Office 2010
You may think is so simple just to go to Site Actions – Site contents and add a new Sub Site using the Business Intelligence Center site template. But there are some considerations that you need to evaluate first because those can impact you end user experience.
Do you need your Business Intelligence Center at the Site Collection or a Sub Site level?
- Site Collections
- Site Collection level means that you site is the root level of the entire site hierarchy. Site Collections are containers of sites and sub sites. Site Collection has a set of configuration controls that can impact the settings of all the site hierarchy. So ask yourself if your BI Center is going to be a Hub for hosting multiple dashboard or BI solutions for your organization/division or group.
- Creating a Business Intelligence Center at Site Collection Level requires you to access the SharePoint Central Administration site and use the Application Management options, use the Create Site Collection link and provide the site collection information, don’t forget to select from Enterprise Tab the Business Intelligence Center Site Template.
Create site collection option in Central Administration
- Site / Sub Site
- Site or Sub Site means that you site will be a sub site under an existing Site Collection. Site or Sub Site are also container of sites and sub sites and have a limited set of configuration controls that only affect the actual site. So ask yourself if your BI Center is going to be targeted just for your area or group, if you need to publish dashboard that your particular department team members are going to access and consume.
- Creating a Business Intelligence Center at Site or Sub Site level requires you to have 2 features activated at Site Collection level and Site Level, so before creating the sub site navigate to the top level site in you site collection, select Site Actions – Site Settings – Site Collection Features and activate PerformancePoint Services Site Collection Features and SharePoint Server Publishing Infrastructure, then navigate to the site that is going to be the parent site of the BI Center sub site and navigate to Site Actions – Site Settings – Site Features and activate both PerformancePoint Services Site Collection Features and SharePoint Server Publishing Infrastructure. Then select Site Actions = Site Contens and add select Add new sub site, then provide the site information and select under the Enterprise Tab the Business Intelligence Center Site Template. The required features are:
Features required to be activated in order to create a BI Center in SharePoint 2013
When you activate a feature in reality you are provisioning functionality and capabilities to you Site Collection or Site / Sub Site, does your users need to have those features?. For example, if you have a Team Site and activate the Publishing Infrastructure features, now you will have a new set of functionality for handling pages and publications, like 7 new libraries in your Team Site for dealing with page publications also new apps for PerformancePoint.
Libraries added by the Publishing Infrastructure Feature
If you are evaluating Business Intelligence Features, just create a new site collection dedicated to BI Center only totally isolated from the rest of the steam site. Whenever you need to activate a feature in your site or site collection, please identify and consider the implications of provisioning new capabilities.
MVP for 11 years now, but always feel like the first time. Thanks to Microsoft for the MVP Award this year. Also thanks to my fellow colleagues and SharePoint community for their awesomeness. I am proud and happy to be around another year especially when new version of our favorite product is coming.
Got approved to participate as speaker in the SharePoint Saturday San Diego event next November 15, 2014. Awesome content, awesome speakers, awesome venue, awesome city. I will share some experiences on how to enhance document collaboration with SharePoint, what out of the box features we can use to simplify how people collaborate en enhance the end user experience. Those little tips & tricks that make the difference for end users.
Enhance the way people collaborate with documents in SharePoint
Come and learn those extra settings we can turn on to enhance the way people collaborate with documents in SharePoint. There is a set of out of the box settings available in a document library that we can configure to provide a friction free experience for document authors and content consumers.
SharePoint Saturday San Diego
I receive a question around Administrator-approved InfoPath form templates. Here is the answer.
Q. Haaron, what really happen when we upload a new version of an InfoPath form in central admin?
A. When you upload an InfoPath form template using SharePoint Central Administration some things happen:
1. In Manage Form Template you can provision the same version of the form in more than one Site Collection, you can manage the form, activate or deactivate.
2. It creates a WSP file based on your InfoPath Form Template version and deploys as a farm solution, automatically creates a Site Collection Feature that you can Activate or Deactivate.
3. In Manage Form Templates page, when we Activate To a Site Collection basically activate a Site Collection Feature in the target Site Collection, and that provision the form in the Form Templates library.
4. Behind the scenes, when the WSP is generated SharePoint maintain a version of the form template. That make sense because forms instances can point to older version of the template
And this behavior is the same for MOSS 2007, SharePoint Server 2010 Enterprise and SharePoint Server 2013 Enterprise.
Thanks attendees for share with me during this presentation. Here are the slides of my session:
Yes, I have older versions of products and development tools that require .NET Framework 2.0 or 3.0 and when trying to run in my Windows 8.1 just doesn’t work. Windows 8.1 inform that you need to add the software required, so when I run the built in download or update wizard I just don’t install what I need. Nothing happen, nothing, nada!. Then, I go and download .NET Framework 3.5 redistribute package and run and again Windows 8.1 download or update windows doesn’t do nothing. Doing some research turns out that there is some Group Policy we need to change in order to make it work.
The following image shows the steps for updating a specific group policy with a setting that will describe the path of the binaries required to update Windows 8.1 software, that mean, that you need to mount your Windows 8.1 installer ISO or put your Windows 8.1 installer DVD.
Update Group Policy in Windows 8.1 for supporting Windows 8.1 system updates
Then you just add the feature .NET Framework 2.0 using the regular Programs section in control panel.
Add .NET Framework 2.0 and 3.0 to Windows 8.1
Tomorrow morning April 10, 2014 I will be part of the Chat with the Experts: All you ever wanted to know about SharePoint, but were afraid to ask online event where Spanish speaking professionals from all over Latin American and Spain will get together in a live Q&A kind of conversation around our favorite product and platform “SharePoint”. We bring together experts from the SharePoint community and we offer you to bomb us questions. Do you dare to ask what you always wanted to know about SharePoint and have never asked?
Some of the attendee are knowledgeable SharePoint experts, Speakers and MVPs:
- Gustavo Vélez
- Juan Carlos González
- Fabián Imaz
- Alberto Díaz
- David Martos
- Miguel Tabera
- Mario Cortes
- Edin Kapic
- Gerardo Reyes
- Ricardo Muñoz
- Juan Manuel Herrera
- Juan Andrés Valenzuela
- Haarón González
- Juan Pablo Pussacq
- Andrés Rojas
- Vielka Rojas
- Adrian Díaz
- David Sánchez
- Santiago Porras
- Marco Antonio Canales
This event brings together people from Spain, Costa Rica, Colombia, Mexico, Argentina, basically anywhere Hispanic. Thanks for the good vibes.