Comments for Stefan Goßner

By the way, I installed CU Sep 2017 on RTM

Hi Stefan Goßner, Thank you so much for everything you share with us,

I think there is a bit typo note at the “SharePoint 2016 November 2016 CU Build Numbers:” that should be “SharePoint 2016 September 2017 CU Build Numbers:”

You are right – thanks for the hint!
I have updated the info.

I’ve updated my SharePoint 2016 Staging Environment with Sept 2017 that has been installed and configured successfully without any issue related to Timer Service,

So I think you should try to check the following:

1. If you can’t stop and start the timer service via CMD, try to open ‘Task Manager’ > In ‘Process’ Tab, check the ‘SharePoint Timer Service’ > Right click, End Process.
2. Now, go to ‘Services’ > Right Click on ‘SharePoint Timer Service’ > Properties > at ‘Log-On’ tab, try to provide again the correct credentials of your farm account
3. Open CMD as Administrator > Start the SP timer service again as “net start SPTimerV4”
4. Also, Make sure that the SQL Server service is running with the correct Log-on information.
5. Now try to start the Sharepoint Configuration wizard to reflect the installed patch on your farm.

Great, another question Please? Is ‘September 2017 update for SharePoint Server 2016’ considered a CU or PU?

In this context it is a CU as it includes all previous PUs and CUs as well.
It also includes a PU which is the language independent part as it includes new security fixes.
Cheers,
Stefan

Hi Hans,

Unfortunately, There is no Modern Team Site in SharePoint 2016 On-Prem yet! The release of ‘Feature Pack 2 for SharePoint Server 2016’ provides you to only use and build the SharePoint Framework **WEB PARTS** hosted in the classic web part pages of SharePoint Server 2016.

Please read more at-

– https://dev.office.com/blogs/now-available-deploy-sharepoint-framework-web-parts-to-sharepoint-server-2016-with-feature-pack-2
– https://blog.devoworx.net/2017/09/16/sharepoint-framework-for-sharepoint-server-2016/
– https://dev.office.com/sharepoint/docs/spfx/sharepoint-2016-support
–

If SharePoint Security Updates, such as KB 3213560, 4011113 and 4011117 are installed separately from the SP CU, is it necessary to run psconfigui?
is it necessary to install the SP CU also?

Hi Dean,
all SharePoint fixes require PSConfig. No exceptions.
The CU is only required if you need a specific fix from the CU.
Cheers,
Stefan

Thanks for the confirmation. That is what I thought.

Hi Stefan!
I have a Windows Server 2012 R2 Standard with a default instance and common components of SQL Server 2016. I would additional install a named instance e.g. SHAREPOINT on SQL Server 2012. Is it possible to run SharePoint 2013 on this named SQL instance SHAREPOINT?
Regards,
Georg

Hi Georg,
it is possible but recommended to use an alias for this. The benefit is that you can later switch to a different SQL server or SQL server instance by just changing the alias configuration and without the need to reconfigure Sharepoint
Cheers,
Stefan

Hi Stefan,

I have a SP 2013 UAT environment with a WFE and APP server currently patched to June 2015 CU. I recently discovered our SCCM team have inadvertently pushed the June 2017 PU and Security Updates to our APP server, thus causing our WFE to be out of sync. No other PUs or Security Updates have been installed or applied until then.

I realize CUs are cumulative, but am concerned if I install the June 2017 PU and Security Updates on the WFE and run PSCONFIGUI.EXE or both servers I will end up breaking my environment because of the current patch level. Should it be ok to just simply apply June PU and Security Updates or would you recommend installing, applying and testing the CU to ensure all required dependencies are present.

Thanks in advance for your help.

Paul

Update: On further look, it appears that all outstanding Security Updates and PUs were installed.

Hi Paul,
if all servers are on the same patch level you should run PSConfig to finalize the update.
Cheers,
Stefan

Unfortunately only one of the servers had the updates installed.

Hi Stefan,
we used to have CU (full server package) for 2013 and didn’t see any language independent or dependent download .However, for 2016 we see something different , I believe we just install language independent package ? when is language dependent package required and impact not installing it ?

Hi Mohanghimire,
the reason is the different packaging model. In SP2013 you would have to maintain 30+ packages for SharePoint and it would be hard to keep all up2date. So we created the full server packages.
With SP2016 we only have two packages – so no need for a full server package as it should be simple to install two packages.
Cheers,
Stefan

Just to add: you always need both packages.
SharePoint comes with an language independent component and one built in language (e.g. if you install russian SharePoint you have the russian language built in) plus additional lanuguages you can install on top through language packs.

Great, your instructions helped me!

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by Anon

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by M.Qassas

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by Stefan Goßner

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by M.Qassas

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by M.Qassas

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by Stefan Goßner

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by M.Qassas

Comment on September 2017 CU for SharePoint 2013 product family is available for download by Dean Gross

Comment on September 2017 CU for SharePoint 2013 product family is available for download by Stefan Goßner

Comment on September 2017 CU for SharePoint 2013 product family is available for download by Dean Gross

Comment on SharePoint 2013 and SQL Server 2016 by Georg Gamsjäger

Comment on SharePoint 2013 and SQL Server 2016 by Stefan Goßner

Comment on June 2017 CU for SharePoint 2013 product family is available for download by PoWaShell

Comment on June 2017 CU for SharePoint 2013 product family is available for download by PoWaShell

Comment on June 2017 CU for SharePoint 2013 product family is available for download by Stefan Goßner

Comment on June 2017 CU for SharePoint 2013 product family is available for download by PoWaShell

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by Mohanghimire

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by Stefan Goßner

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by Stefan Goßner

Comment on Feature Pack 2 for SharePoint Server 2016 (aka September 2017 CU) is available for download by Anon