I believe so.
When the CI runs, I am getting this error which leads me to the Execution
policy thing.
[cid:[email protected]]
So unless I am misunderstanding the error, this is why I am questioning the
Execution policy not being set correct. Now I would love to be wrong with this
as we are just getting started with the DCM stuff.
Here is the script I am running also.
$FeatureName = "TFTP"
If (Get-WindowsOptionalFeature -Online | Where {$_.State -eq "Enabled" -and
$_.FeatureName -eq $FeatureName}) {
$Compliance = "NonCompliant"
}
Else {
$Compliance = "Compliant"
}
Return $Compliance
I got this from the web and it works fine on about 25% of our machines. The
rest just fail with the error above. So I am at a loss.
Mike L.
From: [email protected] [mailto:[email protected]] On
Behalf Of Andreas Hammarskjöld
Sent: Monday, April 11, 2016 3:05 PM
To: [email protected]
Subject: RE: [mssms] Powershell Execution Policy
There are two policies, one for x86 PS and one for x64 PS, got them both
covered?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Linkey, Mike
Sent: den 11 april 2016 21:58
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Powershell Execution Policy
Nope, no GPOs have anything set for powershell.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Jason Wallace
Sent: Monday, April 11, 2016 2:38 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] Powershell Execution Policy
Could you have GPOs affecting the systems?
On 11 Apr 2016, at 19:50, Linkey, Mike
<[email protected]<mailto:[email protected]>> wrote:
We are setting in the computer Agent -> PowerShell Execution Policy to Bypass.
<image001.png>
But our PS scripts in our CI’s are failing on Windows 7 machines. Using
PolicySpy, I can see that it is still set to 0
<image002.png>
Is anyone else seeing this or am I just missing something here? This seems
simple enough, but just does not seem to be changing the clients. Any input
would be appreciated!
Mike L.
CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents
accompanying such) may contain confidential information. Such information is
intended only for the use of the individual or entity named above. If you are
not the named or intended recipient, you are hereby notified that any
disclosure, copying, distribution, or the taking of any action in reliance on
the contents of such information is strictly prohibited. If you have received
this email in error, please notify the sender and then delete the email. Thank
you for your cooperation.
CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents
accompanying such) may contain confidential information. Such information is
intended only for the use of the individual or entity named above. If you are
not the named or intended recipient, you are hereby notified that any
disclosure, copying, distribution, or the taking of any action in reliance on
the contents of such information is strictly prohibited. If you have received
this email in error, please notify the sender and then delete the email. Thank
you for your cooperation.
CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents
accompanying such) may contain confidential information. Such information is
intended only for the use of the individual or entity named above. If you are
not the named or intended recipient, you are hereby notified that any
disclosure, copying, distribution, or the taking of any action in reliance on
the contents of such information is strictly prohibited. If you have received
this email in error, please notify the sender and then delete the email. Thank
you for your cooperation.
