Intel vPro® Platform
Intel Manageability Forum for Intel® EMA, AMT, SCS & Manageability Commander
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
3049 Discussions

Please Re-Signing the PowerShell module with UTF8

idata
Employee
‎06-10-2011 01:56 AM
1,953 Views

Hi, I am a System Engineer live in Japan.

I have tried to use PoweShell modulws: /community/openportit/vproexpert/microsoft-vpro/blog/2011/03/30/powershell-module-for-intel-vpro-technology-version-30-amtsystem-powershell-drive-provider http://communities.intel.com/community/openportit/vproexpert/microsoft-vpro/blog/2011/03/30/powershell-module-for-intel-vpro-technology-version-30-amtsystem-powershell-drive-provider

But some of the powershell script code can not be executed, because of checksum error.

Some specific character sequece with ANSI coding is automatically replased other double byte character on Japanse Windows. ANSI coding is mapped ro Shift-JIS coding on Japanese WIndows.　See attached screen shot. In order to avoid this, please save all of the PowerShell source file with UTF8, and regenerate signature. Would you do this for us?

Preview file
103 KB
0 Kudos

Link Copied

1 Reply
Christophe_P_Intel1
Employee
‎06-14-2011 09:39 PM
1,142 Views

Thank you for letting me know about this!

Intel is going to release the next 3.1 version of the PowerShell module in two weeks. So I will re-encode all the scripts to UTF-8.

Again, thank you for letting me know.

Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.