Export a document library using Export-SPWeb and itemurl


(This is my better version of the TechNet articles on the same CMDlet that does a poor job with the details, I hope that it will help some of you)
SharePoint 2010 | SharePoint 2013
Applies to:  SharePoint Foundation 2010 | SharePoint Server 2010 | SharePoint Foundation 2013 | SharePoint Server 2013 

Exports a site, list, or library.

Export-SPWeb [-Identity] <GUID/Name/SPWeb object> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-CompressionSize <Int32>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-HaltOnError <SwitchParameter>] [-HaltOnWarning <SwitchParameter>] [-IncludeUserSecurity <SwitchParameter>] [-IncludeVersions <LastMajor | CurrentVersion | LastMajorAndMinor | All>] [-ItemUrl <String>] [-NoFileCompression <SwitchParameter>] [-NoLogFile <SwitchParameter>] [-UseSqlSnapshot <SwitchParameter>] [-WhatIf [<SwitchParameter>]]


Export-SPWeb http://site –Path "c:\temp\site export.cmp" -ItemURL "/subsite/documents"

This example exports the document library at http://site/subsite/documents to a new file called ‘site export.cmp' in the ‘C:\temp’ directory.





Identity Required Specifies the URL or GUID of the Web to be exported. The type must be either
– a valid GUID, in the form ‘12345678-90ab-cdef-1234-567890bcdefgh’
– a valid name of a SharePoint site (for example, MySPSite1)
or a URL: http://blog.blksthl.com
or an instance of a valid SPWeb object
Path Required Specifies the name of the export file. If the -NoFileCompression parameter is used, a directory must be specified; otherwise, any file format is valid.
Example: “c:\temp\exportedsite.cmp” or with the -NoFileCompression “c:\temp\exportedsite\”
AssignmentCollection Optional Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment   object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.

When the Global parameter is used, all objects are contained in the global store. If objects are not immediately used, or disposed of by using the Stop-SPAssignment command, an out-of-memory scenario can occur.
CompressionSize Optional Sets the maximum file size for the compressed export files. If the total size of the exported package is greater than this size, the exported package will be split into multiple files.
Confirm Optional Prompts you for confirmation before executing the command. For more information, type the following   command: get-help about_commonparameters
Force Optional -Force Forcefully overwrites the export package if it already exists.The type must be either of the following values:
FalseThe default value is False.
HaltOnError Optional Stops the export process when an error occurs.
HaltOnWarning Optional Stops the export process when a warning occurs.
IncludeUserSecurity Optional Preserves the user security settings except for SPLists that have broken inheritance and item level   permissions set.
(Use Import-SPWeb with –IncludeUserSecurity to preserve security on import)
IncludeVersions Optional Indicates the type of file and list item version history to be included in the export operation. If the
-IncludeVersions parameter is absent, the Export-SPWeb cmdlet by default uses a value of CurrentVersion. The type must be any one of the following versions:
LastMajor “Last major version for files and list items (default)”
CurrentVersion “The current version, either the last major version or the last minor version”
LastMajorAndMinor “Last major and last minor version for files and list items”
All “All versions for files and list items”
ItemUrl Optional Specifies the relative path to the object to be exported. Can also be a GUIDThe type must be a valid relative path, for example, /Subsite/Documents
or a valid GUID in the form: 12345678-90ab-cdef-1234-567890bcdefgh
NoFileCompression Optional Either enables or disables file compression in the export package. The export package is stored in the   folder specified by the Path parameter or Identity parameter. We recommend that you use this parameter for performance reasons. If compression is enabled, the export process can increase by approximately 30 percent.
NoLogFile Optional Suppresses the generation of an export log file. If this parameter is not specified, the Export-SPWeb   cmdlet will generate an export log file in the same location as the export package. The log file uses Unified Logging Service (ULS).It is recommended to use this parameter. However, for performance reasons, you might not want to generate a log file.
UseSqlSnapshot Optional Specifies a SQL Database Snapshot will be created when the export process begins, and all exported   data will be retrieved directly from the database snapshot. This snapshot will be automatically deleted when export completes.
WhatIf Optional Displays a message that describes the effect of the command instead of executing the command. For   more information, type the following command: get-help about_commonparameters



Export a site, list, or document library (Search Server 2010)

Thanks to:

Mattias Gutke – CAG – My main man!


Good Luckl!!


Twitter | Technet Profile | LinkedIn


Move your SharePoint IIS sites from the systemdrive(C:)

Move your SharePoint IIS sites from the systemdrive(C:)
or avoid putting them there in the first Place.


Do you see the lion that is totally in the wrong Place…or is it the Jeeps that are…?

Deal fellow SharePointlovers!

