SharePoint News – Download SharePoint Server 2016 preview now


microsoft_logo_56x56

SharePoint Server 2016 Preview

Yes! SharePoint Server 2016 has finally been released as a preview installation

Long awaited for, longed for by many, feared by the competition…

On  the 24th of august, Microsoft released a preview of the next generation of SharePoint onprem, SharePoint Server 2016. Last I Heard, the release is due sometime Q1 – Q2 of 2015.
Make sure that you have room, the ISO alone is 2.84GB in size…

DOWNLOAD
(Or go straight to the ISO download)

Prerequisites, it will run on

•Windows Server 2012 R2
•Windows Server Technical Preview 2

About the Product from Microsoft

SharePoint Server 2016 IT Preview has been designed, developed, and tested with the Microsoft Software as a Service (SaaS) strategy at its’ core.
Drawing extensively from that experience, SharePoint Server 2016 IT Preview is designed to help you achieve new levels of reliability and performance, delivering features and capabilities that simplify administration, protect communications and information, and empower users while meeting their demands for greater business mobility.
You can choose from a traditional on-premises deployment, a hosted service with Microsoft Office 365 sites powered by Microsoft SharePoint Online, deployment in Azure Infrastructure as a Service (IaaS), or a mix of these options with a hybrid approach, enabling you to enrich traditional on-premises scenarios with the innovation in the cloud.
Need more information about SharePoint Server 2016 IT Preview? See the  product details page.SharePoint Server 2016 IT Preview builds on the investments of previous SharePoint releases to help:
1.Lower IT costs with a cloud inspired infrastructure and scalable collaboration platform
2.Better manage risk by safeguarding your business with secure and reliable capabilities
3.Deliver modern collaboration experiences across devices and screens’

To install SharePoint Server Preview

1.Review SharePoint Server 2013  system requirements
2.Download and install full-featured software for a 180-day trial
3.When prompted, use the following product key: NQTMW-K63MQ-39G6H-B2CH9-FRDWJ

 

References and Credits

Myself, I get all the credit this time as well! 🙂 

   _________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

A quick-guide to setting up OWA with SharePoint 2013 – start to finish


Future and existing Office Web Apps – OWA Lovers!
😁
This time, I just found that a quick guide like this was something that I needed myself, and since I could not find anything that was short and compact enough, I made my own guide…
This Little guide is completely based on the TechNet articles mentioned in the references section, but this is nontheless a lot shorter and easier to follow.

Oakwood_clockx

The old Clock at Oakwood station



Click your OWA task of choice:
Step 1
Prepare a 2008 R2 Server to run OWA
Prepare a 2012 Server to run OWA
Step 2
Install Office Web Apps Server
Step 3
Deploy a single-server Office Web Apps Server farm that uses HTTPS
Step 4
Configure SharePoint to use OWA over https (recommended)
Configure SharePoint to use OWA over http
Additional
Disconnect SharePoint from OWA farm
Configure the Default open behavior for documents
Credits and References




Prepare a 2008 R2 server to run Office Web Apps Server

1. Install the following software (Minimum required):

2. Import the server module
(In a PowerShell prompt running as administrator and with the SharePoint snapin loaded)
Import-Module ServerManager

3. Add the required Features and Roles by running this command:
Add-WindowsFeature Web-Server,Web-WebServer,Web-Common-Http,Web-Static-Content,Web-App-Dev,Web-Asp-Net,Web-Net-Ext,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,Web-Security,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Dyn-Compression,Web-Mgmt-Console,Ink-Handwriting,IH-Ink-Support

4. Restart the server if prompted when the command finishes.

5. Done

TechNet Reference
Back to menu




Prepare a 2012 server to run Office Web Apps Server

1. In a PowerShell prompt running as administrator, add the required Features and Roles by running this command:
Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices

2. Done

TechNet Reference
Back to menu



Install Office Web Apps Server
1. Download Office Web Apps Server from the Microsoft Download Center (Link).

2. Run Setup and walk through the steps in the wizard.
Windows Server 2012, open the .img file directly and run Setup.exe
Windows Server 2008 R2 SP1, use any program that can mount or extract .img files. Then run Setup.exe

3. Download and install the Office Web Apps Server update KB2810007.

