Introduced in SCCM (Current Branch) 1706 is the ability to run PowerShell scripts against Device Collections or individual on-prem managed Windows PCs. So how can the data in this log be returned in an easy to read format while matching the package ID's to its friendly names? If you want to check what package that is, you'll have to find it in Update Retriever using the Package ID, which can be time consuming if there are a lot of updates. You will also see a few lines below that which are the dependencies that are checked to determine applicability. Highlighted in red is a package ID that was found in the repository, but was not detected as being installed. _ExternalDetection(True), mefwdetect.exe /fw 11.0.0.0 ![]() ![]() Key(NE), HKEY_LOCAL_MACHINE\SOFTWARE\INTEL\SGX_PSW Key(NE), HKEY_LOCAL_MACHINE\Software\Intel\Online Connect
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |