Archive

Posts Tagged ‘SharePoint Server 2013’

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

October 15, 2013 9 comments

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

Configure ULS log and Usage and Health log location

June 5, 2013 6 comments

SharePoint jokers!

If you left the settings in SharePoint 2013 as default when installing and configuring, then you will probably have a log path that looks like this for both the ULS log and the Usage and Health log.
C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS

If you want to change this to a new path, maybe on a different disk like D: (recommended) or on a simpler path easier to remember, use the following commands:

You will need to run the commands in a PowerShell running as administrator and you will also need to load the SharePoint snapin first, add-pssnapin.
add-pssnapin microsoft.sharepoint

For the Diagnostics log(ULS)
set-SPDiagnosticConfig -LogLocation “D:\Program Files\Common files\Microsoft shared\Web server extensions\15\LOGS”
or
set-SPDiagnosticConfig -LogLocation “D:\SharePoint Logs\ULS”

For the Usage and Health log
set-SPUsageService -UsageLogLocation “C:\Program Files\Common files\Microsoft shared\Web server extensions\15\LOGS”
or
set-SPUsageService -UsageLogLocation “D:\SharePoint Logs\Health”

set-SPDiagnosticConfig -LogLocation “C:\Program Files\Common files\Microsoft shared\Web server extensions\15\LOGS”

In my environment, the Diagnostics trace log path looks like this:
ULS2

ULS1

And for the Usage and Health log, it looks like this:

U&H2

U&H1

References:

(If the two paths Point to a different location then you may see this in your event log)
6398 ‚Äď The Execute method of job definition‚ĶSPUsageImportJobDefinition

https://blog.blksthl.com/2013/05/27/6398-the-execute-method-of-job-definition-spusageimportjobdefinition/

ULS Log Viewer download
http://archive.msdn.microsoft.com/ULSViewer

Thanks to:

Ankie at my customers, who pointed out the Usage and Health log issue 6398 in the first place.


___________________________________________________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

A quick guide to configuring the Loopback check

May 7, 2013 7 comments

Update: A free tool is¬†available that does all this for you in a GUI: Loopback Check configuration Tool released ‚Äď free¬†download

Hi dear friends!

401.1 Access denied…
If you try to access your newly created web application with a real nice FQDN or NetBIOS name¬†and you end up getting a 401.1 Access denied…

Even after adding the site¬†to the¬†local intranet zone in IE…
Even after beeing prompted 3 times and filling in the correct credentials…
After setting up your Search to crawl you sites in a small farm whith crawl and web services on the same server…

You check and doublecheck your credentials, you add yourself as the farm admin, you try logging on with the farm account, but nothing…still 401.1…

I know this has been written about many times Before, but¬†some things seem to still be missing…
Now everyone seems comfortable with the sparse description on how to ‘add hosts to the list’ which is pretty much what you do when configuring the loopback check the ‘secure way’. You can also disable the loopbackcheck completely, but why if there is no real reason. Read Spencer Harbars excellent post¬†on the topic if you need¬†explaining why this is so. It is a few years but it is still the truth!

The KB article 896861¬†for this is an old one and the title does not really tell you that this is the one you are looking for, ‘type the host name or the host names for the sites that are on the local¬† computer, and then click OK.’ is not crystal…

Jump to:
Configure Loopback check using the GUI
Configure Loopback check using Powershell
Credits and References


What you need to do is this step by step:

In ‘Metro’ mode, type regedit

Regedit1x

Regedit will most likely be the only result, hit enter

Regedit2

In regedit, find the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0

First…

Regedit3x

then…

Regedit4x

Now, create a Multi-String Value under the MSV1_0 key.

Regedit5x

Type in the name of the new Multi-String value: ‘BackConnectionHostNames’, Hit Enter.

Regedit6x

Right click on the value BackConnectionHostNames and coose Modify.

Regedit7x

Add the URL you want to be able to access from a local browser on the server.

Regedit8

Don’t know why, but I seem to Always get this. Click Ok.

Regedit9

Viola!

Regedit10x

Adding multiple URL’s to the list of ‘trusted’ URL’s, simply¬†make a new line¬†between them.

Regedit11

That will look like this.

Regedit12x

To be extra sure that nothing else will sabotage functionality, check so that the URL’s are added to DNS.
(Or local hosts file)

DNS1x

Check so that the URL’s are added as bindings in IIS.

IIS1x

Verify that the URL’s are correct and are added to AAM.

AAM1x

Make sure that the URL is added to the Local Intranet Zone in Internet Explorer (if you need to browse the site from the server, NOT RECOMMENDED!).

IE3x

Try to access the URL in a browser.

IE1x

And the other URL.

IE2x

Done!

Doing the same using PowerShell

Using PowerShell to configure the Loopback check, requires two steps:

1. Add the multistring value to the registry
Get-Item -path “HKLM:\System\CurrentControlSet\Control\Lsa\MSV1_0” | new-Itemproperty -Name “BackConnectionHostNames” -Value (“coolsite.corp.balkestahl.se”, “alias.corp.balkestahl.se”) -PropertyType “MultiString”

