Dear McAfee, I have two virtual machines in a domain (ePO 5.10 and AC Solidcore 8.2.1 on WS 2016, client node with W10 LTSB 2016). Both the machines are solidified, AC is enabled, inventory fetched. I defined a Trusted User (in order to dynamically change the whitelist) and use it to run our main application to install a lot of (about 40) MSI packages (included 3rd-party). This app launches all the packages with such TU and all of them are successfully installed BUT the .NET 4.8. The error is related to the "DismCorePS.dll" which is "not on the corporate whitelist and not allowed to run". The .NET package as said runs with such TU, the same errors occurs if the package is manually installed ("run as that trusted user)". Note that such TU has admin privileges. Why does it happen? I've tried other documented ways to solve it (from the product guide), uselessly.
Regards, Andrea Ferro
PS the DLL appears to be copied many times in "C:\Users\<TU>\AppData\Local\Temp\<HEX number>"
To answer this question we will require the Solidcore.log for checking on the reason why the dll is not whitelisted when extracted via trusted user.
Hi thanks a lot for the quick reply, really appreciated. There are many errors inside the log actually, but not much helpful for me. If I search the "dismcoreps" keyword, it seems to be confirmed that the error is a deny error: the reason is because the file is not in the local whitelist... but of course it is not. But I also found a reference to a process that cannot be "marked" as updater... but I'm not able to come to a solution.
Please note that the "agent failed to send events" (red row in monitor) but it seems not related to this problem as it is refers only to the .NET DLL (not all the other packages successfully installed and then executed). I attached the compressed log and hope you can help me to solve it (or suggest which rule I need).