I keep hating this "security feature" that is part of UAC but does not secure anything, but it does limit me managing a server.
Whenever I need to access a folder for which I have been granted permissions via the administrator group I cannot do what is needed until I add my current login account to the users the have personally access to that folder. I can also create another local group called RealAdmins, I put the same users in that are part of the local Administrators group and give the group RealAdmins Full access on the file system. I see that as a workaround as there simply is no security boundary that forces me to do this. I can simply go to \\server\C$\Directory and I DO have access to that special directory to which the Administrators group has access from ANY other system that can reach the server over the network, which is a lot LESS secure as to who can log on the server itself.
I was told that if I set the UAC to the lowest level, Never Notify, the problem would not exist, but it still does. By completely disabling the UAC via the registry I CAN access the speciefied folder where Admins have access. Please remove the ridiculous limit that slows me down performing maintenance on a server where I am part of de local Admins. It is a useless limit.

Tree is a nice tool. When generating a tree that contains development code, there will be folders like bin/debug, obj/debug and npm (node_modules) packages. Those folders can create unnecessary noise to the tree output.

It would be nice if it was possible to instruct to tree to ignore certain folders.

I haven't fully thought about it, but thought of the .ignore files like .gitignore, .tfignore, etc. These .ignore files are pretty standard.

Maybe a .treeignore would be nice too.

I was thinking along the lines of:

tree /i : (init) create a %USERPROFILE%.treeignore file "standard" and popular .ignore files of say: \bin* and \obj* and **\node_modules*

tree /ti: (treeignore) uses .treeignore files in a path, starting with the SYSTEM, User, folder hierarchy.

tree /di (dot ignore) uses .*ignore files found along the way.

tree /di {filename} uses {filename} as the .ignore.

ex: tree /di .ignore will use .ignore (any in the path).

Question: Cummulative or startover. When two ignore files are found in a path, should they be cummulative, replace the other, or give the user the ability to choose?

Zimbra is a widely used email client application operated by people from all over the world to handle emails and save data in one place. The user while using Zimbra email client application can handle Zimbra file items such as notes, folders, contacts, subfolders, calendars, tasks, and etc. If you are fed up of searching on the internet about the ways on how to migrate Zimbra to PST format, then don’t worry and stop your search. In this blog, we will guide you on how to migrate Zimbra to Outlook format by using Vartika Zimbra to PST Converter automated tool.
Know more click here- https://www.vartikasoftware.com/product/zimbra-to-pst-converter.html

Test-NetConnection is a great tool for troubleshooting network issues, and having it attempt to contact a publicly-accessible, Microsoft-hosted endpoint (internetbeacon.msedge.net) when no -ComputerName parameter is supplied is especially useful.

However, it would be even better if internetbeacon.msedge.net would be configured to respond on any TCP port, so we could run a command like this (to check if a specific port was being blocked on our corporate firewall, for example):

Test-NetConnection -Port 8443

It's possible to do this today by specifying a third-party service (like portquiz.net) in the -ComputerName, but enabling internetbeacon.msedge.net with this capability would both save us typing and lighten the load on these other services.

Under This PC there are a number of items listed that can't just be "Unpinned" in Windows. Specifically:
- Desktop
- Documents
- Downloads
- Music
- Pictures
- Videos

Specifically when working on a server most if not all of these are irrelevant to a server running an application. It should be the (current) user's choice to unpin these and list only what they want pinned under "This PC". There may be registry hacks or other ways to get rid of these unnecessary and cluttering entries, but the UI should give a direct/clean way to remove these and improve usability and productivity of administrators/users who must RDP into the server and work on it.

Every new version makes things harder and harder to access things that used to be simple:

• Changing network settings (Old: Right click the network icon, New: Who even knows? Click the icon, go to network center, click the adapter advanced options if it even shows up...)


• Make Network Profiles Accessible (Old: Right click Network icon, click 'Private' or 'Public', change it, New: Who knows? Go into the Registry? Join a HomeGroup to run a troubleshooter that then tells you that you have change to a Private network type?)


• Search (Old: Press Windows Key, start typing, New: Who knows? You literally can't search for the applications on your own system)

The list goes on and on, but look, instead of putting lipstick on a pig, make the pig stronger, faster, better, more secure, and more solid. Stop adding steps to get to things that used to be easy to get to: We are ADMINISTRATORS on servers, we KNOW THE RISK. I guarantee your support tickets will decrease tenfold.

Get it done.

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

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.

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

I'm using French RSAT for Windows and I found a translation problem when watching parameters of my power options GPP. When configuring the power option GPP, there is no problem. When watching the parameters of the GPO, instead of showing me values with a %, it is written "For XX minutes" You can see the problem in the attachment. The problem is there on my Windows 2012 R2 servers and is still there on my Windows 2019 servers. I don't remember if I had the problem on 2008 R2. Is there a way please to resolve that little translation problem? Thank you!

People like Windows cause its a generally easy operating system to use for a non-techy person. The whole Linux based system of using the command prompt to specify which user or groups can access your so called "server" is utter bullshit because for one thing it adds to the things the user would have to learn to use the operating system. Linux is a complicated operating system. Most of the tutorials on Youtube are HOURS long. Lastly and more importantly, WHY WOULD YOU WANT TO HAVE ANYONE OR ANY OTHER GROUP TO ACCESS YOUR MACHINE? Absolute privacy on a machine should be standard. Windows has been an easy to use operating system. I have used Linux and I hate it. They say its security is the best but it doesnt make any sense if you have to go in your system and manually modify the "permissions" to restrict other users to read, write, or execute files in your server. Please think about removing OpenSSH and implementing a better security approach.