Skip to content

This site is automatic translation of http://www.marcelosincic.com.br, original in portuguese

Fix for SCCM 2016 build 1610 in the OSD for Windows 10

As is known to all that have updated to SCCM 2016, now the builds are downloaded and installed directly on console (https://msincic.wordpress.com/2016/10/03/new-sccm-2016-updates-model/)

However, with the update to build several 1610 had problems of “0x80091007 (Hash value is not correct)” in the OSD log when applied Windows image 10, an error that was not documented.

Well, Microsoft has released on Monday a Hotfix for this problem and a few others who are described in KB 4010155: https://support.microsoft.com/en-us/help/4010155/update-rollup-for-system-center-configuration-manager-current-branch-v

If you have SCCM 2016 Build 1610, between the console and wait for the hotfix installation to download then install it:

image

New RoadMap and Licensing Windows Server 2016

After the release of Windows Server 2016 received several questions about the future (roadmap) and the Windows Server licensing.

New Life cycle for Windows Server

As an example, the Windows 10 was released on build 1511, upgraded to 1606 and other builds are already available for those who are part of the program Windows Insider.

The same concept will be adopted with Windows Server, which guaranteed 10 years of useful life with updates, but with two options:

  1. Windows Server 2016 Desktop Experience (installation pradrão) and Server Core – in this version the lifetime will be of 10 years. This model is the same 10 Windows called LTSB (Long Term Service Branch).
  2. Windows Server Nano -in this version the lifetime is 10 years and the updates are for build and Windows 10. This model of updates is called CBB (Current Branch for Business) and complies with the “Modern Lifecycle Policy”.

Reference: https://blogs.technet.microsoft.com/windowsserver/2016/07/12/windows-server-2016-new-current-branch-for-business-servicing-option/ and https://support.microsoft.com/en-us/lifecycle/search?alpha=windows%20server%202016

We will better understand what it means and how it is different from the current model.

In Windows 2012 new features were always added in R2 and Service Packs, IE, it was necessary to wait up to two years to get the new features of the OS.

For installations of Windows Server 2016 Full and Server Core updates will be sent for update rollups, like a Service Pack. The most current for Windows 10 and Windows 2016 is the Anniversary Update. New features will be sent along with these packages.

In the Windows Server 2016 Nano updates carry new features, namely a new feature released in Windows will be sent to the servers as an optional package of 3 to 4 times a year. There is no need to wait for the update rollup to have access to new features.

In short, we have a Windows updated for 10 years. If you use the Full version will need to wait for the annual cumulative updates for new features. If you use the Nano version can access very quickly when new features stay available.

Licensing

Already known in SQL Server licensing for 2012 CORE becomes the default for Windows Server.

The change has a very simple reason, the number of processors (sockets) to a low and medium profile (e.g. Xeon E3 and E4) began to slow and the number of CORE (stacking) increase with the increased miniaturization of components.

In times past it was common for a machine to 4 Sockets (processors) each with 4 or 8 CORE. Today is much more common 2 Sockets and 48 machines. For example, the Xeon E5-2650 has 10 CORE and the E7-8890 has 24 CORE.

Based on that, manufacturers are changing the charging SOCKET for CORE and imposing a minimum CORE for each server.

To better understand how if earning before a server and what now, taking into account that each license is purchased for 2 or 2 CORE Processors:

SO Procs COREs Total Licensing Licenses Needed
W2012R2 1 2 PROC 1 license 2 Socket(Proc)
W2012R2 1 10 PROC 1 license 2 Socket(Proc)
W2012R2 2 8 PROC 1 license 2 Socket(Proc)
W2012R2 3 24 PROC 2 license 2 Socket(Proc)
W2016 1 2 CORE 8 license 2 CORE (Minimum)
W2016 1 10 CORE 8 license 2 CORE (Minimum)
W2016 2 8 CORE 8 license 2 CORE (Minimum)
W2016 3 24 CORE 12 license 2 CORE

That is, all the physical servers that you have will need to be licensed to at least 16 CORE even if he only has 4 CORE (Xeon E2).

But don’t be alarmed, the value that it paid for a 2-processor license is equivalent to that paid by 8 2 CORE licenses. That is, financially for common servers there will be no difference.

And how are the licenses that already own per processor?

This is the most common question and the answer is simple: for each current license of 2 processors/Socket (Lic2Proc) Microsoft will automatically convert and consider how 8 CORE licenses (Lic2CORE).

But what if I currently have a server with 2 processors and CORE 24, I’m going to have to buy 8 CORE (2 Lic2CORE licenses)?

In this case it is important that you run a SAM (Software Asset Management) before renewing your contract or immediately before changing your server to document that there was this situation.

Once SAM filed and documented, you can count on the 24 CORE licenses on another server, but require attention:

  1. Currently own a 24 CORE server and buy another of 36 CORE: Need to buy 6 licenses (Lic2CORE) to complement
  2. I buy two new servers with 12 CORE each: You will not be able to “break” the 12 licenses, as they are converted to a server and not independent licenses
CONCLUSION

Run a SAM immediately to document the situation of your current servers.

Remember, you only need to pay if you don’t document!!

For further reading and conversion examples, download the licensing document: https://www.microsoft.com/en-us/licensing/product-licensing/windows-server-2016.aspx#tab=2

New Management Packs for SQL

Complementing the previous post about the new Management Packs updated after the release of Windows and System 2016 ( https://msincic.wordpress.com/2016/10/25/new-system-center-operations-manager-2016-management-packs/ ), Update follows.

The Preview of the new Management Pack for SQL has been released today from the 2008 to 2016 release.

Important that this preview already solves some problems that have occurred with databases and indicators in the SCOM 2016 console:

SQL Server 2008/2008 R2 / 2012 MP Features and Fixes

  • No extra permissions on remote WMI are now required for Local System account when Always On hosts have names that are no longer than 15 symbols
  • Fixed: Always On discovery and monitoring scripts can not read cashed values ​​in Windows registry
  • Fixed: Wrong MP version number in some Always On scripts
  • Fixed: CPUUsage and DBDiskLatency scripts fail with the reason: "Index operation failed"
  • Added retry policy in some Always On workflows to make PS-scripts work more stable
  • Updated the visualization library
  • Changed behavior of Always On scripts for cases when WSFC service is stopped

New SQL Server 2014/2016 MP Features and Fixes

  • No extra permissions on remote WMI are now required for Local System account when Always On hosts have names that are no longer than 15 symbols
  • Fixed: Always On discovery and monitoring scripts can not read cashed values ​​in Windows registry
  • Fixed: Wrong MP version number in some Always On scripts
  • Fixed: CPUUsage and DBDiskLatency scripts fail with the reason: "Index operation failed"
  • Added retry policy in some Always On workflows to make PS-scripts work more stable
  • Updated the visualization library
  • Fixed: Always On objects get undiscovered when any Always On discovery crashes

SQL Server Replication 2008/2012/2014/2016 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Fixed: MonitorDistributorSnapshotFreeSpace fails when being launched against SQL Server 2014 SP2
  • Fixed: Wrong source detection in logging
  • Updated the visualization library

New Features in SQL Server Analysis Services 2008/2012/2014/2016 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Fixed: AS workflows sometimes crash
  • Updated the visualization library

New Features in SQL Server Reporting Services 2008/2012/2014/2016 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Fixed: Web Service monitors do not support URL reservation https: // +: <port> / <ReportServerPage> (protocol is HTTPS)
  • Updated the visualization library

New SQL Server Dashboards Features and Fixes

  • Fixed: Tiles content is replaced with question marks after a long period of inactivity

Download and available details https://blogs.msdn.microsoft.com/sqlreleaseservices/released-public-preview-for-system-center-management-packs-for-sql-server/

New System Center Operations Manager 2016 Management Packs

Above new Management Packs available after System Center 2016 (SCOM) launch and install:

New Management Packs:

System Center Operations Manager Management Packs for Windows Server 2016 Essentials

Microsoft System Center Management Pack for SQL Server 2014

Microsoft System Center Management Pack for SQL Server 2016

Microsoft System Center Management Pack for SQL Server

System Center 2016 Management Packs for Open Source Software

Microsoft System Center Management Pack for System Center Service Manager

System Center Management Packs for Data Protection Manager 2016 Reporting, Discovery and Monitoring

Microsoft System Center 2016 Management Pack for Service Provider Foundation (SPF)

Microsoft System Center 2016 Management Pack for Orchestrator

System Center 2016-Updates Rollup

Following the release of Windows 2016 with Rollup 1 (https://msincic.wordpress.com/2016/10/14/upgrade-and-update-of-windows-server-2016/), the same happens with the System Center 2016.

See new SCOM 2016 Management Packs in https://msincic.wordpress.com/2016/10/25/new-system-center-operations-manager-2016-management-packs/ 

Why this happens?

Before a manufacturer releasing a final media to the public, it is distributed to the manufacturers.

For example, the manufacturer of HW needs to make sure that an update did not affect drivers or functionalities of the server.Developers (ISVs) need to make sure your plugins and software are still “talking” with the new version.

As the two products were made available to the media for manufacturers and developers a few weeks before the launch, Microsoft need to catalog and generate a package of updates that occurred between this launch for the manufacturers and the GA (General Availability) audience, which is usually 45 to 60 days.

Update Rollups of System Center 2016

Update Rollup 1 for VMM: https://support.microsoft.com/en-us/kb/3190597

Update Rollup 1 for SCOM 2007: https://support.microsoft.com/en-us/kb/3190029

Update Rollup 1 for Orchestrator: https://support.microsoft.com/en-us/kb/3190603

Update Rollup 1 for DPM: https://support.microsoft.com/en-us/kb/3190600

Update Rollup for SCCM 1609 TP: https://blogs.technet.microsoft.com/enterprisemobility/2016/09/27/update-1609-for-configuration-manager-technical-preview-available-now/

Noting that in the case of the SCCM upgrades and updates is carried out in own console as discussed in https://msincic.wordpress.com/2016/10/03/new-sccm-2016-updates-model/

Installation and Upgrade of System Center 2016

With the launch of the media RTM (Release To Manufacturing or End) of the Windows System Center 2016 2016 and it comes time to do the upgrade of 2012 and 2016 R2 releases Technical Preview.

I will address each of them from 2016 Technical Preview releases since the migration of 2012 R2 versions is typically simpler and supported.

Update: After install or upgrade download Update Rollups of System Center 2016: https://msincic.wordpress.com/2016/10/25/system-center-2016-updates-rollup/ 

System Center Configuration Manager (SCCM)

SCCM is one of the products that were already in 2016 version since the beginning of the year, when it was released as SCCM 1511, following Windows nomenclature 10.

Follow the posts that I’ve written about this version:

https://msincic.wordpress.com/2016/03/24/new-feature-of-system-center-configuration-manager-1511-updates-and-updates/

https://msincic.wordpress.com/2015/12/28/system-center-configuration-manager-1511-change-evaluation/

https://msincic.wordpress.com/2016/10/03/new-sccm-2016-updates-model/

For those who have the SCCM R2 upgrade 2012 is quiet and just run the Setup to work.

System Center Operations Manager (SCOM)

The SCOM upgrade can be done both of the 2012 version R2 as of 2016 Techincal Preview versions in the same way, it supports both paths.

The only recommendation that the setup is to back up the databases (and DW) before, because there’s no way back if errors occur in the middle of the process:

capture20161013145918707

You will need to upgrade the Report Viewer, before we use the RV of SQL 2012 and should now be used RV of SQL 2016, which is found in the link of the actual Setup:

capture20161013150339362

capture20161013155424938

System Center Service Manager (SCSM)

Upgrade both the 2012 R2 as the Technical Preview is simple, requires no type of restriction, occurring very quiet:

capture20161013145905162

It is important to remember at the end which will upgrade the Management Packs from the wizard to the SCOM 2016 has:

https://msincic.wordpress.com/2016/03/24/automatic-updates-in-system-center-operations-manager-2016-tp4/

System Center Virtual Machine Manager (VMM)

This is a product that does not allow the automatic upgrade of the Techinical version Preview, but allows from the 2012 R2.

In the case of Tecnhinical Previwe, the Setup will indicate that already exists and will ask to uninstall:

capture20161013151606238

However, the reinstallation is simple. Just when choosing to keep the database:

capture20161013151636326

When you run Setup again using the same database and directory of libraries:

capture20161013152117951

capture20161013152715060

After that VMM will function normally, but it’s good to remember that you will need to uninstall and reinstall agents, if he doesn’t do the automatic upgrade of the agent.

Recalling that one of the most interesting features is integration with Azure: https://msincic.wordpress.com/2015/06/03/system-center-virtual-machine-manager-2016-tp2-integrated-with-azure/

System Center Orchestrator (SCORCH)

As well as the VMM, it requires reinstalling but it is possible to maintain the database and repointing on new installation:

capture20161013153558520

capture20161013153757300

capture20161013153847695

After the process, the normally appear with the same runbooks Integrations Packs.

In the case of SCORCH Packs and Integrations of the SCOM 2007 is important to upgrade the packages, and in SCOM 2007 is a lot easier to have the menu, while not the Orchestrator.

Upgrade and Update of Windows Server 2016

Last night (10/12/2016) Microsoft released the Windows Media Server Standard and Enterprise 2016 for MSDN subscribers and customers of volume by the VLSC.

This new release brings several new features, such as distributed Storage (similar to VMWare VSAM), new features to the operating system.

On the page https://www.microsoft.com/pt-br/server-cloud/products/windows-server -2016/default.aspx # MenuItem3 is possible to see all the new features and documentation.

Important to note that other than Windows R2, Windows 2012 2016 back having feature differences between the Standard version and Enterprise!

Update Post Installation

It is important that together with the installation media also download the Cumulative Update 1:

https://support.microsoft.com/en-us/kb/3194798

capture20161013105959189

That’s right, the media finals was available along with the first Cumulative Update. The reason is that the availability of media Technical Preview generated data for new fixes, and these were included in the CU1.

2012 R2 Version upgrade and Technical Preview

Is it possible to upgrade from the 2012 version R2 normally in any type of installation.

For those who had already installed some TP is possible to upgrade directly, but only for the version with Desktop Experience installed.

Other cases can be found at https://technet.microsoft.com/windows-server-docs/get-started/supported-upgrade paths

In the example below, the result of upgrading a clustered Hyper-V server that has Storage Spaces with SSD disks and RAID several VMs running:

capture20161013105351510

capture20161013105829117

capture20161013105836439

Upgrade problems

As in previous versions, if an error occurs during the upgrade you can revert to the previous state without problems.

However, unlike a client operating systems (Windows 10) this revert is not possible after the upgrade to be finished.