Living a SharePoint life

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.

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

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

Monday, January 2, 2017

How to remove an unsuccessful AutoSPInstaller job

What do you need to uninstall from your server if the installation with AutoSPInstaller wasn’t successful?

Installing a SharePoint Server with the AutoSPInstaller job has become the gold standard for administrators. It’s much easier for large farms and offers a high degree of quality. However, using AutoSPInstaller can be a bit of a hassle. Until you get the xml configuration right, you normally need a few approaches. You can start the installation again, but you need to remove a few things first before it will re-run successfully.


If you are installing language files with your SharePoint Farm, remove these packages first. Open the Windows Control Panel, go to Programs -> Uninstall a program. Search for any SharePoint Language Package that has been installed and remove them all.

SharePoint Server

Leave the Control Panel open. Search for the SharePoint Server binary installation package and remove that file as well.


These files must not be removed. They can stay on the server.

Internet Information Server

Open the IIS Management and look for any Web Application that was created during the AutoSPInstaller setup. Remove all of them and the Application Pools as well. Because AutoSPInstaller will create all of them again, I normally delete all Application Pools and Web Applications from IIS. This way I’ll have a clean system after setup.

The Web Applications create directories in the VirtualDirectories folder of the IIS working directory. You normally find it here:


Remove the folders from the Web Applications you have deleted from here as well.

Log files

Remove the log files from the ULS logging directory or do a clean up after you sucsessfully installed SharePoint.

Search Index

If the SharePoint Search has been created already, go to the directory where the search index is stored. Delete all GUID directories you find there.

SQL Server

Open the SQL Management Studio and connect with the SQL instance you are using to host the SharePoint databases. Delete any database that has been created by the AutoSPInstaller script. At the prompt to delete the database, you should select to close any connection to the database.


Now reboot your server. After login back into the server you can restart the installation with AutoSPInstaller. Any traces of previous installations will be gone then.

Featured Post

How are Microsoft Search quota consumed?

With Office 365 Search, Microsoft has created a central entry point for the modern workplace. In one convenient spot, users can access all ...