I had a similar problem yesterday and found this link helpful:
http://serverfault.com/questions/566722/power-shell-error-cannot-bind-parameter
The answer mentions:
It looks like you are using PowerShell Vs.2, that version had no support for
the new where syntax.
In version 1 and 2 of PowerShell use:
gci | where {$_.subject -like "UTN"}
You need to put curly brackets around the expression and refer to any
properties with the $_. prefix.
Andrew Hurst
Systems Engineer
Mourant Ozannes
BVI | CAYMAN ISLANDS | GUERNSEY | HONG KONG | JERSEY | LONDON
D +44 1534 676 772 | T +44 1534 676 000 | F +44 1534 676 333
mourantozannes.com<http://www.mourantozannes.com/>
LinkedIn<http://www.linkedin.com/company/mourant-ozannes/> |
Twitter<http://www.twitter.com/MourantOzannes/>
From: [email protected] [mailto:[email protected]] On
Behalf Of Daniel Ratliff
Sent: 12 April 2016 14:34
To: [email protected]
Subject: RE: [mssms] Powershell Execution Policy
Are those machines on PoSHv3, v4, or v5? Pretty sure that cmdlet doesn’t exist
on PoshV2.
Daniel Ratliff
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Linkey, Mike
Sent: Tuesday, April 12, 2016 9:13 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Powershell Execution Policy
Looks like it is only on Windows 7 that it is failing. Seems to work on
Windows 8 and Windows 10.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Troy Martin
Sent: Tuesday, April 12, 2016 7:51 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Powershell Execution Policy
What’s the OS versions between the two e.g. success/failed?
Troy L. Martin | Technical Architect
1E | Software Lifecycle Automation for the Digital Business
US Mobile: +1 (678) 898-6147 | UK Phone : +44 208 326 9141
[email protected]<mailto:[email protected]> |
www.1e.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.1e.com_&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=lfm9K0cSqM44FHIoBa6p0wzT4MWYkn_0HYGNmWgkATs&e=>
Facebook<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_1eglobal&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=RRWJDZaMGcmivktB58TkvRLoQr1bC6jIDj-MN1oDLlE&e=>
|
Twitter<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_1e-5Fglobal_&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=6SY99zYqJ1R5pAavjFi-JmFdxUD0lt-n0XwOK-omJcI&e=>
|
YouTube<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_1enews&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=XWjlpxF0vI8J3n42uqWMrEXgHphlWI2PD9XZHOHhX8U&e=>
|
Blogs<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.1e.com_&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=tKrxeysyE64idSmjz1G3NP2ojp9RhRdpv1OljUgTbyg&e=>
|
RSS<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.1e.com_index.php_feed_&d=BQMFAg&c=Ln8c1CLEgbhz4W2FGOnrXYpHvIYN4k_cXHVmsANM4XI&r=zAhc69MwvUId2afOheLZsnttbIFqxDANe5KRT-ZKir4&m=uHdy6p01-w9GZjdBVTraJ5PHeWP6yKoA_xCBrm33uC4&s=qGt8-ZGt5rG-J3ClWoppG9TfmFKmktUZprrf0vtNjII&e=>
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Linkey, Mike
Sent: Tuesday, April 12, 2016 8:40 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Powershell Execution Policy
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]>
[mailto:[email protected]] On Behalf Of Andreas Hammarskjöld
Sent: Monday, April 11, 2016 3:05 PM
To: [email protected]<mailto:[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.
________________________________
Legal Notice: This email is intended only for the person(s) to whom it is
addressed. If you are not an intended recipient and have received this message
in error, please notify the sender immediately by replying to this email or
calling +44(0) 2083269015 (UK) or +1 866 592 4214 (USA). This email and any
attachments may be privileged and/or confidential. The unauthorized use,
disclosure, copying or printing of any information it contains is strictly
prohibited. The opinions expressed in this email are those of the author and do
not necessarily represent the views of 1E Ltd. Nothing in this email will
operate to bind 1E to any order or other contract.
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.
The information transmitted is intended only for the person or entity to which
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information
in error,
please contact the sender and delete or destroy the material/information.
