Because there's no "product feedback" at <https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities>, I'll post here. I'm the author of a popular Active Server Pages framework, ASP Xtreme Evolution (AXE), and we have a hack to leverage node.js npm packages to work inside our environment <https://github.com/nagaozen/evolved-npm2asp-bundler>.

I evaluated the Windows Server 2019 DE and the ServerCore (with FoD) on a virtual machine and they both support this trick. But we are trying to move into a container strategy and installing FoD on the <mcr.microsoft.com/windows/servercore:ltsc2019> seems impossible for the reasons already explained in this issue <https://github.com/MicrosoftDocs/windows-insider/issues/56>.

I'm sending an attachment with coverage tests to help evaluating the server.

[tests.zip](https://github.com/MicrosoftDocs/windows-insider/files/2966573/tests.zip)

Posted to Bug as all other robocopy posts have been placed here.

It is fairly common for organisations to have a temporary area accessible by all staff to allow a common area to access files. For these type of temporary areas, some sort of scheduled cleaning regime needs to be in place so that files older than a certain number of days are automatically removed.

A common cleaning approach is to move files past a nominated age to a staging folder and then empty the staging folder. Unfortunately robocopy's MINAGE switch operates on Modified Date that makes it non-functional for moving files based on nominated age.

By way of example, a file/s edited many months ago needs to be made available to other staff, so a copy of the file is placed in the temporary area (most staff will use Windows Explorer for this). The Modify Date on the copy does not change from the original and the Creation Date on the copy is obviously set to when the copy was created. A cleaning regime using robocopy will use the Modified Date and remove the file/s the next time it is run.

In summary robocopy needs 2 more switches MINxxx & MAXxxx that operate on Creation Date.

• After installing and promoting to domain controller the network type in the Network & Sharing Center still shows Public when it should be Domain. This blocks many domain only functions from being possible. For example, remote desktop with or without the gateway is not possible unless you go into the firewall settings to allow public access to port 3389 and/or port 443. Setting the Network Location Awareness service to Automatic (Delayed Start) does not provide enough time for other services to start so the correct network type is used. What I had to do was set up a task in Task Scheduler with “net stop nlasvc /y” to execute at system startup with a 5 minute delay. When the NLA service is stopped it will restart automatically, showing the correct network type of “Domain” upon its restart.


• Wireless WAP/WAP2 Enterprise not working. Unable to communicate with RADIUS. Turns out, the built in firewall rules for ports 1812 and 1813 just flat out are not working. To fix, manually create an incoming rule for UDP ports 1812-1813.


• NPS refuses all connections for RD Gateway for remote desktop, wireless and VPN. This is because NPS accounting is unable to write to the log files at C:\Windows\System32\Logs. Even though the default permissions are correct, writing to the logs fails with “permission denied”. To work around this configure accounting to log to a text file on the local computer and remove the checkmark from “if logging fails discard connection attempts”.

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.

Get-AD Cmdlets broken when using "-Filter " and & or "-Properties *"
on Windows 10 1809 with Remote Server Administration Tools 1809:

Name : ConsoleHost
Version : 6.1.1
InstanceId : 376bfa55-d7c2-41ad-89dc-bc63b357ccb8
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-US
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspace

Get-ADobject -Server $Forest.DomainNamingMaster -Credential $Creds.$ForestKey -LDAPFilter "(objectClass=site)" -SearchBase 'CN=Configuration,DC=contoso,DC=com' -Properties *
Get-ADobject : Object reference not set to an instance of an object.
At line:1 char:1
+ Get-ADobject -Server $Forest.DomainNamingMaster -Credential $Creds.$F ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-ADObject], NullReferenceException
+ FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.NullReferenceException,Microsoft.ActiveDirectory.Management.Commands.GetADObject

Same Windows 10 1809 system results with PoewrShell v.5.1.1.x

Get-ADobject -Server $Forest.DomainNamingMaster -Credential $Creds.$ForestKey -LDAPFilter "(
objectClass=site)" -SearchBase 'CN=Configuration,DC=contoso,DC=com' -Properties * | FT DisplayName,WhenCreated -AutoSize

DisplayName WhenCreated

        5/13/2002 12:27:06 PM

        3/6/2002 10:40:48 AM

        11/19/2004 9:59:25 AM

        7/12/2002 3:51:37 PM

...

*NOTE: Format-Table pipeline intentionally excluded under PowerShell Core 6.1.1.x example for clarity. DisplyName & Whencreated attributes used in PowerShell 5.1.1.x to protect live system data.

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!

Recently, I found "Windows Update Cleanup 1.00 MB" in Disk Cleanup (cleanmgr) Tool of Windows Server 2016 with Desktop Experience. I know of another bug that is incorrectly displayed as 3.55 TB, but I found this new 1.00MB bug on two machines (Hyper-V VM and Azure VM). I selected this item on my Hyper-V VM and delete start, it will take a day or more to finally complete, and about 30GB of space will be come back. That's good news, but 1.00 MB display is bug, and the time taken to delete is unusual. I do not have the courage to do this on Azure VM.