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

In the WSUS console, I should be able to search a KB, then get back a list of not only the overall compliance, but get lists of servers that do and don't have the patches installed, without having to dig deep into PowerShell or .NET libraries. I also think the same should be possible for the inverse, where you query a computer and should get back a list of patches WSUS knows is installed/not installed. You can currently sort of do this all via hokey scripts and Excel Vlookup magic, but it would be so much nicer if it was native instead.

Both the ConfigStoreRootPath and SharedStoragePath locations under a hyper-v cluster cannot currently be amended after they are initially set so if you move the cluster storage to another storage array with different volume names you either have to:
1.) recreate the whole cluster to change locations of these values.
2.) rename the volumes to the old paths and then change all corresponding virtual machine paths or
3.) Create a small volume with the same name and path as already set for both ConfigStoreRootPath & SharedStoragePath.

It seems completely bizarre that such a well documented limitation has not be addressed by Microsoft and needs to be fixed.

https://support.microsoft.com/en-gb/help/4488568/cannot-change-configstorerootpath-of-hyper-v-cluster-after-population

https://blog.workinghardinit.work/2018/09/27/live-migration-fails-due-to-non-existent-sharedstoragepath-or-configstorerootpath/

Sigsync is secure email signature software for Office 365 that simplifies the creation and management of email signatures for all Office 365 users. It helps to be compliant and create email signatures seamlessly. No matter from which device you’re sending emails from. Sigsync supports email signature across all the devices (Windows, Mac, Linux, Mobile etc.) and email clients.
Complete control over email signature
Sigsync supports centralized management to have a complete control over email signatures for the entire organization. It retrieves the information such as Name, Company, Address details etc., from the Azure Active Directory and insert into your email signature.

Key features:
Centralized signature management to create and manage your email signatures for teams and company at one place.

A platform Independent email signature service and works on all the devices including Windows, Mac, Mobile, Linux etc.
Automatically configures Exchange online connectors and uses secure TLS channels to for the registration and integration. Also supports Multi-Factor Authentication (MFA) as an additional security.
Various professional signature template layouts for your business needs.
Supports Company branding by allowing including company logo, contact details social media icons, promotional banners etc.
Supports to track the number of email clicks using web analytics and OneClick survey to get customer feedback instantly through signature.
Allows enabling email signature in sent emails

Clicking on the start menu on a server should do far less than on Windows 10. I am always finding delays with the start menu showing when clicking on it on a server and a long wait for the search to start when I start typing. I know part of this is related to disk resources -- I need to make some improvements there on the Host machine as the VMS are sharing disk resources. However, I feel like the functionality behind the start menu on server 2016 could be reduced down to what it used be like on 2008 R2 -- no internet searches or anything like that when I am looking for appwiz.cpl and whatever else would help performance on first launch

Its not an idea its a fact. Its makes the OS more prone to attacks. Why would there be exemptions for wireless setups. I don't have a wireless device. I don't want to access my computer remotely. I makes it more simple for someone to though. I don't use AllJoyn Router. Windows 10 is garbage. That's my opinion and I'm sticking to it. Dont see much that got any better than Windows 7. As a matter of fact yall made it more complicated and even more annoying? Why? It was already annoying as . Most just throw their computer in the garbage. Because Updates mess their up? Yawl should really be investigated by someone because It has to be done intentionally. Someone should put a foot in Microsoft ***! That's how I feel! Thank you and have a good day!

We have two-way forest trust established and would like to manage group policy for both forests from one server.

On a member server where Group Policy Management console is installed, these encryption types are enabled in “Network security: Configure encryption types allowed for Kerberos“:
AES256HMACSHA1
Future encryption types

When I try to add another forest to Group Policy Management console (open “Group Policy Management” console, right click on “Group Policy Management”, click on “Add forest…”, enter domain name and then click “OK”), a message “Access is denied.” pops up.

If I enable “RC4HMACMD5” on the server where Group Policy Management console is installed, I can add a forest in Group Policy Management console without any errors.

Please fix this. I don't like having legacy cypher (RC4) enabled just to be able to manage group policy from two different forests.