Hi Microsoft

WSUS is unusable as it is now unless you know how to write your own PowerShell scripts. 90% of the updates it auto-approves, are completely useless.

It's not even easy to manually decline all the (actually) unneeded updates. If we could sort updates by the criteria we actually use to determine if we need them, we could use this "click&drag"-functionality you implemented (no idea why this was a priority). Right now it just gets in the way of choosing the updates we need to decline.

How about you give us the option to automatically decline ARM64 and x86 updates? How about auto-declining consumer or business editions?

Let us at least sort or group the updates by the architecture.
Or provide us with official scrips that actually work.

Why are en-us and en-gb not separate? Why would the standard be to have both active? Most companies aren't active in the US and the UK... It just bloats the list of available updates. Again, we can't sort/group by language either.

It is seriously baffling to me that WSUS is in the state that it is currently.

Even if there are already easy ways to solve these issues:
1) You could improve the usability of WSUS 100x if you implemented things like this.
2) These already existing solutions (excluding making your own Scripts) seem to be incredibly hard to find.

I'm not hopeful that I'll get a response, but I really would appreciate an explanation for this whole situation.

Thanks.

Hello,
I found a couple of issues with RDP work:
1) Applications sound transfer. Some Win10Pro PCs (only few of many similar ones) have issue with transfere of applications sound. I can hear system sound check, but I can't hear any applications: players, browsers, etc. All settings allowed and correct, other PCs transfere all sounds.
2) If I set all devices to transfer with RDP, transfered screen starts to freeze after some time of work. It happens every time. Screen stops updating, but RDP still works and I can click Remote Desktop, but i won't see what happens until I reconnect to PC with RDP.

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

When I try tu use the "DIR" command line to extract files information, I got some problem when the "Owener name is too long". I didn't see his name but only "..."

Sample command:

ECHO Search entire C drive for MP3 files...
C:
CD \
DIR /S /TA /Q *.mp3

A "correct" output should be:

2020-11-19 11:25 3,000,024 MyDomain\MyUser MySong.mp3

A "bad" output, where username seem to be longer than the allowed column width, give me:

2020-11-19 11:25 3,000,024 ... MySong.mp3

But I also observed for the "file name" is not seem to be an issue when t use a very long name. This one is not truncated.

2020-11-19 11:25 3,000,024 ... MySongWithExtremelyVeryLongNameForSample.mp3

Then, it's impossible to extract a useful report where I need to know who is the owner of all files.

I tried to modify command prompt window setting to expand window/buffer width from 80 through 120 or larger and the DIR output still set with same width on this column.

A exported result through a text file is also limited

DIR /S /TA /Q *.mp3 > C:\result.log

Establish a two-way forest trust.

Try to establish Remote Desktop Connection from a computer in one forest to a computer in another forest, with an account that is a member of “Protected Users” security group. The connection will fail if the computer (from where you’re trying to establish RDP connection) does not have “RC4HMACMD5” kerberos encryption type enabled (i.e. it only has “AES256HMACSHA1” enabled).

On the other hand, if the user that is trying to establish Remote Desktop Connection is using an account that is NOT a member of “Protected Users” security group, and only AES kerberos encryption types are enabled on the computer from where the connection is initiated (i.e. “RC4HMACMD5” is not enabled), the connection would be established because after kerberos authentication would fail, the account would be authenticated using NTLM, which is even worse.

Please fix this!

We must be able to authenticate and connect to another forest (of course, it the trust exist) with Kerberos using AES. Using RC4 is not acceptable, and NTLM is even worse.

Hello,

on a fresh installed and fully patched Windows Server 2019 Std if I enable RDSH role the Windows Search stops working.

Windows Search service looks good and eventlog shows no errors but Indexing Options shows no locations enabled for indexing and I am unable to add them

Things I have already tried

1 - Windows Search service restart

2 - Server restart

3 - Rebuild Index

4 - Enable Windows Search feature

5 - DISM ad SFC

6 - Windows Troubleshoot - shows incorrect permission on C:\ProgramData\Microsoft\Search\Data folder but is unable to fix them. If I manually fix those permissions, search still not works adn permission are automatically reset to previous not working ones

Thank you in advance for help

UPDATE:

Uninstalling RDSH role fix the issue. Unfortunatelly I need both RDSH and Windows Search

BUG confirmed by other users here:

https://social.technet.microsoft.com/Forums/en-US/4c200f89-5905-42b3-ab27-0d7771c0ecb7/rdsh-role-breaks-windows-search?forum=ws2019&prof=required