OpsMgr R2 allows you to embed powershell scripts in a MP - See this MP for an example - http://derekhar.blogspot.com/2009/11/new-agent-maintenance-mode.html
----------
If you want to run powershell, perl or any other scripts not run by cscript.exe from a management pack then you invariably had to create the script and distribute it across all the servers where it needed to run. This could easily become quite complex maintaining all these scripts in multiple different locations. If you are in a situation where you have multiple management groups and none of them are quite the same then you could have multiple different versions of the script and the rule that would call the script.
To avoid this problem it is now possible to embed other scripts in a management pack, not just vbscript and jscript.
To explain how this is done we need to break in to the XML. Open the image below to view the full command. This would be executed using on a recurring basis using a System.Scheduler datasource.
The Write Action aboves enables proxying for all management servers. This check is quite easy to do using the command shell alias.
<ApplicationName>%systemroot%\System32\windowspowershell\v1.0\powershell.exe</ApplicationName>
This line launches the Powershell exe. Remember that Powershell must be installed on any server you are targeting the rule at. The same goes for any other script language that you wish to use.
<WorkingDirectory>%MOMROOT%</WorkingDirectory>
The %MOMROOT% variable point to the Installation path of OpsMgr. This is useful when targeting Powershell scripts at the RMS or Management servers as it allows you to easily load the Command Shell Snap-in. This then gives access to all the Command Shell aliases.
<CommandLine>-Command "& '$File/EnableProxy.ps1$'"</CommandLine>
The arguments being passed specifies to run the script $File/EnableProxy.ps1$. After this the file must be entered.
<Files>
<File>
<Name>EnableProxy.ps1</Name>
<Contents>
The name of the script must match the command line name. While I have not tested this there appears to be the ability to embed multiple files here.
Now we drop into the script itself. This rule is targeted to run only on the RMS so $rootMS is set as localhost. The next 3 lines load the Command Shell snapin, and opens the connection to the local management group.
$rootMS="localhost"
add-pssnapin "Microsoft.EnterpriseManagement.OperationsManager.Client";
set-location "OperationsManagerMonitoring::";
new-managementGroupConnection -ConnectionString:$rootMS;
Here is an example Management Pack
