Disable User Account Control in Windows

Is it a good idea to Disable User Account Control UAC to run tool software smoothly on Windows server?

Before answering this question, let's assume that User Account Control UAC is not disabled. I keep the default settings for all systems that support it in the traditional way. Why? When this feature was first introduced to the customer's system Windows vista, Windows 7) and the server system Windows 2008), I am sure that, like the previous product activation, UAC will not be discarded in a short term. So I think the best way is to get used to it, understand its characteristics, and change your work habits when necessary.

As mentioned earlier, let me explain what caused the entire discussion about whether to disable UAC. A short time ago, a Windows server 2008 R2 server remotely managed by me lacked disk space. I have cleared all common suspect objects: Many archive files that have not been removed from the system and backup sets that are no longer needed.

I decided to check if other users encountered some problems when cleaning up disk space. After some searches, I found an administrator in a blog saying that he had some seemingly hidden disk space over Small Business Server 2008.

The author uses the JAM software company's TreeSize tool to scan the system and determine where the disk space is used. After some fruitless checks, he realized that due to UAC, he had to use the Administrator account to run the program to let the program view everything on the drive. I guess it won't automatically ask for improvement at startup .) This helped him find a lot of things that were not shown before, but caused some doubts:

In earlier versions of Windows Server, should the old administrator disable UAC as a way to get the same expected behavior from a utility?

For multiple reasons, I don't think this is a good idea. First, it is because UAC has a solid user base. For this reason, collaboration with others is the most correct way, rather than just moving forward. For old programs that are not aware of UAC and you are not very trusted, the best solution is to create a shortcut for it and set it to be started as an administrator by default, and rename it "Utility-Admin mode" -- or other similar names. This is not to say that all efforts are common transactions that you need to work with to create a one-stop store, such as folders with shortcuts.

Another reason not to Disable User Account Control is that all interactions with the server will increase the availability of the attack surface, even if it runs a program that looks completely good and justified. It doesn't make sense to disable your boycott in advance.

Finally, it takes more time to disable UAC. You will receive a lot of warnings about trying to modify the system. The warning window gives you the option to stop and consider what will happen. It has indeed avoided my losses for many times, making me not a dumb. I don't mean to run malware, but not to change the system scope .)