Our company uses McAfee Solidifier to lock down our Terminal PC's. I've been looking to find the minimum required folder(s) to re-solidify in order to allow newly attached peripherals to work and I'm wanting to narrow the focus of what we do currently to save time.
Right now I run sadmin so C:\Windows\System32\ from a Batch file and this works to allow what we need, however, as mentioned, I want to be more granular in the sadmin so command.
The question at hand: What is the most granular root directory I can use from Command Prompt / Batch files to solidify the necessary paths for Win 10 to allow my PNP Devices to behave, not including the
DriversorDriverStorefolders below? That is - Where doesWindows 10store the files containing peripheral hardware data/addresses?
Further reading as desired:
The issues we experience only happen when we are in the Windows 10 environment, and never in our Windows 7 environments. From what I can only guess, there's a set of files which must be whitelisted in Win 10 by McAfee in order for McAfee to allow the peripherals to operate. For full context, I do know of C:\Windows\System32\Drivers and C:\Windows\System32\DriverStore, but I do not believe this is what I'm actually looking for.
Examples:
Windows 7 - adding a receipt Journal Printer which uses a COM Port (PNP Device), drivers are installed, and solidified (sadmin so C:\Windows\System32) without the Printer attached to the PC. PC boots up, I can connect the printer of choice without any problems, it works right away, no errors seen in Device Manager
Windows 10 - same process as above, however, when I connect the Printer, it will not work without running sadmin bu on the Command Prompt to allow McAfee Solidifier to be in Update mode. When I leave the Printer connected to the system and run sadmin so C:\Windows\System32 it will allow the printer to work without having to be in Update mode on reboot, so I'm certain the files I'm looking for exist in C:\Windows\System32 but are beyond the Driver or DriverStore directories.
