One basic debugging trick in such a case is to put your command line in a string (between double quotes or within the qq// quoting construct if needed) and to try to print it. This way, you can see how Perl interpolates it and what exactly is being passed to the underlying shell (or powershell in your case): 
my $string = qq/c:\\windows\\system32\\windowspowershell\\v1.0\\powers
+hell.exe -command "Set-ADUser $un -Replace @{thumbnailPhoto=([Byte[]]
+(Get-Content $jpeg -Encoding Byte))}"/;
print $string;

[download]
Once your happy with the quoted string, put it back between backticks.

In reply to Re: Error compiling script running powershell command by Laurent_R
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.