General Feedback

Do you have an idea or suggestion based on your experience with Windows Server? We would love to hear it! Please take a few minutes to submit your idea in the one of the forums available on the right or vote up an idea submitted by another Windows Server customer. All of the feedback you share in these forums is monitored and reviewed by the Microsoft engineering teams responsible for building Windows Server. Suggestions can apply to both released and Technical Preview versions of Windows Server.

2. Requests for feature changes around the end-user experience, such as desktop shell, start menu, individual consumer apps, etc. must be provided through the Windows 10 Feedback Hub tool. We have no ownership of these types of non-Windows Server components.

3. This forum (General Feedback) is used for any broad feedback related to Windows Server. Feedback for specific areas like Storage, Networking, Virtualization, Nano Server, etc., should be provided in one of the forums available on the right. It is not for bug filings. If you find a bug with Windows Server please open a support case at https://support.microsoft.com and report it – these cases are free.

If a Powershell script creates a DFSR RG and invokes the CmdLet "Set-DfsrMembership" multiple times to add several member servers then there is a high probability that the CmdLet will fail.
I have a PowerShell script than creates a new DFSR RG, adds the local server and a folder, then calls the above CmdLet.
if the script is run in a loop (deleting the RG between iterations) then the script will fail after 2 - 5 loops.

I've used .NET Reflector to debug the DfsrPowershell, DfsObjectModel and DfsrHelper DLL's and I found that the error is as follows:
Set-DfsrManagement attempts to modify the Replication Group object under the target computer in Active Directory. It first attempts to perform the operation using the currently logged on user's credential and when that fails it retries using using the target computer account. This normally succeeds however, when it does fail the LDAP response is invalidAttributeSyntax
Examining the modifyRequest command I see one of the attributes is:
modification item operation: delete (1)
modification msDFSR-DfsLinkTarget
type: msDFSR-DfsLinkTarget
vals: 1 item
AttributeValue:
And the AttributeValue is empty - which is invalid!
Now the modifyRequest that was sent using the logged on user's credentials is correct:
modification msDFSR-DfsLinkTarget
type: msDFSR-DfsLinkTarget
vals: 0 items
The difference is the first modifyCommand is built and sent by the DfsObjectModel DLL while the failing command is sent by the DfsHelper DLL which is native code and described in the MS-DSFRH document.
I have debugged the code as far as the interface into DfsrHelper and confirmed that the attributes passed into the DLL are correct i.e. the msDFSR-DfsLinkTarget attribute operation is "delete" and there are no values set. Therefore I am of the opinion that there is a defect in the DfsrHelper DLL implementation that incorrectly appends an empty value when constructing the LDAP command.
I opened a MSDN case with the breakfix group who confirmed it was a bug but were unable (due to internal policy??) to submit their findings to the DFSR dev team.

If a Powershell script creates a DFSR RG and invokes the CmdLet "Set-DfsrMembership" multiple times to add several member servers then there is a high probability that the CmdLet will fail.
I have a PowerShell script than creates a new DFSR RG, adds the local server and a folder, then calls the above CmdLet.
if the script is run in a loop (deleting the RG between iterations) then the script will fail after 2 - 5 loops.

I've used .NET Reflector to debug the DfsrPowershell, DfsObjectModel and DfsrHelper DLL's and I found that the error is as follows:
Set-DfsrManagement attempts…

The Server Essentials Connector client often loses its connection to the server following a Windows Update. This is both frustrating if seen, or an issue if missed (if the icon is not always shown) as it can lead to backups not happening for a number of days. Normally it is then just a case of running the ClientDeploy app, but you have to know where to find this (it is not added to the all programs list).

Ideally the connector should be much more robust to Windows Updates and should simply "just work" but, if it does not connect it should:
1) put up a notification that it has not connected
2) provide a "troubleshooting" option/wizard to attempt to reconnect automagically (including maybe indication of the need to get the server admin to check that the service is running on the server), or at the very least provide option to run ClientDeploy to reconnect the client

The Server Essentials Connector client often loses its connection to the server following a Windows Update. This is both frustrating if seen, or an issue if missed (if the icon is not always shown) as it can lead to backups not happening for a number of days. Normally it is then just a case of running the ClientDeploy app, but you have to know where to find this (it is not added to the all programs list).

