Following this discussion:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/c5f2786c-ffac-4f14-b7a9-00612cdf784e/server-2016-vm-hangs-shutting-downrestarting-when-the-pagefile-is-on-a-different-vhdx?forum=winserverhyperv

The core problem is the following, for example (simple config), for Exchange or SQL servers in a HYPER-V VM under Windows 2016:

systemdrive for windows system (and sql, exchange core),
datadrive for mbx data or sql-databases
datadrive for log file
drive for pagefile

We create for all this drive a separat VHDX file and add this to the VM as SCSI drive.

The drive for pagefile (fast SSD, NVMe or other) is exclusiv for the pagefile reserved. No other data on it. The drive for pagefile is the only drive with a pagefile for this vm. No second pagefile on the systemdrive or elsewhere.
In this case a running VM can't restart or shutdown.
When you do this, the VM hangs. This did not happen with earlier versions of Windows.
It is not recommended (MS Exchange or SQL recommendations) to set up two Pagefiles (split pagefiles), as this greatly reduces performance.

So we must disable the debug funktion completely in the Windows VM - that works. But not a good way.

Please rerelease the functionality as in previous windows versions!

Default servercore:1809 image came with en-US.

• At this moment, for Server Core 2019, you have to install language pack by yourself: https://docs.microsoft.com/pt-br/windows-server/get-started-19/rel-notes-19.


• The way to do it, is using lpksetup: https://support.microsoft.com/en-us/help/4466511/cannot-configure-language-pack-for-windows-server-2019
  


• But lpksetup.exe crashes when running on container

I've described step by step how to reproduce lpksetup.exe error on container, producing crash report logs that I've extracted from container.
All here: https://github.com/sanguedemonstro/docker-playground/issues/1#issuecomment-453078549

With extra details here: https://github.com/sanguedemonstro/docker-playground/blob/master/langpack-on-servercore2019.md#why-am-i-playing-around-this-subject

But I'm not able to understand logs or fix windows base image. And I can't open support ticket once I'm not MS partner.

So if anyone could help I'm here to support.

Thanks!

It would appears I'm not the only one experiencing the issue, I did a fresh install promote it to a Windows Server 2016 Forest and Domain AD. After the reboot I realize the Start Menu settings cannot be changed, next I found that whole load of permission error whenever I try to launch anything that requires Administrator privilege including Server Manager, Settings and Control Panel. After that I went to check the permission settings of the C drive and Windows folder as compared to previous version of Windows Server, "Authenticated Users" is no longer part of the default permissions. This is a fresh install of various edition from VLSC to MSDN to retail to trial download every version media and edition use present the same issue.

Scheduled tasks on the current TP5 of Windows Server 2016, which have a CalendarTrigger with repetition configured, don't seem to trigger and cannot be started manually.
The same trigger without repetition (e.g. after unchecking the "Repeat task every:" checkbox in taskschd.msc) works correctly.
A TimeTrigger with the same repetition configuration works, too.
taskschd.msc calculates and displays the next runtime correctly.

When I try to start such a task manually in taskschd.msc, a message box appears (running any other task works):
de-DE: "Der Aufgabenplanungsdienst ist nicht verfügbar. Die Aufgabenplanung wird erneut versuchen, eine Verbindung herzustellen."
en-US: "Task Scheduler service is not available. Task Scheduler will attempt to reconnect to it."

When I try to start the task by using Start-ScheduledTask, a non-terminating exception is thrown ("Nicht implementiert"="Not Implemented"):
PS C:\Users\Administrator> Start-ScheduledTask -TaskName bad
Start-ScheduledTask : Nicht implementiert
In Zeile:1 Zeichen:1
+ Start-ScheduledTask -TaskName bad
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : NotSpecified: (PS_ScheduledTask:Root/Microsoft/...S_ScheduledTask) [Start-ScheduledTask]

, CimException

+ FullyQualifiedErrorId : HRESULT 0x80004001,Start-ScheduledTask

When I try to start it via schtasks.exe, the same message appears:
C:\Users\Administrator>schtasks /run /tn bad
FEHLER: Nicht implementiert

When the task should trigger by time, there are no events in Microsoft-Windows-TaskScheduler/Operational indicating any activity around this task.

The tasks trigger sections look like this:
working (without repetition):
<Triggers>

<CalendarTrigger>

  <StartBoundary>2016-06-14T00:13:00</StartBoundary>

  <Enabled>true</Enabled>

  <ScheduleByDay>

    <DaysInterval>1</DaysInterval>

  </ScheduleByDay>

</CalendarTrigger>

</Triggers>
not working (with hourly repetion):
<Triggers>

<CalendarTrigger>

  <Repetition>

    <Interval>PT1H</Interval>

    <Duration>P1D</Duration>

    <StopAtDurationEnd>false</StopAtDurationEnd>

  </Repetition>

  <StartBoundary>2016-06-14T00:13:00</StartBoundary>

  <Enabled>true</Enabled>

  <ScheduleByDay>

    <DaysInterval>1</DaysInterval>

  </ScheduleByDay>

</CalendarTrigger>

</Triggers>

On Windows Server 2012R2 this task works perfectly fine.