TechNet Reference
Back to menu



Deploy a single-server Office Web Apps Server farm that uses HTTPS

If components of the .NET Framework 3.5 were installed and then removed, you might see “500 Web Service Exceptions” or “500.21 – Internal Server Error” messages when you run OfficeWebApps cmdlets. To fix this, run the following sample commands from an elevated command prompt to clean up settings that could prevent Office Web Apps Server from functioning correctly:
In Windows Server 2008 R2:
%systemroot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru
iisreset /restart /noforce
In Windows Server 2012:
dism /online /enable-feature /featurename:IIS-ASPNET45

1. Create the Office Web Apps Server farm

New-OfficeWebAppsFarm -InternalUrl <InternalURL> -ExternalUrl <ExternalURL> -CertificateName <CertificateName> -EditingEnabled

<InternalURL> FQDN name of the server that runs Office Web Apps Server
<ExternalURL> FQDN name that can be accessed on the Internet
<CertificateName> Is the friendly name of the https/SSL certificate used
-EditingEnabled, optional and is added to enable editing in Office Web Apps

2. Verify that the Office Web Apps Server farm was created successfully

Go to the https://internal.url.com/hosting/discovery
If you see a (WOPI)-discovery XML file in your web browser then all is good.

Depending on the security settings of your web browser, you might see a message that prompts you to select Show all content before the contents of the discovery XML file are displayed.

3. Done

TechNet Reference
Back to menu



Configure SharePoint to use OWA over https (recommended)
(In a PowerShell prompt running as administrator and with the SharePoint snapin loaded)

The Web Application to be used must be configured to use Claims as authentication method, else OWA will not work.

1. Create new binding:
New-SPWOPIBinding -ServerName <WacServerName>
(<WacServerName> must be the FQDN internal URL)

2. Verify current zone:
Get-SPWOPIZone

3. Change to internal-https if it is set to http:
Set-SPWOPIZone –zone “internal-https

4. Verify https:
Get-SPWOPIZone

5. Verify functionality in a document library (Not using the system account, appearing as sharepoint\system)
Click on the ‘Three dots’ after a documents name and see if you get a preview, if you do, its all good!

6. Done

TechNet Reference
Back to menu



Configure SharePoint to use OWA over http
(In a PowerShell prompt running as administrator and with the SharePoint snapin loaded)

The Web Application to be used must be configured to use Claims as authentication method, else OWA will not work.

1. Create new binding:
New-SPWOPIBinding -ServerName -AllowHTTP
( must be the FQDN internal URL)

2. Verify current zone:
Get-SPWOPIZone

3. Change to internal-http:
Set-SPWOPIZone –zone “internal-http”

4. Verify http:
Get-SPWOPIZone

