First of all, sorry my poor English. Recently my customer bought two Windows Server 2016 Standard and I have a general group policy to disable autoplay and autorun in all computers in this network. Of course, I have an Active Directory implemented with two DCs, one with W2K8R2 and another with W2K12R2. I´ve downloaded the new ADMX files for Windows Server 2016 and Windows 10 "www.microsoft.com/en-us/download/details.aspx?id=53430" and created a Central Store and I made all steps recomended by Microsoft. This Group Policy works well in all versions of Windows 2012/8.1 and below, but doesn´t work in Windows version 2016/10. I reaserched in the Internet for a similiar problem and I didn´t find anything about this. Does anybody have a clue for this problem??? Thanks for any help.

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 de_windows_server_2016_technical_preview_5_x64_dvd_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>

I manage a PC that runs Broadcast Software International's Simian application in production 24/7 for a radio station. It is royally impossible to manage the PC via mstsc which reports "An Internal Error Occurred." There is a VPN involved provided by WatchGuard's appliance. The VPN is NOT the problem. Remote Desktop works for the brother PC that also runs Windows 7 with University of Kansas's Telephone Reader application in production 24/7. My hypothesis is that the broadcast-quality sound card is being accessed, with catastrophic results, by the server part of RDP in Windows 7 even in the case where I configure the setup to not send sound across the Internet. There is also an odd log entry in the System log entries. I have been asking Microsoft to fix this defect for one full year. Microsoft is busy rolling out Windows 10 releases in accord with the DevOps philosophy (sometimes referred to as a methodology). Just a message from one one thousandth of one percent of Windows users worldwide. In closing, I use UltraVNC which provides the remote desktop functionality that Microsoft, the World's Premiere maker of consumer operating systems, does not.

Windows Server 2016: Powershell Imports Appear Broken

Version:
Major Minor Build Revision
----- ----- ----- --------
5 1 14393 2339
Error:
Error: The term 'function' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was includ
ed, verify that the path is correct and try again.

Summary:
Last night, an update was implemented on our system via active directory. Today, I am unable to run file imports that work on other versions (5.1.16299.431 is working fine on my local machine, Windows 10). I'm not 100% sure that this is a bug, but I can't reproduce on other versions and there doesn't appear to be any link I could find to get an upgrade on the OS I'm using. The latest update was KB4284833 run overnight.

Does this look like an end user issue?
Is there a way to upgrade Windows Server 2016 PS to 5.1.16299.431 (working)?

Test Code:
ZipFiles.ps1

Param ($type)

$ScriptDirectory = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent
$date = get-date -UFormat %Y%m%d
$Logfile = "$ScriptDirectory\FileManagement-$date.log"
try {
. ("C:\Program Files (x86)\oneZero\Scripts\SendMail.ps1")
. ("C:\Program Files (x86)\oneZero\Scripts\LogWrite.ps1")
}
catch {
Write-Host "Error while loading supporting PowerShell Scripts"
Write-Host "Error: $($_.Exception.Message)"
exit 1
}
SendMail.ps1

function sendHTMLMail {

Param (
[string]$Body = '',
[string]$Subject = ''
)

$SMTPServer = "smtp.sendgrid.net"
$SMTPClient = New-Object Net.Mail.SmtpClient($SmtpServer, 587)
$SMTPClient.EnableSsl = $false
$SMTPClient.Credentials = New-Object System.Net.NetworkCredential("user", "password");
$EmailFrom = "email"
$EmailTo = "email"
$message = New-Object System.Net.Mail.MailMessage $EmailFrom, $EmailTo
$message.Subject = $Subject
$message.IsBodyHtml = $true
$message.Body = $Body
$SMTPClient.Send($message)
}
LogWrite.ps1

function LogWrite
{
Param (
[string]$logstring,
[string]$logfile)

$date = Get-Date
$log = "$date - $logstring"

if (!(Test-Path $Logfile))
{
New-Item -path $Logfile -type file
Add-content $Logfile -value $log
}
else
{
Add-content $Logfile -value $log
}
}

I've successfully installed Windows Server 2019. I've installed the following Roles: ADDS, DHCP, WDS. Active directory works fine, dhcp work proper. WDS when i try to open the WDS manager will freeze. I've installed in multiple system so it's not a problem with my VMWare Workstation 14. Also i've tried both versions. Standard and Data Center.

Second glitch it's the network settings. When you right click on ethernet icon and try to go to advance option. On the left panel click Ethernet and first option it's to change Adapter option. You will get an error which said that you don't have enough rights to do that. I've created a new user with Domain Admin, Enterprise Admin, Administrators groups yet no success. So the single way to change the ip address on the adapter you have to go to advance option and get back into the ethernet icon.

IIS services will not detect your website if you haven't created before the A record or CN in DNS. So you have to create it it first in DNS the name of the record.

Sometimes the dashboard will not close just hang in there. I assigned to my Server 16 Cores and 12 GB of RAM so i don't think it's a problem with my spec.

After installation of AD DS and automatically restart will occur when the Windows it's loading back it's take at least 10 minute to set up the new settings of AD DS.

Hope this will help in solving this Issues

I am a microsoft trainer for about 8 years so i think its important for you to hear my suggestions about windows server 2016 (the latest update).
Win server 2016 has so many bugs and you are losing your customers.
Everyone tells me that master please dont tell me about winserver 2016 any more its not reliable and has so many issues.
So if you as microsoft server team want to know about all of the problems please send me an email so i will tell you all about the problems that im sure you dont know aboute all of them.
Thaks
Mahyar safaei