At this time we don't allow interactive installers. With that being said Wireshark does NOT have a command line that allows for the installation of Npcap silently as it requires a license/validation. Generally we suggest deploying Npcap separately.
Correct when I said clicking, I meant the option itself not the application I apologize! Additionally, you can't reset some of the settings like Command Line prompt or others, however those default to blank so simply clearing them out will give you the default.
For a full reset you can move the Settings.xml file located in the install directory of the Patch My PC publisher to another location and after reopening the application you will have a fresh slate. This would reset everything however.
Simply clicking them again will uncheck them. For the most part most of the options are either enabled or not. A few do give you the option of adding additional things like files/folders or parameters.
I would suggest adding an exclusion to that particular EXE to start. You may need to explore allowing exclusions on other folders related to content distribution within ConfigMgr but I would start solely with the ScriptRunner.exe. Depending on the security tool it can detect as a false positive just do to the nature of the exe running in the system context.
This was caused when Adobe changed the actual display name for the application, it caused detections to fail or only show as half compliant. With this in mind we adjusted the rules and added a (Rev 1) tag so that no one would have to republish the update manually and be in a broken state.
We don't have a direct way to do it in the publisher today, however if you do set them in Intune you can navigate to our Publisher and on the Intune Apps or Intune Updates Tab select Options, There will be an option to carry over Application Dependencies moving forward.
Would you be able to grab the following logs from an affected client device and email them to [email protected]?
%WinDir%\CCM\Logs\CAS*.log %WinDir%\CCM\Logs\DeltaDownload*.log %WinDir%\CCM\Logs\DataTransferService*.log %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist) This may be found in the %ProgramData%\PatchMyPC\ if the Install was initiated by the user from Software Center. %WinDir%\CCM\Logs\ScanAgent*.log %WinDir%\CCM\Logs\StateMessage.log %WinDir%\CCM\Logs\UpdatesDeployment*.log %WinDir%\CCM\Logs\UpdatesHandler*.log %WinDir%\CCM\Logs\UpdatesStore*.log %WinDir%\CCM\Logs\WUAHandler*.log %WinDir%\WindowsUpdate.log You need to run Get-WindowsUpdateLog on Windows 8.1 and newer in PowerShell. %ProgramData%\PatchMyPC\PatchMyPC-UserNotification.log %ProgramData%\PatchMyPC\UISettings\UINotificationSettings.xml
It will work both ways. You essentially skip the first initial install documentation pieces for Intune and move onto the next steps. So yes you can use the Intune Only documentation for SCCM+Intune.
Ultimately it's going to depend on how you have Co-Management enabled on how things function. The application slider for co-management works differently than all the other sliders. You can move that slider over to Intune and still get applications from ConfigMgr with the added benefit of being able to push them from intune as well.