In Windows 7, Office 2010 I used to be able to search EVERYTHING that was indexed on my computer, files, emails, .psts, etc. INSTANTLY.

I have since been upgraded to Windows 10 and Office 2016 and the searches are a nightmare and very slow. I can only search emails while in Outlook 2016(no longer from Windows Search) and it is significantly slower than the searches on my old computer. Would like to have the ability to search EVERYTHING in my computer returned from Windows Search(Type Here to Search) since I regularly have to find old emails for customers.

I am getting this error 0x800f0954. I am follow this video:https://www.youtube.com/watch?v=-_ivxV6MRSw. Is this right to go? suggest some method

When implementing multiple RelayingPartyTrustsGroup of substantial sizes, we are running into some point points with the Powershell interface.

Add-AdfsRelyingPartyTrustsGroup
- Need a flag to manually specify the name

Remove-AdfsRelyingPartyTrustsGroup
- Need an option to specify the name

Set-AdfsRelyingPartyTrustsGroup
- Command doesn't existing but looking for something similar to the existing Set-AdfsRelyingPartyTrust command modify parameters found in get-AdfsRelyingPartyTrustsGroup

Get-AdfsRelyingPartyTrustsGroup
- is painfully slow currently due to the full enumeration of the RelayingPartyTrusts identifier, should limit results a handful of RPT's to increase performance.
- add an option to limit the number of RPT's enumerated with the query 1/10/20/100/unlimited/ect

In previous versions of Windows Server the command "net statistics server" returned useful server-related information (e.g. # sessions, # files accessed etc.). In Windows Server 2019 (at least with desktop experience) this command fails and indicates that "net statistics workstation" must be used. This command is normally used on workstations and returns a different set of information.

There's a pretty big problem on some servers (at least two Dell PET Servers I've tried so far) that stops Server 2019 from booting/goes into a boot loop once the Hyper-V role is installed.

When connecting to a VDI session (individual win 10 machines) with regular RDP GPU, the session goes black when trying to resize to fullscreen. This is not happening with a session host.

Ok in server 2012, I can switch to a logged user in task manager without password if it's the same user.
But in server 2019, this feature disappeared, I have to type a very long password everytime when I want to change to another session under the same user, which is very annoying.

A lot of small organizations start off using something like Windows 10 Pro for their server, but as the organization grows they'd like to upgrade in place to Windows Server. Right now, you can't do that. So I have seen a lot of organizations stay using the non-server OS basically until the server hardware fails and the recovery needs a clean install anyway. An in place upgrade path would definitely increase sales.

Add Support for Remote Desktop using a Biometric for Key Trust environments

Upgrading Windows Server OS should not remove static routes. This bug has made upgrades to my environment very painful

Vcx

We have been hitting issues lately with the process in which out engineers RDP to remote servers.

We're doing away with embedding RDP windows within legacy winforms apps and instead are just connection to the session via ps.

The only downside of doing so is losing the ability to set a "Friendly Name" title to the session window.

This is an issue as some engineers may be working with 10+ sessions at once

I would like for the ability to set this using a "/title" parameter.

The following conversation is explanatory.I have another
issue regarding MacOS Catalina.I have a Apple Macbook Air, and I am facing huge mailing
issues after upgrading it.I was using previously Microsoft Outlook
as the Mail Client and I have observed that is responding slowly to macos Catalina.
I have discussed with the technical help desk about this issue and followed
their guidelines discussed about thehttps://supportprop58.com/office-setup/how-to-login-microsoft-office/ .Please help us out to resolve this issue.

When Creator Owner is removed from NTFS permissions, change permissions is still given when a person with Modify rights creates a new folder/file. If the Modify permission is the only permission granted, a person who creates a new folder/file should not be granted the Change Permissions when Creator Owner has been removed from the NTFS permissions.

Hi Microsoft Team,

How are you? I hope everything going well.

Long time ago the microsoft decide to stop to Support/Deploy nano server on Bare metal.
However, this position can be very usefully to work with Container, instead to create a physical cluster with Windows Server Core(Swarm of Kubernetes), we can create a cluster to run container and with it, save space, less update, less security issue e with more performance . This is not a simple solution I Know that. But it can be a game change.

Allow the filtering for a scheduled task depending on what operators are used. Similar to CSE advanced options

Post a list of what the error codes mean in the error log for transferring files with storage migration service. I have no idea what code 2, 32 or 40973 mean! Would be nice to know so I can know why files failed to copy.

Error message that i spend 3 month search for a solution no one knows what's the problem

Getting this error in server 2019 and 2016 after closing GPMC.msc

Error ID 1000

The massage is:

Faulting application name: mmc.exe, version: 10.0.17763.1, time stamp: 0x176b88f0
Faulting module name: GPOAdmin.dll, version: 10.0.17763.1, time stamp: 0x84e18916
Exception code: 0xc0000005
Fault offset: 0x00000000000bb4cb
Faulting process id: 0x980
Faulting application start time: 0x01d50e351f75ca91
Faulting application path: C:\Windows\system32\mmc.exe
Faulting module path: C:\Windows\System32\GPOAdmin.dll
Report Id: 918fa381-d469-4623-9544-9a949e90666d
Faulting package full name:
Faulting package-relative application ID: