SharePoint Snippets

Living a SharePoint life

Thursday, February 23, 2017

New updates for SharePoint, Project Server, and Office 2013 Click-to-Run

The following non-security updates for SharePoint Server 2013 and 2016, Project Server 2013, and Office 2013 Click-to-Run are available now:

SharePoint 2016

KB 3141515

KB 314517

 

SharePoint 2013

KB 3115296

KB 3118286

KB 3141485

KB 3141519

KB 3141523

 

Project Server 2013

KB 3141525

 

Office 2013 Click-to-Run

Version: 15.0.4903.1002

Content from: Office Updates http://bit.ly/2law2IQ

Tuesday, February 7, 2017

February 2017 Non-Security Office Update Release

Listed below are the non-security updates we released on the Download Center and Microsoft Update yesterday. See the linked KB articles for more information.

Office 2013

Update for Skype for Business 2015 (KB3161988)

Update for Microsoft Office 2013 (KB3115489)

Update for Microsoft Office 2013 (KB3141491)

Update for Microsoft Office 2013 (KB3127966)

Update for Microsoft OneNote 2013 (KB3141494)

Update for Microsoft Office 2013 (KB3127972)

Update for Microsoft Outlook 2013 (KB3141495)

Update for Microsoft PowerPoint 2013 (KB3141461)

Update for Microsoft Project 2013 (KB3141499)

Update for Microsoft Visio 2013 (KB3141492)

 Office 2016

Update for Microsoft Office 2016 (KB3141504)

Update for Skype for Business 2016 (KB3141501)

Update for Microsoft Office 2016 (KB3114389)

Update for Microsoft Office 2016 (KB3141508)

Update for Microsoft Office 2016 (KB3127991)

Update for Microsoft Office 2016 (KB3141510)

Update for Microsoft Office 2016 (KB3141513)

Update for Microsoft Office 2016 (KB3141505)

Update for Microsoft Office 2016 (KB3128048)

Update for Microsoft OneNote 2016 (KB3141512)

Update for Microsoft Office 2016 (KB3128052)

Update for Microsoft Outlook 2016 (KB3141511)

Update for Microsoft PowerPoint 2016 (KB3128051)

Update for Microsoft Project 2016 (KB3141514)

Update for Microsoft Office 2016 (KB3141509)

Update for Microsoft Visio 2016 (KB3141500)

 

 

Content from: Office Updates http://bit.ly/2jZj70d

Thursday, February 2, 2017

Correction to the list of superseded Word Viewer updates

We made some corrections to the superseded updates lists in three previously released Word Viewer updates on Microsoft Update today. These updates are KBs 3118394, 3128043, and 3128044. There were no other changes to the fixes provided by these updates.

Content from: Office Updates http://bit.ly/2kx1JPc

Wednesday, February 1, 2017

Code Snippet: Load the SharePoint Office PnP Module in PowerShell

How do you load the PowerShell OfficeP PnP module for SharePoint?

Addendum: I've added a try/catch block to the code. This way you can be sure the module is loaded.

# Loading Office Online PnP Module
try {
    if((Get-Module "Microsoft.Online.SharePoint.PowerShell" -ErrorAction SilentlyContinue) -eq $null) {
        Import-Module Microsoft.Online.SharePoint.PowerShell
        Write-Host "PowerShell module Microsoft.Online.SharePoint.PowerShell initialized"
    }
    else {
        Write-Host "PowerShell module Microsoft.Online.SharePoint.PowerShell loaded"
    }
}
catch {
    throw "PowerShell module Microsoft.Online.SharePoint.PowerShell initialization failed"
    exit 3
}

Tuesday, January 17, 2017

Connect to Office365 via Office PnP behind a proxy

How do you connect to your SharePoint Office365 tenant with the PowerShell if you are locked behind a proxy? This hint will probably work for all kind of PowerShell scripts, not only for Office PnP. I tried this with the Microsoft SharePoint Online extensions as well and it worked.