2. Restart the IISADMIN service
Restart-Service IISADMIN

1. Add the multistring value to the registry

Given that you have Everything setup correctly, your AAM’s, your DNS entrys, (URL added to local intranetsites zone in IE), and so forth…you can use this single PowerShell command to exclude the URL’s for your sites from the loopbackcheck, this way, you don’t have to disable the loopbackcheck at all (Way better security).

The following command will add my two URL’s to the exclusion list, edit the values to add your own URL’s.

Run this in a PowerShell prompt running in elevaled mode/as Administrator

Get-Item -path “HKLM:\System\CurrentControlSet\Control\Lsa\MSV1_0” | new-Itemproperty -Name “BackConnectionHostNames” -Value (“coolsite.corp.balkestahl.se”, “alias.corp.balkestahl.se”) -PropertyType “MultiString”

Running this will if Everything is done right, show this

Powershell1

This is how it will look if it succeeds!

Powershell2

If you get ‘The property already exists.’, then you already have the ‘BackConnectionHostNames’ value added to the registry, check using registry editor to see if you can delete it or if it has other values that need to be there.

After a successful execution, check the registry to verify

Regedit12x

2. Restart the IISADMIN service

Now you have to restart the IISADMIN service in order for it to ‘reread’ the registry values and implement our Changes.
This is easy, in a PowerShell prompt running in elevaled mode/as Administrator

Restart-Service IISADMIN

Powershell3

Note the typo/bug in the text, it says stopping twice but what it does it stopping and starting

Done!

The command line¬†in step 1¬†will add two (2) entries to the list, coolsite.corp.balkestahl.se and alias.corp.balkestahl.se. If you need to add more URL’s, add them to the Values, like: -Value (“coolsite.corp.balkestahl.se”, “alias.corp.balkestahl.se”, “mycoolnetbiosname”, “extraname.corp.balkestahl.se”).

Make sure that the doublequotes are formated in the proper way if you copy from this post!

That would make the command

Get-Item -path “HKLM:\System\CurrentControlSet\Control\Lsa\MSV1_0” | new-Itemproperty -Name “BackConnectionHostNames” -Value (“coolsite.corp.balkestahl.se”, “alias.corp.balkestahl.se”, “mycoolnetbiosname”, “extraname.corp.balkestahl.se”) -PropertyType “MultiString”

and

Restart-Service IISADMIN -force

References:

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version
http://support.microsoft.com/kb/896861

DisableLoopbackCheck & SharePoint: What every admin and developer should know. (Spencer Harbar folks)
http://www.harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx

Can‚Äôt crawl web apps you KNOW you should be able to crawl (Todd Klindt’s oldie but goodie)
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=107

Thanks to:

As Always, Mattias Gutke! Now at CAG. Always a great help and second opinion!


___________________________________________________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn

SharePoint Server 2013 Language Packs

April 16, 2013 13 comments

Hi dear friends!

Update: Additional SharePoint Server 2013 LP’s (the full list) made GA, Generally Available since April 30 – SharePoint Server 2013 LP’s

Language support in SharePoint 2013 onprem…
(Lacking better info, I assume that the same list applies to SharePoint online)

IMG_0987x

Remember this anyone?

If you are like me you have not seen anything official on the topic of Language Packs and release dates and availability yet (written April 16, 2013).
I don’t know if anyone has put this info¬†out there yet, but I have not found it and then I figure it won’t hurt to do it here I guess…

In my case, I was looking for Swedish, but others need to find their special local language, now I have some info for all of you:

Jump to:
SharePoint Server 2013 LP’s¬†(44 LP’s)
SharePoint Foundation 2013 LP’s¬†(44 LP’s)
Office Web Apps 2013 LP’s¬†(44 LP’s)
Credits and References

 SharePoint in the languages listed under Server Language packs are also available in a localized server version, these are also available at MSDN  


SharePoint Server 2013
Since (March 28) April 30th, all Language Packs are now available as a free download (link) Select your language in the dropdown or use the directlink in the list below.
(serverlanguagepack.img) I recommend renaming the files when downloaded since all LP’s have the same name, add for example the two letter code for your country after the filename: serverlanguagepack_se.exe (Swedish SPS LP)

TechNet suggests you take one of the following actions:
For Windows Server 2012, open the .img file directly and run Setup.exe (double-click it).
For Windows Server 2008 R2 SP1, use a program that can mount or extract .img files. Then run Setup.exe (double-click it).

Generally Available Server Language packs listed:

