The last Sebtember 2016 update for SP 2016 has, unfortunately, still a serious bug in the “SPTimerRecyleJobDefinition”. The job is never executed correctly!

public override void Execute(System.Guid targetInstanceId)
{
try
{
Process currentProcess = Process.GetCurrentProcess();
if (System.DateTime.UtcNow.Subtract(currentProcess.StartTime).Minutes < 60)
{
ULS.SendTraceTag(7436320u, ULSCat.msoulscat_WSS_Timer, ULSTraceLevel.Medium, "Skipping timer recycle since the process has been running less than 1 hour.");
return;
}
}….

TimeSpan.Minutes is the Minutes part and can not be greater then 59 (TotalMinutes is correct)! This Job is never executed!!!!
The next Bug is Utc. The Process.StartTime is local time (Kind=local)

Please remove the term review so that you can always restart the timer safely!

I posted rescue request from Office 365 Admin page and Microsoft Japan team provided me for their good support, but their way of communication is just through outbound only call and Microsoft Japan does not accept my call-back which is very inconvenient.

While I understand that Microsoft does not want to accept inbound call because of resource allocation difficulties, I don't understand why Microsoft forces them to call and not allow them to use Lync meeting.

Since all of us use Lync, if they want to communicate with us to make sure that their support is sufficient, why not set up Lync meeting instead of repeatedly call when I am out of office.

Let's use office 365 service instead of traditional call center methodology.

By the way, other than above, please note that Microsoft Japan's Sharepoint Support team are very good team and they provides good support to me.

It's shame that their quality of support is somehow deteriorated with the above poor communication rule or methodology. You should be more aggressive to improve customer support communication environment.

I hope you understand this is not a claim for you rather "ganbare" to your success.

Come on, guys. This just won't do:

Attempting to install any variety of SharePoint 2013 on a machine that has the .NET Framework 4.6.1 on it fails because the SharePoint installer says that it can't find .NET Framework 4.5.

Yeah, seriously.

The prerequisite installer happily accepts 4.6.1 (as it should), but the product installer makes a newbie mistake in wanting "4.5" but not "4.5 or later".

Trying to downgrade 4.6.1 is a nightmare because it's inexcusably poorly documented (Aaron Stebner's blog post at https://blogs.msdn.microsoft.com/astebner/2016/03/04/mailbag-how-to-revert-to-older-versions-of-the-net-framework-4-family/#comment-37506) gives the only clear idea of what you have to do - uninstall a KB.

Guys, if you take any pride in your work, *fix this* please.

I went to People and Groups and renamed a SharePoint Group from Fun-Together to "Fun Together" and went I went to Navigation and changed the Audience for a Navigation Heading (A document Library) in SharePoint 2013 Enterprise Edition SP1, it did NOT update the audience, it has a red underline. I had to update it by deleting it and adding the correct one "Fun Together." I do NOT think it is the spaces, I believe it is that it is different and audiences are not updating it. I don't know if a timerjob fixes this, but I noticed this after 5 minutes where I wanted to change the spelling.

O Sharepoint se mostrou uma ótima saída para meus negócios, e achei bastante repetitivo e redundante com relação ao OneDrive, causando uma certa confusão. Acredito que os dois se complementam mas com possibilidades de existir apenas um. Acredito que o Sharepoint possa fazer tudo o que faz mais as funcionalidades do OneDrive, se complementando onde automaticamente toda a biblioteca do OneDrive estivesse no SharePoint e o mesmo do SharePoint no OneDrive. Gostaria que o SharePoint fosse capaz de funcionar com todas as ferramentas do office, como por exemplo mala direta. Senti falta de muita coisa que so tenho acesso em um office instalado na maquina.