Invoking Powershell modules on remote clients via package/command line

Question

Hello Everyone -
I have two modules(functions) that i've written and tested successfully locally in my environment that give me Uninstall and Repair functionality on whatever the string contains. Both .psm1's are delivered via a SCCM pkg that lands both into folders
in the Modules directory. My issue is I can't seem to invoke this in a deployment scenario...as i'd like to deliver the "Invoke-command" using SCCM's command line to simply say...
Invoke-Command -scriptblock { Do-This "<string>" }
The above command works fine locally when...(exePol is set to Bypass).
1.)Modules have respective folders living in WindowsPowershell\Modules directory named xxxx.psm1
2.)Import-Module -name <path\name of module>
3.)Verify Modules are loaded(moduleType is script)
But when fabricating the folders\files above with SCCM, and running the Invoke-Command(in many different ways remotely), i recieve the cmdlet, program doesn't exist and has no idea what i'm talking about. Folders\Files for .psm1's are present and do
show when running Get-Module -Listavailable locally on targeted clients.
Maybe this is related to the Import-Module command and the context i'm trying to delivery it in?
I've tried multiple scenario's of...
A.) Psexec that launches powershell, followed by the Import-Module -name <path\name of module>
B.) .Bat file that launches powershell with the same Import-Module syntax
C.) PS1 that includes the same Import-Module line.
D.) Just straight from the command line of the Pkg/Program.
Has anyone tried this? Is there a better method when trying to deliver invoke-command on a module/function to a client via SCCM? 
TIA 

Answer 1

[I see that the you are running the powershell.exe and then importing the module in the command line for the Program you created in SCCM, so just importing the module will do the repair action for you ??]
Not sure how else i would run a Import-Module without calling upon powershell.exe. The reason for using Import-Module first is it only creates the abilty of whatever the module(function in this case) on the client. So if i can get the remote
Import-Module to work, which would then allow me in the future to use an Invoke-Command -scriptblock { Do-This "string" } on the clients. In this case its both an Uninstall and Repair function with an assortment of switches and arguements that will aide me
in the future in managing our apps. For me to use the Modules, i would need to Invoke-Command as that is how the functions are built.
Okey so the module does get dumped to the end machine.
Suppose you have a test machine TEST01 where the Test.psm1 file  (having Test-Function)is delivered through SCCM.
Then try this and tell if it works:
PS C:\> $session = New-PSSession -ComputerName TEST01
PS C:\> Invoke-Command -Session $session -ScriptBlock {Import-Module Test.psm1 }
PS C:\> Invoke-Command -Session $session -ScriptBlock {Test-Function #inside your Module}#Or Simply try below:
PS C:\> Invoke-Command -ComputerName TEST01 -ScriptBlock {Import-Modules Test.psm1;Test-Function #inside your Module}
I think what you are doing is below.....for the example am taking "webadministration" module:
PS C:\> Invoke-Command -ComputerName Server01 -ScriptBlock {Import-Module web*}
PS C:\> Invoke-Command -ComputerName Server01 -ScriptBlock {get-website}
The term 'get-website' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
+ CategoryInfo : ObjectNotFound: (get-website:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
+ PSComputerName : sdwuweb017
Point here is you need to import the module and work with it in an already opened session....If you specify a computername every time then PowerShell opens the Session does what you want it to do and tears down the session. To persist the importing of the
module it must be done in a session which we make using New-PSSession and then run the commands against that session.
I might have misunderstood the problem but this is what I have got so far.
Hope this helps
Knowledge is Power{Shell}.