Computer Agent -> Powershell execution policy, set to Bypass. From: [email protected] [mailto:[email protected]] On Behalf Of Bradley, Matt Sent: Tuesday, March 17, 2015 10:11 AM To: [email protected] Subject: RE: [External] [mssms] RE: KB detection clause
I typoed when doing the email, but I've got it correct in SCCM. Thanks for checking on your side. Did you have to adjust your default client settings for PowerShell to make this run? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bull, John Sent: Tuesday, March 17, 2015 11:57 AM To: '[email protected]' Subject: [External] [mssms] RE: KB detection clause This works for me: Get-HotFix | Where-Object {$_.HotfixID -eq 'KB2834140'} I believe your missing the period after the underscore. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bradley, Matt Sent: Tuesday, March 17, 2015 9:38 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] KB detection clause In trying to devise a detection clause for an .exe KB deployment, I came across this page (http://myitforum.com/myitforumwp/2013/06/18/deploying-microsoft-hotfixes-via-the-configmgr-2012-app-model-28/ ) detailing a one line PowerShell command: Get-HotFix | Where-Object {$_HotfixID -eq 'KB1234567'} I'm certainly no PowerShell expert, but that sounds simple enough to me, just change the KB number. Unfortunately the statistics on my deployment all show failures, and no successes. Our default client settings require PowerShell scripts to be signed. But does that apply to the detection clause too? Is that possibly why I'm getting failures? Should I be doing this detection clause with a different method?