So my problem was, the company I was working for, had a proxy which could not be bypassed. The proxy settings have been set by a GPO and the network settings where fine so far. However the proxy used user authentication to access the internet. Now if I want to use the SharePoint Online tools, I must authenticate my PowerShell session at the proxy so the tools can access the internet too.

The trick to get your PowerShell connected is quite simple. You only need to enter the following line:

[System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultCredentials

Now you should be able to connect to Office365 SharePoint without problems. If you don't want to enter this line every time you open a new PowerShell, you could add it to your PowerShell profile.

ise $PROFILE
then add this to the profile file:

#Set user default credentials for any webrequest
"Setting the users default credentials for WebRequests..." | Write-Host -ForegroundColor White
[System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultCredentials

Tuesday, January 10, 2017

January 2017 Office Update Release

The January 2017 Public Update releases for Office are now available!

This month, there are 2 security updates (1 bulletin) and 31 non-security updates.

Security bulletins:

All of the security and non-security updates are listed in KB article 3214449

A new version of Office 2013 Click-To-Run is available: 15.0.4893.1002

 

Content from: Office Updates http://bit.ly/2jrvEoc

Thursday, January 5, 2017

A certificate validation operation took nnn milliseconds and has exceeded the execution time threshold

After installing a new SharePoint 2013 farm, I noticed a few messages in the Windows event log:

A certificate validation operation took 14988.6926 milliseconds and has exceeded the execution time threshold. If this continues to occur, it may represent a configuration issue. Please see http://go.microsoft.com/fwlink/?LinkId=246987 for more details.
Source: SharePoint Foundation
Event ID: 8321
Level: Critical

As Microsoft states in their knowlege base article KB2625048:

The SharePoint server does not have access to the Internet, or the server is protected by a firewall that has limited ports open. In this situation, users intermittently experience long delays when they perform certain operations, such as logging in to the site or performing a search. Users may also encounter HTTP timeouts when they perform these operations.

The mean you must either let your server access the internet, what most of the time won't be possible due to policy reasons, or we need a other solution. Good for us that the knowlege base article offers two possible solutions.

Wednesday, January 4, 2017

January 2017 Non-Security Office Update Release

Listed below are the non-security updates we released on the Download Center and Microsoft Update yesterday. See the linked KB articles for more information.

Word Viewer

Update for Word Viewer (KB3141490)

Office 2013

Update for Microsoft Access 2013 (KB3118349)

Update for Skype for Business 2015 (KB3141468)

Update for Microsoft Office 2013 (KB3141474)

Update for Microsoft OneNote 2013 (KB3141465)

Update for Microsoft Outlook 2013 (KB3141466)

Update for Microsoft Project 2013 (KB3141470)

Update for Microsoft Visio 2013 (KB3141462)

Office 2016

Update for Microsoft Office 2016 (KB3127983)

Update for Microsoft Excel 2016 (KB3141472)

Update for Microsoft Office 2016 Language Interface Pack (KB3141450)

Update for Skype for Business 2016 (KB3128049)

Update for Microsoft Office 2016 (KB3141473)

Update for Microsoft Office 2016 (KB3127987)

Update for Microsoft Office 2016 (KB3127992)

Update for Microsoft Office 2016 (KB3128055)

Update for Microsoft OneNote 2016 (KB3141455)

Update for Microsoft Office 2016 (KB3128056)

Update for Microsoft Outlook 2016 (KB3141453)

Update for Microsoft Office 2016 (KB3141451)

Update for Microsoft Project 2016 (KB3141459)

Update for Microsoft Visio 2016 (KB3128045)

 

 

Content from: Office Updates http://bit.ly/2iJCmcv

Featured Post

The Retro Powershell - Looking good in 8-Bit | Part 1

I wrote a little script that, when placed in your PowerShell Profile, will print a message similar to the old boot message you got from you...