This time, I’ll try to show you how to avoid the messed up situation most SharePoint installations are in, with everything on the systemdrive, or C:
Now, us people have over time been better and better at one thing, we understand that the logfiles should not be located on the systemdrive, so we have learned over time to move the ULS log and the Usage and Health log from C:, some have even been clever enough to move even the IIS log from C:

But, what do we still always, always, always, find installed on C:?… … …yes, C:\inetpub!

It not very strange though, the developers of Windows Server have made a point out of not giving us an option to install inetpub on a different path, not unless you do an unattended installation or otherwise script or Control your installation. The ‘Add/Remove roles’ wizards in Server 2008, 2008R2 and 2012 all lack this option (for a reason).

BUT! This is intentially, the default inetpub location should and must be in the systemdrive, IIS is considered an operating system Component and has to be there for a number of reasons. At the end you will find a link to a KB article that explains this in more detail. Leave inetpub and its subfolders where it is!

So, why would we want to do this anyway
why move the inetpub and all of its content, or at least the separate site catalogs to a different drive?
– Separation (Performance and Security)
– Compartmentalization (Performance and Security)
Having averything on the same drive is bad for a few reasons, primarily performance and security. Perfomance since the OS is on the C drive and security because if an attacker by some means gets access to a different less secure applications sitecatalog, they also get access to the systemdrive and possible also all other webapplication sitecatalogs. Moving them to other drives, same or different, helps mitigate both possible issues.
I therefore recommend doing this:

Do your regular installation, add the Web Server role and let the inetpub folder end up on C:, like I said, no worries. Whats important for us will not be located there anyway.
Next, edit the registry to make the default location of inetpub be for example D: (unless this is were you will be putting all of your logfiles, then select a third or fourth drive)
Install the SharePoint as you would normally do, Central administration will now end up were you pointed the default location.
Create your Web Applications using the GUI or PowerShell and leave out the path, the IIS sites will be were you wanted them.

So, how do we do this in more detail? A Guide…

Configure the Web Server(s)

1. Configure the default location

On all of your web servers in the farm, and on your Central Administration server(s), edit the registry key that Controls the default location:

Start regedit by, Right clicking in the very lower left corner and you will get a list of actions, click on Run.


Type Regedit and click Ok.


Click Yes in the UAC dialog.


In Registry Editor, we locate the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp



Under ‘InetStp’ we have a number of keys.


Locate and Edit the key PathWWWRoot from the default: (%systemdrive%)


to: (D: or where you prefer to locate it, E: F: G: H:…)


There you go! All set, no IIS reset or restarts of any kind required.
Like said before, go on and do this on all servers that will host a webserver (WFE or CA). If you don’t, then you will have an inconsistent setup making Everything very hard to setup and t-shoot.

2. Add SharePoint
After this has been changed on all of you r web servers, you can go ahead and install the SharePoint binaries and configure your farm, The Central Administration site will now be located on the drive you have specified, it will be in the exact same path as it normally would but on a different drive. For example: ‘D:\inetpub\wwwroot\wss\VirtualDirectories\20000\’

Note that the Central Administration UI will now be default suggest a different path:


If you create a new site using PowerShell, it will also by default put it in D: even if you don’t specify any path:

New-SPWebApplication -Name TheVeryFirst -ApplicationPool SharePoint -HostHeader theveryfirst.corp.balkestahl.se -Port 80 -Url theveryfirst.corp.balkestahl.se -DatabaseServer blksthl-sql -DatabaseName SP11_Content_TheVeryFirst

As you can see, were done! 🙂


For the logfiles, I’ll make a separate post, they should also be moved, more so even than the sitefolders. Logfiles will fill up the disks, they will slow performance and maybe most importantly, they contain delicate information that you want to keep separated from the OS and IIS.


Guidance for relocation of IIS 7.0 and IIS 7.5 content directories

Configure ULS log and Usage and Health log location

Thanks to:

Mikael Nyström (The Deployment Bunny) – Truesec
Mattias Gutke – CAG


Good Luckl!!


Twitter | Technet Profile | LinkedIn

Configure ULS log and Usage and Health log location

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”
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”
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:


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