Test environment (in case it matters):
Hyper-V Generation 2 VMs on Windows Server 2012R2
Windows Server 2016 Technical Preview 5 Standard with GUI German (installed from dewindowsserver2016technicalpreview5x64dvd_8512319.iso, SHA1 20B276A6EF63AB46FF50A561CD16B48FDF8787AE)
3 VMs, 2 of them fresh installs without any modification except the task

The whole task:
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.4" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">
<RegistrationInfo>

<Date>2016-06-14T10:20:18.9077118</Date>

<Author>WIN-B5GC2VET9K1\Administrator</Author>

<URI>\Test</URI>

</RegistrationInfo>
<Triggers>

<CalendarTrigger>

  <Repetition>

    <Interval>PT1H</Interval>

    <Duration>P1D</Duration>

    <StopAtDurationEnd>false</StopAtDurationEnd>

  </Repetition>

  <StartBoundary>2016-06-14T00:13:00</StartBoundary>

  <Enabled>true</Enabled>

  <ScheduleByDay>

    <DaysInterval>1</DaysInterval>

  </ScheduleByDay>

</CalendarTrigger>

</Triggers>
<Principals>

<Principal id="Author">

  <UserId>S-1-5-18</UserId>

  <RunLevel>LeastPrivilege</RunLevel>

</Principal>

</Principals>
<Settings>

<MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>

<DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>

<StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>

<AllowHardTerminate>true</AllowHardTerminate>

<StartWhenAvailable>false</StartWhenAvailable>

<RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>

<IdleSettings>

  <StopOnIdleEnd>true</StopOnIdleEnd>

  <RestartOnIdle>false</RestartOnIdle>

</IdleSettings>

<AllowStartOnDemand>true</AllowStartOnDemand>

<Enabled>true</Enabled>

<Hidden>true</Hidden>

<RunOnlyIfIdle>false</RunOnlyIfIdle>

<DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>

<UseUnifiedSchedulingEngine>false</UseUnifiedSchedulingEngine>

<WakeToRun>false</WakeToRun>

<ExecutionTimeLimit>PT72H</ExecutionTimeLimit>

<Priority>7</Priority>

</Settings>
<Actions Context="Author">

<Exec>

  <Command>C:\temp\test.bat</Command>

</Exec>

</Actions>
</Task>

If have some issues with Dism after a new Installation with Windows 10 1709 and Upgrade from Windows 1703 to 1709.

Get-WindowsCapability : Error "Get-WindowsCapability". Errorcode: 0x800f0954
Line:1 Zeichen:1
+ Get-WindowsCapability -online
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo          : NotSpecified: (:) [Get-WindowsCapability], COMException

+ FullyQualifiedErrorId : Microsoft.Dism.Commands.GetWindowsCapabilityCommand

Some Lines from Dism Logfile:

DISM OS Provider: PID=7180 TID=6088 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect

DISM Provider Store: PID=7180 TID=6088 Failed to load the provider: C:\Users\ADMIN~1.TES\AppData\Local\Temp\38977CD8-C67C-463B-8721-E72E5E46A990\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

DISM Provider Store: PID=7180 TID=6088 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

2017-10-19 17:39:03, Error DISM DISM Package Manager: PID=7180 TID=6088 Failed enumerating capabilities - CDISMPackageManager::GetCapabilityCollection(hr:0x800f0954)
2017-10-19 17:39:03, Error DISM DISM Package Manager: PID=7180 TID=6088 Failed to get capability collection. - CPackageManagerCLIHandler::ProcessCmdLine_GetCapabilities(hr:0x800f0954)
2017-10-19 17:39:03, Error DISM DISM Package Manager: PID=7180 TID=6088 Failed while processing command get-capabilities. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0954)
2017-10-19 17:39:03, Info DISM DISM Package Manager: PID=7180 TID=6088 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2017-10-19 17:39:03, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0954

Thanks

legacy systems needs to go to cloud

.NET and Win32 softwares will be around for long time, for sure..

why container? 1nd

Large systems with decades of code written, composed by 3rd party components can not be changed right away. So containerizing monoliths, are one important step on the jorney to the cloud

why container? 2st

I'm newbie, but as far as I know, the whole thing about containers is ship it as image once and run it everywhere, with environment isolation and integrity.. right?!

the issue

There is no way to properly set globalization settings like Time Zone, Language, or Windows-Location on Server Core containers. Once I can not control the container host, I don't know where my software will run: Azure AKS, AWS, On-Prem, data centers, Windows Desktops,..
So, I need to ensure some container environment settings..

the feeling

I'm very sad.. Microsoft should realize that globalization settings like language and time zone are fundamental to keep the world running..

Otherwise, Windows Server on container is useless, and if you have an OS useless for containers, what do you have?!

I want to go to cloud, I want to go with Windows platform, please don't stop me...

more details and context

https://github.com/moby/moby/issues/40284

If you use Hyper V Live Migration from Server 2012 R2 (not sure if any other OS) to migrate to Server 2019. The migration works but as soon as you shut down the VM and try to start it again, will no longer boot. It turns on/off 3 times and remains off.

I also did cluster to cluster migration in VMM and this is the same behaviour.

It looks like it is due the migrated MAC address, if I set the VM to get a new dynamic mac address it seems to work. If I set it to it's original mac address as a static it will no longer boot.