Hello,

I want to report one issue that is easy to reproduce, it occurs with any rdp client that connects to Windows10 Pro with enabled RDP connections, actually used mstsc.exe to connect from one Windows10 pro machine to another Windows10 pro machine with enabled RDP.

After ~100 tries to restore interrupted connection the server refuses future rdp connection tries with internal error occurred message reported by mstsc.exe.

It doesn't matter if you have logged off the session during running, as example did 20 connection restorings then logged off, logged in and did next 80 connection restorings, that was only example, only what matters is that you have only to restore any interrupted session at least ~100 times to send server to nirvana. As example after WiFi lost connection or during any network problem that requires rdp connection restoring. Only what helps to restore functionality is to restart remote desktop service in services.msc

I highly assume by restoring connection with reconnection cookie the bug counter counts up and by reaching 100 (the counter seems to be not reset by any action) so finally it completely stops to accept any future connections with internal error occurred message.

Such error doesn't exist on Windows2016 but Windows10 pro is affected.

More over few months ago this bug didn't exist on Windows10 too.

Please forward this issue to your RDP server developers, thank you!

Sincerely yours.

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.

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!

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