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.

Feature Request - DNS zone root apex alias capability in Windows Server DNS

This would allow a customer to direct requests to the root of an DNS hosted zone (e.g. mydomain.com) to cdn/hosted services. This is required because a CNAME alias is not a supported record type for the apex root (@) record in a DNS zone.

Azure supports this, so not sure why windows server team didn't implement this as well:
https://docs.microsoft.com/en-us/azure/dns/dns-alias

AWS Route 53 DNS service gets around this using the concept of an alias which allows the root apex record of a DNS zone to point to cdn/cloud hosted services.

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html

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?

The problem is that server backup will only show a status of set up/configured after running a successful backup despite "webadmin get versions" properly showing the list of backups.

After installing KB4552940 as part of the Extended Security Update for Windows Server 2008 R2 the wbengine.exe in the system32 folder is updated. What happens due to this is that the Microsoft-Windows-Backup service is unable to log Event 4 "The backup operation has finished successfully" & Event 14 "The backup operation has completed" to the Eventlog. After creating an Event Trace Session what you will see for these events is "The description for Event ID 4 from source Microsoft-Windows-Backup cannot be found." below that also saying "the message resource is present but the message is not found in the string/message table".

The BlbEvents.dll & BlbEvents.dll.mui files the EventMessageFile uses are not updated as part of this update so it seems the newer version of wbengine.exe is unable to find the strings it's looking for within those files. Replacing the wbengine.exe dated 4/16/2020 that came with this update, with an older version of the wbengine.exe file dated 3/2/2011 restored this functionality and allowed the server to report backup events as expected.

Side note, start events and failure events are still logged so it seems it's only some event descriptions it's unable to find. This is reproducible by freshly installing Server 2008 R2, and running all windows updates on a machine eligible for Extended Security Updates.

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

We're having issues with IIS 10.0.17763.1, if you want to use a domain service account as the identity on a web site then that web site as stated here that needs to be granted "Impersonate a client after authentication" in the user rights assignment in the local security policy ...

https://techcommunity.microsoft.com/t5/iis-support-blog/500-internal-server-error-when-accessing-the-root-folder/ba-p/1480940

...failing to do so results in 500 errors on static content...

The main issue with this is what does setting a custom account for the identity of the Application Pool have to do with Impersonation? At best it's misleading. We not using impersonation, we're simply changing the Application Pool Identity. This seems more like a bug than by design.

When trying to cook up an Image for our cloud deployments on Windows Server Core 20H2 with the Server Core App Compat FOD
we are starting with a Nov 2020 Patched windows Core SAC image, and then we are trying to add the App Compat FOD.

But after installing the App Compat FOD, the Get-updates want us to also reinstall the Nov 2020 15 GB patch

It seems that the installation of the App Compat FOD , installs old libraries , and then even if that OS is patched, now a new OS patch has to be installed.

this is a problem . because we are building new immutable images using Marketplace AMIs on AWS, and the building of the new AMI should now require that we use an OS patch , as we expect the OS patch to be in the base AMI.