Hi

We have 8 RDS server, all running Windows server 2016, but after installation of Windows server 2016 update KB4593226, Microsoft print to PDF is not working anymore

When I try to print an document to PDF printer, the printer dialog box says following "Before you can print, you need to sect a printer"

I have try to uninstall the "Microsoft print to PDF" and install it again, but when I try to install it again I get following dialogbox from "Network
printer installation wizard"
Printer driver was not installed

The system cannot find the file specified
It look like Windows doesn't now where to find printer driver after installation of December 2020 update KB45933226

When I uninstall KB45933226, everything is working again, please help ?

/Jan

Network Location Awareness is very useful feature on desktops. Particularly in the current climate of people taking machines home, having them detect "Public" networks is useful.

However, it is nearly unheard of for a Windows Server to be picked up and taken to an untrusted network. Instead of the benefits of this feature, there are many reasons wherein a server may decide it's in a public network and firewall itself from access. This will, for example, prevent a file server sharing files, or an Exchange server accepting email. If this occurs to Domain Controllers, it will trigger all other servers to consider themselves on a public network and generate effectively an "all servers down" scenario.

A Google search for "network location awareness" leads to no discussion about the feature, and pages and pages of workarounds for a problem that is clearly quite common.

There is a commonly described workaround involving restarting, or delaying the start of the Network Location Awareness service. But thinking about this logically, it's a "workaround" to a problem that should not occur.

This is particularly relevant to a Server Core installation that would never be taken home for use as a desktop, and can be quite difficult to troubleshoot without a UI.

If a Powershell command or registry edit would allow us to just set a server to "always use domain profile", we could improve resilience and remove these sort of issues from occurring, whilst avoiding workarounds of dubious quality.

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?