(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


ULS Log Viewer download

Thanks to:

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




Twitter | Technet Profile | LinkedIn

6398 – The Execute method of job definition…SPUsageImportJobDefinition


Have this critical error in your Eventlog?

The Execute method of job definition Microsoft.SharePoint.Administration.SPUsageImportJobDefinition (ID ef497ec2-0cbf-4458-91ea-db75422fd9da) threw an exception. More information is included below.

Access to the path ‘C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS’ is denied.

This is a really annoying error in the eventlog, there are many references to this out there but most or even all take the easy way out and that is not for me 🙂

Two suggestions I have seen(that I do not recommend):

1. Add the ‘serviceaccount’ (usually the farm account) to the local administrators Group effectively giving the account full access to the entire filesystem.

2. Give the service account ‘serviceaccount’ (usually the farm account) read/write permissions to the LOGS folder.

Both are wrong, if the system would need access to this Place, why does it not have that allready?
In a real Life scenario I had this in the customers logs, when t-shooting I eventually figured out why they had it. In this customers Environment we had moved the ULS log location.
Central Administration/Monitoring/Configure Diagnostic Logging/Path
We had changed it (during PowerShell setup) to D: as one would…


So far so good, this will not in itself cause you any issues or events.
However, it as the other configurable location that did it. Usage and Health data…

This setting looked like this:


This was the reason…why this setting eaither was changed together with the log or if it would still have access…but no.
We ended up changing this path to D: as well, after all, this is what we really wanted anyway, no eccessive data on C:

Hope this helps anyone else.

Good luck!

Thanks to:

Mattias Gutke at CAG. My main man…




Twitter | Technet Profile | LinkedIn

SharePoint 2013 page loads takes a very long time

Short version: Stopping the Distributed cache service gave me great performance! From 6.10 s to 79 ms


Something is just a liiitle bit off…?

Long story: This is a bit of reality right here…
I was about to give up on one of my labb SharePoint 2013 Environments because it was so extremely slow all the time.
Warmup scripts, reloads, more memory, more CPU, stopping services, stopping search…nothing helped.

I had a constant loadtime of all aspx pages of 6+ seconds, 6.10-6.20 something. Even when the page was just loaded and I pressed F5 to reload, it still took 6.10 seconds.
This was an environment that gave you sensitive nerves…

So, after looking for any solution or more like looking for the little issue that caused this all day, I gave up more or less.
– CPU was at a maximum 40% on SQL, SharePoint cranked it up to 18%…
– Memory consumtion was at 25% of the 12GB SharePoint had…
– SQL was Lightning fast to all other SharePoint farms…
– Network utilization showed about 100Kbps at the most…

I scavenged the internet as usual and found nothing but the standard: add more memeory, add more CPU, stop services, stop search…
None of that helped and I had tried it all…

Then…when all hope was lost, I got on a call with my excellent SharePoint buddy Mattias Gutke, we talked about the issue, his server on a laptop with SSD disks showed 50-100ms loadtime of all pages, reload did nopt even produce a flicker…
Then as often happens, we came to discuss the Distributed cache service, what it did and why it was there and so on…I had already had a look at it but could not find any reason why a default cache would give me this lousy performance. Then, I had a look at the timestamp in the F12 Developer dashbord – Network tab – Start capturing. I saw the home.aspx load and it took the usual 6.10 seconds.
The timestamp could be found in the detailed view and on the response header.
I memorized the timestamp (that was in GMT timezone) and opened up my ULS log. In the log at the exact time of the response header, I saw errors from the distributed cache.


I decided that t-shooting the distributed cache would have to wait, it was getting late…but, before disconnecting the Lync call with Mattias, we decided to try and see just what would happen if I stopped the distributed cache service and loaded the page.
Said and done:


Now, loaded the same site:


Whit the Distributed cache service running:


Notice any difference? Now my SharePoint farm is Lightning fast!!! From 6.10 seconds down to 79 ms!

Why is this so then you ask? No idea, something misconfigured or perhaps this is standard when using a single SharePoint server…anyway, today I don’t care.
Stop the service and the performance is great!

Hope this may help you as it did me!

Thanks to:

Mattias Gutke at CAG. Again, my SharePoint sparring partner no 1…




Twitter | Technet Profile | LinkedIn

A quick guide to configuring the Loopback check

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


Regedit will most likely be the only result, hit enter


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





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


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


Right click on the value BackConnectionHostNames and coose Modify.


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


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




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


That will look like this.


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


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


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


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!).


Try to access the URL in a browser.


And the other URL.



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


This is how it will look if it succeeds!


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


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


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


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”


Restart-Service IISADMIN -force


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

DisableLoopbackCheck & SharePoint: What every admin and developer should know. (Spencer Harbar folks)

Can’t crawl web apps you KNOW you should be able to crawl (Todd Klindt’s oldie but goodie)

Thanks to:

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




Twitter | Technet Profile | LinkedIn

SharePoint Server 2013 Language Packs

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)


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):

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
Chinese – Simplified
Chinese – Traditional
Serbian (Latin) N/A!
Serbian (Cyrillic)
Norwegian (Bokmål)
Malay (Malaysia)

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.


Language Packs for Microsoft Office Web Apps Server

Language Packs for SharePoint Foundation 2013

Office Server 2013 Language Pack on MSDN Subscriber Downloads

Install or uninstall language packs for SharePoint 2013 (Foundation and Server)

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.




Twitter | Technet Profile | LinkedIn