As far as I can tell, perl really ought to treat the "command" as a string and not attempt to compile it.

Did you expect it to leave $un and $jpeg untranslated as well? Or did you expect perl to parse it and replace it with the contents of those variables?

I suspect something similar it going on here. for some reason it is checking Byte (or maybe its the @{...}) as a replaceable part and then finds [] which it doesnt like.

i would do something like this.

my $command='Set-ADUser '.$un.' -Replace @{thumbnailPhoto=([Byte[]](Ge +t-Content '.$jpeg.' -Encoding Byte))}'; my $result = `c:\\windows\\system32\\windowspowershell\\v1.0\\powershe +ll.exe -command "$command"`;


In reply to Re: Error compiling script running powershell command by huck
in thread Error compiling script running powershell command by sweetblood

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.