Language Release date
English March 28, 2013
German April 30, 2013
French April 30, 2013
Hebrew April 30, 2013
Italian April 30, 2013
Japanese April 30, 2013
Spanish April 30, 2013
Catalan April 30, 2013
Portuguese-Brazil April 30, 2013
Chinese – Simplified April 30, 2013
Chinese – Traditional April 30, 2013
Dutch April 30, 2013
Korean April 30, 2013
Russian April 30, 2013
Czech April 30, 2013
Greek April 30, 2013
Hungarian April 30, 2013
Romanian April 30, 2013
Thai April 30, 2013
Turkish April 30, 2013
Ukrainian April 30, 2013
Serbian (Latin) N/A! April 30, 2013
Serbian (Cyrillic) April 30, 2013
Slovak April 30, 2013
Slovenian April 30, 2013
Bulgarian April 30, 2013
Croatian April 30, 2013
Estonian April 30, 2013
Kazakh April 30, 2013
Latvian April 30, 2013
Lithuanian April 30, 2013
Danish April 30, 2013
Finnish April 30, 2013
Norwegian (Bokmål) April 30, 2013
Swedish April 30, 2013
Arabic April 30, 2013
Hindi April 30, 2013
Polish April 30, 2013
Portuguese-Portugal April 30, 2013
Malay (Malaysia) April 30, 2013
Indonesian April 30, 2013
Vietnamese April 30, 2013
Galician April 30, 2013
Basque April 30, 2013

You can also find these on MSDN (and TechNet) (link):
(nn_office_server_2013_language_pack_x64_dvd_nnnnnnn.iso)

SharePoint Foundation 2013
Language Packs for SharePoint Foundation 2013 is a free download (link)
(sharepointlanguagepack.exe) I recommend renaming the files when downloaded since all LP’s have the same name, add for example the two letter code for your country after the filename: sharepointlanguagepack_se.exe (Swedish SPF LP)
Size: Aproximately 29 MB

Language Release date
English October 30, 2012
German October 30, 2012
French October 30, 2012
Hebrew October 30, 2012
Italian October 30, 2012
Japanese October 30, 2012
Spanish October 30, 2012
Catalan October 30, 2012
Portuguese-Brazil October 30, 2012
Chinese – Simplified October 30, 2012
Chinese – Traditional October 30, 2012
Dutch October 30, 2012
Korean October 30, 2012
Russian October 30, 2012
Czech October 30, 2012
Greek October 30, 2012
Hungarian October 30, 2012
Romanian October 30, 2012
Thai October 30, 2012
Turkish October 30, 2012
Ukrainian October 30, 2012
Serbian (Latin) N/A! October 30, 2012
Serbian (Cyrillic) October 30, 2012
Slovak October 30, 2012
Slovenian October 30, 2012
Bulgarian October 30, 2012
Croatian October 30, 2012
Estonian October 30, 2012
Kazakh October 30, 2012
Latvian October 30, 2012
Lithuanian October 30, 2012
Danish October 30, 2012
Finnish October 30, 2012
Norwegian (Bokmål) October 30, 2012
Swedish October 30, 2012
Arabic October 30, 2012
Hindi October 30, 2012
Polish October 30, 2012
Portuguese-Portugal October 30, 2012
Malay (Malaysia) October 30, 2012
Indonesian October 30, 2012
Vietnamese October 30, 2012
Galician October 30, 2012
Basque October 30, 2012


Office Web Apps 2013
Language Packs for Office Web Apps 2013 is a free download (link)
(wacserverlanguagepack.exe) I recommend¬†renaming the files when downloaded since all LP’s have the ame name, add for example the two letter code for your country after the filename: wacserverlanguagepack_se.exe (Swedish LP)
Size: Aproximately 25.5 MB

List last updated May 23, 2013

Language Release date
English
German
French
Hebrew
Italian
Japanese
Spanish
Catalan
Portuguese-Brazil
Chinese – Simplified
Chinese – Traditional
Dutch
Korean
Russian
Czech
Greek
Hungarian
Romanian
Thai
Turkish
Ukrainian
Serbian (Latin) N/A!
Serbian (Cyrillic)
Slovak
Slovenian
Bulgarian
Croatian
Estonian
Kazakh
Latvian
Lithuanian
Danish
Finnish
Norwegian (Bokmål)
Swedish
Arabic
Hindi
Polish
Portuguese-Portugal
Malay (Malaysia)
Indonesian
Vietnamese
Galician
Basque


I hope that this will help you find what you need. This was the kind of info I was looking for and could not find so hopwefully it will help you save time.

References:

Language Packs for Microsoft Office Web Apps Server
http://www.microsoft.com/en-us/download/details.aspx?id=35490

Language Packs for SharePoint Foundation 2013
http://www.microsoft.com/en-us/download/details.aspx?id=35492

Office Server 2013 Language Pack on MSDN Subscriber Downloads
https://msdn.microsoft.com/en-us/subscriptions/securedownloads/hh442898.aspx#FileId=50889

Install or uninstall language packs for SharePoint 2013 (Foundation and Server)
http://technet.microsoft.com/en-us/library/cc262108.aspx

Thanks to:
Wictor Wil√©n who pointed out the simple fact to me that the Server LP’s were available on MSDN…a fact I had somehow managed to miss.


___________________________________________________________________________________________________

Enjoy!

Regards

Twitter | Technet Profile | LinkedIn