Features removed from Windows Server 2016

Share and Storage Management

The Share and Storage Management snap-in for Microsoft Management Console has been removed. Instead, do any of the following:

• If the computer you want to manage is running an operating system older than Windows Server 2016, connect to it with Remote Desktop and use the local version of the Share and Storage Management snap-in.
• On a computer running Windows 8.1 or earlier, use the Share and Storage Management snap-in from RSAT to view the computer you want to manage.
• Use Hyper-V on a client computer to run a virtual machine running Windows 7, Windows 8, or Windows 8.1 that has the Share and Storage Management snap-in in RSAT.

Journal.dll

The Journal.dll is removed from Windows Server 2016. There is no replacement.

Security Configuration Wizard

The Security Configuration Wizard is removed. Instead, features are secured by default. If you need to control specific security settings, you can use either Group Policy or Microsoft Security Compliance Manager.

SQM

The opt-in components that manage participation in the Customer Experience Improvement Program have been removed.

Windows Update

The wuauclt.exe /detectnow command has been removed and is no longer supported. To trigger a scan for updates, do either of the following:

• Run these PowerShell commands:

$AutoUpdates = New-Object -ComObject “Microsoft.Update.AutoUpdate”
$AutoUpdates.DetectNow()

• Alternately, use this VBScript:

Set automaticUpdates = CreateObject(“Microsoft.Update.AutoUpdate”)
automaticUpdates.DetectNow()

Features deprecated starting with Windows Server 2016

The following features and functionalities are deprecated starting with this release. Eventually, they will be completely removed from the product, but they are still available in this release, sometimes with certain functionality removed. You should begin planning now to employ alternate methods for any applications, code, or usage that depend on these features.

Configuration tools

• Scregedit.exe is deprecated. If you have scripts that depend on Scregedit.exe, adjust them to use Reg.exe or Windows PowerShell methods.
• Sconfig.exe is deprecated. Use Windows PowerShell instead.

NetCfg custom APIs

Installation of PrintProvider, NetClient, and ISDN using NetCfg custom APIs is deprecated.

Remote management

WinRM.vbs is deprecated. Instead, use functionality in the WinRM provider of Windows PowerShell.

SMB

SMB 2+ over NetBT is deprecated. Instead, implement SMB over TCP or RDMA.

SharePoint Server 2013 : User Profile Synchronization Service : ERR_Config_DB Resolution

ILM CONFIGURATION: CONFIGURING DATABASE

ILM CONFIGURATION: ERROR ‘ERR_CONFIG_DB’.
USERPROFILEAPPLICATION.SYNCHRONIZEMIIS: FAILED TO CONFIGURE MIIS POST DATABASE, WILL ATTEMPT DURING NEXT RERUN. EXCEPTION: SYSTEM.CONFIGURATION.CONFIGURATIONERRORSEXCEPTION: ERR_CONFIG_DB
AT MICROSOFT.OFFICE.SERVER.USERPROFILES.SYNCHRONIZATION.ILMPOSTSETUPCONFIGURATION.VALIDATECONFIGURATIONRESULT(UINT32 RESULT)
AT MICROSOFT.OFFICE.SERVER.USERPROFILES.SYNCHRONIZATION.ILMPOSTSETUPCONFIGURATION.CONFIGUREMIISSTAGE2()
AT MICROSOFT.OFFICE.SERVER.ADMINISTRATION.USERPROFILEAPPLICATION.SETUPSYNCHRONIZATIONSERVICE(PROFILESYNCHRONIZATIONSERVICEINSTANCE PROFILESYNCINSTANCE).

There is some problem in either connecting to Synchronization DB or at the Synchronization DB on permission settings.

To Track Down:

• Install ULSViewer ( https://www.microsoft.com/en-us/download/details.aspx?id=44020)
• Start ULSViewer – Start Live Feed Tracing – Filter (Category Equals User Profiles)
• You can change the severity level in the top.

To Resolve:

• Check if the service account used to start the services have enough permission on Synchronization DB.  Check if it has DB_Owner schema permission on this db.
• If you have enabled TLS 1.2 only as per security standards – check whether sql server native client supports TLS 1.2. (E.g. SQL Server Native Client 2008 R2 does not support TLS 1.2 by default. Please install the hotfix to support TLS 1.2). Check this link
• Also make sure you have SQL Server Native Client 2008 for SQL Server 2014 DB and you are not latest CU. There was a known issue for this SQL Server 2014 DB and SSharePoint 2013 for UPS service – but it was fixed in April 2014 CU. So if you just update to latest CU – you are good to go.
• Check if the service account used to start the service is part of Local Administrator Group (while starting), Logon as Service, Logon Locally, WSS groups except the restricted one out there.
• The FIM services would remain in disabled before you start this service. You dont have to manually start the FIM services – This UPS Sync service will automatically start those 2 FIM services.