PowerShell V2 and Software restriction policies

Original problem described here:
news:ekQWEJZaJHA.4480@xxxxxx

Microsoft confirm this bug as "by design". Currently I'm not aware about
changes in Software Restriction Policies. Therefore there might be a
situation when SRP silently blocks undefined extensions. As workaround you
must at least one additional rule in SRP:
%HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders\Personal%WindowsPowerShell/Microsoft.PowerShell_profile.ps1.ps1

if you use /\/\o\/\/'s PowerTab then you must add this rule:
%HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell
Folders\Personal%WindowsPowerShell/PowerTab/*.ps1

Please note, if you use registry key values in SRP console and you append a
suffix (for example registry key contain My documents absolute path and you
specify MyDocs subfolders than you must use foreward slash ( / ) instead
backslash ( \ )

also you will have to add additional Path or other rules for all places
where you hold PowerShell scripts.

--
WBR, Vadims Podans
PowerShell blog - www.sysadmins.lv