ConfigMgr 2012 SP1 module on runbooks servers

Question

Let me come out the gate stating I am very new to Orchestrator and somewhat new to powershell.
I want to start testing the ConfigMgr SP1 cmdlets via runbooks.  I found a blog that shows some gotchas on how to run the .Net script action which is great, however all the examples I see show importing the module from an installed management console
directory.
I am assuming that when I run a runbook that needs to reference Configmgr cmdlets that the module must imported from a local path on the runbook server(s) itself.  I am really hoping that this doesnt mean I have to install the SCCM 2012 SP1
admin console on my Orchestrator Runbook Servers?
Am I just missing something obvious here?  I tried copying the entire bin directory that contains the psd1 and all the associated dll's, etc. to another machine and importing the module, but unfortunately it fails with:
Import-Module : The 'C:\tmp\SCCMPowershell\ConfigurationManager.psd1' module cannot be imported because its manifest co
ntains one or more members that are not valid. The valid manifest members are ('ModuleToProcess', 'NestedModules', 'GUI
D', 'Author', 'CompanyName', 'Copyright', 'ModuleVersion', 'Description', 'PowerShellVersion', 'PowerShellHostName', 'P
owerShellHostVersion', 'CLRVersion', 'DotNetFrameworkVersion', 'ProcessorArchitecture', 'RequiredModules', 'TypesToProc
ess', 'FormatsToProcess', 'ScriptsToProcess', 'PrivateData', 'RequiredAssemblies', 'ModuleList', 'FileList', 'Functions
ToExport', 'VariablesToExport', 'AliasesToExport', 'CmdletsToExport'). Remove the members that are not valid ('HelpInfo
URI'), then try to import the module again.
At line:1 char:14
+ Import-Module <<<<  .\ConfigurationManager.psd1
    + CategoryInfo          : InvalidData: (C:\tmp\SCCMPowe...ionManager.psd1:String) [Import-Module], InvalidOperatio
   nException
    + FullyQualifiedErrorId : Modules_InvalidManifestMember,Microsoft.PowerShell.Commands.ImportModuleCommand
Can someone point me in the right direction?
Thanks!!

Answer 1

So I partly answered my own question.  The above error message was due to having Powershell 2.0 on the test machine and not 3.0 which is required.  I updated the powershell version and was able to import without error (and without installing the
full admin console).
So I guess my question then comes down to what is the best practices for things like this?  Certainly do not want to install admin consoles for every SC product on my runbook servers.  It appears that with SCCM I can simply create a directory (standard
on all runbook servers of course) and copy the files there and import from that location.  is that the preffered method for handling this?
Thanks!!