Ideally the connector should be much more robust to Windows Updates and should simply "just work" but, if it does not connect it…

Hello, after applying the below listed patches this past Sunday on Windows Server 2016 dedicated to File / Print services, searching for files on Windows Server 2016 results in the search that appears to be searching but unable to display properly.

If possible I'll send a picture comparing Windows Explorer search results from both Win10 & Win7 (both systems are up to date with latest patches, though the same view from Win 10 happens on Win 2016), a description of what I'm seeing can be described as follows:

Win 10 / 2016; you see the file name only, the rest of the search area is blank (normally it shows content and meta-data) and unlike before, right click doesn't bring up any menu options (such as opening the folder the file is saved in);
Win 7; you see blank lines, as if the fonts were white on white background, so it appears to bringing up similar results as the Win 10, but you only see the light grey line separating each search result;
Running the same search from both client machines on a Windows 2008 older file server (is also up to date on patches) shows the expected results (File name, content below file name, Meta data on the right), which is what I was seeing last week on the Win 2016 server / before applying the patches.
Look forward to feedback and confirmation if there's something else that needs to be enabled on the 2016 file print server.

Hello, after applying the below listed patches this past Sunday on Windows Server 2016 dedicated to File / Print services, searching for files on Windows Server 2016 results in the search that appears to be searching but unable to display properly.

If possible I'll send a picture comparing Windows Explorer search results from both Win10 & Win7 (both systems are up to date with latest patches, though the same view from Win 10 happens on Win 2016), a description of what I'm seeing can be described as follows:

Hi! There is currently no official support for Windows Server 2016 to run ADMT. It remains an important tool and I'm sure many will appreciate not needing to install older versions of Windows to migrate between AD's.

After upgrading a machine to Windows 10 1803 (build 17115) the Essentials Connector no longer connects to the server, does not run any of the apps and deinstallation/reinstallation including fresh install clearing down registry and ProgramData does not fix it. This will block upgrading my estate to Windows 10 1803 if not fixed urgently. Have also reported back through Feedback App on Windows 10.

Pinned locations on Quick Access shows folder name but cannot change display name to differentiate between many folders with the same name in different locations.
Please let us change the display name of a folder in the QuickAccess list as we previously could with the old Favourites list? Or let us put Favourites back on top of the windows explorer navigator?

Unable to change WINS Server, IP Binding in Windows Server 2016. In the MMC of WINS Server, you can see an IP Address which suggests that the WINS Service is only listing on this Network Adapter. Even you change the Network Adapter metric, the IP will be not changed in the WINS MMC Gui. It's only changing, if you disable the used interface. With a netstate you can see that the WINS Service is listening on all Interfaces. This is confusing

It would be great if we could license just the virtual machines, not the entire host. There are lot of mixed environments where customers need to run several Windows Server VMs, but not all of them and not on Hyper-V. The minimum price can be licensing 16 cores, regardless of actual number of cores is less. Running just a few Windows Servers VMs in cluster environment and properly licensing them is way to expensive. This wan't push customers to cloud if that is the intention of present virtual machine licensing.

If any .NET version after 4.5.2 is installed, some dashboard functionality fails (can't remove computer, can't ignore alert) and the dashboard crashes randomly. Removing and blocking .NET 4.6.1, 4.7, and 4.7.1 works around the issue, but that means the server is limited to the 4-year-old .NET 4.5.2. This article has more details:

Single User Admin Passwords
Often I have to run to someone's computer just to enter the admin password. I wish there was some type of generated admin code that I could give someone else to type into the computer for a single time use.

Even better would be a popup sent to another computer where the person knows the admin credentials and they could type them in remotely.
Remote Popup Message "Bob has requested to install (Sage Accounting Software Update) Do you wish to give this person permission to perform this action?"

On fresh install of Server 2016 Standard (several times), once I join the server to the domain, the domain admin account cannot "personalize" the desktop theme to include desktop icons. I get the error above, saying that you (domain admin) may not have the appropriate permissions to access the item. It works fine with local admin before and after the server is joined to the domain, but not for domain admin.

Microsoft should have a tools for Windows server to help ITs select there's needs for example Windows Server 2016 has tons of roles and services none of remember all roles. If there a tools help people for example I ask the tool i need something for policy tool answer GPO or maybe choices you can select things you need and the tools gives you what server and service role you need.