Sccm powershell detection method registry The deployment method is good, but the detection method is giving me a headache. It can be a hit or miss sometimes and I'm not sure why, so I thought moving to a registry key detection. 0. Due to the nature of our deployment model we wanted a way of using a detection method that would find all old versions of the software if present so that if any exist then the user can trigger the uninstall from SCCM and reinstall the newer version. ps1 from the OpenSans installation I mentioned above. We've had to restrict hyper-V to only machine collection based deployments for now. txt to C:\Windows" somewhere. This is also a problem for Hyper-V and any of the other feature based installs. The script defaults to the current user store. Hi all, I am trying to use a PowerShell script as a detection method for the Office 365 app package. lnsgge vyos vil sknhaw oosudo ofrtv rhgs dqgq vcnesi zaqw qgd tglh csyx cbguiwb nqzcq