5. Check AllowoverHttp setting:
(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

6. Set AllowOAuthOverHttp to True.
$config = (Get-SPSecurityTokenServiceConfig)
$config.AllowOAuthOverHttp = $true
$config.Update()

7. Verify change:
(Get-SPSecurityTokenServiceConfig).AllowOAuthOverHttp

8. Verify functionality in a document library (Not using the system account, appearing as sharepoint\system)
Click on the ‘Three dots’ after a documents name and see if you get a preview, if you do, its all good!

9. Done

TechNet Reference
Back to menu



Disconnect SharePoint from OWA farm
(In a PowerShell prompt running as administrator and with the SharePoint snapin loaded)

1. Remove the binding
Remove-SPWOPIBinding –All:$true

2. Done

TechNet Reference
Back to menu



Configure the Default open behavior for documents

1. On a per farm level: Adjust the default open behavior on a per-file-type basis by using the New-SPWOPIBinding and Set-SPWOPIBinding Windows PowerShell cmdlets.

2. On a per Site Collection level by activating the ‘Open Documents in Client Applications by Default’ site Collection feature.

3. On a per Document library level using the Library setting – Advanced setting – ‘Default open behavior for browser-enabled documents’

4. Done

TechNet Reference
Back to menu




References:

Deploy Office Web Apps Server
http://technet.microsoft.com/en-us/library/jj219455.aspx

Configure SharePoint 2013 to use Office Web Apps
http://technet.microsoft.com/en-us/library/ff431687.aspx

Configure the default open behavior for browser-enabled documents (Office Web Apps when used with SharePoint 2013)
http://technet.microsoft.com/en-us/library/ee837425.aspx

Set-SPWOPIBinding
http://technet.microsoft.com/en-us/library/jj219454.aspx

Plan Office Web Apps (Used with SharePoint 2013)
http://technet.microsoft.com/en-us/library/ff431682.aspx

SharePoint authentication requirements for Office Web Apps
http://technet.microsoft.com/en-us/library/ff431682.aspx#authentication

Configuring Office Web Apps in SharePoint 2013 (Steve Peschka – Microsoft)
http://blogs.technet.com/b/speschka/archive/2012/07/23/configuring-office-web-apps-in-sharepoint-2013.aspx

Enabling Licensing and Editing for Office Web Apps in SharePoint 2013 (Steve Peschka – Microsoft)
http://blogs.technet.com/b/speschka/archive/2012/12/31/enabling-licensing-and-editing-for-office-web-apps-in-sharepoint-2013.aspx

Thanks to:

Mattias Gutke! All the time dude!
Ankie D – a great customer who has forced me to learn more on OWA
Stefan K – Another customer who made me refresh my knowledge
Steve Peschka, he wrote the original guide…see ref section


___________________________________________________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

SharePoint 2013 and Office Web Apps 2013 resources


I just thought that it would  be a nice thing to have key links to getting started with Office Web Apps 2013 all in one place:

Download Microsoft Office Web Apps Server

Download Language Packs for Microsoft Office Web Apps Server

TechNet: Deploy the infrastructure: Office Web Apps Server

TechNet: Plan Office Web Apps (Used with SharePoint 2013)

TechNet: Overview of Office Web Apps and how they work on-premises with SharePoint 2013

The Licensing for Office Web Apps is all new:

Licensing Office Web Apps for editing Office files

          Office Web Apps licensing offers two options:

  • View-only. By default, Office Web Apps is view-only. View-only functionality is provided for free.
  • Edit and view. You must purchase an editing license to use the editing features of Office Web Apps with SharePoint 2013. You enable editing when you create the Office Web Apps Server farm.

Enterprise customers who are licensed for Office 2013 through a Volume Licensing program can enable Office Web Apps editing for SharePoint 2013 on-premises. This helps make sure that users have Office editing capabilities at home or in other locations where Office clients might not be installed. Editing licenses for Office Web Apps are not available for separate purchase.

For exact details about your license, refer to the Microsoft Software License Terms that is shown when you install Office Web Apps Server.

SharePoint 2013 provides new license enforcement that works with Office Web Apps. If you enable SharePoint licensing and then enable Office Web Apps editing, only the users who have the appropriate license, which is known as OfficeWebAppsEdit, can actually edit Office files in a browser. If no Office Web Apps editing licenses are applied for users, only viewing is supported. For more information about how licensing works in SharePoint 2013, see Configure licensing in SharePoint Server 2013. The EditingEnabled parameter that enables editing is described in New-OfficeWebAppsFarm and Set-OfficeWebAppsFarm.

Read more here: Licensing Office Web Apps for editing Office files

Remember also, that in 2013 the Office Web Apps server/farm is a shared resource between SharePoint Server 2013, Lync Server 2013 and Exchange Server 2013.

Browser support, see image:

As you can see, owa now supports most common browsers


_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

SharePoint 2013 is finally here!! Download it now


Hi friends.

I just got the word, SharePoint 2013 has been released for download on MSDN and Technet. This is true also for Office 2013, and a few other products…like Project 2013, Visio 2013, Lync 2013, Exchange 2013. The 15 Wave have hit us…
May the race begin, download…!!

TechNet and MSDN subscribers will find the bits there, Volume Agreement customers will find the bits in the normal Volume Lincensing download location.

RTM Evaluation copies of Server can be downloaded here: Download Microsoft SharePoint Server 2013
RTM copies of Foundation can be downloaded here: Download Microsoft SharePoint Foundation 2013 RTM
RTM copies of SharePoint Designer 2013 can be downloaded here: Download Microsoft SharePoint Designer 2013 RTM

_________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn