No sir. I can do that if you think it's a good idea... since it sounds like I'm kind of special.
- Welcome to Support Forum: Get Support for Patch My PC Products and Services.
Patch My PC Support
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#1
Report Update Detection Issues (Enterprises Using ConfigMgr and Intune) / Re: Base Install PS Detection Method Code Signing Error
August 29, 2019, 02:50:41 PM #2
Report Update Detection Issues (Enterprises Using ConfigMgr and Intune) / Re: Base Install PS Detection Method Code Signing Error
August 29, 2019, 11:03:15 AM
Correct. It's in the source content for the deployment with these other files.
Package.xml
PatchMyPC-Sccm.dll
PatchMyPC-ScriptRunner.exe
SketchUpPro2019_19.2.222_x64.msi
Package.xml
PatchMyPC-Sccm.dll
PatchMyPC-ScriptRunner.exe
SketchUpPro2019_19.2.222_x64.msi
#3
Report Update Detection Issues (Enterprises Using ConfigMgr and Intune) / Re: Base Install PS Detection Method Code Signing Error
August 28, 2019, 05:08:04 PM
1.5.0.0
#4
Report Update Detection Issues (Enterprises Using ConfigMgr and Intune) / Re: Base Install PS Detection Method Code Signing Error
August 28, 2019, 04:05:41 PM
Just during normal Application deployments. Tested deployment against a device collection. No user logged into the computer at the time. Windows 10 64 bit domain joined and it gets updates beautifully from PatchMyPC all day long.
#5
Report Update Detection Issues (Enterprises Using ConfigMgr and Intune) / Base Install PS Detection Method Code Signing Error
August 28, 2019, 03:47:15 PM
We're trying to do Base Installs now for Applications. On the Base Install options, we checked the box for "Code-sign the PowerShell detection method script using the WSUS Signing Certificate" and it looks like that signature is getting put in the PS for the detection method for Applications generated by Patch My PC. When we try to deploy the Application, we're getting an error "0x87D00327 Script is not signed" so it fails.
I know I can flip my Client Settings over to set the execution policy to Bypass so it doesn't require the code signing, but is there some obvious mistake we're making that is causing this error?
I know I can flip my Client Settings over to set the execution policy to Bypass so it doesn't require the code signing, but is there some obvious mistake we're making that is causing this error?
Pages1